Upgrading GroupWise Domains

This chapter will cover upgrading GroupWise Domains of all kinds. Primary Domains, Secondary Domains, Domains with GWIAs, Domains with Post Offices. If there is a domain involved, this chapter will address it.

If you have multiple servers to upgrade, after this domain chapter, we will deal with issues regarding Directory Services, and then give you an overview of the new Administration Console before we jump into upgrading the rest of your system.

Most of the images in this chapter will be for the Linux installation. If there are notable differences for Windows, we will point those out.

Now that we’ve looked at the overview of the upgrade process, the first step of the actual work is to upgrade your primary domain to GroupWise 2014. If your GroupWise system is a simple one server system, or even a multi-server system managed by a single administrator, this is a pretty easy task. Your primary domain gets upgraded, and you are on your way! However, if you happen to be in a larger system where the administration is distributed across multiple departments, locations, or even continents, this becomes more complicated. The primary domain MUST upgrade first. In most larger organizations, the primary domain will be a domain that is created solely for the purpose of administration and routing. It will not own any post offices or gateways, and will reside on a separate server. This is done often in larger organizations, and if this is the case, hopefully the owner of that domain will be willing to upgrade it quickly. However, if the administrator owning the primary is not as eager as you to upgrade, then you have a few choices.

  • Wait for your primary domain to upgrade
  • Request that a domain in your control be promoted to primary temporarily until the location that owns the current primary domain decides to upgrade.

While in some organizations this is often seen as a political matter, the primary domain’s main purpose is to provide uniqueness of names throughout the system and replicate all changes in the system to other domains. It is generally not a problem to promote another secondary domain to primary if required in order to begin your upgrade.

How Does the Upgrade Work?

At the domain level, a GroupWise upgrade is really just a database conversion from one version to another. The former GroupWise domain database (version 5.0 through 2014 works the same), is RECOVERED by the administrative thread and CONVERTED to the new version. For a primary domain, this requires a few simple components and prerequisites:

  • The Message Transfer Agent software must be at GroupWise version 2014
  • The dc (dictionary files) in the domain directory must be at version 2014
  • The Primary Domain must be upgraded before any Secondary Domain can upgrade.
  • Secondary Domains must have received the notification from the Primary Domain (through administrative messages passed by the MTAs) that the Primary is at version 2014, and they Secondaries are permitted to upgrade.

The actual process is as follows: The Admin Service first makes a full copy of the wpdomain.db file in the same directory as the domain, and names it recover.ddb. Then the Admin Service also creates a file called creating.ddb in the domain directory. At the point that the creating.ddb file is fully created, the Admin Service puts an internal record lock on the primary domain’s wpdomain.db file, carves the file out from the header down, and places the information from the creating.ddb file into the wpdomain.db file.

Prior to GroupWise 2014, this really was all there was to it. There are a few new twists with GroupWise 2014, involving creating an Administration Console user and assigning Administration Server ports.

This update then triggers a message to be sent to any post offices that might be owned by the domain. If you are upgrading the Primary Domain, the message is also sent to any Secondary Domains that are in the system. This message updates the post offices and secondary domain databases with the information that the primary domain is now a GroupWise 2014 domain. Unless this message is properly delivered (MTAs are down, POAs are down, etc.), the other domains and post offices will not upgrade, even though they may be running the GroupWise 2014 software for their agents. We’ll discuss this more as we walk through this upgrade.

What About ConsoleOne?

As we’ve discussed previously, GroupWise 2014 does not use ConsoleOne for administration, and it is not recommended that you use ConsoleOne with your 2014 domains. Until your upgrade is complete, you will need to keep ConsoleOne around to do some administration of your older version domains and post offices. Since most administrative tasks in a GroupWise system are “store and forward” processes, the 2014 Administration Console can deal with tasks such as creating users, changing passwords, kicking off a GWCheck, etc. for all of the domains and post offices in the system, regardless of version. There will be times when you need access to ConsoleOne for older domains and post offices (rebuilding databases, and the like), so you will need to keep ConsoleOne with GroupWise snapins around on a workstation or two until the upgrade is complete. If you utilize GroupWise Document Management, you will want to revisit the discussion in “What about Document Management?” on page 9.

