Auto-Update through Direct POA Access

Follow these steps to set up your post office for Auto-Update through the direct POA access method:

  1. The installation routine (see “Installing the GroupWise Administration Service” on page 25) copies the client files into the server directories.
  2. The client software is copied to /opt/novell/groupwise/agents/data/client/setup/win32/ directory.
  3. In order to better control the client software installation, we need a new directory under here, also called win32. So you will need to create a directory so that you have /opt/novell/groupwise/agents/data/client/setup/win32/win32, and yes that is /client/setup/win32/win32. You are not seeing double.
  4. There are a couple of files in the installation directory that do not get copied to the GroupWise server directories, and we will need them in this win32 directory.
    • <installationfiles>/client/setup.cfg
    • /client/win32/setup.ini

Copy both of these files into /gwclient/win32/win32.

You should then change them to reflect your wishes upon installation. We have samples of these files later in this chapter.

In prior versions of GroupWise, the setup.cfg file contained settings for enabling auto-update and controlling its use. This has been removed from the setup.cfg, and is now control in the Client Options in the GroupWise Administrative Console. Like all client options, these can be set by user, post office or domain. Let’s do an example of this for a specific post office.

  1. Log into the GroupWise Administration Console.
  2. Click on Post Offices.
  3. Choose your Post Office from the list of available Post Offices.
  4. Click on the Client Options tab.
  5. At the bottom left of the Client Options is Client Auto-Update. Click on that setting.
  6. In the Client Auto-Update settings you have some options here, which we will discuss:
  • linuxinstall084.tifAuto-Update Options
  • Enable: check this box to enable the auto-update.
  • Auto-Update URL: We will discuss this in the next section. For this particular purpose, we will leave this blank.
  • Force Update: This setting was formerly in the setup.cfg file. If you wish to require your users to update check this. This works in conjunction with:
    • Grace Logins: How many times should a user be able to cancel out of the update before being forced to allow the auto-update to occur.
  • Prompt Until Updated: If the user chooses to cancel the update, will s/he be nagged about it until the update is completed.

Finally, before anything will really happen, the administrator must increment Bump Number. The administrator cannot choose the Bump Number, only increment it. To better understand this, let’s look at the Bump Number (also known as the “Software Number”).

  1. In the GroupWise Administration Console, click on Post Offices, and then select the Post Office you wish to modify.
  2. In the Post Office settings, click on the “Diagnostics” dropdown along the top of the settings and select Display Object.
  3. Scroll through the listing until you find “Software Version” In our figure, this is version “1”
  1. linuxinstall081.tifThe Internal Software Version Number

To increment the bump number for a post office, follow these instructions:

  1. In the GroupWise Administration Console, click on Post Offices, and then select the Post Office you wish to modify.
  2. In the Post Office settings, click on the “More” dropdown along the top of the settings.
  3. Choose Client Auto-Update
    1. Choosing Client Auto-Updatelinuxinstall079.tif
  4. When you click the Trigger Update, the Bump Number will change.
  5. linuxinstall082.tifThis increments the Bump Number for the post office by one. If you follow the above instructions again for Display Object, you will see that the Software Version is one higher than before,
    1. Incremented Software Versionlinuxinstall083.tif
  6. As we will explain in a few minutes, if you want your users to upgrade, clicking this button multiple times will not cause problems. However, clicking it just once when you do NOT want to upgrade will cause you some headaches!

The stage is now set to initiate your auto-update. The next time a user logs into the post office, the following exchange will occur.

  1. The client on the user’s PC will query the POA and ask what the Bump Number is.
  2. The client on the user’s PC then compares this Bump Number to the registry value in HKEY_LOCAL_MACHINE\SOFTWARE\Novell\GroupWise\Client\5.0\NewSoftwareBump. For 64 bit machines, this is now in HKLM\software\Wow6432node\novell\groupwise\client\5.0\NewSoftwareBump. If this number is different (higher or lower), then the client continues on to ask for the Build Number.
  3. The Build Number is found in both the version.ini file in the Client Software Update Repository, and in the workstation registry. HKEY_LOCAL_MACHINE\SOFTWARE\Novell\GroupWise\BuildNumber or HKEY_LOCAL_MACHINE\SOFTWAREWow6432Node\Novell\GroupWise\BuildNumber. The client looks at this value, and if the new value in the version.ini file is higher, the client then continues the update query process.
  4. The client then compares the settings in Client Options that affect this user (so user/post office/domain), and if Update has been enabled, the upgrade begins.

It is important to note that the workstation must have access to write to the registry in order for the auto-update process to work. If the workstation cannot write the new Bump and Build numbers to the registry, it will not upgrade, and it will not give the user any indication that there is new software.

Once you know these key steps, it’s easy to see where odd messages users receive about software updates come from. Here are a couple that we see frequently:

  • “There is new GroupWise software available; however you can not access it at this time”: This error can occur if the bump number on the post office in question is different than the one in the workstation’s registry, and the Build Number is higher, but the user cannot receive the files. For a standard auto-upgrade through the POA, this should not happen, but if you are using a web server for the auto-update, and the web server is unavailable, you might see this message.
  • “There may be new GroupWise software available. However, the auto-update process was unable to access the GroupWise Software directory. Please contact your administrator”: This one is interesting, because it means that the bump number is different on the post office than on the workstation, but the version.ini cannot be accessed to verify that the software is actually newer.

If you have an easy method to change the registry at your workstations, you can also simply change the value in the HKEY_LOCAL_MACHINE\SOFTWARE\Novell\GroupWise\Client\5.0\NewSoftwareBump or HKLM\Software\Wow6432Node\Novell\GroupWise\Client\5.0 to “0”. This will ensure that the Bump Number in the registry is different than what is in the wphost.db file, and will restart the upgrade query for all (or a subset if you choose to only change the registry for a group of users) of your workstations.