Moving a GWIA – Windows

In this chapter, we are moving a GWIA to a new Windows server. Since we never run a GWIA on a server remote from its owning domain, that means we also must move our domain to the new Windows server. It’s also possible that this domain owns other gateways like a WebAccess Agent. If this is the case, and if you plan on moving the WebAccess Agent to the new Windows server as well, we can do this all at one time. However, if you only wanted to move the GWIA to the new Windows server, and leave the WebAccess Agent on your source server, you would essentially not be moving a domain to the new Windows server at all. Rather, you would be creating a new domain and GWIA on the new Windows server. If this is your situation, stop now and go to the Chapter entitled “Creating a New Domain on NetWare to Relocate a Gateway”.

The steps we will take are as follows

  • Unload the existing Message Transfer Agent (MTA) for this domain. We will need exclusive access to the domain database, so we must also unload the GWIA and any other gateways that belong to this domain.
  • Rename the domain directory to avoid any accidental access while we are relocating the domain.
  • Copy the domain directory structure from it’s current location to the new Windows server.
  • Load ConsoleOne and edit the domain location, agent address and link information if necessary.
  • Configure the MTA on you new Windows server.
  • Load the MTA with a GUI console for the relocated domain for testing
  • Verify that the MTA is communicating with any post offices it owns, and any other domains for which it has direct links.
  • Install the GWIA software and configure the GWIA
  • Load the GWIA.

 

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:

rcgrpwise status

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.

Unload Your GWIA and Any Other Gateways

Like the MTA, your GWIA and any other gateways that are running under this domain must be unloaded. The instructions are the same as for the MTA. Press F7 where appropriate to unload the gateways, shut down the services on Windows, or stop the daemons on Linux. Make sure all gateways have been shut down before you proceed.

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: Make sure that you prune out unneeded log files, files in the problem directories, etc. The gwprob directory under the GWIA is especially prone to a lot of unneeded files. We’ve seen YEARS worth of files in this directory during health checks. Clean out all of the junk, and the copy of your domain will fly!

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.

  1. Open ConsoleOne to edit the properties of the domain you have moved.
  2. Right-click on the GroupWise domain you have moved to your new Windows server, and choose Properties.
  3. Change the location of the domain to the new location’s UNC path – you can browse for this if necessary.
  4. Now, in the dropdown list that shows “Users”, change the setting to “Message Transfer Agents.”
  5. Find the MTA for your domain, right-click and choose Properties.
  6. On the first screen, change the Platform to Windows if necessary.
  7. 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.
  8. 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.
  9. On the GroupWise tab, change to the Message Log Settings tab. As above, delete any custom location you may have defined there.
  10. 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.

 

 

  1. 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 4-1.

    1. install1.tiffThe main installation screen

  • Click on Install GroupWise System.
  • Click Yes on the next screen to accept the license agreement.
    1. Click Next on the next screen to do a standard install. You will see the window in Figure 4-2.
    2. Install GroupWise AgentsFigureN2.tiff

 

  • “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.
    1. 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.

    1. After you choose the options on this screen you will click next and be presented with the window in Figure 4-3.
      1. configure1.tiffConfiguring the GroupWise Agents

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 4-3 we can enter the information for our domain.

  1. configure2.tifAdding 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.

  1. Next you will be asked for the Windows user for the Service (assuming you are installing the agents as services.
  2. Next you will be presented with a summary screen showing your choices for the install, and the installation will proceed.
  3. 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.

    1. Back in ConsoleOne right-click on the domain and choose GroupWise Utilities|Link Configuration.
    2. From the menu choose View|Post Office Links.
    3. 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 4-5
      1. Figurel-d11.tiffChange the Link Configuration

  • 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).

 

Install the GWIA software and configure the GWIA

Now that the MTA for this domain is up and running in testing mode, we will continue to install the GWIA software and configure the GWIA on this server.

