Avatar of Brainstormer
Flag for United States of America asked on

Installing and Publishing Applications in Citrix Isolation Environment

Specs: Citrix Presentation Server 4.5 farm in Windows 2003 Std using remapped drive letter O instead of C. All servers are identically configured.

I have a basic application called MIRCO, it involves an EXE, some DLLs and a INI file that needs to reside in %WINDIR%.The application requires users to have modify rights to the INI, they may delete it via the app and create a new one. A basic INI is already included. The INI absolutely needs to be in the Windows root directory as far as the application is concerned.

I figured this is a good candidate for the Citrix isolation environment, but got confused during the install/publish phases. Below are my steps:

Using the Citrix Installation Manager Packager I created the WFS package using the "Package Selected Files" option. All application files were instructed to be installed in %PROGRAMFILES%\MIRCO\. The INI file is to be copied to %WINDIR%

Added it to the Install Manager packages ready for deployment.
Created an Isolation Environment called MIRCO using the default rules.
Using the Presentation Server Console ->Installation Manager I pushed to my test farm node using the MIRCO isolation environment. The application installed properly under O:\Program Files\Citrix\AIE\MIRCO.

The executable is located here: O:\Program Files\Citrix\AIE\MIRCO\Device\O\Program Files\MIRCO\mirco.exe
The default INI file is located here:O:\Program Files\Citrix\AIE\MIRCO\Device\O\WINDOWS\MIRCO.INI

Next I wanted to publish the application in the isolation environment, so many users can play around with their own INI file, without impacting everyone else.

I modified the MIRCO isolation environment and created a new rule:
Action: Isolate
Object: Files
Selected "Per User" option

Using the Access Management Console I published MIRCO as a new Installedd Application
Provided the EXE command line directly as O:\Program Files\Citrix\AIE\MIRCO\Device\O\Program Files\MIRCO\mirco.exe
Selected the MIRCO isloation environment so each user can have their own INI file.

My question is: Did I do everything right, or is there another way?

Avatar of undefined
Last Comment

8/22/2022 - Mon

That doesnt sound correct at all to me. Maybe I just could follow along. Im just going to detail the basic steps in creating an isolation enviroment and you see if they match up

1 - Make sure you have your web interface/PN Agent Web site set to Dual Mode ( Streaming and Published )
2 - install the citrix packager on a CLEAN fresh install of windows XP or Server 2003 ( depending on what the os that the isolation enviroment is going to be on )
3 - run the packager wizard and step through. you will come to a part where you have to install the application, do so thus creating the isolation enviroment
4 - isolation enviroment should be placed in a file share with the proper permissions on it.
5 - after it is created, go into the AMC and publish and new STREAMED application
6 - point this to the isolation enviroment files sitting on the file server
7- decide how you want this enviroment sent out, directly to the client, directly to the Citrix server, or dual mode best case
8 - assign users
9 - Make sure the streaming client is installed and present on the end client
10 - User connects to web interface, clicks on app and away it goes..


This is not a streamed application, it is a Citrix ADF package and will be run as an installed application from the server

I think the issue may be similar to this:


but I don't know how to install ADF packages with AIESETUP via CLI
All of life is about relationships, and EE has made a viirtual community a real community. It lifts everyone's boat
William Peck

I was able to overcome the issue, even though the "Application was installed into environment" checkbox in the Isolation Settings dialog box is greyed out. I published the application in its isolation environment and used the MS FileMon tool to monitor for the INI file requests. It turned out Citrix already was redirecting the calls to "%HOMEDRIVE%%HOMEPATH%\Windows" directory. Smply placing the INI file there for each user solved my problem and the application is running.

View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
See Pricing Options
Start Free Trial
Ask your own question & get feedback from real experts
Find out why thousands trust the EE community with their toughest problems.