- PVS managed by Citrix Cloud
This release of Provisioning Services supports a connector for Citrix Cloud integration. It enables VDAs provisioned by Provisioning Services to be used in the XenApp and XenDesktop Service. This provides the same functionality as Provisioning Services and XenDesktop in on-premises deployments.
The following elements are required when using Provisioning Services with Citrix Cloud:
XenDesktop builds a version of the PVS PowerShell snapin (Citrix.PVS.snapin) with a subset of the PVS on-premises cmdlet built specifically to run in Citrix Cloud and communicate with PVS on-premises through the Citrix Cloud Connector.
The Cloud Connector acts as a relay which exposes the Azure Provisioning Service endpoints to enable communication between XenDesktop and the XenApp and XenDesktop Service Delivery Controller.
Additionally, the Cloud Connector contains a WCF endpoint listening on the Azure Service Bus for communicating with the PVS Server.
The PVS Server communicates with the Cloud Connector while establishing SOAP calls to MAPI.
The PVS console installation includes the XenApp and XenDesktop SDK. This SDK must be replaced by the XenApp and XenDesktop Remote PowerShell SDK.
The SDK is used by the XenDesktop Setup Wizard to push VDA records to the Delivery Controller in Citrix Cloud.
For PVS deployments, the Citrix License Server must be on-premises.
The following dependencies exist when using Provisioning Services and Citrix Cloud:
Traditional XenApp and XenDesktop deployments using Provisioning Services require the management of two distinct elements: both the XenApp and XenDesktop deployment and the PVS deployment. Such environments resemble the image below, without the added complexity of illustrating VDA components:
With an on-premises PVS deployment, the XenApp and XenDesktop Service has been extended to work with an on-premises PVS deployment illustrated below:
By extending the XenApp and XenDesktop Service, Citrix eliminates the need to operate and manage the XenApp and XenDesktop deployment while still providing the benefits of a managed Provisioning Services deployment.
Provisioning Services can add PVS-managed VDAs to a machine catalog in the XenDesktop Delivery Controller located in Citrix Cloud, using one of two methods:
The XenDesktop Setup Wizard (XDSW) enables you to create PVS devices and collections, and then create machine catalogs containing these elements. For this functionality to work with the Delivery Controller in Citrix Cloud, the XenApp and XenDesktop SDK must be replaced with the XenApp and XenDesktop Remote PowerShell SDK. This Remote PowerShell SDK is responsible for communicating with the Delivery Controller.
The machine catalog setup wizard imports existing PVS-managed VMs to a XenDesktop catalog. In cases such as these, the VMs must be previously created using the PVS console. Consider:
In Citrix Cloud, PvsPsSnapin has been extended to enable communication from the XenApp and XenDesktop Service to the PvsMapiProxyPlugin, a newly created proxy added to the XaXdCloudProxy in the Cloud Connector.
When using Provisioning Services in a cloud infrastructure, Citrix recommends having at least two Cloud Connectors for each resource location in case of failover. If one Cloud Connector is down, the PvsPsSnapin looks for the other Cloud Connector that is up and is connected to the PVS Server and Citrix Cloud.
If the Cloud Connector goes down during the operations conducted by the machine catalog setup wizard, re-open the wizard. This allows the wizard to re-establish the connection using a new Cloud Connector.
To connect an existing PVS deployment to Citrix Cloud:
When installing this SDK, consider that the PVS console on which this functionality is installed will not be able to contact local XenDesktop deployments. This also applies to the PVS Server; communication exists only to the Citrix Cloud. All devices that are managed by the Delivery Controller in Citrix Cloud will have their vDisk images and VDAs updated to use the Delivery Controller in order to register with XenDesktop.
An on-premises Citrix license server is required in the XenApp and XenDesktop Service deployment. Refer to the Licensing page for more information.
Connecting a PVS deployment to the service requires the addition of the Cloud Connector to your managed components, for example, your resource location. When adding this connector to managed components, consider:
To add the Cloud Connector, refer to the instructions on the Citrix Cloud Connector page.
To use Citrix Cloud with PVS, you must use a version that integrates with the XenApp and XenDesktop Service. For optimum performance, Citrix recommends using Provisioning Services version 7.18. Access the Applications and Desktops Service Downloads page for the appropriate version.
The PVS Console component includes the XenApp and XenDesktop SDK; this must be replaced with the XenApp and XenDesktop Services Remote PowerShell SDK.
To use the new SDK:
1. Uninstall the XenApp and XenDesktop SDK from the PVS Console by removing the following snapins:
2. Download the Remote PowerShell SDK from the Downloads page. Powershell 3.0 is required to be pre-installed.
3. Install the SDK using the command to execute: CitrixPoshSdk.exe PVS=YES.
Install the downloaded SDK from the command line, and include the argument “PVS=YES.”
To verify the new SDK installation:
The Get-BrokerServiceStatus cmdlet indicates that the Delivery Controller is OK.
Firewall configurations typically require zero or minimal updates. Consider the following:
Personal vDisk functionality is not supported.
To add PVS managed VDAs to a machine catalog:
The XenDesktop Setup Wizard creates PVS devices and collections, then creates machine catalogs containing these elements. The Wizard prompts for the XenDesktop Controller address. Provide the address of one of the Cloud Connector machines (rather than the Controller address).
After entering the address of the Cloud Connector, click Next.
The Citrix Cloud authentication screen appears, prompting for sign in credentials. This prompt, invoked by the PVS Console, is generated by the XenApp and XenDesktop Remote PowerShell SDK.
The Citrix Cloud credentials enable the SDK to securely communicate with the XenApp and XenDesktop Service in order to configure the machine catalogs. The remaining steps in the XenDesktop Setup Wizard are unchanged. The only difference is the prompt for the Citrix Cloud sign-in credentials when the wizard first invokes the cmdlet in the Remote PowerShell SDK.
This Studio wizard adds existing managed PVS VMs to a catalog. In this scenario, the VMs were previously created using the PVS console. To use this wizard:
5. On the Device Collection page, provide the address of the PVS Server and click Connect.
6. Provide the login credentials for the PVS administrator and click OK.
After entering the login credentials, Studio communicates with the Cloud Connector, which then forwards requests to the PVS Server using the specified credentials. If a valid PVS administrator is provided, device collections are displayed.
This authentication method represents the only difference between an on-premises XenApp and XenDesktop deployment and a XenApp and XenDesktop Service deployment in Citrix Cloud. In an on-premises case, the identity of the Studio user authenticates to the PVS Server. In the service model, an explicit authentication is required because Studio runs in an AD environment with no trust relationships to the AD of the PVS deployment.
When setting up a machine catalog using the wizard, the Device Collection screen displays the state of PVS cloud connection. If the feature has not been enabled, an error message appears, indicating that “PVS for Cloud feature is not enabled”.
Use the information in this section to troubleshoot issues related to using the XenDesktop Setup Wizard for Delivery Controller connectivity.
To verify connectivity:
To install the remote PowerShell SDK on the PVS Server, you must uninstall the 5 XenDesktop snapins from the PVS Server, then install the remote PowerShell SDK.
Use the information in this section to troubleshoot connectivity problems between the Delivery Controller and the Provisioning Services Server. To verify connectivity:
1. Ensure that the Cloud Connector in the resource location is installed successfully.
2. Ensure that the Cloud Connector is on the same VLAN\VNET as the PVS console system.
3. In Citrix Studio, ensure that the Zones screen properly displays the Cloud Connectors.
4. Verify that at least one Cloud Connector is “Connected.” To do this:
5. Verify that PVS Support in Citrix Cloud is enabled. Ensure that the PvsSupport feature toggle is enabled in the customer’s configuration and by the Citrix Cloud administrator.
6. Verify that the Citrix Remote Broker Provider is up and running in the Cloud Connector. Refer to the Cloud Connector to see if the Citrix Remote Broker Provider Service is running.
Use the information in this section when using the MCS wizard in Studio to import PVS devices into XenDesktop devices. Verify that: