Apparently, I had my syntax reversed: you need to go from most specific to most general (bottom to top), while I was doing the opposite.
I'm having this same issue too. I'm trying to figure out what you reversed to get this working. My output looks like this:
Pool cn=2bbd0ac9-05bc-4945-9138-ba95f685c69c,ou=virtualcenter,ou=properties,dc=vdi,dc=vmware,dc=int::Unable to create new VM - Specified AD container partial distinguished name is not valid
The OU I'm trying to create the clones in is VMwareClones off of the root of the domain. I simply replaced CN=Computers with OU=VMwareClones during the deployment wizard but I guess that's wrong?
1 person found this helpful
Hmm, I'm not sure about that, then. I had nested objects, so my circumstance was different. Is your View Manager server in the same domain as that OU? Also, check the OU properties and make sure it actually is an OU and not, for example, a container. Those are the only things which immediately occur to me.
Do you have to specify the scheme of the created objects...
For example, do I need to specify:
or do I just need ou=vdi,ou=businessunit,dc=domain
or do I have the order incorrect?
leave off the DC token(s).
I also kept running into this error when provisioning Clients with View 4.5.
I posted a list of things to check for that I found can cause the "Specified AD container partial distinguished name is not valid." error.
do we have a fix for this i am getting this with horizon 6.2