Novell is now a part of Micro Focus

GroupWise 6 Deployment Guide - Section 2

Novell Cool Solutions: Feature

Digg This - Slashdot This

Posted: 5 Dec 2001

<Table of Contents

Section 2: Migration and Deployment

GroupWise 6 is easier to implement than any previous version of GroupWise. The process of migrating from GroupWise 5.x to GroupWise 6 is a simple matter of installing the code and re-launching the agents. That's really all there is to it?simple, clean and easy.

This section presents basic information that will help you ensure successful deployment. For detailed, step-by-step information on installing GroupWise 6, please refer to the GroupWise 6 Installation Guide.

General Preparation

If there are no problems with your current GroupWise 5.x system, you can confidently deploy GroupWise 6 on your existing system structure. To prepare your GroupWise 5.x system to be updated to version 6, you should complete the following tasks:

  • Validate your domain and post office databases to make sure that there are no physical inconsistencies with the database. If problems exist, you should recover or rebuild the database. For information about validating, recovering, or rebuilding a database, see the GroupWise 5.x Maintenance Guide at the Novell Documentation Web Site.
  • Back up the domain or post office immediately before updating it. GroupWise's backup utility, GWBACKUP.EXE, allows you to back up (and restore) your databases. For information about using the backup utility, see the GroupWise 5.x Maintenance guide at the Novell Documentation Web Site.

Note: If you are installing GroupWise for the first time, or if your existing GroupWise configuration is not meeting system demands, refer to the General Configuration Guidelines Appendix on page 41 for best practices information on Directory and network configuration.

Piloting the Code

GroupWise is a mission-critical application; therefore, Novell strongly recommends that you pilot the code in your environment before rolling it out across your organization. Although Novell thoroughly tests its code, there are inevitably conditions in your environment that have not been replicated in the Novell labs.

Note: If your site has over 3000 users, or if you are not comfortable migrating your system to GroupWise 6, contact Novell Consulting Services at 888.321.4272 (U.S./Canada) or 801.228.4272 (worldwide). You may also call your local Novell representative or visit

If you pilot GroupWise 6 on a portion of your system, your overall system can continue to function as an integrated whole if you keep the following points in mind:

  • GroupWise 6 agents can interoperate with their 4.x and 5.x counterparts.
  • GroupWise 5.x clients, WebAccess, and GWIA can connect to a 6.x post office.
  • The GroupWise 6 client cannot connect to a 5.x post office. Therefore, post offices should be migrated to version 6 before GroupWise clients.
    • This limitation includes proxy connections. A GroupWise 5.x user can proxy a GroupWise 6 user, but a GroupWise 6 user cannot proxy a 5.x user.
    • If you have a software distribution directory assigned to a POA and the AutoUpdate feature is enabled on the GroupWise client, do not install GroupWise 6 to the software distribution directory until you migrate the POA to version 6. Otherwise, when the clients are automatically updated to version 6, they will not be able to communicate with their 5.x POA.
  • The WebAccess agent, and GWIA cannot connect to a 5.x post office. Consequently, they are the last elements you should upgrade when deploying GroupWise 6.
  • To provide wireless services on your 5.x system, the GroupWise 6 WebAccess application can connect to a 5.x WebAccess agent. For information on providing GroupWise wireless services on a 5.x system, see "Wireless First" on page 20.

Migration Basics

The general steps to upgrade from GroupWise 5.x to GroupWise 6 are as follows:

  1. Install the ConsoleOne snap-ins.
  2. Upgrade the primary domain.
  3. Upgrade the secondary domains.
  4. Upgrade the post offices.
  5. Upgrade WebAccess and GWIA.
  6. Deploy the client.
  7. Deploy GroupWise Monitor

Further information on the migration process is provided in the following sections.

4.x to 5.x

GroupWise 4.x users must migrate to GroupWise 5.5 before migrating to GroupWise 6. For migrations from GroupWise 4.x to 5.5, please review TIDs 2928475, 2941090, and 2941160 at You may also reference the GroupWise 5.5 Migration Guide at

Deploying the POA and MTA

Before installing the GroupWise 6 agents, you will need the following information:

  • Domain name for the MTA
  • Post Office name for the POA
  • UNC path to the domain and post office directories
  • The HTTP port assignment for the monitoring agent (this is only required if you do not use the default port assignment)
  • Sufficient NDS and file system rights

