Knowledge Base

The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides
Search the VMware Knowledge Base (KB)   View by Article ID

Troubleshooting Active Directory issues in the VMware Horizon View environment (1030465)


  • Unable to deploy virtual desktops to a second domain
  • Adding a secondary domain to your VMware Horizon View environment fails
  • You see the error:

    Bad Domain

  • Deploying desktop pools is successful, but the virtual machines are deleted after the deployment


VMware Horizon View Manager environments are dependent on Microsoft Active Directory (AD) services. For your VMware Horizon View environment to function properly, the Active Directory permissions must be set correctly. You must know the correct path names for contextual items and you must set up a two way trust for any additional domains that you want to utilize for authentication or deployment.

This article provides the steps to troubleshoot Active Directory issues within a VMware Horizon View environment.


One way trust relationship between Active Directory domains will be supported from upcoming release of Horizon View.

Each step given here provides instructions and a link to a document for performing the step and taking corrective action as necessary. The steps are ordered in the most appropriate sequence to isolate the issue and to identify the proper resolution. After completing each step, verify if you are able to add a secondary domain to your VMware Horizon View environment. Work through each troubleshooting step in order, and do not skip a step.

To troubleshoot potential Active Directory issues in your VMware Horizon View environment:

  1. Ensure that you have a proper two way trust. For more information, see Adding a domain to the VMware View Composer service on the Connection Broker fails with the error: Bad Domain Name (1026817).
  2. Ensure that you have set appropriate permissions for Composer operations. For more information, see Minimum permissions required for View Composer (1007659).
  3. Ensure that you have set up the destination organizational units (OUs) properly. If this is not set up correctly, the machines will attempt to deploy, and then delete themselves because there are no permissions or ownership over a OU, or the OU does not exist. This may also cause issues if you migrate virtual desktops between OUs. For more information, see Error during provisioning or deploying a virtual machine (1009436).
  4. Ensure that you are using NT 4 compatible encryption with a Windows Server 2008 domain controller. For more information, see View Composer linked clones fail to finish customizing (1028164).

If your problem continues to exist after trying the steps in this article:

See Also

Update History

08/29/2012 - Added View Manager 5.x to Product Versions 09/18/2013 - Added View 5.2 to product versions

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.


  • 1 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.
What can we do to improve this information? (4000 or fewer characters)
  • 1 Ratings