Prepare The Domain Database

We cannot overstate the importance of validating your databases prior to an upgrade. The only times we’ve seen GroupWise upgrades go very badly were when there was corruption in the domain or post office databases prior to upgrading. Due to the complications introduced with the new administration model, and the requirement that databases with versions prior to 2014 be rebuilt at the command line, some administrators will want to skip this step. Do so at your own peril.

From here on out, we will assume that you understand that the Primary Domain must be upgraded first, and references to domains in this chapter will generally be relevant for Primary or Secondary Domains. If there is something specific to a Primary Domain, we’ll let you know! In fact, in the case of preparing the Primary Domain for upgrade, you will use ConsoleOne. Once the Primary Domain has been upgraded, you will need to use new GroupWise 2014 Command Line Utilities to do any database rebuilds that may be required. Thus, if you are upgrading a domain and post office on the same server, we recommend you do the validate on both the domain and post office at the same time from ConsoleOne for simplicity’s sake.

When you are ready to continue your upgrade, we will first check the domain to make sure that it is ready to upgrade. In ConsoleOne, select the domain object and choose Tools|GroupWise Utilities|System Maintenance|Validate Database. If your database shows as valid, you can proceed. If for some reason the database does NOT validate, you should rebuild it. In order to rebuild the database you must first shut down the MTA and any gateways that attach to the domain database. Just be to safe, make a copy of the wpdomain.db file in case something unexpected were to happen during the rebuild (power outage, server room flood, etc.). If this is the Primary Domain, once the agents are shut down, return to ConsoleOne and choose Tools|GroupWise Utilities|System Maintenance, and this time choose Rebuild Database.

If you are checking a Secondary Domain, you can use ConsoleOne to check the validity of the Secondary Domain. If for some reason however, the domain database fails validation, you will need to rebuild the domain database from the new GroupWise 2014 Primary Domain server! Please see the section entitled “Command Line Utilities” on page 128 in the Chapter on “The GroupWise Administration Console”if a rebuild of a Secondary Domain is warranted.

The Domain Upgrade Overview

From this point forward, everything you’ve ever known about upgrading GroupWise has changed!!! The installation routine is different. The upgrade wizard is different. The administration is different. Onward and Upward!

Depending on your setup, you may be simply upgrading your domain during this sitting, or you may be doing more than that. If any other GroupWise components exist on the same server as your domain, you need to upgrade them now too. Let’s look at the possible scenarios.

  • Simple single server – you need to do everything. You will upgrade the Domain (which upgrades the GWIA) and Post Office, and then move to upgrading your WebAccess, etc.
  • MTA & POA on same server – the procedure will upgrade both the domain and the post office, and you’re done with this server.
  • MTA on its own server – perform the steps to upgrade the domain and verify.
  • MTA & GWIA. By default, upgrading the Domain upgrades the GWIA.

Before we go to the administration console, we’ll go over a few structural changes here:

DC Files

In the past, the dictionary (.dc) files were found in the /domain and /po directories of your installation file location. We often had to copy those files directly to the domain directory in order for an upgrade to commence. In theory this should never be required again. These files are now installed along with the GroupWise Server files, and reside in /opt/novell/groupwise/admin/data directory (c:\Program Files\Novell\GroupWise Server\admin\data on Windows). Since the GroupWise Administration Service knows where these files are now (before they literally could have been anywhere), the upgrade procedure copies the files to the domain directory automatically, and avoids the problem of having the incorrect .dc files in the directory during the upgrade attempt.

Startup Files

Also, in the past, startup files for all agents on Linux were maintained by default in the /opt/novell/groupwise/agents/share directory. On Windows they were maintained in the agent executable directories. If GroupWise was in a cluster, these were typically maintained in the domain or post office directory. When you install a new domain or post office with GroupWise 2014, the startup file will be saved in the domain or post office directory. If you are upgrading on Linux and the startup file is in /opt/novell/groupwise/agents/share, it will remain in that directory after the upgrade. On Windows the startup files will all be located in the domain or post office or gwia directories. That said, we have seen instances on Linux where the file was recreated in the domain or post office directory, and you would see two of them on the server. This can happen if the installation routine gets confused and believes there is no file in the share directory, or the paths in the original startup file are believed to be incorrect.

