The steps we will take are as follows:
- Decide how you are going to copy your domain information. For copying a domain to a Windows server, there really is no special software needed (although you could use DBCopy if you really wanted to). The domain directory is small, and you will copy it all in one pass, so you can use whatever method you prefer. Even Windows Explorer.
- Unload the existing Message Transfer Agent (MTA) for this domain. We will need exclusive access to the domain database, so no gateways should be loaded. This should not be an issue, because in this section we are specifically moving a domain that has no gateways. If you need to move a domain that owns gateways, please see the chapters on “Moving a GWIA – Windows” or “Moving WebAccess – Windows”.
- Rename the domain directory to avoid any accidental access while we are relocating the domain.
- Copy the domain directory structure from its current location to the new Windows server.
- Load ConsoleOne and edit the domain location, agent address and link information if necessary.
- Install and Configure the MTA on the new Windows server.
- Load the MTA for the relocated domain
- Verify that the MTA is communicating with any post offices it owns, and any other domains for which it has direct links.
So, let’s see how this all works.
Unload the MTA
First of all, go to the server where your MTA is loaded for the domain that you are moving:
- NetWare: press F7 at the agent console to unload the agent.
- Windows: if the agent is running as an Application, you can also press F7, or use the File Menu and Exit. If the agent is running as a service, you must stop the agent from the services applet.
- Linux: use rcgrpwise command. For example:
rcgrpwise stop DomainName
If you are not certain of the name that is defined for your domain in the rcgrpwise script, first run:
This will show you all agents that the rcgrpwise script controls. Find the name for your MTA and then issue the stop command for your MTA.
Also make sure that no administrators are accessing the domain database through ConsoleOne.
Copy the Files to New Windows Server
Once we are ready to move the domain directory structure to our new Windows server, we will rename the domain directory to avoid any accidental access by administrators using ConsoleOne, NWADMIN, etc. We will copy, not move, all of the files. If needed, you could simply rename your domain directory back to its original name and load your MTA back up on the source server.
Most people will simply connect from a Windows workstation to both the source server and the new Windows server, and then copy the data from the source server to the new Windows location. The domain directory is rarely very large (unless you have a lot of logs saved there), and should copy very quickly.
NOTE: It’s a good idea to look through your domain directory structure for old log files, files in the problem directories, etc. to clean up prior to copying the directory structure. This will ensure that you don’t needless copy unneeded information to the new server.
Edit Important information in ConsoleOne
Now that your domain directory has been moved to the new Windows location, we need to edit the location of the domain directory and fix some information in the agent’s network address configuration.
- Open ConsoleOne to edit the properties of the domain you have moved.
- Right-click on the GroupWise domain you have moved to your new Windows server, and choose Properties.
- Change the location of the domain to the new location’s UNC path – you can browse for this if necessary.
- Now, in the dropdown list that shows “Users”, change the setting to “Message Transfer Agents.”
- Find the MTA for your domain, right-click and choose Properties.
- On the first screen, change the Platform to Windows if necessary.
- Now click on the triangle in the GroupWise tab and change to Network Address. Here you must change the IP address to that of the new Windows server.
- On the GroupWise tab, change to the log settings. If you have a custom path for the log settings, remove it. otherwise logging will generate an error.
- On the GroupWise tab, change to the Message Log Settings tab. As above, delete any custom location you may have defined there.
- If you use SSL to communicate between agents, you will need to regenerate your GroupWise SSL Certificate for this server and make the changes on the SSL settings tab.
You can find information on generating your SSL certificates for GroupWise at http://www.novell.com/documentation/gw8/gw8_admin/data/adqul6f.html. This information is for GroupWise 8.Similar information can be found for all versions of GroupWise, but the instructions for GroupWise 8 are the same as prior versions.
- After you have made all of the above changes, click OK to save the settings.
Installing the GroupWise Agents, and Configuring the MTA on Your New Windows Server
To install the software for your agent, you can use your GroupWise CD, Software Distribution Directory, or simply download new software from the Novell downloads site (http://download.novell.com).
In the root of the location of your GroupWise software, you will see the setup.exe program that will be used for this installation. Our installation here is using GroupWise 8.0. Your agent installation may vary slightly. When you run this program, you see the Window in Figure 3-1.
- Click on Install GroupWise System.
- Click Yes on the next screen to accept the license agreement.
- Click Next on the next screen to do a standard install. You will see the window in Figure 3-2.
- Install GroupWise Agents
- “Install Individual Components”.
- Choose GroupWise Agents as an option to install.
- At the next screen you will be prompted if you wish to install on NetWare or Windows. Of course we will choose Windows here.
- The next screen will give you the option of where to install your files on your Windows server, and options for the installation.
- Install and configure SNMP for GroupWise Agents: If SNMP is available and installed on your Windows server, you can configure your agents here for SNMP.
- Install as Windows services: Most Windows sites will configure GroupWise agents as services. Otherwise the server would need to remain logged in in order for the agents to run.
- After you choose the options on this screen you will click next and be presented with the window in Figure 3-3.
While we are looking at this screen, we should explain its usage so that it’s more easily understood the next time you encounter it. There are a few misconceptions about what is done here, and what you need to put in this location, so we will try to clear those up.
First, this screen is a template for creating new agent startup files (for example the primary.mta file), and your Windows icons or services. When we click the Add button as shown in Figure 3-3 we can enter the information for our domain.
- Adding a domain for configuration
By entering this information, we are instructing the installation routine to create us a startup file called cnc.mta with a /home switch of “d:\domains\cnc (on Windows you may need to convert this to a UNC path manual, such as \\server\d$\domains\cnc),
The installation does not validate the “name” you put here and indeed, you can name things here anything you like. For example, rather than naming our startup file “cnc.mta” as shown above, we could just as easily type “domain” in the name field, and the name of the file would instead be domain.mta. If you put in a name that has more than eight characters (for example Caledonia), the file name will be truncated to eight characters. So, if indeed we were to put “Caledonia” in the name of the domain field, we would have a startup file called “caledoni.mta”. If a “caledoni.mta” file already exists, we will now have a “caledoni.mt1” file in that directory.
- Next you will be asked for the Windows user for the Service (assuming you are installing the agents as services.
- Next you will be presented with a summary screen showing your choices for the install, and the installation will proceed.
- When the installation has completed, choose to launch your agent now, and verify that it can see the post offices that it owns.
As long as your MTA was talking IP to it’s post offices (assuming there are any), there should be no problems with communication. If, however, your domain and post office were on the same server, and you had a direct or mapped connection, you will need to edit the links for the post office.
- Back in ConsoleOne right-click on the domain and choose GroupWise Utilities|Link Configuration.
- From the menu choose View|Post Office Links.
- Double-click on the Post Office that cannot be accessed, and fix the link. It should, of course, be a TCP/IP connection, pointing to the IP address and port on the post office’s server. See Figure 3-5
- If all goes according to plan, your MTA will now show your POA open. Verify all of the links for this MTA (other post offices and domains).
From here, you can move on to moving a gateway to a Windows server, or even your post office.