The Upgrade Overview

Before we jump right in and begin our upgrade, we’ll take a few moments to go over the process of what we will be doing. How you perform your upgrade will be dictated in part by the size, location and complexity of your system. Here are a few possible scenarios:

Small, Single Server System

First of all, we always recommend that you have at least two GroupWise domains for redundancy. So, if your single server system only has one domain, during your upgrade, you might consider creating a new domain for your GWIA on a separate server to satisfy this recommendation. If you truly can only dedicate one server to your GroupWise system, you can run two MTAs on the same server to allow for a second domain. This, of course, does not give you the same type of redundancy, but can provide a backup of your domain in case of database corruption that cannot be otherwise restored.

In any event, if your GroupWise system is contained all on a single server, you will need to plan to perform your entire upgrade (except for the clients) in a single sitting. It is vital that all components of the GroupWise system that reside on the same server be upgraded at the same time. Thus, if you have a small system, you would go through the steps of:

“Installing the GroupWise Administration Service”

“Upgrading GroupWise Domains” for the Primary Domain along with the GWIA.

“Directory Integration and Synchronization” to verify that your Directory Integration has succeeded and correct any errors.

“The GroupWise Administration Console” to familiarize yourself with the Administration Console

“Upgrading GroupWise Post Offices”

“Upgrading GroupWise WebAccess”

“Upgrading GroupWise Monitor”

“Upgrading the GroupWise Calendar Publishing Host”

“Upgrading GroupWise Clients”

Of course, you may not have all of those components in your system, but this is the order we recommend they be installed.

Small, Multiple Server System

If your GroupWise system is fairly small (perhaps even a single post office with primary domain and gateways on another server), you have some options. The key is that all components on the same server must be upgraded at the same time. Your first step of course will be to deal with upgrading your GroupWise Primary Domain. If the Post Office is on the same server as your primary domain, then you will need to upgrade it at the same time. So long as you upgrade all items on each server together, you should not run into any problems.

Complex GroupWise System on Multiple Servers

If you have a very complex GroupWise system, you need to consider a few things that will crop up with the inevitability of not being able to upgrade all of your post offices at the same time. Here are the most important “gotchas” of a gradual upgrade:

  • GroupWise 2014 clients cannot access older post offices. Thus, you cannot begin your client rollout before you actually perform the post office upgrade. This also means that GroupWise 2014 clients cannot proxy to an older GroupWise post office. If you have users on your GroupWise 2014 post offices that need to proxy to an older GroupWise post office, that particular GroupWise 2014 user will need to continue to use the older GroupWise client.
  • If you use your GWIA for POP3/IMAP4 access, you will not be able to upgrade your GWIA to GroupWise 2014 until all of your post offices that service such users have been upgraded. In other words, a GroupWise 2014 GWIA running as a POP3 or IMAP4 server is a GroupWise “client” and cannot access older GroupWise post offices. We will discuss this in more detail in Upgrading Your GroupWise Internet Agent. You may need to provide for an older GroupWise GWIA for your users on older post offices if you wish to upgrade your GWIA before you upgrade all of your post offices. If you are accessing through IMAP4, you might consider allowing your GroupWise Post Office Agents to serve as IMAP4 servers for your GroupWise 6 and newer users, thus allowing you to upgrade the GWIA to GroupWise 2014 right away. There are actually very few good reasons to keep POP3 around (one of them being external processes that cannot use IMAP4). If you can convert all of your external access to IMAP4, moving the IMAP access to your POAs would definitely solve your migration issues.
  • Web Access is also a “client”, and as such a GroupWise 2014 WebAccess Application cannot access an older GroupWise post office. If you can provide for only one WebAccess Application server, you will need to wait until all post offices are upgraded to GroupWise 2014 before you upgrade your WebAccess. If you can provide two WebAccess Application servers, you can create a new WebAccess for GroupWise 2014, and even use it as your “default” WebAccess location. If a user for an older GroupWise version connects to the GroupWise 2014 WebAccess, the user is redirected to the older WebAccess version. We will discuss this in more detail when we get to Upgrading Your GroupWise WebAccess later in the book.