Important - Please Note

This guide is for a new installation of Naverisk 2020 R3. Do not use this guide to install an earlier release, as the procedure is different. If you are upgrading a previous installation, please refer to the Upgrade Guide.

Introduction

The installation and configuration details in this Guide are for setting up and managing an Onsite installation of Naverisk. If you are using our Cloud services, you do not need to install a Site Controller and you are ready to go.

This Guide covers the information needed for a Naverisk administrator to install a Naverisk system and create installations on Windows Servers using SQL Server 2016 SP2 or later. Please note: 32bit operating systems are not supported.

For the purposes of this Guide it is assumed that you have just completed an installation of Windows and SQL Server.

Naverisk can be a resource intensive application and should not have any other services or applications running from the server it is on, including any other websites which can cause issues.

Running Naverisk on a server that does not meet the minimum requirements may cause degraded or unreliable performance. Naverisk reserves the right to request that a server be upgraded to meet the minimum requirements before assisting with performance or reliability issues.

The current version of the Naverisk installer can be downloaded from http://files.naverisk.com/Naverisk_Installer.zip

Note: Once Naverisk has been successfully installed, log in and click on the book Icon in the top right corner of your Naverisk Instance to access the Naverisk Quick Start Videos, User Guides and Knowledge Base Library.

This installation process is broken into three main parts.

       1.0 Set up & Configure the Server

       2.0 Site Controller Installation

       3.0 Install the Naverisk Web Site

1.0 System Requirements

1.1 Site Controller OS Requirements for new installations

Windows Server (64 bit)
     -     2016 or later. 2019 is recommended.
     -     Windows Small Business Server is not recommended or supported.

1.2 SQL Server Editions Supported for new installations

Microsoft SQL Server with Advanced Services – 2016 SP2 or later. 2019 is recommended.

SQL Server Express has limitations in both performance and database size, which can adversely affect the performance of Naverisk. While SQL Server Express will work for small installations of Naverisk it is not recommended. In the event of degraded performance or if database size limitations are reached you will need to upgrade to SQL Server Standard or higher.

If using SQL Server Express it is important to constantly monitor database size to ensure that it does not exceed the limitation of your version of SQL Server Express.

For further details please refer to System Requirements

1.3 Hardware Requirements

Monitored Client Specifications 

20MB free disk space (more if large Script Packs will be run on this Device) 256MB RAM

Server Specifications: These are a rough guideline for a Naverisk Onsite Server excluding the requirements for the Operating system of the server and running of SQL.

Dedicated Server

  • Less than 1000 agents: 2 CPUs, 8GB RAM, minimum 40GB free disk space
  • 1000 – 2000 agents: 2 CPUs, 8GB RAM, minimum 100GB free disk space 
  • More than 2000 agents: 4 CPUs, 16GB RAM, minimum 150GB free disk space

1.4 Additional Prerequisites

.Net 3.5, .Net 4.6.2 redistributable, Windows Installer 3.1, IIS 6 or later with ASP.NET 2.0.50727 allowed in IIS (for the Naverisk Website server).

.Net 4.6.2 can be downloaded from here:

https://www.microsoft.com/en-us/download/details.aspx?id=53344

2.0 Configure the Server

2.1 Pre-Checks

A summary of the installation steps completed so far:

  1. Install Windows Server;
  2. Set the Server to a fixed IP address;
  3. Perform Windows updates to ensure the server is fully up-to-date;
  4. Add .net framework 3.5.1;
  5. Download and install .Net 4.8 runtime from the below link: https://dotnet.microsoft.com/download/dotnet-framework/net48
  6. Install SQL Server;

Optional, but highly recommended:
 

  1. A valid SSL certificate for use with the website (required for https access);                    -     You will have to purchase the SSL certificate from a third-party provider.
  2. DNS 'A' Record to point to your fixed IP address;
  3. MX, SPF, record and rDNS for your local SMTP to ensure that your email provider does not mark emails coming from your instance as SPAM;

It is assumed the end user can achieve these steps or is able to get assistance from Microsoft or your Systems Engineer to carry out the installations to this point.

