In many environments that use Terminal Servers and Citrix XenApp, applications are pooled in application silos, which are separate sets of servers hosting different applications. In a silo environment, users simultaneously log in to different servers to use their applications.
When using a single roaming profile, profile corruption or loss of personal settings is likely to happen. When a roaming profile is updated and loaded on different servers at the same time, the risk of profile-related problems increases. Windows Server 2003 and later allow a separate profile path for Terminal Servers to be configured through a group policy. Separate profile paths for each silo might have a big impact on the number of profiles you need to manage.
Through its integration into group policy, User Environment Manager allows separate configuration settings for application silos. You can do this by using the appropriate VMware User Environment Manager administrative template settings, and combining them with the MIcrosoft Loopback processing of Group Policy solution.
For an easier to manage group policy configuration, create a separate organizational unit in Active Directory for each silo. After enabling silo support in the Management Console configuration, you can create a silo tree similar to the organizational unit structure for the silos.
For each silo you need to create a separate Group Policy Object containing the silo-specific User Environment Manager configuration. Clicking on the relevant silo in the User Environment Manager Management Console displays the silo-specific settings that you need to configure in the VMware UEM Group Policy Object.
For each silo group policy object, you must configure the silo-specific Flex configuration files setting to point to the corresponding configuration file path. Flex configuration files from the Flex configuration file path and the silo-specific path are processed. All other User Environment Manager features, such as user environment settings and condition sets are used generally and are not silo-specific.