How to Create an Unattended Installation of the ICA Win32 Program Neighborhood C

Citrix states in their article: CTX246795

CTX246795 - How to Create an Unattended Installation of the ICA Win32 Program Neighborhood Client versions 4.21.779 to 6.21.986

This document was published at: http://support.citrix.com/kb/entry.jspa?externalID=CTX246795

Document ID: CTX246795, Created on: Sep 8, 2000, Updated: Sep 8, 2003

Products: ICA Win32 Web Client, ICA Win32 Program Neighborhood Client

This technote explains the current method of performing an unattended install with the Program Neighborhood 32-bit ICA Client.

NOTE: The procedure in this article does not apply to client 6.30.1050 and above because the silent installation method for these versions is now effected through the use of the Windows Installer Service and the MSI distribution of the ICA Client for Win32. Please see the Administrator's Guide for Citrix ICA Win32 Client, http://www.citrix.com/download/bin/license.asp?client=w32 ,for more information.

This procedure requires a system that does not have any version of the Citrix ICA Client installed on it. This fresh system is used to create the Setup.iss file necessary for the silent installation to function properly. The client version being updated must be Program Neighborhood build .715 to .779. The WinFrame 1.8 and the MetaFrame 1.0 Remote Application Manager Clients do not work with this procedure.

WARNING: The License Agreement is always accepted without prompting the user.

Extracting the Installation Files

Build 779 of the client is on the MetaFrame 1.8 for Windows 2000 CD and the directories are already extracted.

However, the build 6.0.910 client and higher use a self-installing executable and the files must be extracted manually. Follow the procedure below to extract the files:

1. Download the latest clients from the Citrix Web site at http://www.citrix.com/download.

2. Open the self-extracting .exe file using Winzip 7.0 or higher.

3. Extract the clients into a temp directory.

4. The directory will contain subdirectories labeled Disk1, Disk2, and Disk3.

Creating the Setup.iss File

1. Copy the sample Setup.iss file below to Disk1 of the Program Neighborhood Client build .779 setup disks.

Download setup.iss

OR

Using client build .910 or later, type setup -r at a command prompt within the Disk 1 directory extracted in Step 4 above. This begins the installation process on the workstation.

2. Answer all installation questions as required by your installation needs.

3. During installation, a Setup.iss file is created in the %systemroot% directory of the workstation. This file contains the answers required for the silent install.

4. Copy Setup.iss to Disk 1 of the installation disk set or to the Disk 1 folder of the network share point.

Editing the Setup.iss File

Using Notepad, make any necessary changes to the Setup.iss file. For instance, you may want to make changes to the following options:

szDir=C:Program FilesCitrixICA Client
szEdit1="ICAClient"

where szDir specifies the directory where the client will be installed and szEdit1 specifies the client name. Modify this value to ensure that each client has a unique name.

This allows the installation to use each client device's NetBIOS name as a unique ICA Client name.

NOTE: You can use the Icasetup.bat file below to specify the clientname dynamically. This file was created based on the .779 build. You can easily make the appropriate changes to work with the Setup.iss files created by the .910 or later client builds. The order of the entries in your Setup.iss file may be different based on the client version and options installed.

When Icasetup.bat is executed, it automatically creates the Setup.iss file and launches the ICA client's Setup.exe as long as Setup.exe exists in the same folder as Icasetup.bat. This works perfectly on Windows NT servers but, since Windows 95/98, does not support the %COMPUTERNAME% and %SYSTEMDRIVE% environment variables. As the administrator, you have to do one of two things:

Add a COMPUTERNAME and SYSTEMDRIVE environment variable to each Windows 95/98 server before executing Icasetup.exe

-OR-

Edit the Icasetup.bat file and replace %COMPUTERNAME% and %SYSTEMDRIVE% with hardcoded strings specific to each Windows 95/98 workstation.

NOTE: For information about how to set the Computername and Systemdrive variables on Windows 95/98/ME workstations, see Microsoft article: %UserName% Variable Is Not Supported in Windows 95/98/Me.

Installing the Client

Execute Setup -S from the Disk 1 directory. The -S parameter designates "silent mode" for Install Shield.

OR

Execute Icasetup.bat from the Disk 1 directory. Download icasetup.bat

The installation begins without prompting you for any information. Installation is complete when the Program Neighborhood icons appear on the desktop.



Primary links

Custom Search

Who's new

  • Cachleferah
  • Weedbacuupe
  • vororourn
  • vDonellaCandrah
  • SnnaSusi

Who's online

There are currently 0 users and 5 guests online.

KrissysCorner.com RuthSwensonLaw.com CreativeLizardProductions.com

DISCLAIMER:

None of this has anything to do with us, someone else is responsible for the entire thing, and we have no idea who or why. We do not know anything about it. It may be alien life forms for all we know: we haven't a clue. You cannot blame us for anything that may result from your visit. That was entirely your own personal choice, made by you of your own volition, and without our knowledge. We do not, after all, have any control over you and cannot by any stretch of the imagination be expected to accept or acknowledge, be it legally or morally, any accountability for decisions made by you on an independent basis, utilizing your own free will, and without our intervention. We are therefore in no way, shape, or form answerable to anyone for any consequences arising from the aforementioned or indeed any other actions, similar or otherwise, because it was not us that did, or did not do anything. It is not even remotely our fault, and we are in no way prepared or willing to accept any liability, not even slightly, ever. We are, in fact completely and utterly blameless, in that it is definitely not our concern, and no blame can possibly be laid at our doorstep, even if we had one, the possession of which we hereby reserve as being entirely our own free choice. The onus is not on us at all, and furthermore, never has been. The entire matter is wholly beyond our control, and completely out of our hands, each of which are washed scrupulously clean of the whole business. We are not accountable for anything at all, and we hereby categorically deny all responsibility for all that has ever, or will ever happen. Our innocence is therefore wholly beyond doubt and absolutely unimpeachable, and so cannot, under even the remotest or unlikeliest circumstances, be brought into question. By clicking either on a link on this site, clicking on a link that leads to this site, or by arriving at this site by natural or supernatural means, you are in effect accepting responsibility for the fact that it is all entirely your own fault, down to the most miniscule detail, and that you are wholly accountable for whatever outcome may arise as a consequence of the aforementioned action or actions insofar as they were undertaken personally by you on an entirely voluntary basis and without any persuasion, coercion or influence from any party or parties other than yourself. Don't come sniveling to us, we are only figments of your imagination. I also agree that if I am ever with a contributor to this website during mealtimes I agree to pay for any super-sizing of their meal, or at least a nice dessert or one of those foo-foo drinks with an umbrella or a monkey. By admitting to have seen the worthless spineless drivel on this website (also known as content)

I Agree Wholeheartedly and Without Reservation to the above. (Except maybe for that part about the monkey.)

All Your Base Are Belong To Us.

Soylent Green Is People!

Never make a bet with a Sicilian when Death is on the Line!

No. Really, I do agree.