Creating a New Domain on Windows to Relocate a Gateway

Wikis > Caledonia Private Wiki > Moving GroupWise > Moving GroupWise to or on Windows > Creating a New Domain on Windows to Relocate a Gateway

In earlier chapters we moved a domain and gateway to a new Windows server. There will be times when you wish to relocate a GWIA or a WebAccess Agent to a new Windows server, but the owning domain cannot be moved. In this case, rather than actually moving your gateways, you will create a new domain on your new Windows server and install a new GWIA or WebAccess Agent on that server.

Here we will create the domain on our new Windows server. Afterwards, we will go back to either Chapter 3, to the section entitled “Install the GWIA software and configure the GWIA” or to the section entitled “Install the WebAccess software and configure the WebAccess Agent” in “Moving WebAccess – Windows” to complete the installation of the agent of your choice.

As we discussed at the beginning of this section, you should never separate a GWIA or a WebAccess Agent from its owning domain. Here are a couple of reasons why you might create a new domain on your Windows server, rather than migrating an existing one:

  • You wish to put a GWIA or WebAccess on your new Windows server, but your current gateways are owned by the only domain in your system. This is a perfect time to do two things: separate your GWIA from your primary domain; and have a second domain as an online “backup” of your system (you can recreate your primary domain from a secondary domain in case of catastrophic failure and we always recommend at least two domains in a GroupWise system).
  • You already have your gateways in a separate domain from your post offices, but you only want to move one gateway (GWIA or WebAccess Agent), and they both belong to the same domain.

In either of those cases creating a new domain on the new Windows server makes perfect sense. We will need to attach to the primary domain in order to create a new domain.

Attach to both the server that houses your primary domain, and the new Windows server from your workstation, or directly from the Windows server.

If you are creating a new domain for either a GWIA or a WebAccess Agent, follow these instructions, and then move on to the section for “Install the GWIA software and configure the GWIA” or “Install the WebAccess software and configure the WebAccess Agent” in the previous chapters.

The steps we will take to create our new domain are as follows:

  • Load ConsoleOne and connect to the primary domain.
  • Create a new Secondary Domain on Windows
  • Configure the MTA on Windows.
  • Load the MTA.
  • Verify that the MTAs for the primary domain and the new secondary domain are communicating with each other.

 

 

So, let’s see how this all works.

 

Create Your New Domain in ConsoleOne

It’s time to create your new domain. First we need to open ConsoleOne.

    1. With ConsoleOne open, right-click on the GroupWise System globe and choose New>Domain. Figure 6-1 will appear. Fill in the information for your new domain.
      1. Figurel-d18.tiffCreate GroupWise Domain

  • Note that in our figure we have chosen to configure our link. So we will be presented with some additional windows that assist us in this. On the MTA Link screen, choose TCP/IP and click Next.
    1. Now put in the IP address and port information for your MTA. We recommend that you keep the default ports for the MTA and HTTP monitor unless you are using these ports for something else (Figure 6-2).
      1. MTA NetWork Address screenFigurel-d19.tiff

 

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 6-3.

    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 6-4.
    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.
  • 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 6-5.
      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 6-5 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 6-7
      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).

Now that we’ve covered just about every way imaginable to get a domain to Windows, we’ll move on to moving your post office to a new Windows Server.