BoldNet Neo Installation and Base Configuration

BOLDNET installation is for use by customers who wish to connect to their Manitou environment from the web whether on or off the network. This is an additional license and is a paid service. For ManitouNEO is an included feature and can be found within Manitou Core Installation documents.

Preparation and Requirements

Before starting the install, these items will need to be checked and placed on the server.

  • Microsoft SQL Server Express 2014 or newer
  • Administrative user with full permissions on the server for installation
  • All available windows updates completed
  • Verify the name of the server will not change
  • Install Google Chrome and set as default browser.
  • Manitou Servers have Static IP addresses.
  • Verify hard drive space is sized according to BT99 submitted to customer
  • The following Roles and Features:
    • Application Server Role (This does not apply to Windows Server 2016)
    • Web Server IIS Support Role
    • Web Server IIS
    • Telnet Client
    • Windows Powershell
    • Web Server IIS ? Common HTTP Features ? HTTP Redirection
    • Web Server IIS ? Application ? ASP.NET
    • Web Server IIS ? Security ? Basic Authentication
    • Web Server IIS ? Performance ? Dynamic Content Compression
    • All features .NET 4.X
    • All features .NET 3.5
  • Windows Firewall configured to allow ports 80 and 443
  • Web Edit licensed on Manitou Servers

Running the BoldNet NEO Installer

  1. Navigate to the Manitou Distributer Directory, open the most recent patch folder and launch the Neo Installer:
    • For 1.6.4 it will be called BoldNet_Neo_Setup.exe
    • For 2.0.0 or newer it will be called ManitouNEO_setup.exe
  2. If prompted to import existing settings select OK, then select Modify installation.
  3. Select BoldNetNEO is selected for the Installation Type.
  4. When Prompted for Server Parameters, enter the FQDN of the Mantiou Primary server.
  5. Enter in the details for the SA Account which should be recorded in the CRM.
  6. Click Test DB Settings,  if the test is successful select OK to proceed.
  7. Specify the IIS Server FQDN name associated with the IIS Certificate
  8. Specify the Manitou Sentry Server by using the local FQDN.
    • Multiple Manitou servers will be separated by a comma.
  9. Accept the license agreement and select Next.
  10. Review the installation details, then select Install.
  11. When the installation completes successfully, select Finish.

IIS Configuration

  1. Launch IIS Manager.
  2. Expand the main Servernode then expand Sites.
  3. Highlight Default Web Site, then select Edit Bindings from the Actions pane.
  4. When the Site Bindings window loads, select the Add.. button.
  5. From the dropdown menu, change the Type to https
  6. Leave IP address and Port set to their defaults.
  7. For SSL certificate, click the Select button.
  8. Choose the appropriate SSL Certificate for this installation.
    • NOTE: If the customer does not have an SSL Certificate, a Self Signed can be created for use.
  9. Select OK to confirm these settings.

Creating a Self-signed SSL Certificate

  1. in the IIS, navigate to the SERVERNAME, then locate the Server Certificates tool, then open the feature.

  2. Open the feature, then select Create Self Signed Certificate from the Actions Pane
  3. Specify the name for the SSL Certificate. Using the *ServerName*SSL is appropriate.
  4. From the dropdown, select Web Hosting, then click OK.

Database Setup

  1. Navigate to the inetpub\DBs directory.
  2. Move the contents of this folder to the %MSSQL\Data folder (default installations are located at C:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\DATA)
  3. Navigate up one level the %\MSSQL\ folder, right click the DATA folder and select properties.
  4. Uncheck the Read-Only box, approve changes for all folders and sub-folders and files.
  5. Select Continue when prompted for UAC.
  6. Using the SSMS Tools, login with the SA Account.
  7. Attach the ASPNETDB and WebPrefsDB databases to the Databases Sub Folder.
  8. Close the SSMS tools.

Manitou Configuration

  1. Launch the SWS, logging in with an administrator account.
  2. Select Tools >Options 
  3. In the Navigation Pane, expand the System node then highlight Web Membership Database Details.
  4. Enter the Following Fields:
    • Web Server - Computer Name of server running BoldNET
    • Web Application Name - /
    • Web Database Server - Computer Name where database is located
    • Web Database Name - ASPNETDB (if using SQL Express \SQLExpress may need to be appended)
    • Web Database User - SA
    • Web Database Password - SA Account password found in CRM
  5. Select Save to apply the changes.
  6. Launch Google Chrome and attempt to login to the Boldnet Portal.

For Users Using ManitouNeo & BOLDNET Simultaneously

Rarely, customers will require the use of Manitou and Boldnet from the same webaddress. These steps outline the process to add a radip button to toggle between Manitou and BoldNet user accounts. For additional consideration with this setup communicate with your project manager.

  1. Navigate into the %inetpub\wwwroot\Manitou\ Directory.
  2. Open the api folder, then right click to edit the web.config file.
  3. Change the specified value for NeoInstallationType to "Manitou, BoldNet"
    EXAMPLE: <add key="NeoInstallationType" value="Manitou, BoldNet" />

  4. Save the file once the edit is complete.
  5. Navigate up one folder to return to the %inetpub\wwwroot\Manitou\ directory.
  6. Open the manitou folder, then right click to edit the web.config file.
  7. Change the specified value for NeoInstallationType to "Manitou, BoldNet"
    EXAMPLE: <add key="NeoInstallationType" value="BoldNet, Manitou" />

  8. Save the file once the edit is complete.
  9. Launch the IIS Console, highlight the webserver, and select Restart in the Actions pane.
  10. Attempt to log in to the portal with BoldNet and ManitouNEO logins now that the radio button is present.

Was this article helpful?
Thank you for your feedback!
User Icon

Thank you! Your comment has been submitted for approval.