This guide is for upgrading an existing Naverisk installation version 2019 R1 or later to version 2023 R1.

Do not use this guide to upgrade to an earlier release, as the procedure is different and may result in Naverisk not working or corrupted data. If you are installing a new installation of Naverisk, please refer to the Site Controller Installation Guide. If you have a version pre 2018 R2 please contact support to be updated.

Naverisk versions from 2019 R2 onward have additional database storage requirements, and the database size will increase at a greater rate than on previous versions. To maintain database performance and size it is important to correctly configure the Naverisk data retention setting and ensure the maintenance scheduler is running.

If you are using SQL Server Express, you will need to carefully monitor database size to ensure it does not exceed the limitation of your version of SQL Server Express.

The key areas to note are

These are all covered in the appropriate section of this guide, and the procedures must be followed exactly.

The Naverisk system is designed to be simple and easy to use. The process for upgrading Naverisk is also designed to be as quick and simple, however we recommend a few preliminary steps be taken when running an upgrade; these steps are described in this document.

When upgrading a local installation of Naverisk the administrator need only uninstall the previous version of the Naverisk software and then run the installer for the latest version. There are two installers, one for the Naverisk website and one for the Naverisk Site Controller. "Please Note if you have custom config files these need to be backed up and then restored after upgrade. This as per documentation."

It is best to have a copy of the new installers on the machine before proceeding with the uninstall process to minimise the amount of system downtime.

The installer will automatically update the Web Interface, Database, and Agents of the system. All data will be retained where possible and any new packages will be pushed out automatically to all agents. "Please note this will overwrite custom configurations so those files need to be backed up before running the installation."

The Naverisk installation process is very robust, but certain parts of the system (namely the database and certain system configuration files) should be manually backed up in case there is a need to roll back to the previous installation. It is only necessary to back up the Site Controller machine. Agent machines do not need backing up. "Please Note you must backup Site Controller configuration files if custom written to allow restoration after upgrade."

Important notes: Releases 2018 R4 and later includes a new Naverisk BI reporting engine. If you are upgrading from version 2018 R2 or earlier, Naverisk BI installation has a number of pre-requisites and additional installation steps that must be completed in addition to the normal procedure. These are documented in this Guide, and we strongly recommend following the steps carefully, even if you are familiar with the Naverisk upgrade procedure.

If you are running 2019R1 or above some steps 1-1.3 and step 3.6 will not be needed as these steps will already have been completed

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

Minimum Requirements –

If you are running an earlier version, you will be required to upgrade your server before proceeding any further with the Naverisk installation.

We recommend using SQL 2019 SP2 and Server 2019 or later.

If you are upgrading version 2018 R3 or newer move to Section 2.0

You will need to change the SQL Server permissions so that the installer can create the necessary databases.

2. In the Server Properties, click Security, and enable SQL Server and Windows Authentication Mode

3. Click OK to apply the change and then in the SQL Management Studio, expand Security and then Logins.

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

5. 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:

6. Click OK to save these changes.
7. A restart will be required to apply these changes, but this can be postponed until later.

2. In the Add Roles and Features Wizard, click Next, Next and Next again to bring you to Server Roles Expand out the Web Server role, and then the Application Development Role. Select .Net Extensibility 4.5 and click Next.

3. In the Features selection panel, enable the Windows Identity Foundation 3.5 feature. Note that if you are using Windows Server 2008 R2 this will need to be downloaded and installed, as it is not included in the Server Roles.

4. Click Next and then Install to begin the Roles and Features and installation.
5. A restart will be required to complete the installation

At this point it is a good opportunity to arrange for the server to be restarted  so that the above prerequisites can complete their installation.

Naverisk only supports compatibility mode 2016 or higher. Please check that this is set to 2016 or higher as below.

Go to the following, sql manager -> expand the databases -> right-click Properties on the Naverisk database-> Options panel in the Database Properties pop up

Naverisk backups are important, as they will enable us to restore the server back to its current configuration should anything go wrong with the installation.

The firewall rules are important and will prevent Agents trying to connect to the Naverisk system while it is being started after the upgrade. If this is done, the Naverisk system will take less time to start after the upgrade and prevent the chance of agent installations if the upgrade fails.

To back up the database you can use the SQL Server Management Studio tool.

2. Right click and select Tasks and then Back Up... from the menu.

3. On the General tab, ensure that the Backup Type is Full and that you are comfortable with the backup location. The location can be changed by using the Remove button to delete the existing location and using the Add... button to designate a new location and file name.

4. Please select the Media Options tab within the Select a page panel, and enable the Overwrite all existing backup sets option. 