Note: If the startup filenames are the same as the previous version (domain.MTA and post_office.POA), the GroupWise 6 agent installation will not overwrite your existing startup files. The GroupWise 6 settings will simply merge with your existing startup file and all previous configuration settings will be maintained.

During the agent install, you have the option of launching all agents at the end of the installation process. If you mark this option and the POA and MTA are on the same server, you will have to reload the POA to make it aware of the domain version change.

Migrating Domains

In migrating existing GroupWise 5.x domains to GroupWise 6, the primary domain must be migrated before any secondary domains and all domains must be migrated before their corresponding post offices.

To migrate a domain, follow these general steps:

  1. Install the GroupWise 6 software and administration snap-ins to your software distribution directory. The MTA must have access to the distribution directory, as well as the updated WPDOMAIN.DC file (this is the template used to create the WPDOMAIN.DB file).
  2. Install the GroupWise 6 MTA. The agent install merges the startup files and preserves all previous eDirectory configuration settings.
  3. Unload the 5.x MTA.
  4. Launch the GroupWise 6 MTA to recover the domain database (WPDOMAIN.DB).
  5. Once the domain database has been recovered, verify the domain version in ConsoleOne.

Migrating Post Offices

The primary point to remember when migrating GroupWise 5.x post offices to GroupWise 6 is that you cannot upgrade the post office until you upgrade its respective domain.

To migrate a post office, follow these general steps:

  1. Install the GroupWise POA.
  2. Bring down the previous version Post Office Agent (POA) and then launch the GroupWise 6 POA to recover the post office database (WPHOST.DB).
  3. Once your post office database has been recovered, verify the post office version in ConsoleOne.

Deploying GroupWise WebAccess

WebAccess enables users to access their mailboxes through any standard Internet browser. It is also the foundation piece for Novell's wireless connectivity. WebAccess provides simple, direct, access to GroupWise content without forwarding, without POP or IMAP, and without duplication of items.

To migrate GroupWise WebAccess, follow these general steps:

  1. Install the WebAccess Application.
  2. Install the WebAccess Agent (GWINTER). Installing GWINTER extends the NDS schema to include application objects and provider objects for GroupWise WebAccess.
  3. If you have multiple WebAccess servers, set the default WebAccess server.

WebAccess Configuration

A basic installation of GroupWise WebAccess requires the WebAccess Agent and the WebAccess Application, as shown in the following diagram.

If your GroupWise system is relatively small (one domain and a few post offices) and all post offices reside in the same location, a basic installation of GroupWise WebAccess may very well meet your needs. However, if your GroupWise system is large or spans multiple locations, it may be necessary for you to add additional WebAccess Agents or to have multiple Web servers running the WebAccess Application. For more information on these configurations, see "Optimizing WebAccess" on page 32.

Configuring GroupWise WebAccess for Redirection and Failover Support

Redirection enables the WebAccess Application to direct user requests to specific WebAccess Agents. For example, you may want WebAccess Agent 1 to process all requests from users on Post Office 1 and WebAccess Agent 2 to process all requests from users on Post Office 2.

Failover support enables the WebAccess Application to contact a second WebAccess Agent if the first WebAccess Agent is unavailable. For example, if the WebAccess Application receives a user request that should be processed by WebAccess Agent 1 but it is unavailable, the WebAccess Application can route the user request to WebAccess Agent 2 instead.

For detailed information on configuring GroupWise WebAccess for redirection and failover support, see "Scaling GroupWise WebAccess" in the GroupWise 6 Administration Guide at

Wireless First

If you are incrementally deploying GroupWise 6 on your system, but want to take immediate advantage of GroupWise 6 wireless services, you can deploy the WebAccess Application before upgrading the rest of your system. This is because the GroupWise 6 WebAccess Application can interoperate with a version 5.x WebAccess Agent; it automatically detects the 5.x Agent's version and makes decisions about what features it can expose. For example, the WebAccess Application will provide wireless functionality, but not enhanced WebAccess features link Signatures and rules.

To implement Wireless first, follow these steps:

  1. Run the WebAccess install but only select the WebAccess Application.
  2. Provide the install with the WebAccess Agent's (GWINTER) correct IP address.
  3. After the install completes, use ConsoleOne to ensure that the encryption key is the same for both the Application and the Agent.

