Novell Home

Freshly Updated: The GroupWise 6 Upgrade Guide

Novell Cool Solutions: Feature
By Danita Zanre, Tay Kratzer

Digg This - Slashdot This

Posted: 18 Sep 2002
 

Heads up: GroupWise experts Tay Kratzer and Danita Zanrè have updated their GroupWise 6 Upgrade Guide to include information specific to GroupWise 6, Support Pack 2. We have been given permission to publish Chapter 6 here on Cool Solutions for you. Chapter 6 contains exclusive information about SETUPIP that isn't published anywhere else.

The GroupWise 6 Upgrade Guide provides insights into upgrading your GroupWise system to GroupWise 6.

Topics include:

  • Upgrading to GroupWise 6 Gradually
  • Extending the NDS Schema
  • Installing the GroupWise 6 Software Distribution Directory
  • Installing GroupWise Administration
  • Disabling GroupWise 5.x Administration
  • Upgrading the Primary Domain
  • Upgrading GroupWise Secondary Domains
  • Upgrading GroupWise Post Offices
  • Upgrading The GroupWise Internet Agent (GWIA)
  • Upgrading GroupWise WebAccess

Purchase the GroupWise 6 Upgrade Guide here.

Chapter 6: Upgrading the Windows Client

Implementing a GroupWise Client Upgrade

Upgrading the GroupWise client to GroupWise 6 can be done at whatever pace you may like. However, it's important that you do not try and upgrade users' clients to the GroupWise 6 client before their post office has been upgraded to GroupWise 6. In this chapter we discuss solutions and ideas that you really cannot find adequately documented anywhere else. For example, wouldn't it be nice to upgrade the GroupWise client in an automated fashion? Or if you know how to do that, wouldn't it be nice to upgrade the GroupWise client for a controlled set of users, rather than an entire post office of 500 people in the same day? What if you wanted to audit who has been upgraded to the GroupWise 6 client? All of these ideas are explained in this chapter.

In this chapter we discuss the Auto-update Algorithm in detail. It is best to absorb all of the concepts regarding the "Auto-update Algorithm" before proceeding in any manner. Even if you have a slick software distribution solution, such as Novell's ZenWorks product, the Auto-update Algorithm is good to understand.

We also discuss four different methods of upgrading the GroupWise clients to GroupWise 6. Here they are:

  • Upgrading all users belonging to a particular GroupWise post office. The users will have a mapped drive and rights to the GroupWise <SDD>\CLIENT folder. This is the default manner in which the GroupWise client is designed to upgrade.


  • Upgrading all users belonging to a particular GroupWise post office using SETUPIP which does not require that the users have a mapped drive to the SDD.


  • Upgrading some of the users in a GroupWise post office to the GroupWise 6 client. The value of this is, if you have 700 users on a post office, you may not want to have all of them upgrade to the new GroupWise 6 client in one day. The helpdesk doesn't like that! This method is something Tay has cooked up for use at some of his customer sites. This solution assumes that your users are using the Novell NetWare client.


  • Upgrading the GroupWise client by distributing the SETUPIP utility through an E-mail message. This is particularly helpful when you have GroupWise remote users whose clients need to be upgraded. And finally, we will discuss a way to audit the progress of your upgrade to see which users have actually managed to receive the new client through whatever method you choose for your client upgrade.

The Auto-Update Algorithm

The Auto-update Algorithm is how the GroupWise client, installed at end-users' computers, knows it should upgrade itself to a newer version of the GroupWise client. By using the Auto-update Algorithm to your benefit, you can automate the process of upgrading the GroupWise client with little or no interaction required by your end-users. Here's how it works, let's start from the top:

