AdvanceGuard® Upgrade Instructions
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.
Only upgrades are supported by the standard Witness installer. You cannot downgrade a newer installation to an older version.
Typically all actions / recommendations apply even if you skip a upgrade between older versions, therefore please ensure you check all upgrade notes from the version being upgraded to the version you intend to install. All of these actions and recommended settings only apply when upgrading existing installations, unless otherwise stated, these steps are not required for new installations.
Contents
- 1 Upgrading to 4.12.4.904 from 4.12.3.900 (MongoDb V7.0)
- 1.1 Database Upgrade
- 2 Upgrading to 4.12.3.900 from 4.12.2.896 (MongoDb V6.0)
- 2.1 Database Upgrade
- 3 Upgrading to 4.12.2.896 from 4.12.1.893 (MongoDb V5.0)
- 3.1 Database Upgrade
- 4 Upgrading to 4.12.1.893 (MongoDb 4.4)
- 4.1 Prerequisites
- 4.2 .NET 8 Upgrade
- 4.3 Database Authentication
- 4.4 Log Rotate
- 5 Upgrading to 4.12.0.879
- 6 Upgrading to V4.12.x
- 6.1 Rule Gate Link
- 6.2 UI Streaming
- 7 Upgrading from V4.8.0.x to 4.8.0.578
- 8 Upgrading from V4.7.0.x to 4.8.0.x
- 9 Upgrading from V4.6.0.x to 4.7.0.x
- 10 Upgrading from V4.4.0.x to 4.6.0.x
- 11 Upgrading from V4.3.0.x to 4.4.0.x
- 12 Upgrading from V4.1.x to V4.3.0.303
- 12.1 Reset Views
- 13 Related Information
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.
Please be aware of the following restrictions when upgrading to this release:
You can only upgrade to this version from 4.12.3.900. Because of the database requirements all upgrades must happen in sequence.
You must have started the installation of 4.12.3.900 at least once before upgrading to this version. Please see the note below on the requirements for starting a system at least once.
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:
Copy this certificate onto the targets servers / PCs:
Once copied, right click on the file and select Install Certificate.
Select Local Machine for the store location and click Next: