VMware Horizon Community
tomaddox
Enthusiast
Enthusiast

Specified AD container partial distinguished name is not valid

Hi, everyone,

I'm trying provision desktops with linked clones using QuickPrep in VMware View 3.0.1, and I'm receiving the error above. I have tried using the full DN and the RDN with either CN or OU as the designator, and I am having no luck. The operation works fine on the Computers OU but not on an OU elsewhere in the tree. The permissions appear to be the same, but the OU I would prefer to use has spaces in it. Detailed errors are:

Pool cn=5e49ac1d-6a5b-4710-be3a-a159058c2e8a,ou=virtualcenter,ou=properties,dc=vdi,dc=vmware,dc=int::Unable to create new VM - Specified AD container partial distinguished name is not valid

Desktop Composer Error:VMware.Sim.Fault.AdOperationErrorFault; Error Type:com.vmware.SviService.AdOperationErrorFault;Error FaultActor:null; Error code:Client; Error details:[Lorg.w3c.dom.Element;@15af95a

Any thoughts?

Tags (2)
Reply
0 Kudos
7 Replies
tomaddox
Enthusiast
Enthusiast

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.

Reply
0 Kudos
sdbyrd
Contributor
Contributor

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?

Reply
0 Kudos
tomaddox
Enthusiast
Enthusiast

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.

Mizzou_RobMan
Contributor
Contributor

Do you have to specify the scheme of the created objects...

For example, do I need to specify:

cn=testvm,ou=vdi,ou=businessunit,dc=domain

or do I just need ou=vdi,ou=businessunit,dc=domain

or do I have the order incorrect?

Reply
0 Kudos
pjpg
Enthusiast
Enthusiast

Just

ou=vdi,ou=businessunit

leave off the DC token(s).

Thanks,

...pjpg

Thanks, ...pjpg
Reply
0 Kudos
towlesd
Contributor
Contributor

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.

VMware View 4.5: Specified AD container partial distinguished name is not valid

Reply
0 Kudos
jeetu12iu
Contributor
Contributor

do we have a fix for this i am getting this with horizon 6.2

Reply
0 Kudos