Packages should be created for normal desktop and it can be transformed to work in citrix enviroment by changing the ROOTDRIVE and INSTALLDIR property in command line or in transforms.

Ex:

INSTALLDIR=W:\apps\Adobe\reader 8.0\

ROOTDRIVE=W:\

Cheers

Hi,

Also keep in mind that Citrix users have roaming profiles.

It's been a while since I packaged for Citrix, but I do remember having to write vbscripts to make the application work with their roaming profiles.

For one application a local policy had to be modified. "Right to create global objects", it was.

Maggie (who is still trying to get used to the new site).

Users are not allowed to trigger a repair so you need to make sure any files installed to a user's profile is copied there in some other way. This is normally done by a logon-script. As the users are now allowed to trigger a repair then it would be a good idea to remove any advertise info: use normal (non-advertised) shortcuts , convert COM-Advertise (ex. DLL registration) to Registry table and so on to minimize any entrypoint execution.

You should also read-up regarding shadow registry & timestamp.

Before going for repackaging verify that the application supports to be executed in a TS/Citrix environment. A requirement would be that the application can be launched by two separate users at the same time!

A side-note: active setup doesn't work for published (seamless) application.