In order for the GroupWise Server Migration Utility to run successfully, the following prerequisites must be met:
A share on the Windows server provides read/write access to the domain or post office that you are migrating. If you are not on the server where the share resides, a drive is mapped to the share.
In order to provide access to the domain or post office data on the Windows server, you need to set up a share on that server that includes the domain or post office folder. The share needs to provide read/write access to the domain or post office folder for the user running the Server Migration Utility. This enables the Server Migration Utility to copy the GroupWise data from the Windows server to the destination Linux server and to access existing agent startup files so that existing configuration information can be transferred to Linux.
If you run the Server Migration Utility on a Windows workstation, rather than on the Windows server where the domain or post office is located, you need to map a drive to the Windows server so that the Server Migration Utility can access the domain and post office data.
The samba-client package is installed on the Linux server.
The samba-client package provides the mount command so that the Server Migration Utility can create a Samba file system mount of the source Windows server to the destination Linux server.
The Samba server is running on the Linux server and you have mapped a drive to the Samba share from Windows.
The Samba server enables the Server Migration Utility to create a Samba file system mount of the source Window server to the destination Linux server.
At the Linux server, use the following command to determine if the Samba server is running:
ps -eaf | grep samba
If you see both the smbd and nmbd daemons running, the Samba server is running.
Use your typical method of drive mapping to map a drive from the Windows machine where you plan to run the Server Migration Utility to the Linux server. Use the following format to specify the location on Linux:
\\Linux_hostname\Samba_sharename\path
This provides access between the Windows machine and the destination Linux server.
If the Server Migration Utility is unable to establish a Samba mount, it tries a CIFS mount instead. If the CIFS mount also fails, ensure that the cifs-mount package is installed.
The GroupWise Linux downloaded software image is available. It must be the same GroupWise version that is installed on the source server.
To prepare for the server migration, the Server Migration Utility needs to copy the GroupWise agent and utility RPMs from an existing software location to a temporary location on the destination Linux server. You must use the version of GroupWise software that matches the version of GroupWise that is already installed. You cannot use the GroupWise Server Migration Utility to upgrade post offices and domains from an earlier version of GroupWise during the server migration process
A GroupWise software distribution directory on a Windows server does not contain GroupWise Linux software unless you have placed it there from a GroupWise for Linux software image or software distribution directory.
The Novell Client and ConsoleOne are installed where you are running the utility.
If you are running the Server Migration Utility at the workstation where you typically administer GroupWise, these programs are already available. If you are running the utility on the Windows server, they might not be available. You can obtain them from:
Your GroupWise Installation software (recommended)
The ssh daemon is running on the Linux server with ssh enabled for the root user.
The ssh daemon is a secure shell program that allows the Server Migration Utility to log in to the destination Linux server as root and execute programs there. At the Linux server, use the following command to verify that the ssh daemon is running:
ps -eaf | grep sshd
If it is not running, use the following command to start it:
/etc/init.d/sshd start
You must also ensure that processes from outside the server’s firewall can communicate with the ssh daemon. In YaST, click Security and Users > Firewall. Click Next until you reach the list of available services on the server. Ensure that Secure Shell (ssh) is selected, then click Next until you reach the end of the firewall configuration process. Click Continue to save your settings and restart the firewall.