Upgrading Your GroupWise Clients

Most sites find that upgrading the GroupWise client is the last thing they do, simply because it seems to be time consuming and requires a lot of pre-planning. And, there are many ways to upgrade the GroupWise client, depending on the size and needs of your organization. Smaller sites will have desktop administrators move from desktop to desktop, installing the new GroupWise client (and many sites use this as an opportunity to do other desktop cleanup that has been pending for awhile). Other sites will want more automated solutions. We will look at a number of ways to get your GroupWise system upgraded quickly and smoothly.

 

Overview of the Windows Client Upgrade

There are several methods that can be used to upgrade your users to the new GroupWise 2012 Windows client. We’ll look at the various methods that Novell provides with GroupWise to upgrade your clients.

  • Manual upgrade by launching the setup.exe at the desktop, and walking through the installation dialogs.
  • Semi-automated upgrade by configuring a setup.cfg file for the post office and launching the setup.exe at the desktop.
  • The Auto-Update method
  • SETUPIP
  • ZCM Installation to push the client out automatically with Zen.

 

We’ll see how each of these can work for your environment.

 

The Auto-Update Algorithm

Before we actually get to configuring the post office for the upgrade, we will discuss how the Auto-Update Algorithm affects the upgrade process. GroupWise has a built-in mechanism for notifying the clients that it is time to upgrade. It is called the Auto-Update Algorithm, and it is an integral part of the functionality of the upgrade. The Auto-Update Algorithm is used in conjunction with the GroupWise Software Distribution Directory to allow the client on a Windows workstation to be upgraded automatically and seamlessly. At least that’s the theory! In practice, the Auto-Update Algorithm often causes confusion when the SDD is not properly configured or users do not have proper rights to the SDD. Some of the side-effects of the Auto-Update Algorithm are seen when a user logs into a post office and is suddenly told that there is new software available, but that he does not have rights to it. Or if a user logs into a post office other than her own, and is told that there is newer software available, even though she has just updated her computer to the latest and greatest. This all comes about because the post office is giving the GroupWise client some information about what software is available, and the client is then trying to interpret that to determine if it should upgrade.

In simple terms, here’s how the Auto-Update Algorithm works.

  • Every GroupWise post office must have a Software Distribution Directory defined in ConsoleOne. We find that this is often created with the post office, and then never touched again.
  • When a post office is created, it gets a “bump” number associated with it. The Bump Number is controlled by ConsoleOne, and written to the wpdomain.db and wphost.db for the post office in question.
  • Each version of the GroupWise client has a file called software.inf that has a “Build” Number in the file. For the shipping version of GroupWise 2012, the Build Number is 4100.
  • The setup.cfg file is used to define whether or not clients should auto-update their software when all of the conditions of update are met.

All of these components work together to ensure that clients are notified of the update. Here’s how this fits together:

  1. The administrator places the new software into the client directory of the SDD defined for a particular post office.
  2. Next the setup.cfg that is contained in the /client directory of the SDD is configured to force the auto-update, and this file is copied into the /client/win32 directory of the SDD. In reality, the default of the setup.cfg is to perform the auto-update, so if you wish to prevent auto-update after performing Step 3 following, you should change the AutoUpdate value to Enabled=No and make sure the setup.cfg is copied to <sdd>/client/win32.
  3. The administrator then changes the Bump Number. The administrator cannot choose the Bump Number, only increment it. This is done in the GroupWise view in ConsoleOne, Select Tools|GroupWise System Operations|Software Directory Management. Highlight the SDD for your post office that has the new GroupWise 2012 software and select the “Update” button. In the next dialog box that comes up, select the check box next to the words that read “Force auto-update check by GroupWise components”. Click the “OK” button. This increments the Bump Number for the post office by one. 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. 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 software.inf file in the SDD, and in the workstation registry. The client looks at this value, and if the new value in the software.inf file is higher, the client then continues the update query process.
  4. The client then looks in the setup.cfg, and if the Auto-Update value is set to “Enabled=Yes”, the client upgrades. Since the default for the Auto-Update is “Enabled=Yes” and occurs even if you do not configure the setup.cfg, if you wish to prevent the Auto-Update from occurring once you associate a GroupWise 2012 SDD to your post office (for example, if you have Windows 2000 users you need to be careful), you must place the setup.cfg file into the <sdd>/client/win32 directory, and change the Auto-Update Enabled value to No.

 

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.

 