Note: Please ensure that the following features are selected with the installation of SQL Server
Note that SQL Server 2012 is shown in screenshots. Version 2016 SP2 or later is the supported version, however the settings remain the same.

If you choose to use SQL Express for your Naverisk installation. Please make sure that you understand the limitations of using SQL Express and that you have downloaded the SQL Express edition with advanced Features.

https://www.microsoft.com/en-nz/download/details.aspx?id=42299

Naverisk will not install if you do not use the Advanced Features package of SQL Express.

SQL Server must have SQL and Windows authentication mode enabled.

2.2 Configure Server Roles

  1. Open your Windows Server manager on your Naverisk Server -> Click on Add Roles and Features 
  2. Install the below additional features:

It may only have .Net Extensibility 4.5 and ASP.Net 4.6 showing but it should be fine, e.g.,:

Enable Windows Identity Foundation 3.5 feature

Open the IIS Manager, followed by the Webserver then the Application Pools.

Note: The Application Pool that runs the Naverisk website must be running .Net v4.0.

This can be done by clicking on the Basic Settings option on the right-hand-side panel of the IIS Manager. If you do not set the desired App Pool to V4.0 you will receive a website error when navigating to your Naverisk website later. Set the Managed Pipeline mode to Classic.

Make sure ISAPI and CGI Restrictions are allowed for v4. Follow below steps

  1. Open the IIS Manager and navigate to the server level.
  2. In the Features view, double-click ISAPI and CGI Restrictions to verify that the Web service extension is set to Allowed.

3. If the extension is not in the list, click Add in the Actions pane.
4. In the Add ISAPI and CGI Restrictions dialog box, type the path of the .dll or .exe file in the ISAPI or CGI Path box, or click Browse to navigate to the location of the file.
5. In the Description box, type a brief description of the restriction.
6. (Optional) Check "Allow extension path to execute" to allow the restriction to run automatically. If you do not check this option, the restriction status is Not Allowed, which is the default. You can allow the restriction later by selecting it and clicking Allow on the Actions pane.
7. Click OK.

2.3 Optional: Adding an SSL Certificate  

To import the SSL certificate that you have purchased by a third-party SSL provider, please follow the Microsoft Technet guide included in the link below:

Import an SSL Certificate Using Internet Information Services (IIS) Manager 

Alternatively, if you need to get a Certificate issued, follow the instructions provided in the below link to walk you through the Certificate Authority on how to generate and process the Certificate request and response:

IIS 8 and IIS 8.5 SSL Certificate Installation 

If you wish to assign a paid SSL certificate later and wish to use a server self-signed certificate, please follow the instructions provided in the below link: 

Create a Self-Signed Server Certificate in IIS 7 

Please bear in mind that this will display Insecure Connection messages when navigating to your website:

Your final Certificate needs to be available on the local computer.

2.4 Add the SQL Server Permissions

The Installer needs permission to create the Naverisk Database. Make sure the following change to Security to allow it to work.

  1. Connect to the SQL Server using the SQL Server Management Studio. Navigate to Security > Login.

2. Right Click on NT AUTHORITY\SYSTEM and open the Properties page. 

3. Next click on Server Role from the Select a Page panel on the left-hand-side and ensure that the dbcreator and sysadmin roles are ticked:

4. Click OK to save these changes.

2.5 Configure the SMTP Server

Open the Internet Information Services (IIS) 6.0 Manager from Start - Administrative Tools.

