Citrix states in CTX825537

CTX825537 - How to Install Applications on a Different Drive with Installation Management Services 1.0b and Installation Manager 2.0

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

Document ID: CTX825537, Created on: Jun 23, 2000, Updated: Apr 23, 2003

Products: Installation Management Services 1.0b

This document describes how to install applications on a drive different from the system drive using Installation Management Services.

WARNING! Using Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. Citrix cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk.

For information about how to edit the registry, view the "Changing Keys and Values" Help topic in Registry Editor (Regedit.exe) or the "Add and Delete Information in the Registry" and "Edit Registry Data" Help topics in Regedt32.exe. Make sure you back up the registry before you edit it. If you are running Windows NT, also update your Emergency Repair Disk (ERD).

Installing Applications on a Drive Other Than the System Drive Using Installation Management Services 1.0b

1. On servers where you do not want the application installed on the system drive, set the value of APPINSTALLDISK as mentioned in the Installation Management Services readme.txt:

"You can change this location at any time by editing the following registry key:

HKEY_LOCAL_MACHINESOFTWARECitrixAppCloningPlayerSymbols

Edit the value of APPINSTALLDISK. Before editing the key, use the Control Panel Services applet to stop the Citrix Installer Service. After stopping the service, edit the key (make sure you follow the drive letter with a colon). Then restart the service."

2. When packaging, install the application on a local disk that is not the system drive. The symbol %APPINSTALLDISK% is used in the .wfs file produced by the packager for files installed on this drive (that is, when installing on drive D when the system drive is C).

NOTE: %APPINSTALLDISK% is the only symbol that is replaced by the value of the APPINSTALLDISK setting in the registry. Thus,to use this feature, configure the packaging system with an additional local drive and install the application on this additional drive when packaging.

IMPORTANT: Even though you install the application on a non-system drive, it may still install some files on the system drive. This also affects registry settings that have paths in them. Thus, it is necessary to install the application on a different drive when packaging so that the symbol substitution for %WINDISK% and %APPINSTALLDISK% on both the files and registry settings is done safely.

Installing Applications on a Drive Other Than the System Drive using Installation Manager 2.0

1. On servers where you do not want the application installed on the system drive, set the value of APPINSTALLDISK in the following registry keys:

HKEY_LOCAL_MACHINESoftwareCitrixAppcloningAgentSymbols
HKEY_LOCAL_MACHINESoftwareCitrixAppcloningAgentInstallerSymbols

2. Edit the value of APPINSTALLDISK. Before editing the key, use the Control Panel Services applet to stop the Citrix Installer Service. After stopping the service, edit the key (make sure you follow the drive letter with a colon). Then restart the service.

3. When packaging, install the application on a local disk that is not the system drive. The symbol %APPINSTALLDISK% is used in the .wfs file produced by the packager for files installed on this drive (that is, when installing on drive D when the system drive is C).