SafeGuard Enterprise: How to update to SafeGuard Enterprise 5.50

---

DSchwartzberg wrote:

Hi ssij,

While it looks like you are going down the correct path, I have a feeling a small detail might be overlooked. According to the Release Notes (RN) found with the installation software named readsgn_5_eng.html, section 5.8 explains the steps to upgrade SGN CP 5.35 and higher to SGN 5.50. Here's the pasting from the RN:

SGN ConfigurationProtection Module can’’’’t be updated to SGN 5.50 directly due to security constraints. In order to get the new version of the ConfigurationProtection Module installed properly the existing version has to be removed beforehand.

The approved update procedure is the following:
     Step 1: update SGN (do not reboot afterwards)
     Step 2: remove old CP client (SGN_CP_PortProtectorClient.msi)
     Step 3: install new CP client (SGN_CP_Client.msi)

The existing <Client Config.msi> you created for your location does not need to be removed and reinstalled. The error about the Client Configuration file is correct, but as you pointed out, it's the ClientConfig.scc and not the .msi file.

Also, this is in the RN "On updating the Configuration Protection Module the policy needs to be reapplied to be taken into account."

If you are stil having trouble, try removing CP (SGN_CP_Client.msi (assuming you already tried to upgrade to 5.50 otherwise use SGN_CP_PortProtectorClient.msi for 5.40) using the SGNClient.msi first, do not reboot, remove the CP client, reboot, then install the SGNClient.msi to include the CP component, do not reboot, then install the new CP client (SGN_CP_Client.msi).

---

David,

Your last suggestion (removing the CP component from the SGNClient.msi file and reinstalling it) seemed to work for this one machine, but it makes it difficult to script an install, and doesn't answer the question as to why the approved update procedure is failing consistently on my machines.

My best guess is that when the SGNClient is upgraded, the ClientConfig.scc is either re-created or remains as-is, but by removing the v5.40 CP Client in step two, that file is also removed by the installer.  Thus, re-installing the CP component in the SGNClient.msi re-creates the file and allow the v5.50 CP client to properly install.

If my guess is correct, removing the v5.40 CP Client BEFORE upgrading the SGNClient to v5.50 might solve this problem, but the CP Client doesn't seem to like that (asks for a uninstallation password).  Do you know of a way of getting around this?

I guess it would also be possible to copy the ClientConfig.scc file to a temporary location before uninstalling the v5.40 CP Client and copy it back after the uninstall is complete, but will that cause any other strange problems (with policies being applied, etc)?

---

DSchwartzberg wrote:

Hi ssij,

While it looks like you are going down the correct path, I have a feeling a small detail might be overlooked. According to the Release Notes (RN) found with the installation software named readsgn_5_eng.html, section 5.8 explains the steps to upgrade SGN CP 5.35 and higher to SGN 5.50. Here's the pasting from the RN:

SGN ConfigurationProtection Module can’’’’t be updated to SGN 5.50 directly due to security constraints. In order to get the new version of the ConfigurationProtection Module installed properly the existing version has to be removed beforehand.

The approved update procedure is the following:
     Step 1: update SGN (do not reboot afterwards)
     Step 2: remove old CP client (SGN_CP_PortProtectorClient.msi)
     Step 3: install new CP client (SGN_CP_Client.msi)

The existing <Client Config.msi> you created for your location does not need to be removed and reinstalled. The error about the Client Configuration file is correct, but as you pointed out, it's the ClientConfig.scc and not the .msi file.

Also, this is in the RN "On updating the Configuration Protection Module the policy needs to be reapplied to be taken into account."

If you are stil having trouble, try removing CP (SGN_CP_Client.msi (assuming you already tried to upgrade to 5.50 otherwise use SGN_CP_PortProtectorClient.msi for 5.40) using the SGNClient.msi first, do not reboot, remove the CP client, reboot, then install the SGNClient.msi to include the CP component, do not reboot, then install the new CP client (SGN_CP_Client.msi).

---

David,

Your last suggestion (removing the CP component from the SGNClient.msi file and reinstalling it) seemed to work for this one machine, but it makes it difficult to script an install, and doesn't answer the question as to why the approved update procedure is failing consistently on my machines.

My best guess is that when the SGNClient is upgraded, the ClientConfig.scc is either re-created or remains as-is, but by removing the v5.40 CP Client in step two, that file is also removed by the installer.  Thus, re-installing the CP component in the SGNClient.msi re-creates the file and allow the v5.50 CP client to properly install.

If my guess is correct, removing the v5.40 CP Client BEFORE upgrading the SGNClient to v5.50 might solve this problem, but the CP Client doesn't seem to like that (asks for a uninstallation password).  Do you know of a way of getting around this?

I guess it would also be possible to copy the ClientConfig.scc file to a temporary location before uninstalling the v5.40 CP Client and copy it back after the uninstall is complete, but will that cause any other strange problems (with policies being applied, etc)?