Get to know GroupWise 2014

Wikis > Caledonia Private Wiki > Get to know GroupWise 2014

Danita and Paul here! Are you ready for a change? We sure hope so, because GroupWise 2014 is full of change and new functionality. Some of it will be intuitive, and some not so much. Hopefully by purchasing this book you will get through the newness of GroupWise 2014 without too much trouble.

As long-time GroupWise administrators, users and consultants, GroupWise 2014 brings with it many changes for us. We’ve both used GroupWise since before it was GroupWise! Danita started with WordPerfect 2.0 in 1989, and Paul started with WordPerfect Office 3.0 in 1991 and we’ve used every version since. Here’s a little history that can help you appreciate just what is going on with GroupWise 2014.

Firstly, we do not wish to offend any long-time WordPerfect Office/GroupWise lovers, but we are not going to dwell too much on WordPerfect Office 2.x and 3.x. We will say that WordPerfect Office 3.x had great functionality, and was truly “enterprise worthy” in many respects. However, the seeds of the GroupWise that we know and love really started with WordPerfect Office 4.0 in 1993. This is when the FLAIM database became the engine (and some speculate FLAIM was one of the driving forces for Novell wanting to acquire WordPerfect Corporation), and the directory structure that we know and love actually came into being. If you’ve ever wondered why many directories in “GroupWise” are prefixed with wpcs, that is because it stood for “WordPerfect Connection Server”, the original name of the Message Transfer Agent.

The “migration” from GroupWise 4.1 to GroupWise 5.0 was a really big deal. The 4.x versions of our beloved collaboration system were still rather simple in administration. A stand-alone administration tool, ad.exe, and a few command line utilities that did all of the work. When GroupWise 5.x came along, you were going to need NetWare 4.x and “NDS” (now eDirectory). We installed GroupWise at MANY sites in the beginning where we put a lone NetWare 4.x server with NDS on a desktop somewhere, and it often got turned off when no one needed to administer GroupWise! GroupWise 5.0 killed DOS, OS/2 and Unix agents (and we thought having to give up NetWare and the Mac/Linux clients with GroupWise 2012 was painful)! It dumped all character based clients for DOS and Unix. It was a major undertaking for most of the sites that had really just gotten started with their WPO/GroupWise systems. It was definitely not for the faint of heart. In fact, in the very first GroupWise Administrator’s Guide that Danita co-wrote with Richard Beels and Scott Kunau for Sybex Network Press, she penned this:

“How many of us have received an upgrade to a software package in the mail and just “gone for it”? Most of us are tempted to install software without advanced planning. The likelihood of a successful GroupWise 4.1-to-5.x migration in such a scenario is slim. Although many of the basic concepts behind GroupWise 5.x are familiar to GroupWise 4.x administrators, some major changes have occurred that impact the decision of how and when to move from GroupWise 4.x.”

Looking back at the level of difficulty in a GroupWise 4.1 to 5.x migration, we can only smile. In many ways that was child’s play compared to some of the changes that are included with GroupWise 2014. This is especially valid when you take into consideration that by the time of the initial GroupWise 5.0 release (1996) the familiarity with the basic structure was only 4 years in the making. We’ve had a relatively “consistent” GroupWise now for 17 years, and there is a certain comfort level among seasoned GroupWise administrators that could very well encourage folks to leap before they look.

Of course the biggest change that is introduced with GroupWise 2014 is the new web based Administration Console. Many folks will be inclined to compare it with the move from NWAdmin to ConsoleOne. Sorry! This is so much bigger than that. Think more in terms of how you felt when you originally moved from ConsoleOne to iManager for many Novell related tasks (albeit never for GroupWise, which managed to avoid iManager altogether – to mixed reviews). We’ll warrant that no matter how much you thought you disliked ConsoleOne, you were lost and confused initially when you were faced with finding the new way to deal with once familiar tasks. However, for those of you who have fallen in love with iManager now, GroupWise 2014 has an iManager plugin, which we will discuss later in this guide.

We do want to assure you that the GroupWise team has done a really great job with the new Administrative Console. There was a great deal of thought and planning that went into designing this new administration tool, and it seems apparent that they also took into account some of the major complaints that revolved around the initial rollout of iManager and attempted to prevent the same frustration and confusion. That said, there is much that is simply “different” in the way the new administration model works, and you will really want to be prepared for real change when you make your move to GroupWise 2014.

