Just Published! Threat Report: Exposing Malware in Linux-Based Multi-Cloud Environments | Download Now

Cannot Upgrade Cb Protection Server - Incorrect Version/Build

Cannot Upgrade Cb Protection Server - Incorrect Version/Build

Version

Cb Protection 7.x.x

Issue

Cannot patch server from build-to-build using the patch utility.

Symptoms

Patch log shows, "ERROR: Bit9 Server version of x.x.x is NOT valid for patching. Aborting"

Cause

The registry values are incorrect according to the version and build number of Cb Protection.

Solution

1. Disable the 'Bit9 Server Tamper Protection' Updater rule to allow registry modifications. (From the Console Menu - Rules>Software Rules>Updaters Tab)

2. Open Run > RegEdit

3. Navigate to the registry path for your OS as shown below:

For 32 bit servers - HKLM\Software\Bit9\Parity Server\7.0

For 64 bit servers - HKLM\Software\Wow6432Node\Bit9\Parity Server\7.0

3.1. The registry should show a different version and build from the version and build that is currently running. 

If the incorrect version and build values are found under either of these paths, then adjust the values to the current version and build that is running, as explained below:

For example:

You're current running Cb Protection Version is 7.2.3.3270, but the Registry shows the 'ProductVersion' data to be 7.2.0, and the 'Build' data to be 2101 - these data values would need to be edited to reflect 'ProductVersion' as 7.2.3 and the 'Build' as 3270

NOTE: You will be changing the version and build in the registry to the current running version and build number - NOT to the version and build you are upgrading to.   You can find your current version, if needed, by checking the version number shown in the console.

2017-02-21_15-26-06.png

4. Run the patch utility again and it should patch successfully.

5. Re-enable the 'Bit9 Server Tamper Protection' Updater rule

Labels (1)
Was this article helpful? Yes No
No ratings
Article Information
Author:
Creation Date:
‎09-30-2016
Views:
680
Contributors