Forum.shavlik.com

The latest release of Shavlik NetChk Configure, version 4, provides the option to upgrade from a previous release of Shavlik NetChk Compliance. For instance, this might include an upgrade from Compliance version 3.0 or 3.1 of the product. Upgrade to Configure 4, in some cases, proceeds best if a hotfix has been applied to the earlier release of NetChk Compliance. To determine if such a hotfix is needed, use the following instructions:

Prior to upgrading, in NetChk Compliance use the menu option Help-About to review which version of the product you are using. If the version lists 3.1.x, then you are using NetChk Configure 4 (see Option A below). If the version lists 3.0.0, then you are using NetChk Compliance 3.0. If using NetChk Compliance 3.0, further check if using SQL Server or Access. This will be displayed on the same Help-About screen under \"Using database:\". If using Access, see Option B below. If using SQL Server, see Option C below.


Option A) Upgrading from NetChk Compliance 3.1 to NetChk Configure 4

An upgrade to Configure version 4 from Compliance version 3.1 should occur without issues by ensuring that NetChk Compliance 3.1 is closed at the time of upgrade. We recommend backing up your database prior to upgrade. On the console machine, click on the Configure 4 installation package and follow the installation steps.


Option B) Upgrading from NetChk Compliance 3.0 to NetChk Configure 4 using Access

An upgrade to version Configure 4 from Compliance version 3.0 when using Access should occur without issues by ensuring that NetChk Compliance 3.0 is closed at the time of upgrade. We recommend backing up your database prior to upgrade. On the console machine, click on the Configure 4 installation package and follow the installation steps.


Option C) Upgrading from NetChk Compliance 3.0 to NetChk Configure 4 using SQL Server

If you are connected to SQL Server using Windows authentication, an upgrade to version Configure 4 from version 3.0 when using SQL Server with Windows authentication should occur without issues by ensuring that NetChk Compliance 3.0 is closed at the time of upgrade. We recommend backing up your database prior to upgrade. On the console machine, click on the Configure 4 installation package and follow the installation steps.

If you are connected to SQL Server using SQL authentication, an upgrade to version Configure 4 from version 3.0 when using SQL Server should be performed after a hotfix is applied to version 3.0 prior to upgrade. Determine if the hotfix has been applied by reviewing the menu option Help-About and checking Build number on this screen. Machines REQUIRING the hotfix list have a build number that is LESS THAN Build 301. If your build number is less than Build 301, go to the following forum location to obtain the NetChk Compliance 3.0 hotfix:

viewtopic.php?t=5707

Shut down NetChk Compliance, back up your NetChk Compliance database and then run the hotfix installation package on the console machine. Once the hotfix is applied, open NetChk Compliance and ensure that the Build number EQUALS Build 301. If the hotfix is applied, close NetChk Compliance on the console machine and load the NetChk Configure 4 installation package onto the console machine. Click the installation package and follow the installation steps.