Moving Good Messaging Server and Good Administration Center Server to a New Host

This following procedure allows you to move Good Administration Center (GAC) Server and Good Messaging Server to a new host machine without disconnecting all provisioned handheld.

This procedure assumes:

• You want to move both Good Administration Center Server and Good Messaging Server to a new host machine.
• You have the standard default installation of Good Administration Center Server and Good Messaging Server Service on a single Windows server. This includes SQL Server express which is installed with Good Messaging. If your installation is different, contact Good Technology Support for advanced set up questions.

Important: Moving Good Administration Center Server and Good Messaging Server to a new host machine that has a different host name than the original host is not recommended in Good Messaging Server version 6.x and higher. The new host machine must preferably have the same host name and fully qualified domain name (FQDN) as the original host machine. To achieve this, your IT administrator may have to completely isolate the old machine from the network before bringing up the new machine to avoid network conflicts.

Follow these general steps to move Good Administration Center Server and Good Messaging Server to a new host:

1. Start the new machine with the same host name as of the old host machine.
2. Move Good Administration Center Server to the new machine. This includes moving the SQL database.
3. Move Good Messaging Server to the new machine.
4. Start up both services on the new host machine and do a check.

Preparing to Move Good Administration Center Server

To prepare to move Good Administration Center Server:

1. On the original host machine, stop the Good Messaging Server service and Good Administration Center Server service. After the services stop, set both services to Disabled.
2. Make a copy of the SQL database files by performing these steps:
1. Open the SQL Management Studio: Start > Programs > Microsoft SQL Server 2005 > SQL Server Management Studio Express.

Note: SQL Management Studio Express is installed during initial set up of Good Administration Center Server. If you did not install SQL Management Studio Express, you must install SQL Management Studio Express (2005) now or use SQL Management Studio Express already available in your organization to connect to the database.

2. Log in by selecting <YOUR_MACHINE>\GAC as the Server Name and choosing Authentication as Windows Authentication.
3. Right click on the database and then choose Tasks > Detach.



4. Click OK on the next screen.



5. Complete the procedure.
3. Copy gacdb.mdf and gacdb_log.LDF from C:\Program Files\Good Technology\database\MSSQL.1\MSSQL\Data to a safe location for future use. These files will be attached again when the new host machine is setup.
4. If there are any custom settings made as a part of Good Administration Center Server configuration, copy the following files and keep it for future use:
• Copy config.props from C:\Program Files\Good Technology\GAC Server\original
• Copy config.props, config.props.bak, logdriver and spring.cfg.xml from C:\Program Files\Good Technology\GAC Server
5. Open the registry and write down the License Key, Serial Number Instance Name, and Database name for the Good Administration Center Server. These parameters are located in the registry under:

HKEY_LOCAL_MACHINE\SOFTWARE\Good Technology\EMF Server

For example, the following screen shot assumes a default installation and your system may be different:



6. Uninstall the Good Administration Center Server. (See "Uninstalling Good Administration Center Server")

Preparing to Move Good Messaging Server

To prepare to move Good Messaging Server:

1. On the original host machine, open the registry and write down the Server Name, Serial Number, License Key, Mailbox Name, Cache Directory, Windows logged-on user name (domain\username), and Exchange Server Name where the Good Messaging mailbox resides. (The Good Messaging Server name is usually the same as the computer name.)

These parameters are located in the registry under:

HKEY_LOCAL_MACHINE/SOFTWARE/GoodTechnology/GoodLink Install Parameters/

For example, the following screen shot assumes a default installation and your system may be different:



2. Uninstall Good Messaging Server by choosing Custom Uninstall and selecting the Retain Users option. (See "Uninstalling Good Messaging Server")





3. Complete the uninstallation of Good Messaging Server.
4. Copy the complete Cache folder to a new location for future use. The default location is:

C:\Program Files\Good Technology\Good Messaging Server\cache

5. Shutdown the original host and completely isolate it from the network. We recommend disconnecting the network cable.

Installing Good Administration Center Server on the New Host

To install Good Administration Center Server on the new host:

1. Start the new host machine using the same host name of the original machine.

Note: Before starting the new host machine, be sure to shutdown and isolate the original machine from the network.

2. After the new host machine boots up, set the necessary account permissions and install the required pre-requisites. (See "Pre-installation" and "Installation".)
3. Install Good Administration Center Server using the same License Key, Serial Number, Database Instance Name, and Database Name as the original host.
4. Start the Good Administration Center Server service.
5. After verifying the Good Administration Center Server is running, stop the GAC Server service and set it to Disabled.
6. Follow these steps to detach the new database and attach the database copied from original host:
1. Open the SQL Management Studio: Start > Programs > Microsoft SQL Server 2005 > SQL Server Management Studio Express.
2. Log in by selecting <YOUR_MACHINE>\GAC as the Server Name and choosing Authentication as Windows Authentication.
3. Right click on the database and then choose Tasks > Detach.



4. Click OK on the next screen.



5. Complete the procedure.
6. Copy gacdb.mdf and gacdb_log.LDF from the original host to the following folder on the new host, overwriting the existing files:

C:\Program Files\Good Technology\database\MSSQL.1\MSSQL\Data

7. In SQL Management Studio, right click on the database and then choose Tasks > Attach.



8. Navigate to the GACdb.mdf and GACDB.LDF files and click Add.



The database is now attached to SQL server.

7. Set the GAC Server service to Automatic and start the GAC Server service.
8. Access the GAC Console make sure it is working properly:

http://<servername>:8080

This procedure is now complete. The Good Administration Center Server is now running on the new host.

Installing Good Messaging Server on the New Host

To install Good Messaging Server on the new host:

1. Log in to the new host machine using the Windows logged-on user name (domain\username) for the Good Messaging Server. You wrote this down for the original host machine. (See "Preparing to Move Good Messaging Server")
2. Copy the contents of the cache folder that you saved from the original host machine to the same folder location on the new host machine.

Important: The cache folder must be located in the same path as on the original host machine. For example:

C:\Program Files\Good Technology\Good Messaging Server\cache\UMASERVER1



3. After copying the files, delete the "dbfiles.lck" file from the cache folder.

Important: Do not delete any other files.

4. Install Good Messaging Server using the same License Key, Serial Number and host name you wrote down for the original host. (See "Pre-installation" and "Installation".)
5. When the Installation program prompts you for the cache folder location, specify the location on the new host machine where you copied the cache files.
6. After you complete the installation, start Good Messaging Server.
7. After a few minutes, verify that the Good Messaging Server is operating.

Note: After this procedure, the GAC Console may indicate that Good Messaging Server is disconnected. After approximately 15 minutes, the status should change to Connected.