The example scenario in this document describes the major steps to follow to provision and deliver two Delivery Groups. One Delivery Group is based on a Windows Server 2008 R2 master image but has a Windows 7 look and feel. The other is based on a Windows 8 master image. The following personalization capabilities ensure a consistent logon experience and customizable applications for users in those Delivery Groups:
For simple scenarios, you might consider using Citrix Profile management, which is installed silently on master images when you install the Virtual Delivery Agent. It lets you define profile behavior on a per-Delivery Group basis.
A new corporate desktop strategy means you want to virtualize as many corporate desktops as possible. In this example, you begin with the desktops in two of your organization's teams.
Members of the Accounts team do not need to install their own applications, so they do not require Personal vDisks. However, they typically customize the applications on their physical machines (for example, select a home page). To preserve personalized settings in your new virtualized environment use profile management policies.
The sample scenario assumes the following about your environment:
To implement the new desktop strategy effectively, use these required components:
Use of MCS provides consolidated administration through Citrix Studio.
You must use the Provisioning Services console to manage Provisioning Services.
Studio is the management console that enables you to configure and manage your deployment, eliminating the need for separate management consoles for managing the delivery of applications and desktops.
Studio is a Microsoft Management Console snap-in that displays all of the objects in your deployment. It provides various wizards to guide you through setting up your environment, creating workloads to host applications and desktops, and assigning applications and desktops to users.
After installing required components, configure your environment using the following general steps.
When creating the site, select the storage location for Personal vDisks. Although you store Personal vDisks (.vhd disks) physically on the hypervisor, they do not have to be in the same location as other disks attached to the virtual desktop. This can reduce the cost of Personal vDisk storage.
If using Machine Creation Services: Because users do not need to connect to the same instance of a desktop each time they log on, specify virtual machines of the random type.
If using Provisioning Services: Create the catalog by connecting to a Provisioning Services server and selecting a suitable device collection. Because users want a highly personalized desktop, specify virtual machines of the static type to which you attach Personal vDisks. Also specify the size of the vDisks and the drive letter to use for them.
To each Delivery Group, add accounts for the users in each team (so the right people can access the right desktops). Also add a test user account for each team.
To ensure a consistent experience when an Accounts user connects to different, randomly assigned desktops in that team's catalog, use profile definition policies to specify features such as the location of any redirected folders.
Test the user experience as follows:
Is your Windows 7 desktop displayed correctly in the Desktop Viewer? Does it look and behave like a Windows 7 desktop even though it was created from a Windows Server machine? Change an application setting or preference that will be saved in your profile; then log off and on again. Is the new setting or preference saved?
Is your Windows 8 desktop displayed correctly in the Desktop Viewer? Do you have a drive (the Personal vDisk) that has the letter you specified while creating the machine catalog for this desktop? Can you install applications and save data on that drive?