InstallShield 2016
Some application features are ignored when creating a Citrix profile. Therefore, some additional pre- or post-conversion actions must be taken in order for the virtual application to work.
One action you could take to try to include ignored features in a virtual application is to first repackage the application using the Repackaging Wizard that is included with Repackager, and then convert the repackaged application to a virtual package.
Edition • Repackager is included with AdminStudio.
The following table lists the application features which require additional, manual conversion steps:
Windows Installer Feature |
Manual Conversion Steps |
||||||||||||
User-Defined Custom Actions |
When converting a Windows Installer package to a Citrix profile, all custom actions are ignored. For user-defined custom actions, a warning message is generated. Any modifications to a target machine that a custom action in this Windows Installer package may create will not be propagated into the Citrix profile. The resolution that you should perform depends upon the purpose of the custom action:
To resolve this issue, first attempt to launch the converted package on Citrix XenApp. If you receive any application errors, you need to repackage this application, by performing the following steps. To successfully convert a package with user-defined custom actions:
|
||||||||||||
Services |
Citrix XenApp does not support any type of services. Therefore, to resolve this issue, you need to install any required services outside of the isolation environment on the user desktop machines. To successfully convert a package with services:
|
||||||||||||
COM+ |
While Citrix XenApp supports communicating with COM+ applications, it does not support installing COM+ services. Therefore, an application that contains COM+ services cannot be deployed on Citrix XenApp. |
InstallShield 2016 Help LibraryAugust 2016 |
Copyright Information | Flexera Software |