Microsoft AVD, Citrix, Other Remote Desktop Distribution

To deploy FlexApp One applications in remote desktop environments, three steps are typically required. All three steps are required for Microsoft AVD and Citrix Virtual Apps environments.

  1. Install the prerequisite FlexApp service and run-time engine. This can be done running one of the following:
    1. Run the installer in system context:
    2. Installer.exe --install
    3. OR
    4. Run any FlexApp One application (this application might optionally contain prerequisites):
    5. FlexAppOne.exe --install
  2. Sync the file to a local folder, activate the layer, and do this at the system level using one of the following:
    1. If the app is stored on a UNC, run the FlexApp One in system context with:
    2. \\server\share\FlexApp\Appname\Appname.exe --sync C:\ProgramData\FlexApp\Appname\Appname.exe --index 999 --system
    3. OR
    4. If the app is local, run the FlexApp One in system context with:
    5. C:\ProgramData\FlexApp\Appname\Appname.exe –-index 999 -–system
  3. Finish the app deployment by running the local FlexApp One in system context with the following to add the application to the Start Menu, and create a shortcut in the public area without launching the app using the following:
  4. C:\ProgramData\FlexApp\Appname\Appname.exe -–ctl -–addtostart -–skipactivation --system

Using Session Isolation on multi-user OSes

FlexApp One can be deployed in a way such that activated application folders and files are hidden from users that have not, or cannot, launch the FlexApp One package EXE. Normal operation does not hide the activated application's files from users. If a user cannot access the FlexApp One EXE, they would normally still be able to find the application's files in Program Files and launch the files directly. Enabling Session Isolation prevents a user from being able to see or launch the files.

  1. Add the --sessionisolate option to existing package activation commands, whether on-boot or on-demand using Click-to-Layer (--ctl --sessionisolate). This prevents users without access to the app from looking for the files within Program Files and launching it directly.

  2. Restrict access to the FlexApp One package EXE only to those that should have access. If anyone can access the FlexApp One EXE and launch it with --SessionIsolate, they can unhide the files within Program Files, so an ACL to restrict access is a necessary part of this feature.