How to: Upgrading SafeGuard Enterprise to version 6.10 when Microsoft Windows Server Operating System and Microsoft SQL Server versions are no longer supported (e.g. Windows Server 2003 and SQL Server 2005).

  • Article ID: 120706
  • Rating:
  • 3 customers rated this article 6.0 out of 6
  • Updated: 04 Apr 2014

The current SafeGuard Enterprise 6.00.1 environment is configured in a distributed way (SafeGuard Enterprise Server and Database running on different machines) and needs to be upgraded to SafeGuard Enterprise 6.10. The SafeGuard Enterprise Server is installed on Microsoft Windows Server 2003 and the SafeGuard Enterprise Database is hosted on a Microsoft SQL Server 2005 instance.

As SafeGuard Enterprise 6.10 no longer supports Microsoft Windows Server 2003 for the SafeGuard Enterprise Server and Microsoft SQL Server 2005 for the SafeGuard Enterprise Database, the SafeGuard Enterprise Server machine should be replaced with a new Microsoft Windows Server 2008 R2 / 2012 R2 machine. In addition, the Microsoft SQL Server 2005 instance should be upgraded to a Microsoft SQL Server 2008 / 2012 installation.

The Knowledge Base Article describes the necessary steps to upgrade the environment to SafeGuard Enterprise 6.10.

Frequently Asked Questions:


First seen in


SafeGuard Management Center / Local Policy Editor 6.10.0
SafeGuard Enterprise Server 6.10.0

Operating systems
Windows Server 2008 SP1, SP2
Windows Server 2008 R2 SP1, SP2
Windows Server 2012
Windows Server 2012 R2

What To Do

Before the SafeGuard Environment can be upgraded to version 6.10, the Microsoft SQL Server hosting the SafeGuard Enterprise Database has to be upgraded to Microsoft SQL Server 2008 (R2) / 2012. In addition, all Microsoft Windows Server 2003 installations running SafeGuard Enterprise Server(s) have to be replaced with Microsoft Windows Server 2008 (R2) / 2012 machines.

 

SafeGuard Database (Upgrading / Replacing the Microsoft Windows SQL Server 2005)

The following steps show the SafeGuard relevant configurations that have to be performed when upgrading the Microsoft SQL Server installation where applicable or when replacing the SQL Server machine with a new installation.

 

Upgrading the Microsoft SQL Server 2005 installation:

If applicable, perform an upgrade of the Microsoft SQL Server 2005 installation to Microsoft SQL Server 2008 (R2) or Microsoft SQL Server 2012. For details, review the following articles about the upgrade process of Microsoft SQL Server, available at Microsoft TechNet:

After upgrading the Microsoft SQL Server installation, make sure that the existing SafeGuard Enterprise Servers do fulfill the requirements for SafeGuard Enterprise 6.10.

If the existing SafeGuard Enterprise Servers do not fulfill the requirements for SafeGuard Enterprise 6.10, see "SafeGuard Enterprise Server (replacing the Microsoft Windows Server 2003)" below.

If the currently running SafeGuard Enterprise Servers fulfill the requirements for SafeGuard Enterprise 6.10, continue with the upgrade to SafeGuard Enterprise 6.10.

Refer to the SafeGuard Enterprise 6.10 upgrade guide for a detailed step-by-step description.

 

Replacing the Microsoft SQL Server 2005 installation with a new installation on a different machine:

If the Microsoft SQL Server has to be installed on a new machine (e.g. because the Microsoft Windows Server Operating System version does not support the new Microsoft SQL Server version), the SafeGuard Enterprise Database has to be backed up and restored to the new Microsoft SQL Server.

Please note: If the new SQL Server machine has a different hostname than the original SQL Server, the SafeGuard Enterprise Management Center configurations have to updated (initial Management Center wizard will open up automatically upon first start) and the configuration packages for the SafeGuard Enterprise Servers have to be re-created and re-installed on the existing SafeGuard Enterprise Server(s)!

To begin, install any Microsoft Windows Server Operation System and Microsoft SQL Server version supported by SafeGuard Enterprise 6.10. After the installation, follow the steps as described in the SafeGuard 6.10 Installation Best Practice Guide (Chapter 2).
Instead of creating a new SafeGuard Database in "Chapter 2.3", skip "Chapter 2.3", restore the original SafeGuard Database that was previously backed up using the Microsoft SQL Server Management Studio and continue the configuration until the end of "Chapter 2.5" to setup SQL permissions accordingly.

If required, refer to the Microsoft TechNet documentation that explains how to restore a full database backup:

 

Should the hostname of the new Microsoft SQL Server be different, SafeGuard Management Center configuration(s) and SafeGuard Enterprise Servers have to be re-configured:

Updating the SafeGuard Management Center configurations

To update the SafeGuard Enterprise Management Center configuration, start the Management Center. Instead of the expected Security Officer login mask, a popup message appears stating that "The connection to the database could not be established (..)" - which is expected as the hostname of the Microsoft SQL Server that holds the SafeGuard Database has changed. Click "Yes" to start the Configuration Wizard.

On the "Database Server Connection" window, replace the old hostname for the Microsoft SQL Server with the new hostname of the Microsoft SQL Server that holds the SafeGuard Database. Select an authentication method and click "Next"

