A lot of cluster errors starts here just because the cluster account has no access in the Active directory.
A sample of a DHCP server that is just created is failing.
Cluster network name resource ‘MVPDHCP79’ failed to create its associated computer object in domain ‘mvp.local’ during: Resource online.
The text for the associated error code is: A constraint violation occurred.
Please work with your domain administrator to ensure that:
– The cluster identity ‘CLUSTER12$’ has Create Computer Objects permissions. By default all computer objects are created in the same container as the cluster identity ‘CLUSTER12$’.
In the cluster manager you can see the just created resources and as you can see the DHCP resource is not online. Why ? well in the error screen you can see
Cluster network name resource ‘MVPDHCP79’ failed to create its associated computer object in domain ‘mvp.local’ during: Resource online.
The text for the associated error code is: A constraint violation occurred.
Please work with your domain administrator to ensure that:
– The cluster identity ‘CLUSTER12$’ has Create Computer Objects permissions. By default all computer objects are created in the same container as the cluster identity ‘CLUSTER12$’.
– The quota for computer objects has not been reached.
– If there is an existing computer object, verify the Cluster Identity ‘CLUSTER12$’ has ‘Full Control’ permission to that computer object using the Active Directory Users and Computers tool.
Cluster resource ‘MVPDHCP79’ of type ‘Network Name’ in clustered role ‘MVPDHCP79’ failed.
The cluster identity ‘CLUSTER12$’ has Create Computer Objects permissions. By default all computer objects are created in the same container as the cluster identity ‘CLUSTER12$’.
Ok seams clear to me the Cluster computer object has no access to create a object in the AD.
Easy to fix just give the account god mode and your done… Well yes but I do it different.
In the AD I created a OU where I placed My Cluster resources.
In my OU I do delegation of Control
I pick my cluster netbiosname and choose what to do with it. custom rule
and create object is this folder this way I have control over who and what is creating objects in my AD , all I need is that the cluster computer account can create objects in the AD.
And in my cluster I bring the DHCP online and yes is is online and in the AD there is my DHCP object
And it is creating the objects in the cluster OU
Share this:
Robert Smit MVP Blog 
It’s going to be finish of mine day, except before ending I am reading this fantastic post to improve my know-how.
I had the same problem, do you know why this is happening? It’s no standard procedure to grant permissions by hand here, right?
Develop a internet site that develops your company.
office 2013 [freemanmcadam.mywapblog.com]
Great post, helped me get MSDTC and my clustered File Server up after it kept failing to “start role”….Thanks!!
Thank you for being the mentor on this matter. We enjoyed your
article quite definitely and most of all appreciated how you really
handled the aspect I widely known as controversial. You are always very kind to readers much
like me and help me in my lifestyle. Thank you.
This is the perfect website for everyone who wants to understand this topic.
You understand a whole lot its almost hard to argue with you (not that I actually will need to…HaHa).
You definitely put a brand new spin on a topic that has been written about
for decades. Wonderful stuff, just wonderful!
OR… just configure CAU before you start moving your cluster AD objects around 😉
If you just leave your cluster AD objects in the default ‘Computers’ container in the root of the domain, it will work. you can then move the objects to another OU, it will not break anything, the wizard only needed permissions to create the CAU object in AD, which is has in the default computers container…
this has nothing to do with the creating AD object. If you want to move the AD object to an other location just turnoff the deletion checkbox on the AD object.
using CAU to move AD object is …. You missed the point here. SRY.
Reblogged this on matt2005.
whoah this blog is fantastic i really like studying your articles. Keep up the good paintings! You understand, many individuals are looking around for this info, you could aid them greatly. bgdaafekegga
This is really helpful! Thanks so much. Solved my issue.
Very difficult to see the pictures as they have been compacted too much, but apart from that, you are a genius!
Thanks for your comment I will try to use better screenshots.
Thank you for the article. Just wanted to add what to what ec price recommended. We have a script that automatically moves computer accounts out of the default OU container to an assigned OU based on the computers IP Address. Moving the cluster computer account back to the default computers OU resolved the issue for me.
Thanks Rob. We had an issue when having moved computers out of the default OU in AADDS and then attempting to install clustering features on them – the underlying problem was the permissions on the new OU – your blog helped us quickly sort that – thanks for making the effort to write it up – i know what a lot of work that is from personal experience
Thanks Richard, much appreciated
Great post. Official documentation from MS available here
https://docs.microsoft.com/en-us/windows-server/failover-clustering/prestage-cluster-adds
https://docs.microsoft.com/en-us/windows-server/failover-clustering/prestage-cluster-adds#grant-the-cno-permissions-to-the-ou
Red.