OU Path in the VM Customization Specifications don't work

[woodle]

Hi all,

I hope someone can help me with the following issue.

I deploy machines using templates and VM Customization Specifications (manually and from Omnissa Horizon).

Inside the VM Customization Specification I try to use the "OU Path"-Filed to preset the OU for the Computer Object when joining to the domain.

Domain join works fine, but the computer object is always created in den "default" Computers OU.

I use the entry with the LDAP-Syntax: OU=MyComputer,OU=Site1,DC=domain,DC=tld.

It make no sense if spaces are included or not, I also try with ; instead , without any success.

Take a look at C:\Sysprep\sysprep.xml and there is the part for domain join included, but nothing for my OU.

vCenter and ESXi is patched to the latest releases.

Any comments to find the solution are welcome.

Michael

[Xiaofeng Wang]

Hi there,

This is Xiaofeng from Guest Customization team. I’ve handled a case exactly like yours before.

First, if your guest customization is triggered via vCenter or the vSphere Client, then configuring the OU in that format is completely fine. However, if you’re performing the deployment/customization through Ominissa Horizon, then the domain OU does not need to include the DC components.

For example, in your case, the correct LDAP syntax could be: OU=MyComputer,OU=Site1.

This solution was found by one of our customers while using Omnissa Horizon. Since I’m not an Omnissa Horizon engineer, I don’t know the specific internal behavior, I suspect they may have implemented some additional processing related to the OU field. Anyway,  I recommend giving it a try to see if it resolves your issue.