Citrix MCS in vSphere
This article explains what to consider when publishing to MCS, and building your layers in vSphere.
App Layering appliance
You need these connector configurations to create layers and publish layered images to MCS:
VMware vSphere connector configuration - Gives the appliance the vSphere credentials for the location from which you will import the OS image. The appliance uses this same connector for packaging layers in vSphere.
Citrix MCS in vSphere connector configuration(s) - Supplies the appliance with the credentials it needs to publish layered images to a specific MCS. location.
Layer assignments: Image templates vs Elastic layer assignments
Decide which applications to include in the layered image template, and which to deliver on demand by elastic assignment.
App layers built into the layered image - Include applications that all users receive, and applications that are tightly integrated with the operating system, for example, MS Office. Your MS Office or Visual Studio layer must be included in the image template.
Elastic* App layers delivered dynamically at login - Assign more specialized applications elastically. You can assign these layers to Active Directory groups and users. You can also assign App layers to computer objects (or groups containing computer objects). When the first user logs onto that machine, the layer is mounted, and any users who can connect to this machine receive the layer.
You need a Platform layer for publishing layered images to your provisioning service or hypervisor environment.
For MCS you need a Platform layer with MCS software installed, along with you connection broker software. Also, if the appliance is installed on a different hypervisor than vSphere, install VMware Tools.
Preserve users’ settings and data by enabling User layers in your image template(s).