Problem Definition:

In this example, we will use the CloudConnect Desktop Deployment Wizard to automate the deployment Windows Server 2016 Remote Desktop Session Host for a New Customer in the Multi-tenant Domain (mspCloud).

 

Resolution:

Use the attached PDF Instructions to guide you through the deployment.  If you do not have an existing Remote Desktop Services Connection Broker, do not specify a connection broker when prompted.

Additional Information:

This procedure requires a functional mspCloud with a Windows Remote Desktop Services Deployment including a working Connection Broker, RD Gateway, SSL Certificates, and appropriate DNS rules.

Customers without a functional Windows Remote Desktop Services Deployment should use Citrix Images in place of RDS images when using the Deployment Wizard. See “Deploy a Citrix XenApp Server with the Deployment Wizard” for specific guidance.

Customers wishing to use RDS without a functional Remote Desktop Services Deployment may complete this procedure, however do not select a Connection Broker during deployment. Users will need a VPN or other direct access method to connect using an RDP client.

This procedure is also applicable to Private Domain Deployments, provided the Private Domain has the appropriate prerequisites outlined above.

Applies To:

VMware vCloud Director

Windows Server 2012 RDS

Windows Server 2016 RDS