Cluster network name resource failed to create its associated computer object in domain...
A customer of mine was deploying Hyper-V Replica in their datacenter today, and everything seemed OK during creation.
However, after checking the roles afterwards, the Hyper-V Replica Broker was having some errors.
A closer look at the critical events for this source showed that the cluster account was not able to create child objects in the correct container in Active Directory.
The text for the associated error code is: A constrained violation occurred.
When you enable the Hyper-V Replica Broker Role within a Failover Cluster, you must specify a name for the role as well as an IP address. This is because the Hyper-V Replica Broker is a HA role, where the secondary replica servers will target this object during replication. It is just like any other active/passive cluster role.
The Cluster Name Object (hyper-v_cluster_name$) is responsible for the creation of objects, and if this object does not have the required permissions to create child objects in the same container where it lives, you will get this error.
Talk with your domain administrator to sort this out.Normally the domain administrator will delegate control through Active Directory so that your CNO can create child objects.
After we fixed this, everything was in order and the Hyper-V Replica Broker role was Running, healthy and smiling.