Understanding the Configuration File

The use of a configuration file to install GroupWise is often called an administrator-defined setup. The configuration file, setup.cfg, is an ASCII text file that supports extended ASCII characters. The file contains the responses normally provided by the user during the installation of the Windows client files; for example, the path for the client files, whether to complete a workstation or standard installation, and the folder for the GroupWise icon are specified in this file. Information can be added to the configuration file to add predefined LDAP directory service accounts to the Address Book in the client during installation.

When the GroupWise Windows client setup.exe file is executed, it looks in the same directory for a setup.cfg file. If none is found, the installation proceeds, prompting the user for the needed information. If the setup.cfg file is found, the setup program installs the software, using the information outlined in the configuration file. Depending on the entries in the configuration file, the user might or might not be prompted to provide information during the installation.

If you are going to use a configuration file to install Windows client software, users should be given Read and File Scan rights to the software_distribution_directory\client and software_distribution_directory\client\win32 directories. (This does not apply if you are running AutoUpdate over an IP connection.)

Installing with the Configuration File (setup.cfg)

During the installation of GroupWise Administration, the GroupWise client files were copied to the software distribution directory on your server. For example, if you accepted the default z:\grpwise\software as your target, the GroupWise client software was copied to z:\grpwise\software\client\win32.

Modifying the Configuration File

The configuration file is divided into the following sections. In the configuration file, each section head must be enclosed in brackets [ ] as shown.

• [GroupWiseSetup]
• [ShowDialogs]
• [AutoUpdate]
• [Startup]
• [GWTIP]
• [GWMAILTO]
• [GWCHECK]
• [IntegrationApps]
• [Languages]

Adding LDAP Directory Service Accounts

LDAP directory service accounts provide users with the ability to search directory services such as Bigfoot* for names of people. Each search can check potentially millions of names. After locating a name through a directory service search, users can add those names to their personal address books.

You can add predefined LDAP directory service accounts to the Address Book by adding information to setup.cfg. This information can be added even after the initial installation. After the accounts are added, this information does not have to be removed from setup.cfg. During subsequent installations, GroupWise will add any new accounts listed but will not update or duplicate existing LDAP accounts.

The user can also choose to add LDAP directory service accounts after the GroupWise client is installed.

To add an LDAP account during installation, add the following lines to the setup.cfg file, providing information that is specific to the account:

[LDAP Account 1] 
Description=Ldap Server1 
Server=ldap.server1.com 
Port=389 
SearchRoot=c=us 
Login=TRUE

You can add multiple accounts:

[LDAP Account 2] 
Description=Ldap Server2 
Server=ldap.server2.com 
Port=389 
SearchRoot=0=widget, c=us 
Login=FALSE

Enabling AutoUpdate

AutoUpdate can occur whether users have a mapped drive or IP connection to the software distribution directory. If users have a mapped drive to the software distribution directory, make sure they have Read and Scan rights to the software_distribution_directory\client and software_distribution_directory\client\win32 directories.

IMPORTANT:  To install the GroupWise client using AutoUpdate, you must first make sure GroupWise 6.x Administration and GroupWise 6.x agents have been installed, and that administration, agent, and client software has been updated.

IMPORTANT:  If you did not select all options for Client when you initially created your software distribution directory, you will need to copy the setupip directory from the GroupWise 6.5 Client CD to the software distribution directory. If you are going to use AutoUpdate over an IP connection, copy setupip\setupip.fil to an HTTP web server, or copy the entire client directory to the HTTP web server.

For information about the location of setupip.fil, see Setupip.fil File.

In the following procedure, steps 1-4 apply only if you will be using an IP connection for AutoUpdate.

1. Run software_distribution_directory\setupip\writeip.exe.

   Specify an IP location for setupip.fil (or the IP location of the software distribution client subdirectory). For example, you can specify:

   http://151.155.135.122/gw65/client

   or

   http://intranet.company.com/software/gw65/gwclient

   You can include proxy and port information, for example:

   http://name.mycompany.com/software/gw65/client;proxy.place.mycompany:1690

   You can specify up to five locations. During AutoUpdate, each location is checked, in order, until a connection is made.

   If you select Choose IP Address at Random, the order in which the locations are checked is selected randomly when AutoUpdate occurs. This will balance the load on the web server.

