Auto-Update with POA Access Through a Web Server

In the prior section, we saw the following figure:

  1. linuxinstall084.tifAuto-Update Options

We promised to explain the Auto-Login URL, and so here we are! In prior versions of GroupWise, the Software Distribution Directory (SDD) was used to distribute software for Auto-Update. While the POA was responsible to “hand off” the update of the software to the client, it was required that the user logged into the Windows workstations have read rights to the Software Distribution Directory in order to run the installation routine.

GroupWise 2014 has abandoned the SDD, and has instead compressed the installation files at the Post Office server. In order to continue to provide auto-update for even the smallest of sites with very limited server resources and administrative staff, auto-update at the POA was developed, so that out-of-the-box, without too much additional configuration, auto-update could be delivered to users. Thus, if you use the direct access as described above, the POA will actually deliver the installation files to the users for decompressing and installation.

On an already very busy post office, this can cause some slowdowns first thing Monday morning when all of your users arrive and are presented the auto-update option! To alleviate this, Novell has added a new “web server delivery” method for auto-update. This is very similar to SETUPIP, but requires less configuration, and is still reliant on the auto-update algorithm we described above.

Preparing the Web Server

The steps will be very similar to the above. The first thing you must do is configure your web server. We will not go through installing and setting up a web server for you. Refer to the documentation of the server on which you wish to install web services. There is no reason why you cannot use your GroupWise WebAccess server for this purpose if you choose, or you could fire up a small server for the dedicated purpose of providing GroupWise client installation functionality.

The steps are the same for Apache2 on Linux or IIS on Windows. You must simply start at your document root. On SLES/OES, this is /srv/www/htdocs. On IIS this would be c:\inetpub\wwwroot. We will refer to this from here on out as simply <documentroot> for both Windows and Linux.

  1. Create a new folder under the document root. You can name it anything you like, but gwclient seems reasonable!
  2. The installation routine (see “Installing the GroupWise Administration Service” on page <?>) copies the client files into the server directories.
  3. The client software is copied to <serverfiles>/agents/data/client/setup/win32/ directory. Copy the entire <serverfiles>\agents\data\client\setup\win32 into your web server <documentroot>\gwclient folder that you created above so that you have <documentroot>/gwclient/win32 on the server.
  4. 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 <documentroot>/gwclient/win32/win32 (yes, that’s two win32 folders).
  5. 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
    • <installationfiles>/client/win32/setup.ini

Copy both of these files into <documentroot>/gwclient/win32/win32.

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

Apache Specific Settings

On Apache on Linux, depending on the settings of your server, you may need to give specific access rights to this folder structure before the web server will actually deliver files for you. So perform the following steps for this.

  1. Go to the /etc/apache2/conf.d folder on your Linux server.
  2. Create a new text file here and call it something like gwclient.conf. The name is not really important as long as it has a .conf extension. Just name it something that will make sense to you later.
  3. Place the following contents in this file:

<Directory /srv/www/htdocs/gwclient>

Options Indexes

AllowOverrides None

Order allow,deny

Allow from all


  1. Restart Apache2. i.e., type rcapache2 restart

IIS Specific Settings

On Windows Server, you will need to give specific access rights to your GroupWise client files before the web server will actually deliver the files to your users. Here are the steps required to accomplish this:

  1. Click Start > Administrative Tools > Internet Information Services (IIS) Manager.
  2. Expand the Local Computer object, expand the Sites folder, expand your website, then select the client software directory that you created above under “Preparing the Web Server”. Here we will enable directory browsing so that the gwclient directory can be accessed:
    • In the Features View, double-click Directory Browsing.
    • In the Actions pane, click Enable.
    • Click the client software directory to return to the Features View.
  3. Next, to configure IIS to allow the download of the client software files:
    • In the Features View, double-click MIME Types.
    • In the Actions pane, click Add.
    • In the File name extension field, type .* (a period followed by an asterisk).
    • In the MIME type field, type application/octet-stream.
    • Click OK.
  4. Click the client software directory to return to the Features View.

Is is possible that you have configured file filtering at a higher level in this website. Is so, you must also configure IIS to not filter out files in the client software directory:

  1. In the Features View, double-click Request Filtering.
  2. Click Allow File Name Extension.
  3. In the File name extension field, type .* (a period followed by an asterisk).
  4. Click OK.

Finally, we will restart IIS. You can do this one of two ways:

  1. In IIS Manager, click on the IIS Server Name
  2. In the left-hand column choose “Restart Server”

Alternately, you can restart the IIS service as follows:

  1. Click Start > Administrative Tools > Services.
  2. Right-click World Wide Web Publishing Service, and click Restart.

Web Server Cleanup

Both Linux and Windows leave some files around that will cause trouble with the download of the GroupWise files.

On Windows, specifically, there is a file called web.config in your document root (typically c:\inetpub\wwwroot). This file, while important, will trip up the download of your GroupWise files. To avoid issues, right-click on the file, go to Properties and change the file to “hidden”.

For both servers, look in the win32\win32 directory for any temporary files that might have been created when you were editing the setup.cfg and setup.ini files. On Linux, these typically end with a ~ – for example, setup.cfg~. These extraneous files can also cause download issues. Delete them.