Search

Citrix AIE Issues Explained

Wednesday, 17 May 2006 by Michel Roth

Installing an ADF Package Into an Application Isolation Environment with Installation Manager Creates a Temporary File for Each File Installed
If you deploy an ADF package into an Application Isolation Environment using Installation Manager and this package copies files, you may notice that a temporary file is created for each file that is copied. For example, if a file called citrix.hlp is copied into the Application Isolation Environment, a temporary file called citrix00.tmp is be created.
This temporary file is empty, has a 0Kb size, and can be deleted.

This is by design of the Installation Manager and Application Isolation Environment. These temporary files are used and deleted by installation using ADF packages. However, deletion of virtualized files is achieved by creating a "deleted" entity (marker 0 size stream), marked as such through meta-data in the Application Isolation Environment. These files are maintained as 0-byte files under INSTALLROOT.

When An Application is Installed Into the Application Isolation Environment, Changing the Default File Path of the Application Isolation Environment Does Not Take Effect
When an application is installed into the Application Isolation Environment, changing the default file path of the Application Isolation Environment under the Farm properties or Server properties does not take effect on the already created Application Isolation Environment. Only new Application Isolation Environments write to the new path (in case of Farm changes). Creating a new Application Isolation Environment and modifying the path upfront on the properties of the particular Application Isolation Environment works. For example, if you change the file path as follows:

From: Farm Properties > Isolation Settings > User Profile Root > Files: %appdata%\citrix\AIE

To: Farm Properties > Isolation Settings > User Profile Root > Files: C:\NEW_AIE_Folder\AIEApp

The Files path under the User Profile Root for the Application Isolation Environment properties reflects the new farm settings as: C:\NEW_AIE_Folder\AIEApp, but it wont take effect even after flushing the user root and install roots after the change. This behavior is by design. Once something is installed into the Application Isolation Environment, the roots are locked.