5. Please click OK on the bottom right and please be aware of the progress indicator in the bottom left. When the backup is complete you should receive a notification.

6. Perform a backup for "ExagoReports" and "Quartz" database by following steps 2        to 5 for them both.

And

Note: If you have an alternative backup tool, it can be used instead. Whichever method is used, you should ensure that you are able to perform a successful restore from that backup.

You should back up the following files below to preserve any customization you may have made to your Naverisk that could be overwritten by the upgrade, and to ensure that Naverisk Support can restore your server to its current configuration if required by a failed installation.

NOTE: Not all of these files are to be restored after the upgrade.

It is recommended to create a separate folder for the backups that is date stamped. These will include the below required files as well as the database backup. Having these backups in a centralised location will make it easier for Naverisk Support to assist you if you require some help.

Site Controller Files to Backup

Reporting Service Files to Backup

Naverisk Sync Service Files to Backup (If it has been installed)

Naverisk Website Files to Backup

Naverisk Agent & NC Configuration files to Backup

Naverisk BI Configuration files to Backup

Note: It is not required to back up the Naverisk XML Data or Historical Data while upgrading Naverisk. It is best practice to have a backup of these files in the event of a server failure however.

The XML Data and Historical data can be found in:

If you have the ability to take a Snapshot Backup of your Naverisk server, it is highly recommended that you do so. This will be the best form or roll back that you could have in case of a failed upgrade. 

To install the new Naverisk system you must run new installers. After these have been run the Naverisk system will automatically start the appropriate services and begin updating Agents.

2. Please ensure that Naverisk Site Controller is ticked as this is mandatory.

Naverisk Sync Service is optional and is only required if you use the Naverisk e-         automate integration.
Naverisk BI is our new Business Intelligence Reporting engine and we                         recommend installation. If you are upgrading from a previous version where Naverisk BI was installed, you must select the option to re-install Naverisk BI.

Please make you selection and click Install.         

This image is pre 2022R2

This image is post 2022R2

3. Please click Next to proceed with the Site Controller Installation

2. Read the License Agreement. Indicate acceptance by clicking the 'I Agree' option.        Acceptance is required to continue installation. When ready, click Next.

3.  Choose the Location for the installation (if different from the default) and continue by clicking Next

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

5.  During the installation you will find a second MSI icon will appear in your taskbar

6.  Select it and you will be presented with a SQL Server authentication prompt

NOTE: Please exercise caution when entering the database authentication; database errors and failures during installation are most often caused by incorrect settings.

7.  Please click OK to proceed
8, The Naverisk Site Controller can take a while depending in the size of your Database, and the age of the Naverisk version you are upgrading from. Please do not be alarmed if the installer sits at this stage for a while it is perfectly normal. 

9.  When completed you will be presented with the below installer window

Click Next and the installation is done, click Close to exit.

NOTE: If you do not see the above window when performing an upgrade installation but rather a window asking you for details to be entered such as Company Name and SMTP settings etc. This will indicate a failed upgrade and a new blank database has been created. Most likely causes for this issue are having incorrect SQL authentication or insufficient SQL permissions. Please jump to section 8.0 for the roll back procedure. 

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

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

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

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

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. Then Close and Exit.

Open IIS and Locate and edit the Naverisk Website (Default Website)

Click Basic Settings and correct the Physical Path as it has changed

Change the path as the image below,

The below config files need these changes. (Assuming you are using the default locations.)

C:\Program Files (x86)\Naverisk\SiteController\NaveriskSiteController.exe.config

C:\Program Files (x86)\Naverisk\ReportingService\Naverisk.Reports.ReportingService.exe.config

C:\Program Files (x86)\Naverisk Sync Service\Naverisk.Sync.Service.exe.config

C:\Program Files (x86)\Naverisk\Website\web.config

Transfer over the <AppSettings> section from the original file (from your backup) to the new config file as per below which will have been generated by the new update.

Example of the Naverisk.Sync.Service.exe.config

Important Note: Additionally, if you have customised changes in your web.config file you will need to also copy these to the new web.config file.

2. Make sure ISAPI and CGI Restrictions are allowed for v4. Follow below steps
3. Open the IIS Manager and navigate to the server level.
In the Features view, double-click ISAPI and CGI Restrictions to verify that the Web service extension is set to Allowed.

