What Can I Do If I Desktop Provisioning Fails When Using Custom Subnets?

Scenarios

If desktop provisioning fails when using a custom subnet created on the VPC console or through an API, the possible cause is that the DNS of the AD server is not configured for that subnet. You can perform the following operations to configure the DNS and provision desktops again:

Procedure

1. Log in to the management console.
2. In the navigation pane, choose Tenant Configuration > Basic Settings. The Basic Settings page is displayed.
3. Click Edit VPC and Subnet on the right of the VPC, as shown in Figure 1.
   Figure 1 Editing the VPC and subnet
   

4. On the right pane of the Edit VPC and Subnet page, select the custom subnet under Subnet, as shown in Figure 2.
   

   By default, the custom subnet is not selected on the Workspace console.

   Figure 2 Selecting the subnet
   

5. Click OK.