Customizing WebAccess Templates

GroupWise WebAccess uses a series of java templates to reformat GroupWise content for Internet browser or wireless devices with limited bandwidth, smaller screen size, and limited browsers (no frames or JavaScript).

Currently, the WebAccess Application can translate HDML, WML, and simple HTML; however, it is an open, java application so you can customize existing templates to meet your organization's needs or create new templates to access GroupWise content through virtually any protocol.

For detailed information on modifying and creating WebAccess templates, refer to the template sections of the documentation in the Novell Developer Kit: GroupWise WebAccess Customization (

Deploying the GroupWise Internet Agent (GWIA)

The GroupWise Internet Agent allows communication between GroupWise users and users of other messaging systems who use the Internet to send e-mail. The Internet Agent receives inbound e-mail messages from the Internet in SMTP format and passes them to the GroupWise MTA.

For outgoing messages, transported by the Internet, the GroupWise MTA passes the message to the Internet Agent, which then converts the message to Internet messaging format, and then sends it to the designated Internet address.

To migrate the GroupWise Internet Agent, follow these general steps:

  1. Ensure that the TCP/IP NLM is functioning correctly in your system and you have the correct version before installing the Internet Agent NLM.
  2. Make sure DNS is correctly configured on your server.
  3. Verify the IP address and the fully qualified DNS host name where the program is running in your HOSTS file
    Set the /hn switch in the GWIA.CFG file.
  4. Install the Internet Agent.
    Installing the Internet Agent creates the Internet Agent object in NDS, configures the startup files for the Internet Agent, and tests the server you are installing to for correct Internet configuration.
    If you install the Internet Agent with the Copy Only option, GroupWise will not overwrite the current configuration file; it will only update the NLM.

If you have a heterogeneous system with GroupWise 5.x and GroupWise 6.x post offices, the GroupWise 6 Internet Agent will not be able to access a GroupWise 5.x post office with POP or IMAP clients.

If you intend to use SSL to secure POP, IMAP, and SMTP transmissions, you must have a certificate. In order for GWIA to access the certificate, it cannot be password protected.

Deploying the Client

The GroupWise client for Windows can be installed to users' workstations by the user or by the system administrator. For centralized distribution via ZENWorks, the GroupWise 6 client is available in Application Object Template (AOT) format in the SP1 release of GroupWise 6.

The Windows Messaging Application Programming Interface (MAPI) is an essential element in client deployment. Users must have specific MAPI versions for Windows 95/98 or Windows NT/2000 to run the GroupWise client. If you are upgrading, these files should already be present on the users' workstation. If this is a new install, you may have to install MAPI to the workstations before installing the client. (You can automate the MAPI install using ZENWorks.)

The GroupWise client can be deployed through one of two methods:

  • A mapped connection to the software distribution directory
  • A TCP/IP connection

Deploying the Client via a Mapped Connection

Deploying the client through a mapped connection is the standard method of installation in network environments. This method requires that users have a mapped drive to the Software Distribution Directory. Once they have a minimum of Read and File Scan rights to the Software Distribution Directory, users can run the client install by launching Setup.EXE from the network or you can e-mail the file to them and they can launch the install from their workstations.

By default, users can select which client components to install and whether to run the client from the network or their workstation. To restrict which selections the user can make during installation, the administrator can use a configuration file (Setup.CFG). For more information on the configuration file, see "Setup.CFG" on page 22.

Deploying the Client via SetupIP.EXE

SetupIP.EXE is the method of installing the GroupWise client via a web server. SetupIP does not require mapped connections. Instead, users simply launch the SetupIP.EXE file from a specific Web address or you can e-mail the file to them and they can launch the install from their workstations.

Unlike Setup.EXE, the administrator must configure the SetupIP.EXE file. The WRITEIP.EXE utility, located in the software/admin/utility/setupip directory, provides an interface for configuring the SetupIP.EXE and WRITEIP.INI files. In configuring the SetupIP.EXE file, the administrator is prompted to enter the IP address or DNS name of up to 5 Web servers where users can access the client software. These Web servers must use "fancy" indexing (Novonyx) to support file dates and must be able to list 400 files without truncating the list.

SetupIP.EXE can be configured to run the install from the server or to download the installation files to the workstation and then launch the install from the workstation. While running the install directly from the server is faster, it does have an associated risk. The client install directly overwrites the existing GroupWise client. Consequently, if a user loses his IP connection mid-way through the install, his existing GroupWise client will no longer work. The user must then re-launch and complete the install before he will again have access to GroupWise.

The preferred SetupIP.EXE install is to run the install from the user's workstation. To start this process, the client install files are first downloaded from the server to a temporary directory on the user's workstation. Once the files are downloaded, the install is automatically launched from the workstation. When the install is complete, the files in the temporary directory are removed.


AutoUpdate gives administrators a way to force and automate client updates. It can be used for mapped drive or SetupIP installations and it can be used in conjunction with Setup.CFG.

The AutoUpdate feature relies on two thresholds: the GroupWise build number and your system bump number. Novell controls the build number. Each time a new version of GroupWise is released (including interim releases and enhancement packs), Novell sets a new build number. The bump number is system-specific and indicates how many times the GroupWise client has been installed on the system.

Both the build number and bump number thresholds must be triggered in order for AutoUpdate to launch. The basic process is as follows:

  1. When a user logs into the network, the client compares its bump number against the bump number registered in NDS.
  2. If the NDS bump number is different, the client requests the POA to return the build number registered in the Software Distribution Directory.
  3. If the build number is different, the client requests the location of the Software Distribution Directory from the POA and launches the install.


The Setup.CFG file is used to standardize GroupWise client installations. Using Setup.CFG, administrators can control what menus users see as well as which options users can access within each menu. For example, to completely standardize the client install, the administrator would set the Show Dialogs option to "No," Standard install to "Yes," and define all client configuration options. In running this installation, the only thing the user would see is the final screen saying the installation is complete.

Setup.CFG can drive either mapped drive or SetupIP installs and it may be used in conjunction with the AutoUpdate feature. By default, Setup.CFG is configured for a mapped drive install. To configure a SetupIP installation, you must set the SetupIP option to "Yes."

Setup.CFG is a simple text file and may be edited from any text editor. The template file is located in the software\client directory. Any items except [GroupwiseSetup] Version=6 can be deleted from the Setup.CFG template file. When an item is deleted, the default setting will be used.

In order for Setup.CFG to be detected and used in an install, it must be saved to the software/client/win32 directory.

Sample Setup.CFG File

The following is an example of the GroupWise 6 Setup.CFG file:








Lotus WordPro=Yes
Microsoft Binder 97=Yes
Microsoft Excel 7.0=Yes
Microsoft Excel 97=Yes
Microsoft Excel 2000=Yes
Microsoft PowerPoint 97=Yes
Microsoft PowerPoint 2000=Yes
Microsoft Word 7.0=Yes
Microsoft Word 97=Yes
Microsoft Word 2000=Yes
Corel Presentations 7.0/8.0/9.0=Yes
Corel Quattro Pro 7.0/8.0=Yes
Corel Quattro Pro 9.0=Yes
Corel WordPerfect 7.0=Yes
Corel WordPerfect 8.0=Yes
Corel WordPerfect 9.0=Yes


Deploying GroupWise Monitor

GroupWise Monitor is a monitoring and management tool that allows you to monitor GroupWise agents and gateways from anywhere a browser and a connection to the Internet are available. Additionally, some agent administration can be performed from your Web browser.

GroupWise Monitor consists of two modules: the Monitor Agent and the Monitor Application. The Monitor Agent and the Monitor Application can run on different machines or the same machine. For full functionality, run the Monitor Agent on Windows NT/2000. (The Monitor Agent also runs on Windows 95/98, but with slightly limited functionality.) The Monitor Application can run on NetWare, UNIX Solaris, or Windows NT/2000 in conjunction with a Web server running on one of those platforms.

Before deploying GroupWise Monitor, you must have a functional Web server. After configuring your Web server, follow these general steps to migrate GroupWise Monitor:

  1. Install the Monitor Agent.
  2. Install the Monitor Application. Installing Monitor extends the NDS schema to include application objects and provider objects for GroupWise Monitor.

The default configuration of the GroupWise Monitor Agent is adequate to begin monitoring existing GroupWise agents such as POAs, MTAs, Internet Agents, and WebAccess Agents.

You can also download the full .pdf version of this new Deployment Guide here:


Table of Contents


Novell Cool Solutions (corporate web communities) are produced by WebWise Solutions.

© Copyright Micro Focus or one of its affiliates