On the "Database Setting" window, choose "Select an available database" and select the previously restored SafeGuard Enterprise Database (i.e. "SafeGuard") and click "Next".

On the "Security Officer Data" window, select the Security Officer that should be used to authenticate against the SafeGuard Database. Click next to complete the configuration and start the SafeGuard Management Center.

 

Updating the SafeGuard Enterprise Server(s) with new Server Configuration packages.

To update the SafeGuard Enterprise Server(s) with the new SafeGuard Database location information, the Server Configuration package has to be modified and re-installed.

To do this, open the SafeGuard Enterprise Management Center and log on with a Security Officer account. Select "Tools | Configuration Package Tool ...". On the "Servers" tab, all previously configured servers are shown.

Option A: The existing SafeGuard Enterprise Server(s) do fulfill the requirements for SafeGuard Enterprise 6.10 and should be reconfigured / upgraded to 6.10 afterwards.

Select a server that should be changed and click into the "Database connection"-area to open the "Database Connection window". Replace the old hostname for the Microsoft SQL Server with the new hostname of the Microsoft SQL Server that hosts the SafeGuard Database. Click on "OK" to confirm the changes.

Switch to the "Server packages" tab and select the SafeGuard Enterprise Server that has just been updated. Click on "Create Configuration Package" to create the new SafeGuard Enterprise Server configuration package that contains the SQL Server connection information changes that were just performed.

Hint: It is recommended to delete old Server configuration *.msi packages as they contain outdated information that is no longer required.

Copy the SafeGuard Enterprise Server Configuration Package to the SafeGuard Enterprise Server and install the package. There is no need to uninstall the old Server configuration package before installing the new one.

The package does not need a reboot but restarting the IIS after the installation has completed is recommended. 

The SafeGuard Enterprise Server should now be able to communicate with the new Microsoft SQL Server hosting the SafeGuard Database. To verify the results, please run the "Invoke Test" (SafeGuard 6.10 Installation Best Practice Guide - Chapter 4.4 Running the invoke test) on the SafeGuard Enterprise Server.

Repeat the steps described in "Updating the SafeGuard Enterprise Server(s) with new Server Configuration packages" for all SafeGuard Enterprise servers.

Now that the Microsoft SQL Server has been upgraded to version 2008 / 2012 the SafeGuard Database can be upgraded to version 6.10. As the Microsoft Windows Servers also fulfill the requirements for SafeGuard Enterprise Server 6.10, the actual upgrade to SafeGuard Enterprise 6.10 can now be performed. Refer to the SafeGuard Enterprise 6.10 upgrade guide for a detailed step-by-step description.

 

Option B: The existing SafeGuard Enterprise Server(s) do not fulfill the requirements for SafeGuard Enterprise 6.10 and will be retired / replaced with new SafeGuard Enterprise 6.10 installations.

Select the SafeGuard Enterprise Server(s) that will be retired and click on "Remove", to remove the SafeGuard Enterprise Server configuration from the Database.

Follow the steps below ("SafeGuard Enterprise Server (replacing the Microsoft Windows Server 2003)") to replace the old SafeGuard Enterprise Servers with new installations.

 

SafeGuard Enterprise Server (replacing the Microsoft Windows Server 2003)

The following steps show the SafeGuard relevant configurations that have to be performed when replacing the Microsoft Windows Server 2003 installation with new machines running Microsoft Windows Server 2008 (R2) / 2012.

Installation and configuration of SafeGuard Enterprise Server version 6.10 and IIS 7, 7.5 on Windows Server 2008 or IIS 8 on Windows Server 2012

The basic installation and configuration of the SafeGuard Enterprise Server for version 6.10 and IIS 7 / 7.5 on Microsoft Windows Server 2008/2008 R2 and IIS 8 on Microsoft Windows Server 2012/2012 R2 is described in the SafeGuard Enterprise Installation Guide for version 6.1 - "Chapter 3 - Setting up SafeGuard Enterprise Server".

Alternatively, "SafeGuard 6.10 Installation Best Practice Guide - "Chapter 1 - Installing the SafeGuard Enterprise Server" describes the required steps to setup the SafeGuard Enterprise Server for version 6.10 and IIS 8 on Microsoft Windows Server 2012/2012 R2.

Registering the SafeGuard Enterprise Server and Installing the configuration package

To complete the installation of the SafeGuard Enterprise Server, perform the steps described in "SafeGuard 6.10 Installation Best Practice Guide - "Chapter 4 - Installing the SafeGuard Enterprise Server configuration package"


Please note: If the new SafeGuard Enterprise Server running on Microsoft Windows Server 2008 / 2012 has a different hostname than the old SafeGuard Enterprise Server running on Windows Server 2003 then new SafeGuard Client Configuration packages need to be created with the new SafeGuard Server(s) specified in the packages. The new client configuration packages have to be installed on all SafeGuard Enterprise Clients!

Please see "SafeGuard 6.10 Installation Best Practice Guide - "Chapter 6.5 - Creating the SafeGuard Enterprise Client configuration package" for details.

 
If you need more information or guidance, then please contact technical support.

Rate this article

Very poor Excellent

Comments