In the root of the location of your GroupWise software, you will see the setup.exe program that will be used for this upgrade. Our installation here is using GroupWise 8.0. If you are installing software prior to GroupWise 8.0, you should go to the Internet/GWIA directory of your software distribution and run “install.exe /copyonly” to avoid having to answer all of the GWIA questions again. The you can skip to step 6 below.

When you run this 8.0 intallation program, program, you see the Window in Figure 4-6.

    1. FigureW-3.tiffThe main installation screen

  • Click on Install GroupWise System.
  • Click Yes on the next screen to accept the license agreement.
  • “Install Individual Components”.
  • Choose GroupWise Internet Agents as an option to install.
  • Click the box that says “Install the Software Files but do not configure the Internet Agent”. This will avoid many questions that we do not need to answer in this move of the GWIA!
  • 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.
  • When prompted, enter the path to your domain, and the name of the directory for your GWIA.
  • 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, do not launch the agent yet. We need to do a few things.
  1. Copy the gwia.cfg from your source server to both the\domain\wpgate\gwia directory, and the location where you installed your GWIA files, as determined in Step 7 above.Edit the gwia.cfg and change the /home and /dhome directory to point to the location of the domain on the new server.
  2. If you have special Access Control Rules defined, these are located in the gwac.db file. If you have moved your GWIA to this server, then these rules will have moved with you. If you are returning to this section from the Chapter on”Creating a New Domain on Windows to Relocate a Gateway”, then you need to copy this gwac.db file from the original gateway directory to the gateway directory on the new server.

Load the GWIA on the Windows Server

If you installed your GWIA as a service, you load it by going to the Services panel, right-clicking on the GWIA service, and choosing “Start”. If you did not choose to load the GWIA as a service, there will be an icon for the application in your Programs menu.

 

A few things to remember about moving a GWIA.

  • You may need to change your MX records if the public IP address for your GWIA will change due to the move to the new server. Otherwise, you may have to change the natting at your firewall, or change the IP address that an anti-spam appliance or other GWIA front-end sends to.
  • You may need to change the firewall settings for outbound SMTP if you limit the IP addresses on your network that are allow to sent mail on port 25.
  • If your outbound IP address will change for your GWIA, you should also have your PTR (reverse dns lookup) changed to reflect this, as well as any SPF records that are maintained for your domain.

 

Your domain is moved and your MTA and GWIA are up and running. If this domain also owns a WebAccess Agent, you can jump ahead to “Install the WebAccess software and configure the WebAccess Agent” in the chapter regarding “Moving WebAccess – Windows” to install the WebAccess Agent software and configure your WebAccess agent.

 

Important Information If You Create a New GWIA

If you came to this section from the chapter on “Creating a New Domain on Windows to Relocate a Gateway”, there are a few things you should check about your GWIA prior to creating a new one.

  • If your current GWIA relies heavily on gateway aliases and you decide to create a new GWIA rather than moving the current one, you will need to be careful when you create the new GWIA to ensure that all of your gateway aliases continue to work. If you are on GroupWise 7.0 or GroupWise 8.0, we strongly recommend that you get rid of your gateway aliases. The best way to do this is to use the Gateway Alias Migration tool in ConsoleOne. This is new with GroupWise 7.0, and while it is conceivable that you are moving your GroupWise 6.5 system to Linux, we sincerely hope that you are upgrading to at least GroupWise 7.0 (even better 8.0) before you do your move to NetWare! Changing the Gateway Alias Type for the new GWIA to match the old GWIA should allow your existing Gateway Aliases continue to work.
  • Another “legacy” option for the GWIA that can cause difficulties when creating a new GWIA is that some older versions of GroupWise allowed administrators to treat the GWIA like a post office, and create “external system users” under the gateway. If such a situation exists in your organization, you would need to convert those users to users under an external foreign domain before you move the GWIA. Otherwise the users would not be accessible. Information on this is found on the Novell documentation site at http://www.novell.com/documentation/gw65/gw65_admin/data/bsy1t7v.html. There is, of course, similar information in the documentation for GroupWise 7 and GroupWise 8.