Is there any way I can install and configure the 32-bit Citrix client on a new workstation automatically, without user interaction?
The short answer is yes. Citrix administrators have been asking for remote installation and configuration for a long time, and Citrix has provided a complete solution in its latest client, Program Neighborhood. First, you configure the client for connection and client parameters; then, you automate the install to eliminate the need for client response.
When administrators hear the name ReadyConnect Client, they often start looking around for a utility under MetaFrame Tools. ReadyConnect Client is really just a name for the process of configuring a client install for standard default configuration. Despite the absence of a friendly wizard, the ReadyConnect Client process is easy, and it works.
- Use Citrix Client creator to create the two install diskettes.
- Install the client on a new machine.
- Using the Program Neighborhood interface, configure the client the way you want all users to see it the first time they log on. Exit Program Neighborhood.
- Rename the following files from *.ini to *.src and copy them to the second install disk:
- appsrv.ini the application server configuration file, which contains user settings that define applications.
- module.ini a file that contains all the configuration information for demand-loadable client modules; the client modules that module.ini supports include transport drivers, protocol drivers, Winstation drivers, and virtual drivers.
- wfclient.ini the Citrix ICA client configuration file, which contains initialization information for the Citrix ICA Client program.
- pn.ini the Program Neighborhood configuration file, which can set the Program Neighborhood environment (e.g., the application set).
Now you're ready to use the install diskettes to create a new, preconfigured workstation.
The setup.exe program installs the Citrix client using Install Shield. Install Shield typically creates a wizard that walks you through an installation, but it can also run in a silent (unattended) mode. To run setup.exe in silent mode, use the following parameters:
- -r causes setup.exe to automatically generate a silent response file (.iss), which records the installation input to the setup wizard screens in the %systemroot%.
- -s performs a silent installation using the .iss file to enter install parameters.
- -f1<path\ResponseFile> points to an alternate location and name of the .iss file. Without this parameter, setup.exe looks for the response file setup.iss in the same folder as setup.exe.
- -f2<path\LogFile> points to an alternate location and name of the log file for the install. By default, the setup program creates and stores the setup.log file in the same folder as setup.exe.
For example, type setup.exe -s -f1C:\windows\setup.iss to initiate a silent installation of the components you specified with the -r option in the setup.iss response file.
You can only run a silent install for the Program Neighborhood client; the silent install process doesn't work for Remote Application Manager or any other ICA clients. The silent install must be the first installation of the client to a clean system, or the installation will fail.
You can make changes to the setup.iss file manually. For example, if you want to change the directory that the client installs to, change the line szDir=C:\Program Files\Citrix\ICA Client to point to the new directory location. You can also create an .iss file in a text editor. The following is an example:
szDir=C:\Program Files\Citrix\ICA Client
szFolder=Citrix ICA Client