GroupWise has "Software Distribution Directories" (SDD for short, it'll save on so much typing!). These directories house the GroupWise software after it has been installed from the CD. When patches are released, they are applied to a GroupWise Software Distribution Directory. A GroupWise SDD is not only a location for software, but it can be defined in GroupWise Administration and assigned to post offices. In GroupWise 6 using ConsoleOne, the GroupWise Software Distribution Directories are defined under Tools|GroupWise System Operations|Software Directory Management. See Figure 6-1.

Figure 6-1: GroupWise Software Distribution Directory Management

A GroupWise SDD has a value called a "bump" number associated with it. The "bump" number starts at "0" and can be incremented to 1, then 2, then 3, etc. Later on we will discuss more on how and why to increment the bump number on a SDD. Controlling the bump number is essential to controlling the GroupWise client upgrade process.

Every GroupWise post office should have an SDD associated with it. In fact, when you go to create a GroupWise post office, one of the required fields is the SDD that will be associated with the post office. You can configure an SDD that can be used by several post offices. For upgrade purposes, creating post office specific SDDs is often the best practice. An SDD is primarily used so that the GroupWise client knows where to look in order to upgrade itself to a newer version of GroupWise. Even if you intend to use a solution such as ZenWorks, GroupWise requires you to define which SDD is to be used each post office. To see or change the SDD associated with a GroupWise post office, view the properties of that post office and select the "Post Office Settings" property page from the GroupWise tab. See Figure 6-2.

Figure 6-2: The SDD Associated with a Post Office

The GroupWise SDD should and typically will have the GroupWise 32-bit client installed into it. The GroupWise client is located in the <SDD>\CLIENT folder. Sites using the GroupWise SDD for GroupWise client software distribution must grant end-users Read and File Scan rights to the <SDD>\CLIENT folder and subfolders of the <SDD>\CLIENT folder. Users should not have rights in any other location of the SDD. If you are using ZenWorks or a similar solution, or if you use "SETUPIP" which is explained later in this chapter, it is not essential that end-users have rights to the SDD. Figure 6-3 shows a GroupWise post office with a post office specific SDD placed off of the root of the post office.

Figure 6-3: A GroupWise SDD Located at a Post Office

When you define a Software Distribution Directory, the path to the SDD should not include "CLIENT". The "CLIENT" portion is assumed, so the directory that is the parent to the "CLIENT" directory is where the SDD should point to. In the <SDD>\CLIENT folder are two files that are an essential part of the GroupWise upgrade, and Auto-update Algorithm. These files are SOFTWARE.INF and SETUP.CFG. In addition to these files from the SDD, a value in the WPDOMAIN.DB and the WPHOST.DB files known as the "Bump" number is an essential part of the Auto-update Algorithm. All of these factors are detailed below.

SETUP.CFG

The SETUP.CFG file resides in the <SDD>\CLIENT directory. This is a "template" file that allows the administrator to customize the way in which the GroupWise client is installed at the user's workstation. Rather than explain the SETUP.CFG file, we have included a copy of the configured SETUP.CFG file for Missive Corporation. This SETUP.CFG file has been modified from the SETUP.CFG that originally shipped from Novell. To save space we have placed this SETUP.CFG file in a table. It should be read first down the left-hand column, and then down the right-hand column to match the order of the actual file.

SETUP.CFG CONTENTS
[GroupWiseSetup]
Version=6
StandardInstall=Yes
Path=C:\Novell\GroupWise
Folder=GroupWise
;DefaultIPAddress=x.x.x.x
;DefaultIPPort=xxxx

[ShowDialogs]
HideAllDialogs=Yes
Welcome=No
SetupOptions=No
DestinationDirectory=No
SelectOptionalComponents=No
SelectProgramFolder=No
SelectStartUpFolderSoftware=No
LanguageSelection=No
SoftwareIntegrations=No
StartCopyingFiles=Yes
SetupComplete=Yes

[AutoUpdate]
Enabled=Yes
SetupIPEnabled=Yes
ForceUpdate=Yes
GraceLoginCount=0
PromptUntilUpdated=Yes

[Startup]
Notify=No

[GWTIP]
Default=Yes
Hide=No
Workstation=Yes

[GWMAILTO]
Default=Yes
Hide=No
Workstation=Yes

[GWCHECK]
InstallGWCheck=Yes
GWCheckEnabled=Yes
[IntegrationApps]
Lotus WordPro=No
Microsoft Binder 97=No
Microsoft Excel 7.0=No
Microsoft Excel 97=No
Microsoft Excel 2000=No
Microsoft PowerPoint 97=No
Microsoft PowerPoint 2000=No
Microsoft Word 7.0=No
Microsoft Word 97=No
Microsoft Word 2000=No
Corel Presentations 7.0/8.0/9.0=No
Corel Quattro Pro 7.0/8.0=No
Corel Quattro Pro 9.0=No
Corel WordPerfect 7.0=No
Corel WordPerfect 8.0=No
Corel WordPerfect 9.0=No

[Languages]
Default=English
Arabic=No
ChineseSimplified=No
Chinese=No
Czech=No
BrazilianPortugese=No
Danish=No
Dutch=No
English=Yes
Finnish=No
French=No
German=No
Hebrew=No
Hungarian=No
Italian=No
Japanese=No
Korean=No
Norwegian=No
Polish=No
Russian=No
Spanish=No
Swedish=No
Thai=No
Turkish=No

The important settings for the SETUP.CFG file as pertains to the Autoupdate Algorithm are under the [AutoUpdate] section. The "Enabled" value must be set to "Yes" in order for the automatic update to occur.

SOFTWARE.INF

The SOFTWARE.INF file is an ASCII file containing a small amount of information. In fact here are the entire contents of the SOFTWARE.INF file from the GroupWise 6 SDD.

[General]
BuildNumber=2042

That's it! The BuildNumber is really the version number in development terms. GroupWise development releases versions of the GroupWise software in versions that you and I typically know as 5.5, 5.5.2, 6.0.0, 6.0.1 or 6.0.2. The BuildNumber of 2042 is the GroupWise 6.0.2 client which is GroupWise 6 with Support Pack #2 applied. The BuildNumber version of the GroupWise 6 Support Pack #3 client (which is has not released and won't be for a while after Support Pack # 2) could very well be "2060", (we don't know this - this is just for the sake of discussion). This would mean that at Novell, before the GroupWise client was released for Support Pack #3, there were 18 build cycles of the GroupWise client between Support Pack #2 and Support Pack # 3. Now here's what the BuildNumber means to the Auto-update Algorithm. Whenever the GroupWise client is installed, the BuildNumber of the GroupWise client is put into the Windows registry. The BuildNumber string value is kept in the following location:

HKEY_LOCAL_MACHINE\SOFTWARE\Novell\GroupWise

See Figure 6-4 which is a screen shot of the Windows registry. I'm sorry to expose you to the Windows registry. I know it gives some people the creeps!

Figure 6-4: The GroupWise BuildNumber in the Windows Registry

The Bump Number

Now we need to digress for a moment in order to fully explain the relevance of the BuildNumber. You might remember that every GroupWise post office has a SDD associated with it. The SDD has a "Bump" number associated with it. Each time the GroupWise client loads, it asks for the Bump number associated with the SDD for the end-user's post office. This Bump number is obtained for the GroupWise client from the WPHOST.DB file. When the GroupWise client loads and contacts the POA, the conversation goes something like this:

CLIENT: Hi Post Office Agent (POA) at IP address 192.168.100.237, port 1677. I need a Client/Server session with you. Here are my authentication credentials.

POA: Here's a Client/Server session, and here's the port we will speak at.

CLIENT: Hey POA, before I completely load the User Interface of this client, what is the Bump number for the SDD associated with my post office.

POA: It's "5".

CLIENT: Ok, let's see, the last time I installed the GroupWise client the Bump number was "4". This is held in the Windows registry at the following location:

HKEY_LOCAL_MACHINE\SOFTWARE\Novell\GroupWise\Client\5.0 The value is called "NewSoftwareBump"

In our example, we find that the Bump number for the SDD is different than the Bump number in the Windows registry. Thus, the GroupWise client must look further to see if it is essential to upgrade the GroupWise client. Let's keep going.

CLIENT: Hey POA, what's the location of my SDD.

POA: It's in the DENVER\MAIL:DENPO\GW6 folder.

CLIENT: Ok, let me look at the DENVER\MAIL:DENPO\GW6\CLIENT folder, and look at the SOFTWARE.INF file. The BuildNumber is "2024" in the <SDD>\CLIENT\SOFTWARE.INF file, and the BuildNumber in the Windows registry on my machine is "1807". It seems like it's time to upgrade. Now let me check one more thing. I'll just look at the SETUP.CFG file in the <SDD>\CLIENT\WIN32 folder to see if the "[AutoUpdate]" section of this file has a line that reads: "Enabled=Yes". Yes it does! It's upgrade time!

So here's a quick synopsis of what you just learned:

If the BUMP for the SDD associated with a post office is DIFFERENT (not higher per se, just different) than the BUMP in the Windows registry then the client compares the BUILD in the SOFTWARE.INF file with the BUILD in the Windows registry.

If the BUILD in the SOFTWARE.INF file is GREATER THAN the build in the Windows registry then the GroupWise client looks at the SETUP.CFG file.

If the [Auto-Update] section in the SETUP.CFG files contains "Enabled=Yes," the GroupWise client will attempt to upgrade itself.

The GroupWise client will then upgrade itself by using one of the configurations that is detailed in the following sections.

Upgrading All Users on a Post Office with a Mapped Drive to the SDD

The GroupWise administrator can fully configure what end-users will see during the GroupWise client upgrade, and just what will be installed. Before we get into the steps of the upgrade, let's explain Missive Corporation's technical directives with the upgrade of the GroupWise client.

  1. End-users will be forced to update their GroupWise client.
  2. End-users should not be asked any questions regarding components to install etc.
  3. GroupWise Document management integration will not be enabled by default
  4. GroupWise Notify will not be put in the Windows startup folder
  5. GroupWise Tips will be enabled
  6. The Mail To functionality from the user's browser will be implemented
  7. The client version of GWCHECK will be installed
  8. The Language is English. Users will not be prompted for the language.

Here are example procedures for upgrading a post office. Our hope is that after reading this section you can easily modify this scenario to match the needs of your organization.

  1. Create a GroupWise 6 SDD. The SDD that you create needs only a full copy of the CLIENT folder and subfolders from a GroupWise 6 SDD. At our example company "Missive Corporation" there's a complete or "Master" GroupWise 6 SDD created by Tay Kratzer, the GroupWise administrator at Missive Corporate Headquarters. If you need a refresher on creating a complete GroupWise 6 SDD, you can refer back to Chapter 3 of this book. At Missive Corporation, the Master Group- Wise 6 SDD is located at MCORP01\APPS\GW6. This GroupWise 6 SDD is used only as a master Software Distribution Directory. It is not associated with any post offices. All other GroupWise administrators have only Read and File Scan rights to this SDD. Tay is going to upgrade the users on the PALO_ALTO_PO post office. Tay creates a folder off of the post office directory called GW6 and copies the <GroupWise 6 SDD>\CLIENT folder structure to the <post office>\GW6 directory. You are welcome to put the SDD in some other location than the post office directory. However, there is no harm done in putting it in a folder off of the post office, so long as the users have rights to this location and no other folders or files in the post office directory structure.

  2. Go to the <post office>\GW6\CLIENT folder, and find the SETUP.CFG file. Copy the SETUP.CFG file to the <post office>\GW6\CLIENT\WIN32 folder. Then edit the SETUP.CFG file. When installed, this file defaults to a read-only file. You need to change this attribute. In Windows Explorer, you can remove the read-only attribute by changing the properties of the file, and unchecking the readonly attribute. The technical directives numbered 1 through 7 at the beginning of this section can be fulfilled with the SETUP.CFG file as follows:
    • [AutoUpdate] - ForceUpdate=Yes
    • [ShowDialogs] - HideAllDialogs=Yes
    • [IntegrationApps] - all apps have a value of No
    • [Startup] - Notify=No
    • [GWTIP] - Default=Yes; Workstation=Yes
    • [GWMAILTO] - Default=Yes; Workstation=Yes
    • [GWCHECK] - InstallGWCheck=Yes; GWCheckEnabled=Yes
    • [Languages] - Default=English; English=Yes

  3. After the SETUP.CFG file is modified, the SETUP.INI file needs to be edited. This file is found in the <post office>\GW6\CLIENT\WIN32 folder. This file lets you control whether users will be prompted for a language. At Missive the end-users will all use English, so they should not be prompted for the language. In this file, change
    EnableLangDlg=Y
    To
    EnableLangDlg=N
  4. Go into ConsoleOne, and define the newly created SDD. Select Tools|GroupWise System Operations|Software Directory Management. Click the create button. Give the Software Distribution Directory a name. For example PALO_ALTO_PO GW6 SDD. See Figure 6-5.

    Figure 6-5: A Newly Defined GroupWise 6 SDD

    Warning: taking the next steps can cause the GroupWise clients to upgrade the next time users log into GroupWise.

  5. Assign this new GroupWise 6 SDD to the post office. To do this, edit the properties of the post office and select the "Post Office Settings" property page from the GroupWise tab. In the Software Distribution Directory field, select the appropriate SDD for this post office. See Figure 6-6.

    Figure 6-6: Selecting a Newly Created GroupWise 6 SDD For A GroupWise Post Office

  6. Step 5 may have been enough to kick off the auto-update process. But there's a chance that it didn't. Here's why. If the original GroupWise 5.x SDD for the post office you are upgrading had the same Bump number as the SDD for the GroupWise 6 SDD you just created, then the GroupWise client doesn't pick up on a Bump number change. A change in the Bump number is the first part of the Auto-update Algorithm, so the Bump number must change before GroupWise will discover the new GroupWise client it should upgrade to. You should identify the Bump number of the GroupWise 5.x and GroupWise 6 SDD to see if you need to increment the GroupWise 6 SDD to kick off the upgrade process. Here's how you do this:
    1. On the computer where you are running ConsoleOne, exit ConsoleOne if it is loaded.
    2. Create a file at the root of the C: Drive called "gwsupp.fil". This file does not have to have anything special in it, it can just be an ASCII file with any characters inside it. Just make sure it has the exact name of gwsupp.fil.
    3. Run ConsoleOne, and you should see in ConsoleOne the menu option "GroupWise Diagnostics" under the Tools menu.
    4. Choose Tools|GroupWise System Operations|Software Directory Management, and fill in the description field of the GroupWise 5.x SDD that is currently assigned to the post office. Do the same for the GroupWise 6 SDD that you are preparing for the post office. This will allow you to determine which SDD is which in step 6.e.
    5. Select the menu option Tools|GroupWise Diagnostics|Record Enumerations. In the drop down list, select "Areas by ID". Find the GroupWise 5.x SDD that was originally defined for the post office you are upgrading.
    6. Compare the "Software Version" number (which is really the "Bump" number) of the GroupWise 5.x and GroupWise 6 SDDs. Are they different from each other? If they ARE NOT different, the GroupWise client will not know that it needs to upgrade. If they ARE different, and even if the GroupWise 6 SDD's "Software Version" is lower, the GroupWise client will detect the change in the bump number which will factor into the Auto-update Algorithm.
    7. If you need to increment the "Software Version" of the Group- Wise 6 SDD (i.e., if the GroupWise 5.x SDD and the GroupWise 6 SDD have the same "Software Version" number) go back into Tools|GroupWise System Operations|Software Directory Management, and highlight the GroupWise 6 SDD. Select the "Update" button, and then check the "Force auto-update check by GroupWise components" option. Click the "OK" button. This action will increment the Software Version/Bump number by 1.

    The next time that users try to log into GroupWise, their client will detect a change in the GroupWise client, which will begin the process initiated by the Auto-update Algorithm to upgrade the users.

Upgrading the GroupWise Client Using SETUPIP

Using the SETUPIP utility, users can upgrade the GroupWise client without needing a drive mapping to a file server. This solution is particularly useful for administrators who have post offices with users spread throughout the NDS tree, without easy file access to an SDD, or perhaps even GroupWise users who have no NDS accounts at all.

The SETUPIP functionality can exist alongside the Mapped drive solution discussed earlier in this chapter. Thus, if a user does have rights to the SDD for the post office, the GroupWise client will run the SETUP.EXE from the <SDD>\CLIENT\WIN32 directory. On the other hand, if a user does not have rights to the SDD, then the <SDD>\CLIENT\WIN32\SETUPIP.EXE utility will kick in, and the user will upgrade via an IP connection to the POA and a web server.

You do not necessarily have to use SETUPIP in conjunction with your post office software distribution method. But you can generate a SETUPIP.EXE and send it to remote users, or put it on a web server for your at-home or mobile users to download. The SETUPIP.EXE file is pretty small (180 KB), so it's kinda like distributing the GroupWise client without the need to burn CDs. Here are the architectural concepts behind SETUPIP. It is important that you have read the preceding sections of this chapter to fully understand the workings of SETUPIP.

When a GroupWise client detects that the Bump number for the user's post office is different than the Bump number in the Windows Registry, it seeks to find the SOFTWARE.INF file, and a SETUP routine such as the SETUP.EXE in the <SDD>\CLIENT\WIN32 folder. If the GroupWise client determines that it does not have the capacity to get a drive letter mapping to the SDD for the post office, it asks the POA to help the client get it's hands on the SOFTWARE.INF file from the <SDD>\CLIENT directory.

It's important that the GroupWise POA have access to the GroupWise SDD in order to retrieve the SOFTWARE.INF for the GroupWise client. For this reason, it's generally best to house the GroupWise SDD on the same server that houses the post office.

The client then looks at the "BuildNumber=" value and compares it to the BuildNumber in the Windows Registry. If the BuildNumber in the SOFTWARE.INF file is greater than the BuildNumber in the Windows Registry, the GroupWise client requests that the POA retrieve the SETUP.CFG from the <SDD>\CLIENT\WIN32 directory. The GroupWise client then looks for the lines in the SETUP.CFG file for this value:

[AutoUpdate]
Enabled=Yes
SetupIPEnabled=Yes

Both of these lines must be set to "Yes" to allow for SETUPIP.EXE to be used as an upgrade method. If SETUPIP is enabled, the GroupWise client requests that the POA retrieve SETUPIP.EXE from the <SDD>\CLIENT\ WIN32 directory. The GroupWise client then runs the SETUPIP. EXE utility which is pre-configured by the GroupWise administrator to pull the GroupWise client from a web server location.

Notes From the Field With SETUPIP

All the software needed for SETUPIP is not shipped with GroupWise 6 Support Pack #2. Don't worry, we've gone throught hours of testing on your behalf, in order to figure out how to make SETUPIP work.

Obtaining Additional SETUPIP Software

  1. Download the "GroupWise 6 SP2 English SETUPIP.FIL" at the following location:
    http://support.novell.com/cgibin/ search/searchtid.cgi?/2963391.htm
  2. Run the *.EXE file which will produce four pertinant files
    SETUPIP.FIL.
    WRITEIP.DAT
    WRITEIP.EXE
    WRITEUS.DLL
  3. Copy all fo these files to the SDD\ADMIN\UTILITY\SETUPIP directory
  4. Copy the SETUPIP.FIL file to the SDD\CLIENT\WIN32 directory.

Configuring the Web Server - Compressed SETUPIP

The reason we titled this section "Compressed SETUPIP" is this method of SETUPIP only requires that 45 megabytes of data be downloaded to the user's machine. In the section titled "Uncompressed SETUPIP" about 150 megabytes is downloaded.

These instructions will enable SETUPIP functionality for your post office. The instructions for this procedure are based upon using a Netscape Enterprise web server on a NetWare 5.0 server. If you are using another web server, there may be some special things to take into consideration. For example: the Microsoft Windows IIS server may not allow downloading of files by default. This may be a right that you must assign in IIS administration.

  1. On the server with the Netscape Enterprise web server make a folder under the SYS:NOVONYX\SUITESPOT\DOCS directory called GWCLIENT.
  2. Make a folder off the of the SYS:NOVONYX\SUITESPOT\DOCS\GWCLIENT directory called WIN32.
  3. Locate your GroupWise 6 Master SDD. Do the following:
    1. Copy the "SETUPIP.FIL" file from your GroupWise 6 ADMIN\UTILITY\SETUPIP directory to the SYS:NOVONYX\ SUITESPOT\DOCS\GWCLIENT folder.
    2. From your Master GroupWise 6 SDD copy the SETUP.CFG from the CLIENT folder to the SYS:NOVONYX\SUITESPOT\ DOCS\GWCLIENT\WIN32 folder.
  4. Modify the SETUP.CFG mentioned in the prior step so that it matches the installation criteria for your GroupWise system. Make sure that the [AutoUpdate] section reads:
    Enabled=Yes SetupIPEnabled=Yes
  5. Now proceed to the section titled "Configure the Post Office SDD to Support SETUPIP".

Configuring the Web Server - Un-compressed SETUPIP

The reason we titled this section "Un-compressed SETUPIP" is this method of SETUPIP requires that 150 megabytes of data be downloaded to the user's machine. The reason you would want to use this method of SETUPIP over the compressed method is if you wanted flexibility beyond the canned GroupWise 6.0.2 client. For example you may want to implement a C3PO or some sort or a new DLL that shipped after GroupWise 6.0.2.

These instructions will enable SETUPIP functionality for your post office. The instructions for this procedure are based upon using a Netscape Enterprise web server on a NetWare 5.0 server. If you are using another web server, there may be some special things to take into consideration. For example, the Microsoft Windows IIS server may not allow downloading of files by default. This may be a right that you must assign in IIS administration.

  1. Configure the Netscape Enterprise server to support downloads from a directory with about 2,500 files. To do this modify the MAGNUS. CONF file located in the SYS:\NOVONYX\SUITESPOT\HTTP- <web_server_name>\CONFIG directory by adding the following line: MaximumFilesReturnedInIndex 2500
  2. Restart the web server for this setting to take effect.
  3. On the server with the Netscape Enterprise web server make a folder under the SYS:NOVONYX\SUITESPOT\DOCS directory called GWCLIENT.
  4. Locate your GroupWise 6 Master SDD. Go to the SDD\CLIENT folder and do the following:
    1. Copy the "SOFTWARE.INF" file from your GroupWise 6 SDD\CLIENT folder to the SYS:NOVONYX\SUITESPOT\ DOCS\GWCLIENT folder.

      NOTE: Do you need to increment the BuildNumber in the SOFTWARE.INF? Make sure to do so if needed. For more details see the section in this guide on the SOFTWARE.INF. Make sure that the SOFTWARE.INF file on the web server and the SOFTWARE.INF file in the SDD directory have identical values for the BuildNumber.

    2. Copy the OFVIEWS folder and contents from the <SDD>\CLIENT folder to the SYS:NOVONYX\SUITESPOT\DOCS\GWCLIENT directory. So now there should be a folder off of SYS:NOVONYX\SUITESPOT\DOCS\GWCLIENT called OFVIEWS.
    3. Copy the <SDD>\CLIENT\WIN32 folder and its contents to the SYS:NOVONYX\SUITESPOT\DOCS\GWCLIENT directory. So now there should be a folder off of SYS:NOVONYX\SUITESPOT\ DOCS\GWCLIENT called WIN32.

  5. From your Master GroupWise 6 SDD copy the SETUP.CFG from the CLIENT folder to the SYS:NOVONYX\SUITESPOT\DOCS\GWCLIENT\WIN32 folder.
  6. Modify the SETUP.CFG mentioned in the prior step so that it matches the installation criteria for your GroupWise system. Make sure that the [AutoUpdate] section reads:
    Enabled=Yes SetupIPEnabled=Yes

    NOTE: Make sure the SETUP.INI file in the...GWCLIENT\WIN32 directory has the "EnableLangDlg" equal to "N".

Configure the Post Office SDD to Support SETUPIP

The Software Distribution Directory (SDD) associated with a GroupWise post office that will support SETUPIP should be accessible to the POA servicing the post office. The POA retrieves certain files from the SDD on behalf of the client. You will either want to put the GroupWise SDD for this post office on the same server where the POA is running, or your POA will need to have the /user-<nds login name> and /password-<password> switches enabled. The server that houses the SDD must have a R/W or Master replica of the partition containing the OU where the user in the "/user-<nds login name>" resides.

  1. Completely configure the GroupWise 6 SDD for this post office as explained in the section "Upgrading All Users on a Post Office with a Mapped Drive to the SDD." Do everything - but do not increment the bump number at this time!
  2. Modify the SETUP.CFG file in the SDD\CLIENT\WIN32 folder for the SDD associated with the post office to be upgraded. Make sure that the [AutoUpdate] section reads:
    Enabled=Yes SetupIPEnabled=Yes
  3. Go to the Master GroupWise 6 SDD, and access the ADMIN\UTILITY\SETUPIP folder. Run the utility called "WRITEIP.EXE". Fill in the DNS name or IP address of the web server with the appropriate location of the GroupWise 6 SDD on the web server. For example: http://www.missive.com/gwclient When you click on the OK button, WRITEIP.EXE will compile a new SETUPIP.EXE file. This file contains the information that you just entered using WRITEIP.EXE.
  4. Copy the SETUPIP.EXE to the GroupWise 6 <SDD>\CLIENT\WIN32 directory associated with this post office which you want configured to support SETUPIP. This is NOT the SDD on the Novonyx web server.
  5. Make sure the SETUPIP.FIL file is in the SDD\CLIENT\WIN32 directory associated with this post office. This file is used by SETUPIP simply for reference, even if you are going to use the "Un-compressed SETUPIP" method explained earlier.
  6. Now everything is in place for an upgrade of the GroupWise client via SETUPIP. You may increment the Bump number for the post office you are attempting to upgrade. Go back to the section "Upgrading All Users on a Post Office with a Mapped Drive to the SDD" and increment the Bump number as needed.

The next time your users log in to GroupWise, if they have file system rights to the SDD they will launch the SETUP.EXE process to upgrade the GroupWise client. Otherwise, they will launch SETUPIP.EXE to perform the upgrade from the web server.

Upgrading Remote GroupWise Users with the SETUPIP Utility

What if you have GroupWise Remote users who access the post office through GroupWise Remote 100% of the time? How do you upgrade their GroupWise client? The GroupWise Remote client is not designed to query the POA about the Bump number of the post office. Because of this, the Auto-update Algorithm is never initiated, and the GroupWise Remote client is oblivious to upgrades to the GroupWise client for the user's post office.

With the SETUPIP utility, upgrading GroupWise Remote users can be much easier than shipping them a CD. Send them the SETUPIP utility that you generate. Here's what you might do.

  1. Follow the instructions in the section just prior to this one called "Upgrading the GroupWise Client using SETUPIP".
  2. Take the utility that you generated called SETUPIP.EXE and e-mail it to the users who are remote GroupWise users. In the mail message, instruct the users to a) connect to the Internet, and b) Highlight the attached SETUPIP.EXE, click the right mouse button and select "Open".

    The SETUPIP.EXE utility will proceed to download the GroupWise client. If the user exits the SETUPIP utility prematurely when it is launched again it will pick up where it left off before the user exited.

