Cloudpaging can be used to deploy applications in both single session and multi-session VDI/RDS environments. The defaults provided when packaging with Cloudpaging Studio will typically work in both single session and multi-session environments, there are assets of some applications that are not well suited for multi-session environments. For example, an application may contain a printer driver that will be visible across sessions and this may not be desired. 

How to Package for a Multi-session Environment

Here is a list of application assets that can affect multi-session:

  • Files and Registry keys Dispositions – Depending on the location of Layer-2 or Layer-1 files and keys, these assets can affect multi-sessions. If the asset is located in system location (i.e. %windir%, HKLM, etc.) then this application package can affect sessions. It is recommended to limit Layer-2 usage to user defined folders (e.g. %appdata%) and/or hives (e.g. HKCU).
  • Services and Drivers – Services are shared, system wide resources in the Windows environment and cannot be easily siloed from other user sessions.
  • Virtualization Settings
    • Fonts – By default Fonts are shared, system wide resources in the Windows environment. It is recommended to use private fonts to avoid multi-session sharing, if necessary.
    • Printer drivers – Prints are made available to all users in Windows and selecting to register a printer driver by selecting Restart Print Spooler can affect multi-sessions.
    • Start-up items – It is recommended that startup items registry keys (i.e. “Run” keys) to be set to Layer-3. If set to Layer-2, these items can affect the whole machine when rebooted.
    • System reboots – Occasionally there are some applications containing boot drivers that will require a system reboot. These applications should be avoided in a multi-session environment, or should be tested without rebooting as many will still function properly.
  • Security Settings – Process overrides allowed system services and processes access to Layer-3 assets in an application container can affect multi-sessions. Only processes within a user session should be allowed in an override and all others overrides should be removed to work in a multi-session environment.
  • Configurable AppEvents (CAE) – As CAE's are scripts that can modify the base system, these must be used to only modify user defined data on the system (i.e. %appdata%, HKCU, etc.).

NOTE: Layer-4 registry keys in a multi-session environment should be kept to a minimum and only set at the upper level keys and avoid marking all child keys to achieve best performance.