Update with SetupIP

Upgrading the GroupWise Client with SETUPIP

Earlier in this chapter we discussed how you can now trigger auto-update by domain, post office or even user. However, there is no way to multi-select subsets of users and edit their client options, or change the client options of a group.

This is where SETUPIP really shines, because you can configure a distribution of the GroupWise client, and then you can simply distribute a small executable to multiple users (via email, or placing it on a web server for download) and manage a more controlled rollout of the client.

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

Additionally, SETUPIP can be used to install GroupWise fresh on a PC that has never had GroupWise before. This allows you to get the client to remote workers who have never had their laptops in the office!

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. The procedure is almost identical to our previous settings under “Auto-Update with POA Access Through a Web Server”.

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 25) 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 contents of <serverfiles>\agents\data\client\setup\win32 into your web server <documentroot>\gwclient folder that you created above.
  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.
  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.

  1. In the win32 folder you will have all of the available language files (e.g. setupip.xx, where xx is an appropriate language designation such as en for English or fr for French-France. If you have more than one language file the client will be presented with a list of languages that can be downloaded and extracted. If the user selects more than one language, the GroupWise Client will be installed in all of the selected languages. You should remove all language files from this folder for languages that are not needed for your organization. If only one language file exists, users will not be prompted to select languages for the installation. If you require more than one language file for your system, configuring your setup.cfg file will allow you to set the default language. Also, you must indicate “Yes” for any languages you wish to have installed. Otherwise only the default language will be installed.

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

</Directory>

  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.

Test the Software Availability

Regardless of your web server platform, you should test to verify that the client software is available from a browser. Follow these instructions to do so:

  1. From your browser, navigate to http://web_server_address/gwclient (assuming this is the directory you chose for your installation).
  2. Verify that you can see files and or directories related to your installation.

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. The setupip.exe file contains the location (URL) to your web server(s) where you have hosted the GroupWise client as explained previously. The procedure to create the setupip.exe file is a Windows application (writeip.exe). If your GroupWise server is on Linux, this presents a bit of a complication, because you have not “installed” server files on Windows in order to extract these files. There are a couple of ways to get access to these files for our purposes. A few ideas are:

  • If this is an OES server, place the <serverfiles>/agents/client directory and your <installationfiles> on a NCP accessible drive.
  • Configure SAMBA for shares to the <serverfiles> and <installationfiles> and map drives from Windows to these SAMBA shares.
  • Download the Windows GroupWise full distribution and extract the files by doing the following:
    • After downloading the full Windows distribution zip file, right-click on the file and choose “Extract All” and place it in a directory of your choice. For example c:\temp\gwinstall. This would then serve as your <installationfiles> directory for the rest of this SETUPIP section.
    • change to this new <installationfiles>\server\win64 directory
    • run setup.exe /extract c:\temp\gwserver (or any location you choose). Use this location as your <serverfiles> location for accessing the required client files.

Our preference is actually the latter. In any event, you must have access from Windows for this process!

To generate your setupip.exe follow these steps.

  1. From your <serverfiles>/data/client/setup/win32 folder, run the utility called writeip.exe.
  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. linuxinstall086.tifThe Write IP interface

NOTE: You can define multiple web servers for the GroupWise client download. This allows the client to be downloaded 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 <serverfiles>/agents/data/client/setup/win32 directory called setupip.exe.
  2. Copy the setupip.exe file to the into the <documentroot>/gwclient directory of the web server.
  3. You can instruct users to set up their GroupWise client by going directly to http://yourserver.com/gwclient/setupip.exe – then when they download this file, the installation of the client will begin.
  4. Alternatively, you can email the setupip.exe to your users. Instruct them to save the attachment locally, close groupwise and run setupip.exe to upgrade.

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.

Some of the more common problems with SETUPIP are

  • not putting in the entire path to the files in the http: links
  • not configuring the web server to be able to access the files
  • having errors in the gwclient.conf on Apache