Auditing the GroupWise 6 Upgrade

The GroupWise 6 POA has a feature that can give you a quick look at who has upgraded the GroupWise client to GroupWise 6. In order to see this feature your GroupWise 6 POA should have three switches enabled in the startup file. Here are the switches, along with examples of how the switches might be configured:

/httpport-7181
/httpuser-admin
/httppassword-notell

After enabling these switches in the POA's startup file, restart the POA. Then go to the POA's http port in this manner in your browser:

http://137.65.211.105:7181

You will be prompted for the User Name and Password. Once you've gotten into the POA via http, go to the C/S Users link. From here you can view the version of GroupWise client that your various users are using. See Figure 6.7 for an example of the screen you will see.

Figure 6-7: The GroupWise POA's HTTP Monitoring Screen

Adding the following switch will highlight any user who is using a client older than the version you indicate.

/gwclientreleaseversion-[version number e.g. 6.0.2]

Adding this switch will highlight any user whose client date is older than the date you indicate.

/gwclientreleasedate-[mm-dd-yyyy]

MAC Client "Update"

Although there is no Macintosh client for GroupWise 6, you can continue to use the MAC client version 5.2.8 on your GroupWise 6 post office. If you are running a client prior to 5.2.8, we recommend that you download this version at http://support.novell.com/servlet/tidfinder/2956929. Additionally, you should download the new MAC views for your post office, which are available at http://support.novell.com/servlet/tidfinder/2959455.


Purchase the GroupWise 6 Upgrade Guide here.


Other books and articles written by Tay Kratzer and Danita Zanrè:

Visit Caledonia Network Consulting's web site for more information: http://www.caledonia.net/index.html


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

© 2014 Novell