We will discuss all of the changes that you need to know about GroupWise 2014 in the next chapter, “Preparing Your GroupWise System”. There are, however, two major changes that need to be addressed before you continue.

With GroupWise 2012, Novell discontinued NetWare as a server platform for GroupWise. This means that if you are still on NetWare, moving to GroupWise 2014 will not be a simple upgrade. Rather, we will need to do a migration/upgrade.

Novell does not support upgrading directly to GroupWise 2014 from any versions older than GroupWise 8. Thus if you have a GroupWise 7 or older system, you may need to do a two step upgrade for GroupWise 2014. That said, we have upgraded as far back as GroupWise 6.5 . We do not see any major problems upgrading from GroupWise 5.0 or later.

A Few Important Conventions

In writing this book, we’ve endeavored to be as consistent as possible with formatting and naming. Here are a few of the key things to keep in mind:

  • URLs are shown in all lowercase.
  • Filenames and locations are shown all in lowercase and in this format: filename.ext. Since this book must take into account Linux case sensitivity, we have opted to show all commands and file names in lowercase to help avoid confusion for administrators working with multiple OSs. If, however, a Linux process is in mixed case (like running /usr/ConsoleOne/bin/ConsoleOne), we will of course show the case requirements for the command.
  • Information you must type, or commands you must execute will be formatted like this: setup.exe.
  • We will refer to this version as GroupWise 2014 in this book, with the version number typically listed as merely 14.
  • Since GroupWise Linux files always have the build number included in the file name (for example novell-groupwise-server-14.0.0-115059.x86_64.rpm), the names we show in this book might not have the same build number as your software. Substitute your build number in any commands we list in the guide.
  • This guide is of course written for both Linux and Windows. We admittedly use Linux more for our own personal use. We will attempt to keep terminology straight. However, when we discuss the GroupWise “Server” directories on your server, these will be:
    • Linux: /opt/novell/groupwise/
    • Windows: c:\Program Files\Novell\GroupWise Server\

These GroupWise Server directories will be abbreviated throughout this guide as <serverfiles>/ and as an example, c:\Program Files\Novell\GroupWise Server\agents\data will be simply listed as <serverfiles>\agents\data

  • The installation files that you extracted from your download will be referred to as <installationfiles>/ and as an example we might refer to the install.sh file being at <installationfiles>/install.sh

We ask Windows administrators’ forgiveness in advance if we occasionally just give the Linux paths to locations! Just substitute the Windows paths above when in doubt! Linux and Windows administrators alike should remember that Linux uses forward-slashs and Windows users back-slashes!

How This Guide is Organized

The new upgrade procedures for GroupWise 2014 have necessitated a bit of a rework of our former upgrade guide organization. Rather than having separate chapters for upgrading the Primary Domain and Secondary Domains, all domain upgrades will be covered in a single chapter. You must simply remember that the FIRST domain to upgrade must be the primary. We will discuss upgrading a Post Office alone on its own server, and we will also combine a Post Office upgrade with a Domain on the same server in the Domain chapter. The GWIA chapter will be more of an overview of strategies for upgrading the GWIA, as it will be upgraded automatically with its Domain, and that is covered in the Domain chapter.

We are upgrading from GroupWise 8 and GroupWise 2012, and while we have tested GroupWise 6.5, Novell is not testing (and thus not officially supporting) any version prior to GroupWise 8 for a direct upgrade. Any time there is a version specific process to be dealt with, the version will be noted. We will upgrade our primary domain CNC, our CNC2 secondary domain, and our Caledonia post office in this guide. Additionally, we will upgrade our GroupWise Internet Agent, WebAccess, GroupWise Monitor, Calendar Publishing Host, and a couple of clients to usher you on your way.

Our figures may show GroupWise 2012 objects, GroupWise 8 objects, and in some cases perhaps even GroupWise 6.5 objects. We have tested upgrades with systems as old as GroupWise 6.5.

If you are upgrading in place, follow the procedures and sections outlined in _____________.

If you are moving/migrating your GroupWise system to a new server, follow the procedures and sections outlined in ___________,