Upgrading to GroupWise 6 From GroupWise 5.x
Articles and Tips: article
Danita Zanrč
01 Aug 2001
Editor's Note: This article is based on the authors' book GroupWise 6 Upgrade Guide, which is published by Caledonia Network Consulting. This book is available at http://www.caledonia.net/.
GroupWise 6 includes many new features for administrators and users alike. For the administrator, GroupWise 6 includes features such as a rock-solid back-end, better user management (such as disk quotas and caching mode), and enhanced backup and restore options. For the user, GroupWise 6 includes features such as archive access through enhanced web access and Network News Transfer Protocol (NNTP) support.
In addition, GroupWise 6 offers low-cost licensing for web access and wireless access. This licensing scheme allows companies to connect both their traditional e-mail users and their "deskless workers." (For more information about connecting deskless workers, see "Novell Brings Messaging to the Deskless Work Force," Novell Connection, July 2001, pp. 24-25.)
In fact, after using GroupWise 6 for almost a year now, we feel the question is not "why should you upgrade to GroupWise 6?" but "how do you upgrade?"
Upgrading to GroupWise 6 can be broken into two separate components: an upgrade of the actual GroupWise software (such as the GroupWise clients, agents, administration, and WebAccess) and an upgrade of the GroupWise data stores. This article provides an overview of the issues you must consider before you begin a GroupWise 6 upgrade.
SOFTWARE UPGRADE
When you first install GroupWise 6, you are prompted to install the GroupWise 6 software to a software distribution directory. When you do this, you should create a new directory for GroupWise 6. Do not overwrite an existing GroupWise 5.x software distribution directory.
When upgrading a GroupWise system, you should be aware of the following GroupWise software components:
Administration
Domains
Post Offices
Clients
GroupWise Internet Agent (GWIA)
GroupWise WebAccess
Gateways
You should understand how to upgrade each of these components, and you should also know which GroupWise 5.x components are compatible with GroupWise 6 components.
Administration
You now manage GroupWise through ConsoleOne rather than the NetWare Administrator (NWADMIN) 32 utility. Consequently, you should not use the NWADMIN utility to manage GroupWise 5.x domains. (For information on how to disable the GroupWise 5.x snap-in modules for the NWADMIN utility, see Chapter 3 of GroupWise 6 Upgrade Guide.)
Novell's official position is that you must disable the GroupWise 5.x snap-in modules for the NWADMIN utility. Unfortunately, the GroupWise snap-in modules for ConsoleOne don't provide the same functionality as the GroupWise snap-in modules for the NWADMIN utility. For example, in the original shipping version of GroupWise 6, the GroupWise import function is not available. As a result, you cannot use ConsoleOne to convert a GroupWise external entity into an NDS eDirectory user. In addition, you cannot search on resources or distribution lists.
By the same token, some new GroupWise 6 features are not exposed by the older snap-in modules for the NWADMIN utility. For example, you cannot use the snap-in modules for NWADMIN utility to access mailbox limitations preferences and new GroupWise WebAccess and GWIA settings.
You should use ConsoleOne as your primary management tool. If a management function isn't available in ConsoleOne, you can revert to the NWADMIN utility. Of course, Support Pack 1 for GroupWise 6 will address most of these issues, but until Novell releases this support pack, you may need to use both management tools. (Novell plans to release Support Pack 1 for GroupWise 6 by November.)
As a beta tester of GroupWise 6, we encountered no problems in using the NWADMIN utility with the GroupWise 5.5 snap-in modules. We beta tested GroupWise 6 for more than six months and used these snap-in modules to manage our GroupWise system. Although Novell's official view is that you should abandon the NWADMIN utility, our unofficial view is that you will need to keep it. Of course, you should take a few precautions when using multiple tools to manage your GroupWise system:
For all domains that have been upgraded to GroupWise 6, flag the GWDOM.DC and the GWPO.DC files in the domain directory as Read-Only. This prevents the GroupWise 5.5 snap-in modules for the NWADMIN utility from attempting to "update" your files when it senses they are "different."
Do not use the NWADMIN utility to perform System Maintenance routines. Also note that the System Maintenance routines in ConsoleOne are more than three times faster then they are in the NWADMIN utility. That's a nice bonus!
Do not use GroupWise 5.2 snap-in modules to manage a GroupWise 6 system; you will damage your GroupWise system! The GroupWise 5.2 snap-in modules are designed for use with the NetWare Administrator 95 and NetWare Administrator NT utilities. For GroupWise 6, you should use only the GroupWise 5.5 snap-in modules that are installed in the PUBLIC/WIN32 directory.
If you have already installed ConsoleOne, you will simply need to install the GroupWise 6 snap-in modules. You should confirm that you are using ConsoleOne 1.2.d.1 or above before you install the GroupWise 6 Administration snap-in modules. The GroupWise 6 Administration snap-in modules work only with the Windows version of ConsoleOne 1.2.d.1 or above. If you are using another version of ConsoleOne--such as the version that is included with Novell's eDirectory for Linux--GroupWise snap-in modules are not available.
You can use the GroupWise Administration snap-in modules for ConsoleOne to manage GroupWise 5.x and GroupWise 6 domains. However, you cannot use GroupWise Administration snap-in modules for ConsoleOne to manage or rebuild GroupWise 4.1 domains. If you must continue to manage GroupWise 4.1 domains, you must keep the GroupWise snap-in modules for the NWADMIN utility or use the GroupWise 4.x AD.EXE utility.
Domains
Upgrading the software for a GroupWise 5.x domain to GroupWise 6 is as easy as installing the GroupWise 6 Message Transfer Agent (MTA) and overwriting the existing GroupWise 5.x MTA software. After you have installed and run a GroupWise 6 MTA against a GroupWise domain, however, do not run the GroupWise 5.x MTA against that domain.
The GroupWise 6 MTA NetWare Loadable Module (NLM) is officially supported and tested on NetWare 5.x and above. If you are using NetWare 4.11 or above, you will probably be fine. We tested GroupWise 6 running on NetWare 4.x and found the MTA NLM is quite solid on NetWare 4.x. Keep in mind, however, that Novell does not officially support this configuration.
If you intend to run your GroupWise MTA and/or Post Office Agent (POA) NLM on a NetWare 4.x server, you should include the following LOAD statements at the top of the GRPWISE.NCF file or before any GroupWise NLMs are loaded on the server:
LOAD CLIBAUX
LOAD CLIB
LOAD FPSM
LOAD NLMLIB
LOAD NWSNUT
LOAD REQUESTR
LOAD THREADS
Most of the items listed after CLIBAUX.NLM have already been loaded on the server, and you will receive a message indicating these items are already loaded. However, reloading these items after initializing CLIBAUX.NLM apparently enables the GroupWise 6 NLMs to load properly. Without these statements, you will probably receive unknown public symbol errors.
The GroupWise Windows MTA is also supported on Windows NT 4.0 (Server or Workstation) and Windows 2000 Professional and Server platforms.
You can run both the GroupWise 6 and GroupWise 5.x MTAs on the same server. You can also run a GroupWise 6 MTA and a GroupWise 5.x POA on the same server if necessary.
The GroupWise 6 MTA uses a core GroupWise engine called GWENN3, whereas the GroupWise 5.5 MTA and POA use GWENN2. These two core GroupWise engines can be loaded in memory at the same time.
When you install the GroupWise 6 agent software, you should not install it in the directory that holds the GroupWise 5.x agent software. For example, if the GroupWise 5.5 MTA is installed in the SYS:SYSTEM folder, you could install the GroupWise 6 MTA in the SYS:SYSTEM\GW6 folder.
A GroupWise 6 MTA can communicate with GroupWise 5.x MTAs, ADAs, and POAs. A GroupWise 6 MTA can also communicate with the GroupWise 4 message server and GroupWise 4 gateways.
Post Offices
Upgrading the software for a GroupWise post office is a two-part process. You upgrade the POA to GroupWise 6, and then you upgrade the clients to the GroupWise 6 Windows client. Because the GroupWise 6 Windows client is not compatible with a GroupWise 5.5 POA, you must upgrade the POA for a GroupWise post office before upgrading users' client to GroupWise 6.
The GroupWise 6 POA has the same operating system requirements as the MTA. Like the MTA, the GroupWise 6 POA runs quite nicely on NetWare 4.x, although Novell does not support this configuration.
Clients
GroupWise 5.x clients are compatible with a post office that has been upgraded to GroupWise 6. However, Novell has not performed any extensive testing to determine all of the potential compatibility issues between the GroupWise 5.2, 5.1, and 5.0 clients and the GroupWise 6 agents.
If your company runs GroupWise 5.2 or below, you should proceed with caution and perform some initial testing on your own. Also, read the "WebAccess" section so that none of your GroupWise users are caught without a WebAccess solution as you upgrade.
Upgrading users to the GroupWise 6 client is much like rolling out the GroupWise 5.x client. Whatever method you used to upgrade clients to GroupWise 5 (such as manual installation or ZENworks for Desktops) will work with GroupWise 6.
GroupWise Internet Agent
Upgrading the GWIA from GroupWise 5.x to GroupWise 6 is relatively painless. Before you begin upgrading, however, you should understand the GWIA's relationship to the client.
Because the GWIA acts as both a gateway and an agent, it talks directly to GroupWise post offices for user access via POP3 or IMAP4. Officially, the GroupWise 6 GWIA cannot talk directly to GroupWise 5.x post offices. As a result, you should wait to upgrade the GWIA to GroupWise 6 until all post offices that require POP3 or IMAP4 access have been upgraded.
We say "officially" because, quite frankly, accessing a GroupWise 5.x post office isn't supposed to work (and vice versa)! In our testing, however, we found that a GroupWise 6 GWIA can indeed talk to a GroupWise 5.5 Enhancement Pack POA and that a GroupWise 5.5 GWIA can also access POP3/IMAP4 mail for a GroupWise 6 post office.
We did not perform this test with any version lower than the GroupWise 5.5 Enhancement Pack with Support Pack 1. According to Novell, this configuration does indeed seem to work, but Novell does not support it. Consequently, you must use it at your own risk. Although we have not experienced any database corruption when using this configuration, we recommend that if you use this configuration, your GWIA post office links should be client-server only.
GroupWise WebAccess
WebAccess is perhaps the most confusing of the upgrades from GroupWise 5.x to GroupWise 6. You can successfully configure WebAccess to keep all of your users accessing the system during an upgrade. Although the details are beyond the scope of this article, you should keep in mind that the GroupWise 6 WebAccess application can communicate with any 5.x or above WebAccess Agent (GWINTER). With proper configuration, you can roll out the new GroupWise 6 user interface to all of your current users long before all of the post offices are upgraded. (For more information, see GroupWise 6 Upgrade Guide.)
Gateways
The other 4.1 and 5.x gateways that you used with your GroupWise 5.x system are fully compatible with GroupWise 6. As a result, you can easily upgrade the domains that include these gateways to GroupWise 6, without upgrading the gateways themselves. Everything will work just fine.
The gateways themselves are unaware that the domain is a GroupWise 6 domain. The MTA is the only entity that must communicate with gateways. The MTA makes up for any differences between the version of the MTA and the version of the gateway.
The only issue we have encountered in running GroupWise 4.1 gateways with a GroupWise 6 system has to do with NetWare 4.x. Specifically, the GroupWise Async gateway will not load properly on a NetWare 4.x server that is also running the GroupWise 6 NLMs. A new Async gateway that uses GroupWise 5.x technology is currently in beta, and this gateway will eventually replace the GroupWise 4.1 gateway.
DATA UPGRADE
GroupWise has two main kinds of data--the directory store data, which contains the system address book and system information, and the message store data, which contains the actual contents of the users' universal mailbox.
Upgrading the GroupWise 6 Directory Store
The GroupWise directory store includes GroupWise information in eDirectory, the GroupWise domain databases (the WPDOMAIN.DB file), and the GroupWise post office databases (the WPHOST.DB file). When you install GroupWise 6, you will be prompted to extend the eDirectory schema. You must extend the schema before continuing the upgrade process.
This schema extension is generally performed only once. If your company's GroupWise 6 system spans multiple trees, you must extend the schema for each eDirectory tree.
The GroupWise 6 installation program also sets in motion the first steps needed for the WPDOMAIN.DB and the WPHOST.DB files to be upgraded to GroupWise 6. Unlike the schema extensions, these files are not upgraded automatically.
The GroupWise WPDOMAIN.DB and WPHOST.DB database files have their own "dictionary" files--the GWDOM.DC and GWPO.DC files--which determine the structure and fields in these databases. Before a GroupWise domain or post office can be upgraded, the new fields in the GWDOM.DC and the GWPO.DC files must be incorporated into the domain and post office databases.
The GroupWise WPDOMAIN.DB and WPHOST.DB files are typically upgraded the first time the GroupWise 6 MTA runs against them. For example, when a GroupWise 6 MTA runs against the WPDOMAIN.DB file, that MTA recovers the database on the fly and converts it into a GroupWise 6 WPDOMAIN.DB file. (For more information about upgrading these files, see Chapters 3, 4, and 5 in GroupWise 6 Upgrade Guide.)
Upgrading the GroupWise 6 Message Store
The GroupWise message store is composed of the users' messages, which are contained primarily in the OFUSER, OFMSG, and OFFILES folders located in each post office directory. Generally speaking, you upgrade a GroupWise post office database by loading the GroupWise 6 POA against it. (Some other conditions must be met. For specific information about upgrading a GroupWise post office, see Chapter 3 in GroupWise 6 Upgrade Guide.)
The GroupWise message store does not go through a massive upgrade. In fact, a user's mail is upgraded the first time a user logs in to the post office, and the user is not even aware of the upgrade.
Only the user databases need to be upgraded for a GroupWise post office message store to be upgraded. Although the MSGXX.DB files will need to support new attributes of GroupWise 6 messages, those additions are made on-the-fly as needed. The GroupWise message store is fully backward compatible with GroupWise 5.x clients. The new fields added for GroupWise 6 functionality are simply ignored by the GroupWise 5.x clients.
THE UPGRADE PROCESS
When you insert the GroupWise 6 CD into your CD-ROM drive with the intention of upgrading your GroupWise system, the wizard under GroupWise Administration performs four tasks. (See Figure 1.)
Extends the eDirectory schema
Installs GroupWise snap-in modules for ConsoleOne
Creates a GroupWise 6 software distribution directory
Updates an existing GroupWise 5.x system
Extending the eDirectory Schema
As mentioned earlier, GroupWise 6 requires a few additions to the eDirectory schema. The installation CD reads the SCHEMA file from the installation CD's ADMIN folder. The wizard compares the schema of your eDirectory tree to see if it contains the information in the GWSCHEMA.SCH file in the ADMIN folder. (This ASCII file is written to an eDirectory standard for extending a tree's schema.)
If the information is different, the wizard prompts you to extend the schema. Otherwise, the wizard informs you that the schema is already extended and continues with the installation. To extend the eDirectory schema, you must have ADMIN rights to the Root object of the eDirectory tree.
Installing the GroupWise 6 Snap-in Modules for ConsoleOne
Although GroupWise 6 uses ConsoleOne as its administration utility, ConsoleOne does not inherently know about GroupWise objects. The GroupWise 6 snap-in modules allow ConsoleOne to understand and display GroupWise-specific schema extensions. These snap-in modules also access the WPDOMAIN.DB files that GroupWise uses as its directory store.
The GroupWise 6 snap-in modules are copied to directories underneath the ConsoleOne directory. If you ever want to disable the GroupWise snap-in modules for ConsoleOne, you simply cut and paste the GROUPWISE folder to another location. When you want ConsoleOne to know about GroupWise objects, you can copy the GROUPWISE folder back to the ConsoleOne directory.
Creating a GroupWise 6 Software Distribution Directory
The GroupWise 6 software distribution directory is similar to the GroupWise 5.x software distribution directory. Novell recommends that you do not overwrite a GroupWise 5.x software distribution directory during the GroupWise 6 upgrade. Instead, you should create a new directory for the GroupWise 6 software distribution directory.
Updating an Existing GroupWise 5.x System
When you first load ConsoleOne with the GroupWise snap-in modules and select the location of the GroupWise primary domain, the installation wizard copies the GroupWise 6 GWDOM.DC and GWPO.DC files from the GroupWise CD to the root of the domain directory. The installation wizard also installs the GroupWise 6 NGWGUARD.DC file to the domain\WPOFFICE folder.
If the WPOFFICE folder does not exist, the installation wizard does not copy the NGWGUARD.DC file into this folder. Unfortunately, this can cause problems with the upgrade of your post offices. Consequently, you must ensure that this file exists before you begin the upgrade process.
Installing GroupWise Agents
The GroupWise MTA and POAs really do all of the work to upgrade a GroupWise system. During the installation process, you are encouraged to install the GroupWise agents on the server that houses the primary GroupWise domain database. Although you can run agents remotely on another server, Novell generally recommends that you don't choose this configuration.
Upgrading the GroupWise Primary Domain
You must upgrade the primary domain to GroupWise 6 before you upgrade any other domain or post office in your GroupWise system. (See Figure 2.) The GroupWise 6 MTA cannot upgrade the secondary domain until the primary domain sends a message to the secondary domains, confirming that the primary domain is running GroupWise 6.
When a GroupWise 6 MTA loads against the primary domain for the first time, that MTA looks in the domain directory at the "#VERSION=NNN" line of the GWDOM.DC file. The MTA then compares this value with the GroupWise version in the WPDOMAIN.DB file. A GroupWise 6 GWDOM.DC file reads as follows:
#VERSION=600When the GroupWise 6 MTA detects this difference in the GWDOM.DC file, the MTA begins to recover the WPDOMAIN.DB file to incorporate the new fields defined in the GroupWise 6 GWDOM.DC file. While the GroupWise WPDOMAIN.DB file is being rebuilt, the following events occur:
The MTA first makes a complete copy of the WPDOMAIN.DB file in the domain directory and calls this file RECOVER.DDB. The MTA then creates a CREATING.DDB file in the domain directory. If you were to watch the CREATING.DDB file as the MTA recovers the WPDOMAIN.DB file, you would not see the size of the file increment. The file increments in size at the end of the recovery operation. After the CREATING.DDB file is completed, the MTA puts an internal record lock on the primary domain WPDOMAIN.DB file and carves this file out from the header down. The MTA then replaces the information in the WPDOMAIN.DB file with the information from the CREATING.DDB file. By viewing the Admin Status at the GroupWise MTA (select F10|Admin Status), you can see that the Status reads "Recovering."
While the GroupWise primary domain is being recovered, the administrative thread of the MTA ceases processing administrative-type messages. The MTA continues to handle other messages sent for the primary domain.
After the GroupWise 6 MTA has recovered the WPDOMAIN.DB file, the MTA sends a message to all of the other GroupWise domains, adding a new kind of record to their databases. This record is the GroupWise 6 version record. As mentioned earlier, until this new version record has been sent to the secondary domains (confirming that the primary domain has been upgraded), you cannot upgrade a secondary domain to GroupWise 6. The GroupWise 5.x snap-in modules for the NWADMIN utility do not display the 6 version number when you view the properties of the primary domain. These snap-in modules show only that a GroupWise 6 domain is version 5.0 or 5.5 or some other 5.x variant. If you use ConsoleOne, on the other hand, you can see that the primary domain is version 6.
Upgrading a Secondary Domain
GroupWise secondary domains are upgraded in almost the same manner as the primary domain. You should be aware of the following when upgrading a GroupWise 5.x secondary domain to GroupWise 6:
The GroupWise 6 agent software (MTA and POA) must be installed on the server where the MTA for that GroupWise domain runs.
The first time the GroupWise 6 MTA loads, it looks at the version record of the secondary domain. The GroupWise 6 MTA then looks at the version record of the primary domain. (The GroupWise 6 MTA does not look at the domain database of the primary domain. The GroupWise 6 MTA simply checks its own record of the primary domain object.)
If the GroupWise 6 MTA discovers that the primary domain has been upgraded to GroupWise 6, the MTA running at the secondary domain then checks the version of the GWDOM.DC file in the secondary domain's directory to see whether or not the GWDOM.DC file has been upgraded to GroupWise 6.
If the GWDOM.DC file is indeed a GroupWise 6 file, the GroupWise 6 MTA begins to recover the domain database, following the same procedures as outlined for the primary domain.
If the GWDOM.DC file is not a version 6 file, the GroupWise 6 MTA requests that the primary domain send the GroupWise 6 GWDOM.DC, GWPO.DC and NGWGUARD.DC files to the secondary domain. When the secondary domain MTA receives these files, it copies the GWDOM.DC and the GWPO.DC files to its domain directory. The MTA also copies the NGWGUARD.DC file to the domain\WPOFFICE folder. After copying these files, the GroupWise 6 MTA restarts itself.
When the GroupWise 6 MTA restarts, it goes back through its routine of checking versions and determines that the needed *.DC files are available to begin a recover operation. The MTA then follows the recover steps outlined under the "Upgrading the GroupWise Primary Domain" section.
Upgrading a GroupWise Post Office
A post office upgrade happens in the following manner:
The GroupWise 6 agent software (MTA and POA) is installed on the server where the POA loads against a GroupWise post office.
When the GroupWise 6 POA loads, it checks if the version of the post office's WPHOST.DB file matches the version of the domain the post office is in or if the domain is version 6. Because the versions that the POA uses to compare are contained in the WPHOST.DB file, the POA does not need to access the domain database to obtain the version number. If the domain that owns this post office is a GroupWise 6 domain, the POA requests the GWPO.DC and NGWGUARD.DC files from the domain's MTA. The MTA retrieves the GWPO.DC file from the folder in which the domain is located and retrieves the NGWGUARD.DC file from the domain\WPOFFICE folder.
After the GroupWise 6 POA receives the new NGWGUARD.DC and GWPO.DC files, the POA recovers the WPHOST.DB file and makes it a GroupWise 6 WPHOST.DB file. While this file is being recovered, the POA copies a complete backup of the old WPHOST.DB file and renames this file RECOVER.HDB. The POA also creates the new WPHOST.DB file in a file called CREATING.HDB. After the CREATING.HDB file is completed, the POA puts an internal record lock on the post office WPHOST.DB file. The POA carves the file out from the header down, replacing this information with information from the CREATING.HDB file. Note. If you are a trivia buff, you may notice that GroupWise 6 uses a CREATING.DDB file for the domain database and a CREATING.HDB file for the post office database. The D stands for domain, and the H stands for host. Of course, this naming convention is based on WordPerfect Office's domains and hosts.
If the GroupWise 6 POA has access to the software distribution directory, the POA will copy the files from the software distribution directory\CLIENT\OFVIEWS\WIN folder to the post office\OFVIEWS\WIN folder. If the POA does not have access to the software distribution directory, you will need to manually copy the views to the post office directory.
The NGWGUARD.DC file contains new record-type information that should be incorporated into the NGWGUARD.DB file. The GroupWise 6 POA rebuilds the NGWGUARD.DB file to incorporate this information. The NGWGUARD.DB is now a GroupWise 6 file.
The GroupWise 6 NGWGUARD.DB file contains new record-type information that will need to be incorporated in each user database. The first time a user logs in to a GroupWise 6 post office with a GroupWise 6 client, the new record information from the NGWGUARD.DB file is merged into the user's database.
Message databases in the post office\OFMSG folder are updated on-the-fly when a new GroupWise 6 field needs to be incorporated.
Files in the post office\OFFILES folder are not upgraded in any manner.
Upgrading to GroupWise 6 Gradually
Most companies will roll out GroupWise 6 gradually. GroupWise 6 does support this approach, although you should keep the following things in mind:
The GroupWise 6 WebAccess agent is not designed to access a GroupWise 5.x post office. According to Novell, only the GroupWise 5.5 Enhancement Pack WebAccess agent with Support Pack 3 can access a GroupWise 6 post office. (Support Pack 3 is not yet released. You can check http://support.novell.com/ periodically to see when this support pack is released.) As you upgrade to GroupWise 6, make sure that you have a WebAccess solution for all GroupWise users.
A user running the GroupWise 6 client cannot proxy to a GroupWise 5.x post office.
You should associate GroupWise 6 soft-ware distribution directories only with GroupWise 6 post offices. If you associ-ate a GroupWise 5.x post office with a GroupWise 6 software distribution directory, users will be prompted to upgrade their GroupWise client prematurely.
The rollout of the GroupWise 6 client does not need to correspond with the actual upgrade of a GroupWise post office. You simply cannot upgrade the client before you upgrade the post office.
CONCLUSION
Novell has designed the GroupWise 6 upgrade process to be fairly painless, and we found that for the most part it was. If you keep in mind the key points outlined in this article, you should be able to avoid any pitfalls in upgrading your company's GroupWise system.
A Master CNE, Tay Kratzer has supported Novell GroupWise for eight years. Tay writes for Novell's GroupWise Cool Solutions magazine and co-authored Administering GroupWise 5.5, which is published by McGraw Hill. Tay is also the winner of the Software Support Professionals Association's year 2000 "Outstanding SuperStar" award.
Danita Zanrč has been using GroupWise since 1989, when its predecessor was known as WordPerfect Office 2.0. She is experienced in all aspects of GroupWise, from design and installation to training administrators and users. Danita is one of the primary consultants responsible for the day-to-day operations of Caledonia Network Consulting and is the coauthor of the GroupWise 5.2 Administrator's Guide and GroupWise 5.5 Administrator's Guide. (For information about these books or to purchase the GroupWise 6 Upgrade Guide, visit http://www.caledonia.net/.) Danita is also a sysop on the Novell Support Connection (http://support.novell.com/).
* Originally published in Novell Connection Magazine
Disclaimer
The origin of this information may be internal or external to Novell. While Novell makes all reasonable efforts to verify this information, Novell does not make explicit or implied claims to its validity.