Product Documentation

Delivery Groups

May 03, 2015
Delivery Groups are collections of machines, and specify who can use a group of desktops or applications. Create Delivery Groups for specific teams, departments, or types of users. With Delivery Groups, you can:
  • Specify groups of users who access desktops, applications, or desktops and applications
  • Add users and groups of users

Delivery Group users

To deliver applications and desktops, you add users or user groups to Delivery Groups. You can select user groups by browsing or entering a list of Active Directory users and groups.

For Desktop OS Delivery Groups, you can import user data from a file after you create the group.

Delivery Group user experience

A Delivery Group's characteristics are based on the desktops or machines within the group's machine catalog. A desktop is a virtual or physical machine that is created manually through the Create Machine Catalog wizard. For Server OS and Desktop OS machine catalogs, they can also be provisioned automatically using Machine Creation Services or Provisioning Services. The desktop characteristics come from the machine catalog to which they are assigned.

A machine catalog is a collection of physical computers and virtual machines that you assign to users through the Delivery Group. What the user sees depends on the machine type:
  • Server OS desktops and applications — Users experience a Windows server environment. This type lets multiple user sessions share a single Windows Server environment. This option is appropriate for users who perform well-defined tasks, and do not require personalization. This is a random desktop environment that let users connect to any available Windows server environment.
  • Desktop OS desktops and applications — Users experience a Windows client environment. This type lets multiple users log in to one Windows client environment. This option provides the following desktop environments:
    • Static environment for users and lets them connect to a personalized desktop or application
    • Random environment in which the machine state is reset on user logoff, and are available for other users
  • Remote PC Access machines that provide users with remote access to their office desktops.

Neither machine catalogs nor Delivery Groups can contain a mixture of these types; they must include either all Server OS, Desktop OS, or Remote PC Access machines.

Delivery types

Depending on your environment as described in Delivery Group user experience, you can select a Delivery Groups type that determines what Delivery Groups provide to user devices:
  • Desktops only
  • Applications only
  • Desktops and applications (not available for static Desktop OS machines)

Personalize desktops for users

The example scenario in this topic 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:

  • Policies and Active Directory Group Policy Objects provide global management of user personalization settings across both 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.

  • The Personal vDisk feature retains the single image management of pooled desktops while allowing users to install applications and change their desktop settings. This feature is used for the Delivery Group that is based on a Windows 8 image.

Desktop strategy

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.

  • The Accounts team use a large number of physical workstations installed with several standard financial applications. The workstations run Windows 7. To replace these with virtual desktops, create a Windows Server 2008 R2 Delivery Group with a Windows 7 look-and-feel for this team.

    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 Sales team are eager to upgrade to Windows 8 on workstations that they use to test their customers' applications. The team must be able to install and uninstall the desktops themselves, so use the Personal vDisk feature to enable that capability.

Desktop environment

The sample scenario assumes the following about your environment:

  • Your network has fast, low latency connections
  • You have estimated the space needed for Personal vDisks based on the actual and expected levels of personalization in the enterprise

To implement the new desktop strategy effectively, use these required components:

  • A supported hypervisor
  • XenApp or XenDesktop
  • A provisioning solution:
    • Machine Creation Services (MCS) is available by default if, when creating an application and desktop delivery site, you configure a Host and specify that MCS is to create VMs.

      Use of MCS provides consolidated administration through Citrix Studio.

    • Citrix Provisioning Services (PVS) is another option for use with System Center 2012 Virtual Machine Manager. To prepare for Provisioning Services use, you must separately install the Provisioning Services server and configure a Provisioning Services master vDisk image. VDA installation installs the Provisioning Services agent on the master images for Windows 7 and Windows 8.

      You must use the Provisioning Services console to manage Provisioning Services.

    Note: A provisioning solution is not required to deploy unmanaged physical desktops.
  • Master image for Windows Server 2008 R2 and for Windows 8
  • Citrix Receiver, installed on a user device to test access to your new virtual desktops

Studio

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.

Configuration