TIP - Check to ensure that you have set the SMTP service to start automatically and start the service.

  1. Right click in [SMTP Virtual Server #1] then open Properties.

2. In the Access tab, go to Connection control and click Connection.

3. Only allow Connections from the Local Host. Select OK.

4. Back in [SMTP Virtual Server #1] - Properties, go to Relay Restrictions and click Relay...

5. Only allow Connections from the Local Host. Select OK.

6. Apply the Settings and Exit.

Once you save these changes, Naverisk will be able to send Email Alerts through this SMTP server. 

Once the Naverisk installation has completed, log into Naverisk, click on the Settings tab, and click on the System Settings icon. Here, you can configure SMTP Settings, and send a test email.

Click the Send Test Email button to verify your SMTP configuration is correct.

It is also advisable to review the limits imposed on the Messages tab of the SMTP server’s Properties dialog. These limits can cause some email traffic to be refused; for instance, if you are generating Reports which are too large for these settings, sending these Reports via email will not work.

A recommended setting would be to make it 20480kb as per the screenshot below:

Note that the example Settings above will prevent any single email larger than 20MB from being sent. This will allow sending of Naverisk Email Alerts but will be too small for large Reports that include several Devices.

2.6 Firewall Ports

Add the following Rules to the firewall Port, REGARDLESS If you have a hardware firewall that controls incoming connections. Having extra control over a software firewall can be a life saver if an upgrade goes wrong;

  • Incoming TCP 8092 (Network Controller – Agent listener)
  • Incoming TCP 9202 (Site Controller - ACT (Agent) listener)
  • Incoming TCP 9999 (Site Controller – Network Controller listener)
  • Incoming TCP 9990 (Remote Control relay)
  • Incoming UDP 9990 (Remote Control relay)
  • Incoming TCP 8443 (Exago/Business Intelligence Reporting)
  • Incoming TCP 8081 (eAutomate Sync Service) – Only to be installed if you use eAutomate
  • Outgoing TCP 9993 (Management Service)

with 1 port per rule the firewall looks like this inbound. Please keep the rules separate and not combined as it can come in very handy later when troubleshooting to have full control over each port:

And outbound

3.0 Site controller Installation

3.1 Installation Process

  1. Execute the NaveriskBundleInstaller.exe from the installation pack:

2. Please ensure the Naverisk Site Controller and Naverisk BI are ticked as they are          required. Naverisk Sync is optional and to be installed if you use e-automate and          click install:

3. Click Next

4. Read the license agreement. Indicate acceptance by clicking the 'I Agree' option.          Acceptance is required to continue installation. Click Next.

5. Choose the Location for the installation; acceptance of the Default is highly                    recommended. If you are concerned about making backups of the Naverisk                  Directory, it is better to have a backup product that automatically backs up you             Naverisk files to an external location or a secondary drive. A better method would        be to have snapshots taken on an incremental regular basis.

6. The installation is ready to proceed. Click Next.

7. During the installation, you will find a second MSI icon will appear in your taskbar:

8. Select it and enter your SQL details. Choose your SQL server from the "Server              name" drop-down box, and your authentication method (and user name and                 password where required). In some cases, the SQL server may not appear on the         "Server name" box automatically;l if not, enter it manually.
9. Click OK.

Notes:

Make sure your Authentication mode and login work with your server configuration. If you are attempting to install Naverisk with its database on a remote computer, use of SQL authentication is required (i.e. you will need to enter a username and password in the SQL Server Settings dialog shown above). Windows Authentication will not work for remote database servers. Exercise caution when setting up the database configuration; database errors and failures during installation are most often caused by incorrect authentication settings.

Enter the General Settings for your Naverisk installation.

  • The User Settings will determine how the default user logs on to the Naverisk system. This user has all administrative permissions for the system.
  • Enter your Company Settings as appropriate; the Company Name will be used for the default client in the Naverisk system.
  • The Company Name must match the name used for licensing Naverisk.
  • The Naverisk system needs to know the URL which will be used to access the system; enter it in the Website Settings area. If using a secure https configuration, you may need to set up a Security Certificate to allow easy access to your Naverisk system website. This URL needs to refer to the computer on which the Site Controller is installed. If it does not, some aspects of the Naverisk system may fail (e.g. Remote Control, Agent connection process). It is not straightforward to change this setting later, as it is used to configure multiple parts of the Naverisk system, so it is advisable to ensure that this is correct before installing Naverisk. 
  • Important to NOTE: Please read the below before proceeding with the SMTP configuration.
  • The Email Settings are used to allow the Naverisk system to send Email Alerts. SMTP Gateway is the address of your SMTP (outbound email) server, used to send Email Alerts.  
  • In this case we have set it to localhost as it is the preferred and recommended method. If you choose to your own SMTP provider, you may encounter issues with notifications not being sent due to incorrect permissions on your external SMTP service. This will be up to you to resolve the permission issue on your external SMTP server and is not supported by Naverisk. 
  • SMTP Username is a username which can be used to log in to your SMTP server.  (blank for localhost)
  • SMTP Password is the password required to log in to your SMTP server with the username specified above (blank for localhost)
  • Please ensure that ‘SMTP uses SSL’ is unticked for localhost SMTP server.

10. Click OK once all settings have been entered.

Important to Note: The Company name must match the name used for licensing Naverisk. If you do not insert the Company name as per your License agreement with Naverisk you will either be requested to change the Company Name or required to sign a new Agreement. 

11. Please verify that the URL used for your website resolves to the external IP                   address of your Site Controller. If it does not, then your Agents won’t be able to           connect successfully. Likewise, this URL should resolve correctly internally – you          may need to add an internal DNS record for this.

12. You are returned to the installer window. Click Next. The installations is done, click Close to exit.

3.1 e-automate Naverisk Sync Service Installation (optional)

  1. If you selected the Naverisk Sync Service to be installed you will be presented with this installation next to install.

2. A dialogue box requesting the SQL database details will appear. Please choose the      correct Database server and login credentials as you did for the Naverisk                      Installation. Click OK to proceed.

3. Once the SyncService has finished installing, the Naverisk Business Intelligence reporting will start

3.2 Business Intelligence Reporting Installation

  1. The Naverisk BI installation will just be a selection of the SQL Database to install.

2. A dialogue box requesting the SQL database details will appear. Please choose the correct Database server and login credentials as you did for the Naverisk Installation. Click OK to proceed

The Naverisk installation has been completed. Next, we will need to install the website

4.0 Install the Naverisk Website

It is strongly recommended that the Naverisk website is published in a secure fashion, i.e. via https. Use of http is not secure and may allow third parties to gain access to your Naverisk system.

To use HTTPS, you require a certificate. It is usual for the installation to be available from the internet. So, it is recommended you get an SSL certificate from one of the many certificate providers. Self-signed Certificates are NOT recommended.

If you require the Naverisk Website’s Network Listening port to be different to the default, it is recommended that you choose a supported option from the list below. If you choose a port not listed, the Naverisk Forum Server and the Script Pack Repository will be unable to authenticate your session, and you will be unable to use these services.

The supported non-standard Ports are:

  • 444
  • 4433
  • 4443
  • 8080
  1. Execute the Naverisk Website Installation Pack (NaveriskWebsiteInstaller2008andLater.msi).

2. Select the Location for the Naverisk website install. It is recommended to leave the installation directory as the default set by the installer.

3. The Installer notifies that the installation is ready to begin. Click Next.

4. Wait for the installation process to complete. Close to Exit.

4.1 Configuring the Internet Information Services (IIS) Manager 

  1. Open the Internet Information Services (IIS) Manager and select the Default Website.

2. In Actions panel on the right-hand-side, select Bindings

3. Click Add. Select type as https. You will also need to select the SSL Certificate you wish to use for the connection.

4. Please repeat the same steps above for the Exago Website and set the binding to 8443:

5. In the connections panel, navigate to the default Web Site. Select Advanced Settings from Actions.

6. In the Advanced Settings set the Physical Path to the Naverisk Web Site Directory. By default, this is C:\Program Files (x86)\Naverisk Website\Website. Click OK.

4.2 Enable Compression on the Naverisk Website

From the Internet Services (IIS) Manager enable both the dynamic and static Content Compression and specify the thresholds for Compression as per the following screenshot.

  1. Edit the Compression module of the Default (Naverisk) Web Site so that both Dynamic and Static Content Compression are enabled

2. Highlight the top-level IIS structure and open the Configuration Editor

3. Navigate to the system.webServer/serverRuntime section of the configuration Editor and configure it as follows

4. Please ensure that the frequentHitThreshold is set to 2 and the frequentHitTimePeriod is set to 00:10:00. This will ensure more frequent caching for files than you would have by default.

4.3 Naverisk BI Configuration

  1. Open IIS

2. Right click on Applications pools, > Add Application Pool

3. Create a new Application Pool with the following details:

4. Right click the Application Pool Exago and go to the Advanced Settings.

5. Make sure that "Load User Profile" setting is set to true

4.4 Add ExagoWeb application

  1. Right Click on Default Web Site -> Add Application

2. Now do the same for the ExagoWebAPI application to the Naverisk Website
3. Right click on Default Web Site > Add Application

NOW Time to manually edit the IIS ROOT web.config. You'll find this config in the below folders depending on the architecture.

64bit: C:\Windows\Microsoft.NET\Frameworks64\v2.0.50727\CONFIG\web.config

Add the following to the ROOT web.config file after the green section:

<configSections>
<sectionGroup name="system.web.extensions" type="System.Web.Configuration.SystemWebExtensionsSectionGroup, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35">
<sectionGroup name="scripting" type="System.Web.Configuration.ScriptingSectionGroup, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35">
<section name="scriptResourceHandler" type="System.Web.Configuration.ScriptingScriptResourceHandlerSection, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" requirePermission="false" allowDefinition="MachineToApplication"/>
<sectionGroup name="webServices" type="System.Web.Configuration.ScriptingWebServicesSectionGroup, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35">
<section name="jsonSerialization" type="System.Web.Configuration.ScriptingJsonSerializationSection, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" requirePermission="false" allowDefinition="Everywhere"/>
<section name="profileService" type="System.Web.Configuration.ScriptingProfileServiceSection, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" requirePermission="false" allowDefinition="MachineToApplication"/>
<section name="authenticationService" type="System.Web.Configuration.ScriptingAuthenticationServiceSection, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" requirePermission="false" allowDefinition="MachineToApplication"/>
<section name="authenticationService" type="System.Web.Configuration.ScriptingAuthenticationServiceSection, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" requirePermission="false" allowDefinition="MachineToApplication"/>
</sectionGroup>
</sectionGroup>
</sectionGroup>
</configSections>

Now to amend the Naverisk web.config file that you will find under > C:\Program Files (x86)\Naverisk Website\Website

Remove the <configSections> and replace with the following:

<configSections>
<section name="microsoft.identityModel" type="Microsoft.IdentityModel.Configuration.MicrosoftIdentityModelSection, Microsoft.IdentityModel, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" />
</configSections>

4.5 Additional configurations for specific SQL server scenarios

If your SQL database is installed on a separate server, or if you have multiple SQL instances, the following files also need to be edited.

  1. C:\Program Files (x86)\Naverisk\Naverisk BI\ExagoWeb\Config\WebReports.xml

<datasource>
<id>0</id>
<name>Naverisk</name>
<dbtype>mssql</dbtype>
<dataconnstr>Data Source=Name of SQL Server\Instance;Initial Catalog=Naverisk;user=navreporting;password=p2p553Gt66D1</dataconnstr>
</datasource>

2. C:\Program Files (x86)\Naverisk\Naverisk\Naverisk BI\ExagoWeb\web.config
    and
    C:\Program Files (x86)\Naverisk\NaveriskBI\ ExagoWebAPI \Web.config

<connectionStrings>
<add name='DefaultConnection" connectionString="Server==Name of SQL Server\instance;Database=ExagoReports;user=navreporting;password=p2p553Gt66D1" providerName="System.Data.SqIClient" />
</connectionStrings>

The default value of Name of SQL Server\Instance is localhost. Replace this with the server and the instance names for your environment. For example

  1. SqIserver
  2. Localhost\instance
  3. SqIserver\Instance

4.6 Configure e-automate Sync

If you installed the e-automate Sync Service we will need to configure it. Currently it will be using default installation settings which may not work with your environment.

Please ensure that port 8081 is opened on your firewall.

The port number can be changed depending on your internal infrastructure configuration, however you will need to update the communication port in the Naverisk Sync Service config file.

  1. Navigate to C:\Program Files (x86)\Naverisk Sync Service on your Naverisk Server
  2. Open the file called Naverisk.Sync.Service.exe.config with your preferred text editor

3. The NaveriskURL key will need to be changed to your Naverisk instance URL as in what is the URL that you use to externally access your Naverisk instance on:

4. The ServicePort key is the port that the Sync Service will communicate on. It is recommended to keep the port standard however if you need to change this configuration, please remember to update your firewall rules as well so that the Sync Service can communicate on that port. 

5. If you have a self-Signed HTTPS server certificate you will need to add the below parameter:
<add key="IgnoreSSLCertificate" value="true"/>

6. This is so that the Sync Service is not prevented from communicating when reaching the below:

Once this is completed you can then access your Naverisk instance in the server by navigating to localhost within the browser.

Should you receive the below screen when navigating to localhost, please check and confirm that your DefaultAppPool is set to use .NET v2.0 and not .NET v4.0 as specified in section 2.0 page 12: 

It is an easy fix:

  1. Navigate to IIS
  2. Application Pools
  3. Select the Default App Pool
  4. Click on Basic settings and change it to use .Net 2.0:

You can then login with the admin account you created during the installation of the Site Controller and see that you have your Naverisk Site Controller Agent online:

5.0 Naverisk BI (Exago) Configuration

Now that the installations have been completed, we will need to configure Naverisk BI so that it will work in the Naverisk Website. Currently it will be using default installation settings which may not work with your environment.

  1. Navigate to settings > System Settings and take note of the Naverisk Website and Reporting URL:

2. Both of these URLs should be the same.
3. When you have entered your URL, click the Check button for the Naverisk to do a test that it can connect to your Naverisk BI Reporting server. You will get a green tick if it is successful:

4. Connections must be over HTTPS. You can get the check to pass with a non=HTTPS URL in the System settings but Naverisk BI will not work of you try to access it via reporting.

5. Naverisk will sit trying to load but will display the below:

6. You may also find an error popup in the bottom right hand side of your screen

7. If you open the browser built-in developer tools, you will see an error stating that the connection must be over HTTPS

8. If the database instance is a named instance rather than 'localhost', the web.config for ExagoWeb and ExagoWebAPI, and the webreports.xml for ExagoWeb needs to be updated with your server name.

You can find the configurations here:-

  • C:\Program Files (x86)\Naverisk\NaveriskBI\ExagoWeb\Web.config
  • C:\Program Files (x86)\Naverisk\Naverisk BI\ExagoWeb\Config\WebReports.xml
  • C:\Program Files (x86)\Naverisk\NaveriskBI\ ExagoWebAPI \Web.config

You can check the correct instance name by opening SQL Management Studio, and it should be displayed on the login details.

It is in the connectionStrings section:
<connectionStrings>
<add name="DefaultConnection" connectionString="Server=localhost;Database=ExagoReports;user=navreporting;password="providerName="System.Data.SQIClient" />
</connectionStrings>

Please ensure that your bindings are correct, that your website is served over HTTPS and your firewall ports are open. Once Naverisk BI is configured correctly you will need to be able to access it through the reporting tab under business intelligence and will see the below

6.0 SQL Server Permissions

The SQL Server permissions modified in Section 2.4 must now be reset them back to the default settings. Using the same procedure, for the NT Authority\System user, deselect the dbcreator and sysadmin roles, ensuring that only the public role is selected.

Important - Leaving these roles selected may pose a security risk to your SQL server.

6.1 SQL Update the Recovery Model

Due to the large SQL log files for the new Databases - Exago and Quartz Databases, we will need to change the recovery model to "Simple".

  1. Right click on database name and select properties
  2. Go to the Options page
  3. Under the Recovery model select "Simple"
  4. Click "OK" to save

7.0 e-automate Configuration (Optional)

If you installed the e-automate Sync Service we will need to configure it. Currently it will be using default installation settings which may not work with your environment.

Please ensure that port 8081 is opened on your firewall.

The port number can be changed depending on your internal infrastructure configuration, however you will need to update the communication port in the Naverisk Sync Service config file.

  1. Navigate to C:\Program Files (x86)\Naverisk Sync Service on your Naverisk Server
  2. Open the file called Naverisk.Sync.Service.exe.config with your preferred text editor

3. The NaveriskURL key will need to be changed to your Naverisk instance URL as in      what is the URL that you use externally access your Naverisk instance on:

4. The ServicePort key is the port that the Sync Service will communicate on. It is              recommended to keep the port standard however if you need to change this               configuration, please remember to update your firewall rules as well so that the           Sync Service can communicate on that port.

5. If you have a self-Signed HTTPS server certificate you will need to add the below        parameter:

<add key="IgnoreSSLCertificate" value="true" />

6. This is so that the Sync Service is not prevented from communication when                   reaching the below:

7. Once you have configured the Sync Service config file to match the configurations in your environment, click save.

8. We will now need to restart your Naverisk services.
9. Please stop the Naverisk services in the following order
     -     NaveriskServiceMonitor
     -     NaveriskSiteController
     -     NaveriskReportingService
     -     NaveriskAgent
     -     Naverisk BI Monitoring Service
     -     Naverisk Sync Service
10. Once the services have stopped, please start them in the following order:
     -     Naverisk Sync Service
     -     Naverisk BI Monitoring Service
     -     NaveriskSiteController
     -     NaveriskServiceMonitor
     -     NaveriskReportingService
     -     NaveriskAgent
This ensures that the Sync Service is started first so that when the SiteControllerService gets to the point in its start up process it is able to communicate with the Sync Service.

8.0 Host Optimisation

The main concept behind the optimisation of your Naverisk Site Controller host server is to ensure there are sufficient resources for Naverisk to run, and to prevent other applications on your server from competing with Naverisk for these resources.

To that end, the following is recommended:

  • Make sure that your host server meets the recommended hardware specifications.
    - Less than 1000 agents – 2 CPUs, 2GB RAM, 40GB Disk.
    - 1000 – 2000 agents - 2 CPUs, 4GB RAM, 100GB Disk.
    - More than 2000 agents - 4 CPUs, 8GB RAM, 150GB Disk.
  • Add an exception for your antivirus software to specify that you do not wish to scan the folder “C:\%programdata%\Naverisk\Network Controller\DataStorage\”, or any of its sub-folders. This is a temp folder which contains transient information.
  • For best performance, a dedicated server (physical or virtual).
  • Should you consider using a SBS system, please be aware that you will run into issues later when you have more Agents and more Clients as SBS systems were not designed by Microsoft in the same way as a Server Standard system. You will need to look at migrating your instance to a dedicated Server Standard machine later. 

9.0 Database Optimisation

Naverisk has the functionality to perform Daily Maintenance operations out of the box. This involves the cleaning of very old monitoring statistics and the moving of old Archived Tickets to a separate table (thereby reducing the time required to find and retrieve ticket information). By default, Naverisk database maintenance runs at 1am for 2 hours daily.

9.1 Naverisk Database Maintenance 

To customise this, you just need to edit the Site Controller Configuration File to specify at what time you would like to start database maintenance work and how long you would like this maintenance window to run for. The Site Controller Configuration File is located under:

C:\program files (x86)\naverisk\sitecontroller\NaveriskSiteController.exe.config (64-bit systems only)

The steps for enabling SQL database maintenance are as follows:

  1. Edit the NaveriskSiteController.exe.config file in Notepad
  2. Search for the word "MaintWindowStartHour".

    If this key does not exist, then please add it to the <appSettings> section of the config file like so:

    <add key="MaintWindowStartHour" value="x"/>

    "x" in this context is the circadian time you wish to start database maintenance (0-23 with 0 being midnight), taking into account the time zone of your Site Controller server.
  3. Search for the word "MaintWindowLengthHours".

    If this key does not exist, then please add it to the <appSettings> section of the config file like so:

    <add key="MaintWindowLengthHours" value="x"/>

    "x: in this context represents the number of hours you permit database operations to run. A value of 0 means that Naverisk will not only run daily maintenance operations.
  4. Arrange for the Naverisk Site Controller Service to be restarted at a suitable time, so that the changes you have made can take effect.

9.2 Standard Database Maintenance

Microsoft SQL server makes an LDF file for each Database (MDB) file created. The purpose of the LDF file is to hold a Database Transaction Log. Some partners find that this LDF file grows unchecked, because SQL does not clear the Transaction Logs as it should. The LDF file can only be reduced in size after a successful backup.

To keep this File regularly maintained it is advisable to schedule a regular SQL Database backup. Some points to consider with regards to this backup are:

  • When using the Database Full Recovery model, ensure log backups are made on a regular basis to keep the log file size under control. More regular log file backups will result in smaller log files.
  • If you are using 3rd party reporting tools with your Naverisk database, these may leave File Locks in place that prevent the LDF file from shrinking during backups. If you find that this is happening, try restarting your SQL server (to remove these file locks) then rerun the SQL backup when there are no locks in place.

10.0 Backing up the Site Controller

Making use of an image backup program like StorageCraft ShadowProtect for creating images of your Naverisk server would be more suitable than file/folder backup. Contact support@naverisk.com for further details regarding StorageCraft. 

Note: It is not necessary to restore from a backup as part of the normal Naverisk upgrade process. See the Naverisk Upgrade Guide for information on the upgrade process.

10.1 Content to Backup

To back up the Naverisk Site Controller and Website such that they can be restored to their previous settings after a fresh install using the Naverisk installers, it is necessary to back up the following:

The SQL database:
'Naverisk'

The following folders and files:

  • ProgramFiles(x86)\Naverisk\SiteController\HistoricalDataStore
  • ProgramFiles(x86)\Naverisk\SiteController\XmlData
  • ProgramFiles(x86)\Naverisk\SiteController\NaveriskSiteController.exe.config
  • ProgramFiles(x86)\Naverisk Website\Website\web.config
  • Program Files (x86)\Naverisk\Naverisk BI\ExagoWeb\web.config
  • Program Files (x86)\Naverisk\Naverisk BI\ExagoWebAPI\web.config
  • Program Files (x86)\Naverisk Sync Service\Naverisk.Sync.Service.exe.config
  • %ProgramData%\Naverisk\Network Controller\NC.cfg

If you have custom report images:

  • Program Files (x86)\Naverisk\ReportingService\Images

If you have a customised website image:

  • [WebsiteInstallFolder]\Resources\Images\irisLogo.png

If you have customised reports:

  • ProgramFiles(x86)\Naverisk\ReportingService\Reports

If you have created any Script Packs:

  • ProgramFiles(x86)\Naverisk\SiteController\ScriptPack\

Substitute the correct Program Files folder for [Program Files] above; this will usually be ‘Program Files’ or ‘Program Files (x86)’ on your System Drive. 

10.2 Database to Backup Job

It is recommended that you setup a SQL DB backup job on your Naverisk instance via the scheduler to back up the SQL Database each day at a time of your choosing to ensure that you always have a recent DB backup. 

This can be done via the below three separate scripts:

Naverisk DB Backup

IF NOT EXIST D:\Backup md D:\Backup

sqlcmd -Slocalhost -Q"BACKUP DATABASE Naverisk TO DISK = 'D:\Backup\Naverisk.bak' with INIT, SKIP"

Exago DB Backup

IF NOT EXIST D:\Backup md D:\Backup

sqlcmd -Slocalhost -Q"BACKUP DATABASE ExagoReports TO DISK = 'D:\Backup\ ExagoReports.bak' with INIT, SKIP"

eAutomate DB Backup


IF NOT EXIST D:\Backup md D:\Backup

sqlcmd -Slocalhost -Q"BACKUP DATABASE Quartz TO DISK = 'D:\Backup\ Quartz.bak' with INIT, SKIP"

These will need to be saved as three separate *.cmd files and uploaded into your Naverisk instance to create a Naverisk Script pack. Each Script pack can then be scheduled in 30 minute intervals of each other to ensure less of a performance hit on resources during this time on the server.

Please read the Applying Script Packs document in Naverisk Help and watch the video Patching and Scheduling for more information.

https://www.youtube.com/watch?v=pveGoAZ2fHg

11.0 Restoring the System

To restore the Naverisk System, follow these steps if using a file/folder backup method.

Note: This should only be done if the Database has been corrupted or you need to restore previously backed-up data

  1. Restore the SQL Database. This must be done before reinstalling the System
  2. Reinstall the Naverisk System using the current Installers
  3. Stop the Naverisk Service Monitor and the Naverisk Site Controller Services
  4. Restore the File Data (as listed above)
  5. Restart the Services from step3.
Did this answer your question?