2. Specify other options, such as the location for downloading the client installation files (setupip.fil or the client subdirectory files).

   You can have files downloaded to a temporary or specific directory.

   If you select Allow the User to Change the Download Directory, the user is prompted for the location of the download directory and can change the default location.

3. Click OK.

   The setupip.exe file is created. The writeip.ini file is also created, which stores the options you selected in writeip.exe.

4. Copy setupip.exe to the software_distribution_directory\client\win32 directory.

5. Make a backup copy of software_distribution_directory\client\setup.cfg.

6. Using an ASCII text editor, edit the setup.cfg file entries with the values you want.

   1. Under the [AutoUpdate] heading, specify

      Enabled=Yes

   2. Specify

      ForceUpdate=Yes

      if you want GroupWise to automatically update the users' client software

      or

      ForceUpdate=No

      if you want users to be prompted to update their client software.

   3. Specify the number of grace logins you want to allow a user before forcing an AutoUpdate, for example:

      GraceLoginCount=2

      This entry is ignored if ForceUpdate=No.

   4. If you will be using an IP connection for AutoUpdate, specify

      SetupIPEnabled=Yes

7. Save the file as setup.cfg. Copy setup.cfg from software_distribution_directory\client to software_distribution_directory\client\win32.

8. If necessary, modify addon.cfg files with the values you want. See Modifying the addon.cfg File for more information.

9. Log in to ConsoleOne as an Admin equivalent.

10. Click Tools > GroupWise System Operations.

11. Double-click Software Directory Management.

12. Click the software distribution directory > Update.

13. Select Force Auto-Update Check by GroupWise Components.

    This causes the GroupWise client to check for a new version. If a new version is found, the next time a user starts the GroupWise client, he or she is prompted to update the client software. If you have set ForceUpdate=Yes, the user will not be prompted before installation begins. If a mapped drive to the software distribution directory is found, the client software is installed from the mapped drive. If a mapped drive to the software distribution directory is not found, GroupWise looks at the IP locations you specified in writeip.ini and installs the client software.

    In the event that no connection to the software distribution directory can be made, the file setupip.err is created in c:\windows of the user's workstation. This file explains why none of the connections could be made.

Modifying the addon.cfg File

The addon.cfg file is an ASCII text file that supports extended ASCII characters. The GroupWise client setup program uses the addon.cfg file to install additional components on users' workstations. The components might include software not shipped with GroupWise. The addon.cfg is specific to each program being installed. The required program files and the associated addon.cfg file must be copied to a subdirectory under software_distribution_directory\client\win32\addons.

During the client installation, the GroupWise setup program will search the subdirectories under the \addons directory for any addon.cfg files. The setup program will then execute the installation program for that component using the settings specified in the addon.cfg. If an entry is missing in the addon.cfg file, the installation program will prompt the user for the required information.

The addon.cfg files for Internet Browser Mail Integration and GroupWise Tip of the Day are included in the corresponding subdirectories under \addons, but the basic control for installing these two components is in the [GWMAILTO] and [GWCHECK] sections of setup.cfg.

For information about installing GroupWise Messenger as an additional component by modifying the addon.cfg file, see "Installing the Messenger Windows Client as a GroupWise Windows Client Add-On" in "Managing Messenger Client Users" in the Messenger 1.0 Administration Guide.

When creating an addon.cfg file for a different component, you must include at least the following section headings and associated entries. If the installation program requires additional information, you can include that information as additional entries. The required entries are as follows:

• [GroupWiseAddon]
• [Name]
• [Description]

Error Log File

If an error occurs during the installation and ShowDialogs=No, the error message is logged in gwsetup.err in the user's \windows directory. If ErrorMessage=error_text has been added as the last entry under the [GroupWiseSetup] section, the error text will be displayed. Otherwise, a generic error message will be displayed notifying the user to contact the system administrator. The log file is an ASCII text file.

Startup Switches for Administrator-Defined Setup

The following startup switches can be used in conjunction with an administrator-defined setup. These switches can be used individually or in combination.

• config=setup_filename
• noconfig
• record