Search the VMware Knowledge Base (KB)
View by Article ID

Cannot browse OU during virtual desktop pool customization (2150420)

  • 0 Ratings

Details

You must enter the OU information when you use the desktop pool creation wizard for instant clones or linked clones. The OU’s in the environment must adhere to the specifications provided in RFC 2253 at http://www.ietf.org/rfc/rfc2253.txt.

Non-compliant RFC names in the OUs leads to “InvalidNameException” errors such as in the logs below:


2016-08-30T15:34:35.985-04:00 DEBUG (0398-174C) <ajp-nio-8009-exec-9> [ADContainer] Error while retrieving rdn com.vmware.vdi.adamwrapper.ad.ADContainer.a(SourceFile:147)
javax.naming.InvalidNameException: Invalid name: OU=30\\+ days since last logon (stale),OU=Transition User Accounts,OU=SyncAccounts,OU=Navy,DC=med,DC=ds,DC=osd,DC=mil
 at javax.naming.ldap.Rfc2253Parser.doParse(Rfc2253Parser.java:111)
 at javax.naming.ldap.Rfc2253Parser.parseDn(Rfc2253Parser.java:70)
 at javax.naming.ldap.LdapName.parse(LdapName.java:785)


Solution

To fix this problem, you must change the OU names in the AD environment to make them compliant with RFC 2253.

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.

Feedback

  • 0 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)




Please enter the Captcha code before clicking Submit.
  • 0 Ratings
Actions
KB: