To deploy applications to machines managed by Provisioning Services, you create each application using a base deployment type of MSI, App-V, or Script, and then deploy the applications to device collections containing update devices and machine clones.
The following table describes where you target deployments based on how user data is handled and whether a deployment is intended for all users. In Configuration Manager, the Connector uses an update device to represent a VM with a master image.
|OS type||User data handling||Deploy to:|
|Desktop OS or Server OS||Discarded||Device collection containing an update device|
|Desktop OS||On PvD||
The following table indicates whether the Connector or Provisioning Services handles various orchestration tasks. Applications are available for publishing to users after all specified clone machines are updated. For more information about deployment orchestration, refer to Deployment orchestration.
|Provisioning method||OS type||Product handling orchestration tasks|
|Deployment to master image||Deployment to clones||Notifications|
|Provisioning Services||Desktop OS||Connector||Provisioning Services||Not applicable|
To deploy applications to machine catalogs managed by Provisioning Services, you work with Configuration Manager, XenApp or XenDesktop, and Provisioning Services. The following diagram and discussion describe the Provisioning Services setup process.
The Connector integration with Provisioning Services incorporates the tasks that you normally perform during provisioning setup and configuration (steps 1 through 4 in the diagram) and synchronizes provisioned assets with Configuration Manager.
A list of all devices that have the Citrix VDA installed and configured as a master image appears. If the list is empty, either the VDA is not installed on any devices managed by Configuration Manager or Configuration Manager has not performed a hardware inventory on VDAs configured as a master image.
The update device is added to the device collection, increasing the member count by one.
The Deploy Software Wizard appears.
Do not change the Collection.
For information about scheduling deployments, refer to Microsoft TechNet documentation for System Center 2012 Configuration Manager.
Green check marks on the Completion page indicate that the application is scheduled for deployment.
If the application deployed, a green success item appears and, under Asset Details, the name of the update device appears.
After the application deploys, the In Progress tab lists the clones of the image, with a status of "Waiting For Orchestration."
For more information, refer to "Promote the new vDisk version to production" in Using Provisioning Services with Citrix Connector 7.5 for Configuration Manager.
The Connector then orchestrates the installation of applications and updates on the update device for both Server OS and Desktop OS machines. The Connector orchestrates the reboot of Server OS clones after the vDisk is promoted to production. Use the Provisioning Services console to reboot PVS Desktop OS clones after the vDisk is promoted to production.
If the application deployed, a green success item appears and, under Asset Details, the names of the update device and machine clones appear.