If you need to move your primary domain to another server, you need to have the GroupWise software installed and configured on the new server (with a different DNS name and IP address) before you make it the primary domain server. In the steps below, the old primary domain server is called gw_old and the new primary domain server is called gw_new. To move the primary domain to the new server:
Copy the domain folder from the old primary domain server (gw_old) to the new primary domain server (gw_new).
Next, modify the gw_old MTA and change the IP address to the gw_new server. You need to launch a detached version of the GroupWise Admin Console to do this. Launch the gwadmin service on gw_new in detached mode by running the following command:
/opt/novell/groupwise/admin/gwadminservice.sh -detached -home <path to gw_old domain folder that was copied over to gw_new server> -ip <gw_new ip address> -adminPort <specify a temporary admin console port>
This command starts a JAVA based service within the command line/terminal. Wait a minute or so for the service to start up, and then open the GroupWise Admin Console for gw_new using the temporary port and change the IP address for the gw_old MTA to the gw_ser server and regenerate the TLS certificate for the MTA.
On the gw_new server, generate new GroupWise system certificates by running the following command:
gwadminutil ca -d <path to gw_old domain folder that was copied over to gw_new server> -g -f
This creates a new system GUID directory on the gw_new server with the system certificates in the GroupWise certficates directory (/opt/novell/groupwise/certificates on Linux or C:\Program Data\Novell\GroupWise\gwadmin\certificates\<GUID> on Windows).
IMPORTANT:Do not copy the old system GUID folder from gw_old to gw_new. It contains server hostname information that can cause problems if copied to the new primary domain server.
Terminate the JAVA gwadmin service in the command line/terminal by keying Ctrl+C.
At this point, you have a new system CA certificate and a new certificate and key file for the primary domain MTA.
Next you need to generate a new gwha.conf file on the gw_new server by running the following command:
gwsc -i <path to the gw_old domain folder that was copied over to the gw_new server>
This command creates a new gwha.conf file with the entry for the primary domain. This means you can now run the rcgrpwise start script to start the gwadmin service and MTA with their new certificates.
Open the GroupWise Admin Console and change the IP and TLS settings for any other agents that were on the gw_old server. If you are moving a POA to the gw_new server, copy the PO folder from the gw_old server to the gw_new server. Run the corresponding command from the list below to create a new start configuration file for any agents where you changed the IP address and TLS settings:
MTA: gwsc -i <path to the gw_old domain folder that was copied over to the gw_new server>
GWIA: gwsc -i <path to the gw_old domain folder that was copied over to the gw_new server>/wpgate/gwia
POA: gwsc -i <path to the gw_old post office folder that was copied over to the gw_new server>
DVA: gwdc -i dva
You can now use rcgrpwise start to start all of the moved agents on the gw_new server.
Because you generated a new CA for you primary domain server, your other GroupWise servers need to have their certificate recreated. Stop the gwadmin service on the other server and run the following command on each of the servers:
gwadminutil certinst -ca <primary_domain_ipaddr>:<admin_port> -db <secondary_domain_path> -a <gw_admin_user> -p <gw_admin_password>
NOTE:If your server is only running a POA with no domain, point to the post office folder instead of the domain folder.
Start the gwadmin service on each GroupWise server and regenerate the TLS certificates for any MTA, GWIA, and POA on the servers, restarting the agent after the new certificates have been generated.