Product Documentation

Machine catalogs managed by Provisioning Services

May 09, 2015

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
  • Device collection containing an update device, if deployment is intended for all users
  • User collection, if deployment is optional

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
Server OS Connector Connector Connector
Tip: The Connector provides a summary of machine catalog characteristics, including information about how to handle the catalog. To view that information, navigate to Device Collections > Citrix Delivery Sites > Catalog, right-click a catalog in the list, and choose Machine Catalog Properties.

Prepare for application deployment

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.

PVS setup workflow

 

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.

  • Steps 1 - 3: A Citrix administrator uses Provisioning Services to create maintenance and clone VM templates, create a vDisk, and then run the XenDesktop Setup Wizard to deploy virtual desktops to VMs and to add the virtual desktops to a machine catalog. For more information about the tasks performed in the Provisioning Services console, refer to Using Provisioning Services with Citrix Connector 7.5 for Configuration Manager.
  • Step 4: A Citrix Studio administrator creates a Delivery Group.
  • Step 5: A Configuration Manager administrator designates an update device for the master image and then deploys applications.

Deploy applications to an update device

 

Use the following steps to target application installation to a device collection containing an update device for:
  • Server OS (hosted shared) or Desktop OS (VDI) session machines that discard user data
  • Desktop OS (VDI) session machines that store user data on a PvD
    Important: When user data is stored on a PvD, you target deployment to a device collection containing an update device if the application deployment is intended for all users. If the application is not intended for all users, deploy it to user collections instead. If a user chooses to install the application, it is installed on the user's personal vDisk.
For your reference, a workflow diagram follows the steps.
  1. Choose an update device:
    1. In the Configuration Manager console, expand Assets and Compliance > Device Collections > Citrix Delivery Sites > Catalog, right-click the catalog name, and then choose Designate Update Device.

      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.

    2. Select the machine name and then click Verify and Select. After the machine is verified, click OK.
      Tip: If Configuration Manager cannot contact the machine, an error message displays and you have the choice of continuing or canceling. For more information, refer to Troubleshoot issues.

      The update device is added to the device collection, increasing the member count by one.

  2. To deploy the application, select the catalog name and then click Home > Deploy > Application.

    The Deploy Software Wizard appears.

  3. On the General page: Across from Software, click Browse and then select the application you want to deploy.

    Do not change the Collection.

  4. On the Content page, choose a distribution point for MSI or App-V applications. For Script based applications the application is already on the host and there is nothing to distribute, so just click Next.
  5. On the Deployment Settings page: For Purpose, choose Required so that Configuration Manager forces the application to install.
    Important: If you do not choose Required, Configuration Manager will not deploy the application to the device collection containing the Citrix machine catalog.
    Deployment Settings

  6. On the Scheduling page: Specify a date and time that the application should be available and an installation deadline. The schedule defaults to as soon as possible.

    For information about scheduling deployments, refer to Microsoft TechNet documentation for System Center 2012 Configuration Manager.

  7. Follow the on-screen instructions to complete the wizard.

    Green check marks on the Completion page indicate that the application is scheduled for deployment.

  8. Manage the vDisk image:
    1. In Provisioning Services, create the new vDisk version.
    2. In your hypervisor, boot the Provisioning Services maintenance VM with the new vDisk version.

      For more information, see Updating vDisks and Versioned vDisk Upgrade.

  9. Verify that the application deployed to the update device:
    1. In the Configuration Manager console, click Monitoring > Deployments, right-click the application, and then choose View Status.

      If the application deployed, a green success item appears and, under Asset Details, the name of the update device appears.

    2. If the application has not deployed, wait a while and then click Run Summarization.
      Caution: Do not continue until the View Status screen reports a successful deployment for the update device.

      After the application deploys, the In Progress tab lists the clones of the image, with a status of "Waiting For Orchestration."

  10. In the Provisioning Services console, promote the new vDisk version to production.

    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.

  11. To verify that all clones in the machine catalog are updated: In the Configuration Manager console, click Monitoring > Deployments, right-click the application, and then choose View Status.

    If the application deployed, a green success item appears and, under Asset Details, the names of the update device and machine clones appear.

  12. You can now publish the application. The Connector delays publication until all active machines in the Delivery Group report compliance. Active machines are those that are online and not in XenApp or XenDesktop maintenance mode.
    PVS image maintenance workflow