Microsoft System Center Configuration Manager environments
Sites that use Microsoft System Center Configuration Manager (Configuration Manager) to manage access to applications and desktops on physical devices can extend that use to XenApp or XenDesktop through these integration options.
- Citrix Connector 3.1: Citrix Connector provides a bridge between Configuration Manager and Citrix Virtual Apps and Desktops. The Connector enables you to unify day-to-day operations across the physical environments you manage with Configuration Manager and the virtual environments you manage with Citrix Virtual Apps and Desktops. For more information, see Citrix Connector 3.1.
- Configuration Manager Wake Proxy feature: The Remote PC Access Wake on LAN feature requires Configuration Manager. For more information, see Remote PC Access.
- XenApp and XenDesktop properties: XenApp and XenDesktop properties enable you to identify Citrix virtual desktops for management through Configuration Manager. (Configuration Manager uses the former name of Citrix Virtual Apps and Desktops: XenApp and XenDesktop.) These properties are automatically used by the Citrix Connector but can also be manually configured, as described in the following section.
Properties are available to Microsoft System Center Configuration Manager to manage virtual desktops.
Boolean properties displayed in Configuration Manager may appear as 1 or 0, not true or false.
The properties are available for the Citrix_virtualDesktopInfo class in the Root\Citrix\DesktopInformation namespace. Property names come from the Windows Management Instrumentation (WMI) provider.
|AssignmentType||Sets the value of IsAssigned. Valid values are: ClientIP, ClientName, None, and User (sets IsAssigned to True)|
|BrokerSiteName||Site; returns the same value as HostIdentifier|
|DesktopCatalogName||Machine catalog associated with the desktop.|
|DesktopGroupName||Delivery Group associated with the desktop.|
|HostIdentifier||Site; returns the same value as BrokerSiteName.|
|IsAssigned||True to assign the desktop to a user, set to False for a random desktop|
|IsMasterImage||Allows decisions about the environment. For example, you may want to install applications on the master image and not on the provisioned machines, especially if those machines are in a clean state on boot machines. Valid values are: True on a VM that is used as a master image (this value is set during installation based on a selection), or cleared on a VM that is provisioned from that image.|
|IsVirtualMachine||True for a virtual machine, false for a physical machine.|
|OSChangesPersist||False if the desktop operating system image is reset to a clean state every time it is restarted; otherwise, true.|
|PersistentDataLocation||The location where Configuration Manager stores persistent data. This is not accessible to users.|
|PersonalvDiskDriveLetter||For a desktop with a Personal vDisk, the drive letter you assign to the Personal vDisk.|
|BrokerSiteName, DesktopCatalogName, DesktopGroupName, HostIdentifier||Determined when the desktop registers with the Controller; they are null for a desktop that has not fully registered.|
To collect the properties, run a hardware inventory in Configuration Manager. To view the properties, use the Configuration Manager Resource Explorer. In these instances, the names may include spaces or vary slightly from the property names. For example, BrokerSiteName may appear as Broker Site Name.
- Configure Configuration Manager to collect Citrix WMI properties from the Citrix VDA
- Create query-based device collections using Citrix WMI properties
- Create global conditions based on Citrix WMI properties
- Use global conditions to define application deployment type requirements
You can also use Microsoft properties in the Microsoft class CCM_DesktopMachine in the Root\ccm_vdi namespace. For more information, see the Microsoft documentation.