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.