A Delivery Group is a collection of machines selected from one or more Machine Catalogs. The Delivery Group specifies which users can use those machines, plus the applications and/or desktops available to those users.
Creating a Delivery Group is the next step in configuring your deployment after creating a Site and creating a Machine Catalog. Later, you can change the initial settings in the first Delivery Group and create other Delivery Groups. There are also features and settings you can configure only when editing a Delivery Group, not when creating it.
For Remote PC Access, when you create a Site, a Delivery Group named Remote PC Access Desktops is automatically created.
To create a Delivery Group:
- If you have created a Site and a Machine Catalog, but haven't yet created a Delivery Group, Studio will guide you to the correct starting place to create a Delivery Group. If you have already created a Delivery Group and want to create another, select Delivery Groups in the Studio navigation pane and then select Create Delivery Group in the Actions pane.
- The Create Delivery Group wizard launches with an Introduction page, which you can remove from future launches of this wizard.
- The wizard then guides you through the pages described below. When you are done with each page, click Next until you reach the final page.
Select a Machine Catalog and select the number of machines you want to use from that catalog.
Good to know:
- At least one machine must remain unused in a selected Machine Catalog.
- A Machine Catalog can be specified in more than one Delivery Group; however, a machine can be used in only one Delivery Group.
- A Delivery Group can use machines from more than one catalog; however, those catalogs must contain the same machine types (Server OS, Desktop OS, or Remote PC Access). In other words, you cannot mix machine types in a Delivery Group. Similarly, if your deployment has catalogs of Windows machines and catalogs of Linux machines, a Delivery Group can contain machines from either OS type, but not both.
- Citrix recommends that you install or upgrade all machines with the most recent VDA version, and then upgrade Machine Catalogs and Delivery Groups as needed. When creating a Delivery Group, if you select machines that have different VDA versions installed, the Delivery Group will be compatible with the earliest VDA version. (This is called the group’s functional level.) For example, if one of the machines you select has VDA version 7.1 installed and other machines have the current version, all machines in the group can use only those features that were supported in VDA 7.1. This means that some features that require later VDA versions might not be available in that Delivery Group. For example, to use the AppDisks feature, the VDAs (and therefore the group's functional level) must be a minimum version 7.8.
- Each machine in a Remote PC Access Machine Catalog is automatically associated with a Delivery Group; when you create a Remote PC Access Site, a catalog named Remote PC Access Machines and a Delivery Group named Remote PC Access Desktops are created automatically.
This page appears only if you chose a Machine Catalog containing static (assigned) desktop OS machines. Choose either Applications or Desktops on the Delivery Type page; you cannot enable both.
(If you selected machines from a Server OS or Desktop OS random (pooled) catalog, the delivery type is assumed to be applications and desktops: you can deliver applications, desktops, or both.
To add an AppDisk, click Add. The Select AppDisks dialog box lists available AppDisks in the left column. The right column lists the applications on the AppDisk. (Selecting the Applications tab above the right column lists applications in a format similar to a Start menu; selecting the Installed packages tab lists applications in a format similar to the Programs and Features list.)
Select one or more checkboxes.
For more information, see the AppDisks article.
Specify the users and user groups who can use the applications and desktops in the Delivery Group.
Active Directory user lists are specified when you create or edit the following:
- A Site’s user access list, which is not configured through Studio. By default, the application entitlement policy rule includes everyone; see the PowerShell SDK BrokerAppEntitlementPolicyRule cmdlets for details.
- Application Groups (if configured).
- Delivery Groups.
The list of users who can access an application through StoreFront is formed by the intersection of the above user lists. For example, to configure the use of application A to a particular department, without unduly restricing access to other groups:
- Use the default application entitlement policy rule that includes everyone.
- Configure the Delivery Group user list to allow all headquarters users to use any of the applications specified in the Delivery Group.
- (If Application Groups are configured) Configure the Application Group user list to allow members of the Administration and Finance business unit to access applications A through L.
- Configure application A’s properties to restrict its visibility to only Accounts Receivable staff in Administration and Finance.
There are two types of users: authenticated and unauthenticated (unauthenticated is also called anonymous). You can configure one or both types in a Delivery Group.
To access applications and desktops, the users and group members you specify by name must present credentials such as smart card or user name and password to StoreFront or Citrix Receiver. (For Delivery Groups containing Desktop OS machines, you can import user data (a list of users) later by editing the Delivery Group.)
For Delivery Groups containing Server OS machines, you can allow users to access applications and desktops without presenting credentials to StoreFront or Citrix Receiver. For example, at kiosks, the application might require credentials, but the Citrix access portal and tools do not. An Anonymous Users Group is created when you install the first Delivery Controller.
To grant access to unauthenticated users, each machine in the Delivery Group must have a VDA for Windows Server OS (minimum version 7.6) installed. When unauthenticated users are enabled, you must have an unauthenticated StoreFront store.
Unauthenticated user accounts are created on demand when a session is launched, and named AnonXYZ, in which XYZ is a unique three-digit value.
Unauthenticated user sessions have a default idle timeout of 10 minutes, and are logged off automatically when the client disconnects. Reconnection, roaming between clients, and Workspace Control are not supported.
The following table describes your choices on the Users page:
Enable access for
Add/assign users and user groups?
Enable the "Give access to unauthenticated users" check box?
Only authenticated users
Only unauthenticated users
Both authenticated and unauthenticated users
Good to know:
- You cannot add applications to Remote PC Access Delivery Groups.
- By default, new applications you add are placed in a folder named Applications. You can specify a different folder. For details, see the Manage Applications article.
- You can change the properties for an application when you add it to a Delivery Group, or later. For details, see the Manage Applications article.
- If you try to add an application and one with the same name already exists in that folder, you are prompted to rename the application you are adding. If you decline, the application is added with a suffix that makes it unique within that application folder.
- When you add an application to more than one Delivery Group, a visibility issue can occur if you do not have sufficient permission to view the application in all of those Delivery Groups. In such cases, either consult an administrator with greater permissions or have your scope extended to include all the Delivery Groups to which the application was added.
- If you publish two applications with the same name to the same users, change the Application name (for user) property in Studio; otherwise, users will see duplicate names in Receiver.
Click the Add dropdown to display the application sources.
- From Start menu: Applications that are discovered on a machine created from the master image in the selected catalog. When you select this source, a new page launches with a list of discovered applications; select those you want to add and then click OK.
- Manually defined: Applications located in the Site or elsewhere in your network. When you select this source, a new page launches where you type the path to the executable, working directory, optional command line arguments, and display names for administrators and users. After entering this information, click OK.
- Existing: Applications previously added to the Site, perhaps in another Delivery Group. When you select this source, a new page launches with a list of discovered applications; select those you want to add and then click OK.
- App-V: Applications in App-V packages. When you select this source, a new page launches where you select the App-V server or the Application Library. Select the applications you want to add from the resulting display and then click OK. For more information, see the App-V article.
If an application source or application is not available or valid, it is either not visible or cannot be selected. For example, the Existing source is not available if no applications have been added to the Site. Or, an application might not be compatible with the supported session types on machines in the selected Machine Catalog.
The title of this page depends on the Machine Catalog you chose earlier in the wizard:
- If you chose a Machine Catalog containing pooled machines, this page is titled Desktops.
- If you chose a Machine Catalog containing assigned machines and specified "Desktops" on the Delivery Type page, this page is titled Desktop User Assignments.
- If you chose a Machine Catalog containing assigned machines and specified "Applications" on the Delivery Type page, this page is titled Application Machine User Assignments.
Click Add. In the dialog box:
- In the Display name and Description fields, type the information to be displayed in Receiver.
- To add a tag restriction to a desktop, select Restrict launches to machines with this tag and then select the tag from the dropdown. (See the Tags article for more information.)
- Using the radio buttons, indicate who can launch a desktop (for groups with pooled machines) or who will be assigned a machine when they launch the desktop (for groups with assigned machines). The users can be either everyone who can access this Delivery Group, or specific users and user groups.
- If the group contains assigned machines, specify the maximum number of desktops per user. This must be a value of one or greater.
- Enable or disable the desktop (for pooled machines) or desktop assignment rule (for assigned machines). Disabling a desktop stops desktop delivery; disabling a desktop assignment rule stops desktop auto-assignment to users.
- When you are finished with the dialog box, click OK.
Enter a name for the Delivery Group. You can also (optionally) enter a description, which will appear in Receiver and in Studio.
Review the summary information and then click Finish. If you did not select any applications or specify any desktops to deliver, you are asked if you want to continue.