NOTE: If you want to enable Auto-Update, and at the same time prevent Windows 2000 users from upgrading, you can change the BuildNumber value in HKEY_LOCAL_MACHINE\SOFTWARE\Novell\GroupWise\BuildNumber to the same value as the software.inf file (shipping version this is 4100). Make sure this is in decimal format.

 

Once you know these key steps, it’s easy to see where some of the 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 logged into the workstation does not have proper rights to the SDD.
  • “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 software.inf cannot be accessed to verify that the software is actually newer.

 

Now that we know what the client looks for in order to know to upgrade automatically, let’s look to see how we can make this work to our advantage.

 

NOTE: By the way, if you do not use Novell’s methods to distribute the GroupWise client to your users (i.e., you go to individual workstations and install the client, or you use some automation tool like zenworks, you do not really need to keep your SDD up to date. Just make sure that you never go into ConsoleOne to the Software Directory Management and choose to update the software bump just to see what might happen!

 

Creating a Software Distribution Directory for your Post Office

In this guide, we have done most of our work simply by relying on our “Master SDD”, which is essentially a full copy of the GroupWise 2012 software. For the purposes of your post offices and providing software to your users, you do not need to have a full SDD on the post office server. You simply need to have the files required to install the client.

In order to even create a post office, you must define an SDD for the post office. All of your post offices will have an SDD assigned to them, and for some sites that do not feel a need to have an SDD available to users (for example, those installing with Zenworks or manually), the same SDD may be defined for ALL of the post offices.

As we saw when we upgraded our post office, part of the role of the SDD is to provide new OFVIEWS to the post office directory when the POA is upgraded. If you use the same SDD for all post offices in your system, of course this can’t work. That is why when upgrading the post office we always manually copy those OFVIEWS files to the post office directory. It’s impossible to know if all sites have their SDDs up-to-date and available, so it’s a simple, quick step we take to ensure the success of the upgrade.

If you are unsure about what SDD is defined for your post office, this is easy to see in ConsoleOne. Simply view the properties of your post office and look under the “Post Office Properties” to see what SDD is assigned to this post office. See Figure 11-1.

    1. poa1.tiffThe SDD Associated with a Post Office

 

Of course, in order for an SDD to be used for a client upgrade, it must have the client software available. The GroupWise client is always found in the sdd\client directory. If your users are to be able to use the SDD to upgrade their clients, you must grant Read and File Scan rights to the <sdd>\client folder and subfolders. Users do not need, and should not have rights to any other location of the SDD. In order to prevent accidental access to other parts of the GroupWise system, we do not recommend that you place your SDD under your post office directory, or any other location where you need to restrict rights from standard users. In order for the GroupWise auto-update procedures to work correctly, the SDD should be in a location also accessible by the POA.

Also in ConsoleOne you can see where this SDD actually exists. Under Tools|GroupWise System Operations|Software Directory Management you can see that our CNCMail SDD referenced in Figure 11-1 is located at \\LOCHEE\VOL1\grpwise (Figure 11-2)

    1. poa2.tiffSoftware Directory Management

 

 

 

SETUP.INI

The setup.ini file in the <sdd>/client/win32 directory is full of interesting settings for the Microsoft Installer. It also has one very important setting that you will want to set if you wish to totally automate your installation. You can disable the language dialog in the installation by verifying that the EnableLangDlg setting is set to No (N).

 

SOFTWARE.INF

The software.inf file simply designates the “development version” of the GroupWise software. For the shipping version of GroupWise 2012 the contents of this file are:

 

[General]

BuildNumber=4100

 

Whenever the GroupWise client is installed, the Build Number of the GroupWise client is put into the Windows registry. The BuildNumber string value is kept in the following registry location:

 

HKEY_LOCAL_MACHINE\SOFTWARE\Novell\GroupWise

 

SETUP.CFG

As we mentioned above, the setup.cfg is a very important file in the Auto-Update Algorithm. There is a setup.cfg file that ships with GroupWise 2012 in the <sdd>\client directory. This is a template file that is used for customizing the GroupWise client installation. This file does not have an effect on the installation of the GroupWise software unless it is copied in to the <sdd>\client\win32 directory. If the setup.cfg resides in this directory, it will be used to set parameters for the client installation. The important settings for the setup.cfg file as pertains to the Auto-Update Algorithm are under the [AutoUpdate] section. The “Enabled” value must be set to “Yes” in order for the automatic update to occur. There are a number of other options you can set for the installation through the setup.cfg file. Here are some of the more common:

  • If you wish to force your users to update the GroupWise client:

[AutoUpdate]

Enabled=Yes

ForceUpdate=Yes

Remember that Windows 2000 workstations should not be allowed to upgrade, so use this option only if you can ensure that your Windows 2000 users can be reverted back to their former client easily.

 

  • If you wish to make the installation automatic for the users so that they are asked no questions and only see the progress and ending of the installation:

ShowDialogs=No

ShowProgress=Yes

ShowFinish=Yes

 

(Remember to also check the setup.ini file for EnableLangDlg=N)

 

  • GroupWise Notify will not be put in the Windows startup folder

Notify=No

 

  • GroupWise Tips will be enabled

[GWTip]

Default=Yes

 

  • GroupWise Document Management integration will not be enabled by default

[Integrations]

=No for all components

 

 

 

  • The Language will be English.

[Language]

Default=English

English=Yes

 

 

Choosing Your Windows Client Installation Method

Once you have prepared your SDD to deliver software to your users, there are a couple of methods you can use to complete the process. We can do any of the following:

 

  • Manual installation: This means the setup.exe is launched manually at the desktop. You would then walk through the dialogs for the installation.
  • Semi-Automatic Upgrade: If you follow the procedures above, this would launch the setup, but honor any settings in the setup.cfg (in the <sdd>/client/win32 directory) and the setup.ini files. Thus, you could semi-automate the installation. For this, you could run the setup.exe manually, as a Zen startup application, through a login script, or any other way you would want to launch the setup.exe.
  • Auto-Update Direct Access: This method relies on the client being notified through the Bump/Build number combination that there is new GroupWise software, and launches the installation when the client logs into the post office. This method requires that users have direct file access to the SDD.
  • Auto-Update through SETUPIP: This method allow you to automatically upgrade users who do not have direct access to the SDD.
  • Pushing the Client Upgrade through ZCM: If you use ZCM to manage applications for your users, you can push down the client through ZCM with no intervention by the user.

Auto-Update through Direct Access

In order to avoid having users prompted to upgrade before we are ready, we will create a new SDD as discussed above and assign it to the post office once we are prepared to kick off the upgrade.

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

  1. Create the directory structure for your new GroupWise 2012 SDD for the post office you are wishing to upgrade. All you need is the /client directory from your master SDD in order to populate this directory. Make sure users have Read and File Scan rights to this directory and its sub-directories.
  2. Make the relevant changes to the setup.cfg file found in the <sdd>/client directory, and save it into the <sdd>/client/win32 directory.
  3. Make sure that the setup.ini file reflects your wishes regarding the language dialog.
  4. Configure your new SDD in Tools|GroupWise System Operations|Software Directory Maintenance. Click Create to define the SDD at the location you created in Step 1 above.
  5. Edit the properties of the post office and select the “Post Office Settings” property page from the GroupWise tab.
  6. In the Software Distribution Directory field, select the SDD that you created in Step 4 above and then select OK.

The simple act of associating your post office to the new software distribution directory may be enough to trigger the upgrade when users log in. This is dependent on only one factor that we discussed above: the Bump Number. As long as the bump number in this new SDD is different than the bump number in the workstation registry, the upgrade query process will kick off when the user launches GroupWise. If you need to increment the bump number (i.e., the software is not upgrading), follow these steps:

  1. In ConsoleOne, connect to the primary domain and under Tools|GroupWise System Operations choose Software Directory Management.
  2. Highlight the new GroupWise 2012 SDD that you recently created and select the “Update” button.
  3. In the next dialog box that comes up, select the check box next to the words that read:

“Force auto-update check by GroupWise components.

  1. Click the “OK” button.
  2. If needed, repeat tasks 1 through 4 again until users are being prompted to upgrade. Triggering this option multiple times will not affect any users who have already upgraded. If the Build Number is correct for upgraded users, the client will simply ignore the bump number increase.

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 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.

Upgrading the GroupWise Client with SETUPIP

Using the SETUPIP utility, users can upgrade the GroupWise client without needing direct access to a file server where the GW 8 software is located. These users might not have network accounts, or may have the SDD on a server for which they have no access.

SETUPIP requires a web server to serve up the client files. When you deliver the GroupWise client using SETUPIP, it downloads a compressed version of the GW client from a file called setupip.fil. Any additional languages you wish to include will only add 3-5 MB per language to the download. After everything is downloaded, SETUPIP launches the GroupWise client setup.exe installation program from the users local hard drive and the installation begins.

The SETUPIP functionality can exist alongside the direct access 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. Alternatively 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.

 

Configuring Your Web Server

You can use any web server available that allows connections on port 80. Here are the steps to configure your web server.

 

  • Determine the document root directory for your Web Server. By default on Linux this is /srv/www/htdocs
  • Under the document root, create a directory called gwclient where you will place your GroupWise files. For example on a Linuxserver the whole path to this directory would be: /srv/www/htdocs/gwclient. This directory must match the directory you define in the writeip.exe utility which is discussed in detail later on.
  • Create a sub-directory under the gwclient directory called win32. For example on Linux the whole path to this directory would be /srv/www/htdocs/gwclient/win32
  • In your SDD locate the admin\utility\setupip directory.
  • Copy the setupip.fil file from the <sdd>\admin\utility\setupip directory to the web server’s <document root>\gwclient directory. This file is the compressed GroupWise client.
  • Copy the proper language file(s) from your <sdd>\admin\utility\setupip directory to the web server’s <document root>\gwclient directory. Language files are named setupip.xx where the XX represents the language code. Users can pick what language they want to download if you have more than one language file in the gwclient directory. For example if you wish users to be able to install the GroupWise client in German, you would copy the setupip.de file to the gwclient directory. We will discuss more about these language files when we create the setupip.exe file in the next section.
  1. In your post office specific SDD, locate the file called setup.cfg. This file should be in the client\win32 directory as we defined in Step 2 of the “Auto-Update through Direct Access” section above.
  2. Copy the setup.cfg file to the web server’s <document root>\gwclient\win32 directory.
  3. Copy the setup.ini from your <sdd>/client/win32 directory to your web server’s <document root>\gwclient\win32 directory.

 

Now that you’ve configured your web server, we can create the setupip.exe that will control the installation of the GroupWise client through the web server. The next section entitled Configure and generate the setupip.exe executable will explain this process.

 

Configure and Generate the setupip.exe Executable

The setupip.exe file is used to download and launch the GroupWise client installation over an IP connection to a web server. When executed, the setupip.exe file downloads the compressed GroupWise client and then launches the setup.exe file. It contains the location (URL) to your web server(s) where you have hosted the GroupWise client as explained previously. To generate your setupip.exe follow these steps.

  1. From your Master SDD, run the utility called writeip.exe in the \admin\utility\setupip directory.
  2. In the WRITEIP utility fill in the DNS name or IP address of the web server with the appropriate location to the GroupWise client directory on the web server. Based on the previous section this would be http://<your server IP or DNS name>/gwclient
    1. setupip1.tiffThe Write IP interface

NOTE: You cannot download the GroupWise client via an SSL connection. So you cannot use the syntax https:// for your download location.

 

NOTE: You can define multiple web servers for the GroupWise client download. This allows the client to be downloaded from randomly from the sites you define if you check this option. Otherwise, if the first web server is down, the client will be downloaded from the next web server on the list. If you are providing SETUPIP functionality for users both on your network and across the Internet, you might want to provide URLs with both private and public IP addresses to the same web server location.

 

  1. After filling in the information in the WRITEIP utility select the OK button, which will generate a new executable in the admin\utility\setupip directory called setupip.exe.
  2. Copy the setupip.exe file to the into the client\win32 directory of the SDD for the post office for which you are configuring SETUPIP. If the user does not have access to the post office’s SDD, the Post Office Agent will send this file to the user, and the installation will be launched. On the other hand, if the user does have rights the install is simply started directly from the SDD rather than through setupip.exe.

 

NOTE: If your users need to use an http proxy to reach your SETUPIP web server, you can add the proxy information to the URL while running writeip.exe. Place the proxy information and port on the URL with the syntax of http://<server>;proxy:port. For example if my proxy server was known as HTTPProxy.cnc.com and worked on port 8080 my URL would be http://mail.cnc.com;HTTPProxy.cnc.com:8080

Troubleshooting SETUPIP

 

The SETUPIP utility makes a file called setupip.err in the Windows program directory. The Windows program directory is usually c:\windows. If you experience problems with SETUPIP, look at this file for some clues.

 

Upgrading Mobile Users with SETUPIP

If you have users who access GroupWise outside of your network with Remote or Caching Mode, they may never get the notification to upgrade. For those users you can simply e-mail the setupip.exe file that you generated above. While the user is connected to the Internet, he can simply launch the setupip.exe attachment (save it to a temporary location first) and the setupip.fil file will be downloaded and the upgrade can commence. You can also put the setupip.exe file on a web server for download.

 

NOTE: The setupip.exe utility can be used to install the GroupWise client on a computer that has never had GroupWise installed before. SETUPIP is not just an upgrade utility. Simply deliver the setupip.exe to the user by whatever means available, and when the user launches the program it will install GroupWise.

 

Upgrading Users with ZCM

The following information is applicable to ZCM 11, SP1. If you have earlier versions of ZCM, these instructions may not work in your environment. We will not cover any other ZCM versions for this guide. Also, we will not cover every permutation of ZCM that you might need for installing GroupWise. If you are using ZCM, we assume you are familiar with the ZCC dialogs, and that you know how to assign your own relationships and requirements to your application bundles. The steps below are only intended to show the part of the ZCM setup that is specific to the GroupWise 2012 client installation.

The first thing that we do when preparing the GroupWise client for ZCM is to generate the GroupWise MST file required for the installation. This is done by using the gwtuner.exe file that is supplied with GroupWise 2012. The gwtuner.exe file is found in your SDD under /admin/utility/tools.

  1. Run the gwtuner.exe file. You will see the information in Figure 11-4.

 

    1. gwtuner1.tiffThe GWTuner Client Directory Window

 

  • At this screen, enter the location of your client directory in your SDD. For example f:\gw12soft\client.
  • The next screen shows the options for the installation. For our purposes, we wish to have ZCM control the client entirely, so we will go over the options here. In order to allow ZCM to control these options, we are unchecking most of the boxes in the dialog:
  • Install path: Enter your installation path. The default is shown in the figure below.
  • Program folder: This is the name of the Program folder, should you choose to create one (as you will see later, we will not be creating a program folder during our setup).
  • Add GroupWise to the Desktop: If you choose, you can add a GroupWise icon to the desktop during installation. For our purposes this is unchecked.
  • Add GroupWise to the Quick Launch: We can also add an icon to the Quick Launch. We are leaving this unchecked.
  • Add Notify to the Startup folder: We wish to control this with ZCM, so we are leaving this unchecked.
  • Install Internet Browser Mail Integration: This adds “mail to” functionality to your browsers to launch GroupWise when a “mail to” link is clicked.
  • Add icons to the Start Menu: If we leave this checked, the Program folder listed above will be created for the Start Menu.
    1. gwtuner2.tiffThe GWTuner General Settings
  • The next screen will allow you to choose the languages you wish to install. You can, of course, choose as many languages here as you require. If you choose more than one language, the next screen will prompt you for the default language for the installation.
  • The next screen shows software integrations. Any application on the installation computer that is available to be integrated with GroupWise Document Management will be listed here, and they will all be checked. If you are NOT using GroupWise Document Management, please uncheck all of these to avoid helpdesk calls after the fact. These integrations are only used with GroupWise Document Management, and do not, for example, have anything to do with “send to” functionality from within an application.
  • When you click Finish, your groupwise.mst file will be created in the win32 directory under the client directory you specified in Step 2 above. In our case, this is f:\gw12soft\client\win32\groupwise.mst.

Now that our groupwise.mst file has been created, we can configure the ZCM routine to deliver this client to the workstation. Novell has made some modifications to the GroupWise and ZCM settings that allow this to happen with much less work that in past versions. As we saw in the “Upgrading the GroupWise Client with SETUPIP” section above, the GroupWise client for SETUPIP is packaged in a file called setupip.fil that contains the complete GroupWise client for distribution. This is found in your SDD under /admin/utility/setupip. ZCM will be able to use this file, and a few other files to manage the GroupWise installation, rather than thousands of individual files as in the past. The only files we will need for our ZCM repository are setupip.fil, extract.bat and the language files we chose in the GroupWise Install Tuner. So, if we had chosen English and German as our languages to install above, we would need to also have setupip.en and setupip.de for our bundle. We will walk through those steps now.

  1. Launch your Zenworks Control Center in your browser, and choose Bundles.
  2. Create a new bundle by clicking on “New” and then choosing “Bundle” and then indicating it is a Windows Bundle and click Next.

 

  1. zen1.tiffCreating a new ZCM Windows Bundle
  2. Create this as an empty bundle so that we can configure the actions as necessary.
  3. On the next screen we will need to fill in a number of values:
  • Bundle Name: Give your bundle a name such as “GW2012”
  • Folder: The default is /Bundles.
  • Icon: GroupWise 2012 has specified an icon for this use. Browse to your SDD/client/win32 directory and choose grpwise12.ico as your icon file.
  • Description: Enter your description for GroupWise 2012 here.
  1. On the next screen ZCM 11 will allow you to create your bundle as a “Sandbox” version if you choose to do so until you are ready to publish the bundle for installation. Leave “Define Additional Properties” checked here so that we can further customize the application.

 

Next we will create some installation actions for our bundle.

  1. Click on the Install tab to create some new actions.
  2. Choose “Install File(s)” as the action. In this action we are essentially having ZCM put the installation files in a temporary location on the workstation so that the extract.bat can perform the installation. Name this action something that will make sense to you. For example “Install files to temporary installation folder”.
  3. Click on Add to get to the Select Files dialog, and click Add again to find the files. As we mentioned above, we need to go to the SDD/admin/utility/setupip folder and select the extract.bat, setupip.fil, and our language files (in our example, setupip.en and setupip.de). Click “Open” to include these files in the Select Files dialog.
  4. The setupip.fil file is already a compressed file, so it not necessary to compress these files further. Thus, check the box that says “do not compress or encrypt uploaded content”.
  5. When you click Okay, you will see a confirmation screen to show you the files that will be uploaded to your repository.
  6. Once the files are uploaded, you will be returned to the Select Files dialog. Now you will need to specify where these files should be placed on the local machine. Remember this is a temporary installation directory, so you can choose any location you like. An example would be c:\gwclient. Select Okay.
    1. zen2.tiffThe completed Select Files dialog
  7. At the next screen, you can select to run this installation as a secure system user to avoid any rights problems during the copy. Select okay to save this action.

 

The next action we need to create is one to extract the files from the setupip.fil file for GroupWise.

  1. Back on the Install Tab, click Add to create a new action, and choose Run Script as the action.
  2. In our first action, we copied extract.bat to c:\gwclient, so we can enter c:\gwclient\extract.bat as the Script File Name. The extract.bat file will then extract all of the files under this directory into c:\gwclient\win32. This is important for our final installation step.
  3. Click the radio button next to “When Action is Complete” for the wait parameter for this script.
    1. zen3.tiff Creating the Run Script Command
  4. Before you leave this screen, you should give the Action Name a more specific name, such as “Run Script to extract GW2012 files”.
  5. Click on the Advance tab and choose to run the script as dynamic administrator to avoid problems during the extraction.
  6. Click OK and you will now see two actions in your Install tab.

 

The next step is to copy the MST file that we created with the GroupWise Install Tuner to the local temporary installation directory. The following steps will do this:

  1. Click Add again to create a new action. Choose “Install File(s)”, and give the action a name that designates that you wish to “Copy groupwise.mst to local directory”.
  2. Click Add to show the Select Files screen, and click Add again to show the add dialog.
  3. Browse to your SDD/client/win32 directory and choose the groupwise.mst file that we created above. Click OK. The file will be uploaded to the ZCM repository.
  4. Next you will be asked where this file should be copied. The extract.bat process created c:\gwclient\win32 (if you used c:\gwclient as your temp directory). This is where the groupwise.mst file must reside.
  5. Leave the copy option as Copy Always.
  6. Change to the Requirements tab and run the process as Dynamic Administrator.

 

Our final action will be to actually install GroupWise using the groupwise.mst file.

  1. Again, at the Install Tab, add a new action of “Launch Executable”. Name this Action “Launch install.bat for GroupWise 2012”.
  2. The command name in our case will be c:\gwclient\win32\install.bat.
  3. For command line parameters you can choose:
    • /unattended – this will show the typical GroupWise progress statuses for the installation
    • /silent – the user will not see anything while GroupWise installs
  4. Click on Add under Environment Variables and add the following:
    • Name: GW_INST_TRANSFORM_FILE
    • Value: groupwise.mst – note that this assumes the same folder as the install.bat file, which in our case is correct.

Click Ok.

  1. Click on Add under Environment Variables for a second variable to update existing GroupWise installations to match our current installation msi:
    • Name: GW_INST_REMOVE_MSI
    • Value: True

Click OK

  1. zen4.tiffOur action for running install.bat
  2. Next click on the Advanced tab and select “When action is complete” for the wait time. Also choose to run as dynamic administrator. Click OK.

 

Next we will create a launch action for the GroupWise 2012 bundle.

  1. Click on the Launch Tab, then click on the Add button and choose “Launch Executable” as the type.
  2. For the command, you will have “c:\program files\novell\groupwise\grpwise.exe” (assuming you installed in c:\program files).
  3. For command line parameters you can choose any parameters you typically use.
  4. Click on the Advance Tab. Since this is for the launch of the client, you should choose “no wait” and “Run as logged in user”. Click OK.
  5. Apply your changes.

Back at the script parameters for the installation, we had the choice of running the installation in “unattended” or “silent” mode. If you chose silent, you might wish to allow ZCM to control the dialog that users see. To do so, go back to the Summary page of your new bundle, and scroll down until you see “Show Bundle Activity”. If you change this to “Yes”, ZCM will provide the status information to the user as the application installs.

Next, change the “Displayed Version” at the top of the Summary from Sandbox to Published. To do so, click on the “Publish” button, publish as a new version.

To complete your installation, add your relationships, requirements, icon choices and schedule.

 

Adding Grace Logins Before a Forced Upgrade

You may want to allow your users some “Grace Logins” before they must upgrade their GroupWise client. This allows users the flexibility to install the GroupWise client at a time that may be more convenient for them.

 

In order to do this, edit the setup.cfg in the SDD assigned to the post office. Place a value in the GraceLoginCount= argument. For example, if you wanted the user to have five grace logins before upgrading, then the setting would looks as follows:

GraceLoginCount=5

 

The GraceLoginCount= argument when combined with the ForceUpdate=Yes causes the GroupWise client installation to allow for Grace Logins before users are forced to upgrade.

 

Upgrading the Linux Cross-Platform Client

There is no upgraded GroupWise Linux client for GroupWise 2012. The GroupWise 8 client is available for you in your GroupWise 2012 media. If you need to install the GroupWise Linux client, follow these instructions.

  • As root, run the install script from the \client\linux directory of the GroupWise Linux installation CD.
  • Install the RPM manually from the \client\linux\ directory of the GroupWise Linux installation CD. You can install the RPM as follows:

 

rpm -Uvh novell-groupwise-gwclient-8.0.0-84910.i586.rpm

SuSEconfig

 

Of course, the actual version of the RPM will change over time. The name of the RPM above is simply the shipping version.

 

Upgrading the MAC Cross-Platform Client

There is no upgraded GroupWise Mac client for GroupWise 2012. The GroupWise 8 client is available for you in your GroupWise 2012 media. If you need to install the GroupWise Mac client, deploy the groupwise.dmg file to your Mac users.

 

Auditing the GroupWise Client Upgrade

The GroupWise 2012 POA has a feature that can give you a quick look at who has upgraded to GroupWise 2012. In order to see this feature your GroupWise 2012 POA should support HTTP monitoring and your post office must have enabled the setting for tracking a minimum client version. You can either enable HTTP monitoring in ConsoleOne or in the startup file of the POA. The advantage of using Console One to apply these settings is that the POA will pick up the settings dynamically, and you will not need to restart the post office agent.

The minimum client version settings will highlight in red the version number or release date of the GroupWise client for any user who is using a client older than the version or date you indicate.

 

Below is how you can enable these settings through Console One:

 

  1. Go to the properties of the Post Office object in Console One
  2. Select Client Access Settings under the GroupWise tabs drop down list
  3. Enter the version you would like for your Minimum Client Release Version (12.0 would represent the GroupWise 2012 client).
  4. Make sure you do not check the box next to the Minimum Client Release or only your GroupWise 2012 users will be able to log in.
  5. Click Apply, then OK to exit.

 

NOTE: If you check the check box to Lock Out Older GroupWise Clients then users will get a message before even entering their GroupWise password that states “The version of GroupWise you are using is older than the minimum version allowed by the system administrator.” You need to be careful about enabling the lock out function, as the user will not even be given the opportunity to update their client if you select this option. You may be better off using the grace login option in the SETUP.CFG file to give the user X number of grace logins before they are able to login without updating.

 

After enabling these settings you can monitor the client versions from your browser. Go to the POA’s http port in this manner from your browser:

 

http://192.168.100.238:7181

 

NOTE: If you are not sure what HTTP port your POA is using, you can hit the C/S port (1677) and it will redirect you to the HTTP Port.

 

You may be prompted for the User Name and Password for the POA HTTP Monitor. Once you have loaded the Web monitor for the POA, click on the C/S Users link. From here you can view the version of GroupWise client that your various users are using. Any user that is using an older GroupWise client than you specified will show up in red. Any user that is using at least the GroupWise client version you have specified will show up in blue.

 

Configuration Settings of Note

Here are a few things that you might be interested in as you upgrade the clients:

 

Sent Items Folder Issues:

  • Renamed Sent Items Folder: The first time a former GroupWise 6.0 and earlier user logs into the GroupWise 2012 post office, the POA will convert the Sent Items folder into a new system level folder, rather than the former search folder that was the Sent Items folder in earlier versions. This will generally be transparent to the users. However, if the user has in the past deleted the Sent Items search folder and then recreated it, the user may find that there is now both a Sent Items folder, and an “Old Sent Items” folder just above the Sent Items folder. The “Old Sent Items” is also a search folder, and can be deleted without removing any messages.
  • No Sent Items In a GroupWise 5.5x or 6.0x Client: If as in the above case, the new Sent Items folder is created, but your users continue to access GroupWise with an older 5.5x or 6.0x client, it will not recognize the new Sent Items folder, and will not appear to have a Sent Items folder at all. You can recreate the Sent Items query folder if necessary. Of course it’s better to just upgrade the client if possible!

 

GroupWise 2012 Home View

In GroupWise 7, Novell introduced the new Home View. The first time a new GroupWise 2012 user clicks on the Home folder, he will see a “Welcome” screen that explains the home view usage. However, if your upgrade is from GroupWise 7 or GroupWise 8, the user has already been confronted with this welcome screen before, and if the “Do not show this screen again” box has been checked, it will not appear when opening the Home View with the GroupWise 2012 client. This s a registry setting found here:

HKEY_CURRENT_USER\Software\Novell\GroupWise\Client\Setup\Show Home Folder Help

Change this key entry to “1” (for yes) and the Home View Welcome will reappear.

 

Hopefully this chapter will get you on your way to finishing up your GroupWise upgrade. Good luck!