4. If the extension is not in the list, click Add in the Actions pane.
5. 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.
6. In the Description box, type a brief description of the restriction
7. (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.
8. Click O.K.

At this point it is recommended to log into your Naverisk Website and confirm that the Naverisk Site Controller upgrade was successful.

NOTE: Due to significant changes in the website it is recommended that you clear Cached Images and Files from your browser cache.
You should be able to see your previous client lists and devices confirming that the installation completed successfully, so we now need to restore your customisation's;

NOTE:- If you are upgrading from any version before 2022R2 you will have already completed these steps in section 3.6. If you have only upgraded from 2022R2 or later then you do not need to restore files 1-4 as below but restore files 5-8.

Additionally, if you have customized your Website and/or Report logos, you will need to restore those specific images contained in the below directories that were backed up:

If you don't have the BI configured then additional server configuration is required to setup the Naverisk BI component

     2. Expand the Server Connection and right click on Application Pools, and click on           Add Application Pool

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

4. Navigate to the list of Application Pools and right click on the newly created                 Exago application pool and select Advance Settings.

       5. Under the Process Model configuration set the Load User Profile value to True            and click OK

6. In the connections panel, expand out Sites, select and right click on the Default Web Site choose Add Application from the menu

7. In the Add Application window please enter the following details:
    Alias: Exago
    Application Pool: Exago
    Physical Path: C:\Program Files (x86)\Naverisk\Naverisk BI\ExagoWeb
    If you have installed the Naverisk Site Controller to another location, please adjust       the Physical Path appropriately

8. Click OK to continue
9. Once again right click in Default Web Site choose Add Application from the menu

10. This time please enter the below deatils:
     Alias: ExagoWebAPI
     Application Pool: Exago
     Physical Path: C:\Program Files (x86)\Naverisk\Naverisk BI\ExagoWebAPI
     If you have installed the Naverisk Site Controller to another location, please adjust       the Physical Path appropriately

We must now manually edit the IIS ROOT web.config.

Please copy and add text below:

<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="roleService" type="System.Web.Configuration.ScriptingRoleServiceSection, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" requirePermission="false" allowDefinition="MachineToApplication"/>
        </sectionGroup>
      </sectionGroup>
    </sectionGroup>
</configSections>

4. Save the changes and copy the web.config back from the desktop into the directory if required.

Next we must now manually edit the IIS ROOT web.config. Important: Do not replace this file with the backup copy made earlier. You must edit the new web.config file and add any customisations made by copying them from your backup copy. 

And replace the following:

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

Example:

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.

If you are upgrading from 2018 R3 or later you will need to set the Data Source again as the previous value is not retained. You must edit the WebReports.xml file with the required values. DO NOT restore this file from a backup as other values may have changed.

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

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

     Sqlserver
     Localhost\instance
     Sqlserver\instance

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".

At this point we need to reboot the Naverisk Server so that the changes we have made to the web.config files are picked up by the OS. The Naverisk services are most likely still offline from earlier in this guide, so it should just be a straight up reboot of the server.

3. Please use the Check button to confirm that the Naverisk BI access is working correctly

If successful the button should be temporarily replaced with a tick

4. Finally click Save Settings at the bottom of the page to save the configuration

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.

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:

6. If you have restored the Sync Service config file from a previous installation )i.e. you are upgrading) you will also need to add the following key to the config file:

<add key="CustomerAndContactSyncFrequency" value="5" />

By the Time you've done this, the Naverisk services should have started and you can now login to the website to make the following changes:

If you modified the SQL Server permissions in Section 1.1, you will need to 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 you SQL server.

In Section 2.0 we changed the firewall rules to prevent the Agents from connecting on ports 8092 and 9202. We can now remove this block or otherwise reactivate the rules to allow for the agents to connect again.

The Naverisk Agents will be automatically updated, and each updated Agent will download all of its packages from the Site Controller. Depending on the speed of the network, this may take some time. Agents will show as disconnected in the web interface until they have upgraded and reconnected.

There are multiple ways of initiating Agent Upgrades after upgrading your Naverisk.

3. Click the Edit button

4. Under Client Details, set the Agents Update: box to Automatically

5. Scroll down and click Save

3. Click on Select a task and choose Upgrade Agents

4. Click OK

        on the left to bring out your Clients list
   3. Choose the Client you wish to create a Scheduled Job for
   4. Click 

        in the top right corner of the screen
    5. Configure your Settings, click  Enabled (if you wish to enable now) then click on            Action

    6. Fill in your desired Pre-Action settings, click Upgrade Agent for Action, fill in your         desired Post-action settings, then click Save.

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

If you took a Snapshot of your Naverisk server, roll back to the working snapshot of your Naverisk instance. It will be the fastest and easiest way to get your Naverisk back online. If you do not have a Snapshot image, please follow the below steps.