Introduction

These instructions cover any requirements or preparation required when upgrading from older to newer versions of AdvanceGuard™. We strongly recommend that you check these instructions and review the relevant release notes before starting any upgrade. AdvanceGuard® Release Notes

All upgrades should be performed by running the installer from the latest version and selecting the Upgrade option when prompted.

Contents

Upgrading to 4.12.4.904 from 4.12.3.900 (MongoDb V7.0)

Database Upgrade

This version has no new features and is intended only to upgrade the database version from V6.0 to V7.0.

Upgrading to 4.12.3.900 from 4.12.2.896 (MongoDb V6.0)

Database Upgrade

This version has no new features and is intended only to upgrade the database version from V5.0 to V6.0.

Upgrading to 4.12.2.896 from 4.12.1.893 (MongoDb V5.0)

Database Upgrade

This version has no new features and is intended only to upgrade the database version from V4.4 to V5.0.

Upgrading to 4.12.1.893 (MongoDb 4.4)

Prerequisites

This release includes version 4.4 of the MongoDb database server. This version requires the Visual Studio C++ 2019 x64 redistributable library. Technically this has been part of the Witness pre-requisites since the release of 4.11, however we recommend this is checked before installing Build 1099. Please see Software Prerequisites for more information.

.NET 8 Upgrade

This version is built on the latest Microsoft .NET technology stack. All necessary support files are shipped with the product so additional action is required, however be aware that .NET 8 is only supported on the following versions of Windows:

• Windows 10 Build 1607 and newer.

• Windows 11 Build 22000 and newer.

• Windows Server 2012 and newer.

Database Authentication

Database authentication is supported in this release. If you need to implement it then please refer to Database Authentication. All configuration associated with the database authentication is done after installation.

Log Rotate

This version now automatically installs a Windows Scheduler Task to rotate the MongoDb logs every 24 hours. It is strongly recommended that any existing logs associated with older methods of log rotation are deleted before the task first runs to avoid any potential conflicts and confusion.

Upgrading to 4.12.0.879

Code Signing Certificate

Version 4.12.0.1073 and above use a new code signing certificate because the old one expired. If the target systems for these versions have an internet connection then everything will work as expected. However if the systems do not have a standard internet connection then the code signing check may fail because it won’t be able to verify the digital certificate embedded in the application files against the root certificate. To resolve this issue you need to install the root certificate on all systems running any part of the Witness software, excluding stand alone database servers. The process for installing the certificate is:

1. Copy this certificate onto the targets servers / PCs:
   
   

   
   
   

2. Once copied, right click on the file and select Install Certificate.

3. Select Local Machine for the store location and click Next:
   
   

   Open

   

4. Select the option Place all certificates in the following store and select Browse.
   
   

   Open

   

5. Select the Trusted Root Certificate Authorities and select OK:
   
   

6. Select Next and then Finish.

Upgrading to V4.12.x

Rule Gate Link

Any rule with a Gate Link needs to be checked and tested after the upgrade because of the new modes and updated behaviour. It’s expected that the behaviour of any existing rule using this link will change after the upgrade.

UI Streaming

Improvements to the UI streaming feature mean that you must now always switch off streaming in a PPI window before activating another window. In addition, any changes to the streaming protocol or network port in the user settings will cause the streaming server to stop and the user must be re-activate the feature.

Upgrading from V4.8.0.x to 4.8.0.578

VMS Integration Plugins

Due to improvements made in the camera mapping logic in the Milestone, Genetec and BVMS integration plugins, existing configurations will be automatically updated when upgrading to this version. However we recommend that these mappings are checked once the upgrade is complete.

Upgrading from V4.7.0.x to 4.8.0.x

User Interface Panel Layout

Due to the change to store the panel layout in each user’s settings any existing panel arrangements will be lost and will need to be recreated. If at any stage you need to reset the layout to ensure correct operation please use the Reset View option from the system menu.

Licencing

All V4.8 deployments will require a new licence when migrating from V4.7.

Upgrading from V4.6.0.x to 4.7.0.x

Open Street Map Tile Cache

With the introduction of live Google Maps tiles into the Helvellyn user interface, the folder structure associated with caching tiles on disk has changed. If Open Street Map was being used in an offline mode (i.e. no internet connectivity, cached tiles only), then the old tiles need to be moved to a new location. If the client has internet access then no action is required, although we would recommend the old tiles are deleted. The instructions below identify which folders can be removed.

To move an existing Open Street Map (OSM) tile cache with no internet access:

1. Ensure the system has been fully upgraded including all client applications.

2. Move the map tiles from the existing folder to the new one. If the new folder does not exist you should create it:

   1. Old OSM Cache Folder - C:\ProgramData\Navtech\MapCache

   2. New OSM Cache Folder - C:\ProgramData\Navtech\MapCache\OpenStreeMap
      
      
      

       

3. All the old folders will be numbered as illustrated in the image. The Google and OpenStreetMap folders are part of the new structure.

4. Start the client application and ensure the cached tiles are loading as expected.

To re-create the Open Street Map (OSM) tile cache with temporary internet access:

1. Ensure the PC running the client has temporary internet access.

2. Start the client application and then pan and zoom as required across the site to ensure the relevant tiles are saved to the correct cache location.

3. Delete the old numbered folders inside MapCache.

Upgrading from V4.4.0.x to 4.6.0.x

There is one key issue associated with the upgrade that impacts the ICD-001 plugin configuration. There is a breaking change in the new ICD-001 configuration that will force the existing configuration to be reset to defaults. This includes disabling the plugin.

Upgrading from V4.3.0.x to 4.4.0.x

There are a number of issues to check with this upgrade, although the upgrader should handle all the required changes.

Database Server Upgrade

V4.4.0 has moved to V4.x of the Mongo database server. In order for this upgrade to work successfully, the database must be upgraded from V3.6 which was included with later version of Witness V4.2.

To be certain that the database is at the right version, please upgrade to the latest version of 4.3.x before upgrade to V4.4.

Classification Changes

The classification option list has changed to support multiple classification options in configuration, such as the rule classification check node. In order to support this change the classification model options have all been changed, The software upgrade will handle the database changes, but we recommend the following configurations are checked:

1. The Classification Models

Upgrading from V4.1.x to V4.3.0.303

Although this is a significant upgrade there are no major considerations other than ensuring that you have reset the views for both non-configuration and the new configuration modes.

Reset Views

From V4.3.0.303 onwards, the configuration tab has been replaced with a configuration button. This button shows the appropriate panels for making changes and also enables the edit control buttons. The user interface has a normal view and edit view for the Live tab and these need to be reset after the upgrade.

To reset the views:

1. Ensure you are on the Live tab and not in configuration mode

2. Select Reset View from the system menu

3. Remain on the Live tab and enable configuration mode by selecting the configuration button.

4. Select Reset View from the system menu again

5. Once this process is complete you can adjust these views to suit your needs

Related Information