The downside to this is that on Linux starting agents by hand can be a bit more cumbersome. Since it was assumed that startup files were in the share directory, you could start the agents from the /opt/novell/groupwise/agents/bin directory with a simple command like:

./gwmta @domain.mta

If the startup file is not in the share directory, you will need to specify the location thusly:

./gwmta @/grpwise/domains/cnc/cnc.mta

You can move these files back to the /opt/novell/groupwise/agents/share directory if that is your preference, but you will also need to edit the paths in the gwha.conf file if you choose to do this.

Alternatively, you could also create a symlink for the file. For example, if our file was /grpwise/domains/cnc/cnc.mta, we could change to /opt/novell/groupwise/agents/bin and create a symlink as follows:

ln -s /grpwise/domains/cnc/cnc.mta cnc.mta

Then we would no longer need to type the full path to the startup file.

So, let’s get down to it.

In our last chapter, we installed the GroupWise Administration Server. This installed all agent software required for the GroupWise Agents (MTA, POA, GWIA).

Now that your agent software has been updated, we need to move on to the actual process of upgrading the domain to GroupWise 2014.

Performing the Domain Upgrade

At this point, you have installed the software required to take your domain to GroupWise 2014, but your domain has not actually upgraded. This will not happen until you access the Installation Console and choose to upgrade your system. Let’s discuss how this has changed from the methods we used in GroupWise 2012 and earlier.

For prior versions of GroupWise, the key to an upgrade was providing the primary domain with new dictionary (.dc) files, and loading the new agents up to perform the upgrade. It really was as simple as that. Barring any complications, those two steps performed a successful upgrade every time. While these two steps are also necessary with GroupWise 2014, there are some additional steps required, and the locations of files have moved around a bit.

Back in the “Installing the GroupWise Administration Service”section, we loaded up the Installation Console after installing the Administration Service. Now we need to look at the upgrade steps for our system.

Hopefully you set your Installation configuration to use “user” mode as we described in ”Changing the Installation Console Access Method”. Otherwise you will need to follow the “token” instructions above in that section to access the Installation Console (assuming it’s been more than 5 minutes since you completed the installation of the files and received your first token).

  1. Go to https://yourserver:9710/gwadmin-console/install

We have set our installation mode to “user”, so we can login with our “gwinstall” user we defined above.

  1. linuxinstall011.tifThe Installation Login Screen
  2. We now see the Installation options screen
  3. Installation Optionslinuxinstall012.tif
  4. Click on “Upgrade an Existing Domain or Post Office to GroupWise 2014”. We will show two examples in this chapter as follows:
  • Domain (Primary or Secondary) with or without a GWIA but no Post Office
  • Domain (Primary or Secondary) with GWIA and/or Post Office

Domain With or Without a GWIA (No Post Office)

In this section, we have a Domain, but no Post Office. Since all agents on the same server must be upgraded together, a domain that owns a GWIA will have the GWIA upgraded transparently during the upgrade procedure. There are some considerations for upgrading GWIAs. You will not be prompted for anything regarding the GWIA during the upgrade. If changes need to be made (for example, changing the IP address if this is a move/migration), you can make those after the upgrade. Please remember that the GWIA acts as a client. Thus, if you are using IMAP4 or POP3 to access your Post Offices, you cannot upgrade the GWIA until after all of the affected Post Offices have also been upgraded.

  1. Since we have moved our domain to this server, and have not installed a former version of GroupWise on the server, there is no gwha.conf configured. When we open the Installation Console and click on “Upgrade” we see the figure listed below.
    1. linuxinstall032.tifNo Objects found in gwha.conf for upgrade.

  1. In order to add our Domain to the list of objects to be upgraded, we click on the add button. We then are shown a file browser which we can use to browse to the domain directory. Click okay, and you will see the next figure that shows our domain, IP address, and the suggested admin port for this MTA.
    1. linuxinstall014.tifDomain Address and Port
  2. We have moved our domain, and this IP address is probably no longer valid. We will change the IP address to that of our new server, and click OK

Now that our domain is in the list to upgrade, we can continue.

  1. With your domain properly listed in the upgrade section, click Next.
  2. If this is the Primary Domain, you will be required to set an administrator and password for your GroupWise system. This is a very important user and password, and should not be forgotten. This is neither a GroupWise nor an eDirectory/AD user. This userid is written to the domain database and is used when you launch The Administration Console.

It’s our recommendation that you use a user specific to this task here. Just as we used gwinstall for our installation user in our install.cfg, we’d use something like gwadmin here to differentiate it from other administrative accounts you might have.

If you choose a “weak” password, Novell will alert you, but you can continue to use the password even if you are told it is weak.

  1. linuxinstall016.tifDefining the Super Admin userid and password

Set your administration user name and password and click Next.

If this is a secondary domain, you will not see the above figure that prompts you to create a new admin user and password. Rather, you will be prompted for location and credentials of your Primary Domain admin service.

  1. linuxinstall062.tifConnecting to the Primary Domain to complete an upgrade
  2. You will now see a summary screen. In our case, our GroupWise system is called “Beta”, so you see the name of the system, the domain to upgrade, and the settings for the domain.
  3. linuxinstall017.tifUpgrade Summary
  4. Click Finish to complete the upgrade. In the background, the Administrative Service will prepare the domain for upgrading and launch the MTA to complete the process.

The Admin Service, MTA and POA all have the ability to upgrade the pertinent databases. The process for upgrading is thus: in the Installation Console, you choose the databases to be upgraded. The installation process then copies the 2014 dictionary (dc) files to the pertinent directories, and instructs the Admin Server to proceed to upgrade. The dc file is essentially a text file that contains the database schema for creating a GroupWise 2014 database. The gwdom.dc shows the version number at the very top line as #VERSION=1400. This version number at the top of the file verifies that you have the GroupWise 2014 dc file in your domain directory. The Admin Service looks at the databases and sees if they are eligible to upgrade (i.e., it’s either a Primary Domain which can upgrade simply by being told “upgrade”, or a Secondary Domain or Post Office that has been granted the right to upgrade). If the domain is eligible to upgrade, the Admin Service will launch a recovery of the database, effectively converting the domain to GroupWise 2014. You will see a notice to restart your MTAs and POAs, and a link to access your Administration Console. In our experience, a restart is not required.

Geek note: the MTA and POA still have the ability to upgrade the databases as well, but it’s a job that’s been officially delegated to the Admin Service.

You will see a notice to restart your MTAs and POAs, and a link to access your Administration Console. In our experience, it’s not actually necessary to restart anything at this point.

  1. linuxinstall018.tifUpgrade Complete

If you are watching during the upgrade procedure, you will see the creating.dbb and recover.dbb files described above temporarily in the domain directory.

-rw-r–r– 1 root root 39983 Jan 27 14:15 0127gwbk.001

-rw-r–r– 1 root root 301056 Feb 5 15:37 creating.ddb

-rw-r–r– 1 root root 877 Feb 5 15:37 dzrec.log

-rw-r–r– 1 root root 21737 Jan 23 09:37 gwdom.dc

-rw-r–r– 1 root root 21284 Jan 23 09:37 gwpo.dc

.

.

-rw-r–r– 1 root root 784384 Feb 5 15:37 recover.ddb

-rw-r–r– 1 root root 4 Sep 27 14:11 uid.run

drwxr-xr-x 10 root root 4096 Feb 5 15:37 wpcsin

drwxr-xr-x 5 root root 4096 Sep 27 14:23 wpcsout

-rw-r–r– 1 root root 301056 Feb 5 15:38 wpdomain.db

-rw-r–r– 1 root root 11561 Jul 6 2005 wpdomain.dc

drwxr-xr-x 7 root root 4096 Sep 27 14:30 wpgate

-rw-r–r– 1 root root 10942 Jul 6 2005 wphost.dc

drwxr-xr-x 2 root root 4096 Feb 5 15:37 wpoffice

drwxr-xr-x 2 root root 4096 Sep 27 14:39 wptemp

To verify that the domain is in fact version 14, you will launch the Administration Console and check the version in the properties of the domain. We’ll do this below in the “Verifying the Upgrade” section below.

Domain With Post Office (GWIA optional)

As we saw above, any time you upgrade a domain that owns a GWIA, the GWIA is automatically upgraded for you. Thus in this section, if a GWIA is on the server you are upgrading, the only real difference from the prior section will be will be upgrading the post office simultaneously with the domain. Earlier, we recommended that you move and upgrade your domain separately from the post office, but if you have moved them both, that is really not a problem. You can perform the upgrade for both at the same time. You may need to consult the “Checking the MTP Link” on page 189 if you are experiencing communications problems with your MTA and POA.

Before we begin, you should read the chapter on ”Upgrading GroupWise Post Offices” on page 135, through the section on “Preparing the Post Office Database” on page 137. Once you have performed all of the tasks delineated prior to the section entitled ”Preparing the Post Office Database”, return here.

Since all agents on the same server must be upgraded together, a domain that owns a GWIA will have the GWIA upgraded transparently during the upgrade procedure. You will not be prompted for anything regarding the GWIA during the upgrade. If changes need to be made (for example, changing the IP address if this is a move/migration), you can make those after the upgrade.

  1. Since we have moved our domain and post office to this server, and have not installed a former version of GroupWise on the server, there is no gwha.conf configured. When we open the Installation Console and click on “Upgrade” we see the figure listed below.
    1. linuxinstall032.tifNo Objects found in gwha.conf for upgrade.

  1. To add our Domain and Post Office to the list of objects to be upgraded, we click on the add button. We then are shown a file browser which we can use to browse to the domain directory. Click okay, and you will see the next figure that shows our domain, IP address, and the suggested admin port for this MTA
    1. linuxinstall014.tifDomain Address and Port
  2. We have moved our domain, and this IP address is probably no longer valid. We will change the IP address to that of our new server, and click OK
  3. Repeat this process for the post office. Click on the add button. Browse for the Post Office location and click okay. Change the IP address to that of the new server if, and click OK.

Now that our domain and post office are in the list to upgrade, we can continue.

  1. With your domain and post office properly listed in the upgrade section, click Next.
  2. If this is the Primary Domain, you will be required to set an administrator and password for your GroupWise system. This is a very important user and password, and should not be forgotten. This is neither a GroupWise nor an eDirectory/AD user. This userid is written to the domain database and is used when you launch The Administration Console.

It’s our recommendation that you use a user specific to this task here. Just as we used gwinstall for our installation user in our install.cfg, we’d use something like gwadmin here to differentiate it from other administrative accounts you might have.

If you choose a “weak” password, Novell will alert you, but you can continue to use the password even if you are told it is weak.

  1. linuxinstall016.tifDefining the Super Admin userid and password

Set your administration user name and password and click Next.

If this is a secondary domain, you will not see the above figure that prompts you to create a new admin user and password. Rather, you will be prompted for location and credentials of your Primary Domain admin service.

  1. linuxinstall062.tifConnecting to the Primary Domain to complete an upgrade
  2. You will now see a summary screen. In our case, our GroupWise system is called “Beta”, so you see the name of the system, the domain and post office to upgrade, and the settings for the domain and post office.
  3. The Upgrade Summary Screenlinuxinstall061.tif

Click Finish to complete the upgrade. In the background, the Administrative Service will prepare begin the upgrade process of the domain and post office and launch the MTA and POA.