After installing required components, configure your environment using the following general steps. For detailed instructions, see Create a site.

  1. To ensure business continuity, enable the AlwaysOn Availability Groups feature in SQL Server 2012.
  2. After you install the mirror database software on a different server, use Studio to create a full deployment Site on the server where you installed the Delivery Controller. Depending on your database permissions, Studio will configure the principle and mirror Site Configuration Databases, or you can generate scripts that your database administrator can use to configure them. The Controller then automatically recognizes that the Site Configuration Database is replicated and uses the mirror if necessary.

    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.

  3. Use the Create Machine Catalog wizard to create two catalogs for your two master images:
    • A Server OS machine catalog for the Accounts team's Windows Server 2008 R2 desktops.

      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.

    • A Desktop OS machine catalog for the Sales team's Windows 8 desktops.

      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.

      Tip: Remember to run the Personal vDisk inventory if you change the master image used in the Desktop OS machine catalog. When you do this depends on your Provisioning Services setup. For more information, see Provisioning Services.
  4. Using the Create Delivery Group wizard, create two Delivery Groups for your two catalogs:
    • One containing desktops and applications for the Accounts team
    • One containing desktops for the Sales team

    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.

Testing

Test the user experience as follows:

  1. Confirm that your new desktops are registered with the Controller by selecting your Delivery Groups in Studio and clicking Test Delivery Group. Follow the advice in any errors that are displayed.
  2. From the user device, log on to Receiver as a member of Accounts.

    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?

  3. Repeat the last step, logging on to Receiver as a member of Sales.

    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?

Create a new Delivery Group

Delivery Groups specify which users can access desktops or applications, usually based on user characteristics, such as the types of users. Before creating a Delivery Group, note the following:
  • You can only create a Delivery Group if at least one machine remains unused in the machine catalog you select.
  • You cannot use a machine in more than one Delivery Group.
  • You can create Delivery Groups from multiple machine catalogs with the same characteristics.
  • A machine catalog can be associated with one or more Delivery Groups.
  • Multiple catalogs can reference the same Delivery Group.
  • In Studio, you cannot create mixed Delivery Groups from machine catalogs with different machine types. Machine catalog characteristics must match if you want to put the machines into a single group. For example, you cannot mix machines from:
    • Server OS machine catalogs with Desktop OS machine catalogs
    • Allocation type static machine catalog with random machine catalog
  • For Remote PC Access Delivery Groups, any machine added to a Remote PC Access machine catalog automatically is associated with a Delivery Group.

To create a Delivery Group

  1. In Studio, select the Delivery group node and click Create Delivery Group.
  2. Click Add Machines, select a machine catalog for this Delivery Group, and then enter the number of machines the group consumes from the machine catalog.
    Tip: The total number of available machines in the machine catalog appears in the display.
  3. On the Users page, click Add users to add the users or user groups that can access the desktops or applications. You can select user groups by browsing or entering a list of Active Directory users and groups each separated by a semicolon. For Desktop OS Delivery Groups, you can import user data from a file after you create the group.
  4. On the Delivery Type page, select what the desktops deliver to users:
    • Desktops only
    • Applications only
    • Desktops and applications (Not available for static Desktop OS machines)
  5. If the Delivery Group provides applications, on the Applications page, select applications from the display, or add applications as described in Create a Delivery Group application.
  6. On the StoreFront page, select StoreFront URLs to be pushed to Citrix Receiver so that Receiver can connect to a StoreFront without user intervention. Note that this setting is for Receiver running on VDAs.
    • Select Automatic to select server URLs from the list.
    • Select Manually to enter a server address if it does not appear in the list.
    • Select No to omit adding StoreFronts and go to the Summary page.
    • Select Yes to select from existing store URLs listed in the Selected stores display.

      You can also add a new store by clicking Add new and entering the StoreFront's URL if you do not see the StoreFronts you want in the display, and you know the store exists.

  7. On the Scopes page, define which administrators can access the Delivery Group.
  8. On the Summary page, check all details and then enter a display name that users and administrators see and a descriptive Delivery Group name that only administrators see.

You have now created a delivery group. For information about applications that Delivery Groups can deliver to end user devices, see Hosted applications.

Test a Delivery Group

Delivery Group configuration testing occurs:
  • Automatically after you create a Delivery Group
  • By clicking Test Delivery Group:
    • In the Common Tasks page
    • As an action performed on a Deliver Group in the Delivery Groups page

To test a Delivery Group

  1. If you have not already done so, click Studio to display the console.
  2. Select a delivery group and then click Test Delivery Group.
  3. When the test completes, perform the following actions: