If your GroupWise agents use SSL on the source server, they need a certificate file and a key file on the destination Linux server. Although you can have the Server Migration Utility copy the existing files from the source server to the Linux server, this is not a viable permanent solution, because the original certificate file and key file have the IP address and hostname of the source server, not the destination Linux server. Unless the Linux server already has its own certificate file and key file, the recommendation is to generate a new certificate file and key file for the Linux server.
If you need to create new certificate and key files, you can do it now, during the planning phase, so that the Linux server is ready for the agents to run with SSL.
Create a new certificate file and key file for the Linux server as described in the following section of the GroupWise Administration Guide for your version of GroupWise:
GroupWise 2012: Server Certificates and SSL Encryption
in Security Administration
GroupWise 8: Server Certificates and SSL Encryption
in Security Administration
GroupWise 7: Server Certificates and SSL Encryption
in Security Administration
Save the new files in a convenient location on the Windows machine where you plan to run the Server Migration Utility.
On each Agent object in ConsoleOne, remove the path information for the files on the source server and, if necessary, update the file names of the certificate file and key file.
For GroupWise 2012 instructions, see the following sections of the GroupWise 2012 Administration Guide:
For GroupWise 8 instructions, see the following sections of the GroupWise 8 Administration Guide:
For GroupWise 7 instructions, see the following sections of the GroupWise 7 Administration Guide:
|
GROUPWISE MIGRATION WORKSHEET |
|---|
|
Under Item 12: SSL Information, specify the full path names of the certificate file and key file if your GroupWise agents use SSL. You can specify either new (preferable) or old files. |