The Admin Service, MTA and POA all have the ability to upgrade the pertinent databases. The process for upgrading is thus: in the Installation Console, you choose the databases to be upgraded. The installation process then copies the 2014 dictionary (dc) files to the pertinent directories, and instructs the Admin Server to proceed to upgrade. The dc file is essentially a text file that contains the database schema for creating a GroupWise 2014 database. The gwdom.dc shows the version number at the very top line as #VERSION=1400. This version number at the top of the file verifies that you have the GroupWise 2014 dc file in your domain directory. The Admin Service looks at the databases and sees if they are eligible to upgrade (i.e., it’s either a Primary Domain which needs no further permission, or a Secondary Domain or Post Office that has been granted the right to upgrade). If the domain database is eligible to upgrade, the Admin Service will launch a recovery of the database, effectively converting the domain to GroupWise 2014. Then the process will happen for the Post Office. You will see a notice to restart your MTAs and POAs, and a link to access your Administration Console. In our experience, a restart is not required.

Geek note: the MTA and POA still have the ability to upgrade the databases as well, but it’s a job that’s been officially delegated to the Admin Service.

If you are watching during the upgrade procedure, you will see the creating.dbb and recover.dbb files described above temporarily in the domain and post office directories. Here’s an example

-rw-r–r– 1 root root 39983 Jan 27 14:15 0127gwbk.001

-rw-r–r– 1 root root 301056 Feb 5 15:37 creating.ddb

-rw-r–r– 1 root root 877 Feb 5 15:37 dzrec.log

.

.

-rw-r–r– 1 root root 784384 Feb 5 15:37 recover.ddb

-rw-r–r– 1 root root 4 Sep 27 14:11 uid.run

To verify that the domain is in fact version 14, you will launch the Administration Console and check the version in the properties of the domain. We’ll do this below in the “Verifying the Upgrade” section below.

Verifying the Upgrade

When you completed your upgrades in the sections above, there was a link to the Administration Console in the “upgrade completed”. There is also an icon on your server desktop. To go there manually, type this URL in your browser:

https://yourserver:9710/gwadmin-console

Since the installation created a self-signed certificate, you will be prompted to accept the untrusted certificate. Once you have done that, you will be at the Administration Console login screen.

  1. Login Screen for the Administration Consolelinuxinstall019.tif

Log in with the username and password you created above.

You will now see the Administration Console Dashboard. We will not go into great detail about this screen here, but will make a few comments.

  1. linuxinstall113.tifAdministration Console

Here we see that our system has two domains, two post offices and a GWIA. Any domain or post office that is NOT GroupWise 2014 will show the version number next to its object. For example, in our figure, the Caledonia PO is still at 2012, and the CNC2 Domain and Italia PO are GroupWise 8.

To verify that our CNC domain is indeed version 2014, we can click on the name CNC, which is a link to the domain properties.

  1. linuxinstall021.tifDomain Objects Properties

You will first see the “Object” screen shown above. Just click on the General Tab to see the details for the domain.

  1. linuxinstall022.tifDomain General Properties

Notice that our domain shows version 1400 on the General Tab, so we have in fact upgraded our primary domain.

Follow the same instructions for the Post Office to check the version.

To verify that all of your agents are loaded, the simplest way is to access the HTTP monitors for each agent upgraded. You should have verified back in “Enabling the HTTP Monitor for Your Agent” on page 11that your HTTP monitors were operational. The default paths for these monitors are:

  • MTA: http://yourserver:7180
  • POA: http://yourserver:7181
  • GWIA: http://yourserver:9850

If you cannot connect to your monitors, verify on the server that the agents are actually running:

.

  • On Linux, go to a terminal prompt and type rcgrpwise status
  • On Windows, go to the Services monitor (Start|Administrative Toosl|Services) and look for “GroupWise” services to see if they are running.

Additional Post Office Steps

If you have upgraded a Post Office in tandem with its Domain, you should check the steps in “Upgrading GroupWise Post Offices” beginning with “Configuring and Verifying a DVA for your Post Office” on page 141.

Where to from here?

Depending on the size and complexity of your system, and your overall upgrade plan, there are a number of “next steps” that you can take. The main rule of thumb is that you must upgrade ALL components of GroupWise that reside on the same server. Let’s look at a couple of very common configurations that you might be looking at.

Single Server

Sites with a single GroupWise server have everything in one place. This is acceptable for very small sites, although we always DO recommend that a site have a second domain as a fail safe measure. That said though, today we’re upgrading, not redesigning your system, so we’ll work with what we have. Single servers in very small organizations often house the following components:

MTA for the Primary Domain

POA for a single Post Office

GroupWise Internet Agent

GroupWise WebAccess Agent (GroupWise 8 and older)

GroupWise WebAccess Application

GroupWise Monitor

GroupWise Calendar Publishing Host

If this scenario fits your situation, then your Domain, GWIA and possibly Post Office are already upgraded, and all you need to do is upgrade the WebAccess Application (the GroupWise 8 and earlier WebAccess Agent is no longer used). So just jump over to the chapters on moving and upgrading your GroupWise Post Office, GroupWise WebAccess, GroupWise Monitor and GroupWise Calendar Publishing Host and Upgrading your GroupWise Clients. You’ll be finished in no time!

Multiple Servers

There are as many configurations of multiple server GroupWise systems as there are GroupWise customers it seems!

If your primary domain resides on a server all by itself, you are finished with this server. You can stop here, or move on to upgrading any post offices that belong to this primary domain, upgrading a secondary domain server, etc. It’s possible you might wish to go ahead and upgrade your GWIA at this point, but remember that you won’t want to do this if you have users in older GroupWise post offices accessing via IMAP4 or POP3 through your GWIA. See the chapter on Upgrading Your GroupWise Internet Agent.

If your system is small, and you will be upgrading all of your post offices over a weekend (for example), and you can afford to have WebAccess down for some users while you upgrade, you might choose to upgrade your WebAccess now. If you can provide for two separate WebAccess Application servers, you can upgrade your WebAccess and make it the default web server for WebAccess while you continue to upgrade your post offices. See the chapter on Upgrading Your GroupWise WebAccess.

Primary Domain and Post Office on the Same Server

It might be that you have a small system with your primary domain and post office on one server, and another server with a secondary domain for your GWIA and web server for WebAccess. In this situation, you will move the second server and perform the domain/gwia upgrade as noted above. Finally, you can proceed to upgrade WebAccess.

Troubleshooting Domain Upgrade Problems

There are very few things that can go wrong during a domain upgrade. If you find that your domain refuses to show as a GroupWise 2014 domain in ConsoleOne, do a couple of things:

  • Double-check that the installation actually copied the dc files into the domain directory. Open the gwdom.dc file with a text editor to verify that it is in fact the GroupWise 2014 file.
  • If this is a secondary domain, verify that the secondary domain KNOWS that the primary domain is a GroupWise 2014 domain. You can do this by connecting to the secondary domain in ConsoleOne and looking at the properties of the primary domain. It should show as version 1400 (or just 14 since ConsoleOne does not know about GroupWise 2014). If the primary does NOT show as a GroupWise 2014 domain when viewed from the perspective of the secondary domain, you will need to launch the Administration Console in your browser to verify (as described above) that it shows as a GroupWise 2014 domain (look in the properties of the primary). Once you have confirmed that the primary is GroupWise 2014, rebuild the secondary domain. You will need to use the command line utilities for GroupWise 2014 to rebuild the secondary domain database. See the section on “Command Line Utilities” on page 128 in the chapter on “The GroupWise Administration Console” to see how to accomplish this.

Troubleshooting Post Office Upgrade Problems

There are very few things that can go wrong during a post office upgrade. If you find that your post office refuses to show as a GroupWise 2014 post office in the Administration Console do a couple of things:

  • Double-check that the upgrade procedure copied the new dc files into the post office directory. Open the gwpo.dc and ngwguard.dc files with a text editor to verify that they are in fact the GroupWise 2014 files.
  • Double-check that the domain owning this post office is actually a GroupWise 2014 domain (i.e., it shows as version 1400 in the Administration Console).
  • Unload and reload the POA to see if this solves the problem.
  • It is possible that communications issues have prevented the post office database from receiving the news that its parent domain is a GroupWise 2014 domain and thus is allowed to upgrade. Remember that just loading the GroupWise 2014 agent software is not enough. If all else fails, rebuild the post office database. See “Validating or Rebuilding a Post Office Database”in “The GroupWise Administration Console” on page 115.

Once you are ready to continue, just turn to the next chapter in your upgrade plan.