While trying to install VMM as a Highly Available following the steps in this article, I kept running into the same issue over and over and over again. The installation would start, run for a few minutes, and then fail and rollback with this error at the end: “Creation of the VMM resource group VMM failed.Ensure that the group name is valid, and cluster resource or group with the same name does not exist, and the group name is not used in the network.”
I first thought it was because I had pre-configured the DNS entry, but even after removing the DNS entry and verifying that neither cluster node could resolve it anymore the installation still failed. Next I rebooted both nodes of the cluster. The installation still failed. My next thought is maybe I can’t use VMM as the HA VMM name so I used XXXVMM and sure enough it worked. Now, whether or not that is because I had the VMM DNS entry created previously and it screwed something up, or because you really can’t use the VMM name, I don’t know.
At this point it said setup completed successfully, but with warnings.
Starting the clustered VMM service XXXVMM failed.Ensure that the user has permission, the VMM service is installed properly, and cluster resources can be brought online.A service connection point (SCP) could not be registered in Active Directory Domain Services (AD DS) for the VMM management server.Run “D:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\setup\ConfigureSCPTool.exe -install XXXVMM.com XXX\XXXVMM$” in a command window and then check AD DS. If an SCP is not registered, VMM consoles on other computers will not be able to connect to this VMM management server and deploying a Hyper-V host to a bare-metal computer will not work.
I ran the setup as a domain administrator, and am logged into the cluster node as this same domain administrator.
Looking at the Cluster event logs, this is the error I get when I try to manually bring the service online:
Failed to bring the resource VMM Service XXXVMM online. Error code 0x80071736 The Resource failed to come online due to the failure of one or more resource providers.
Looking at Services, the System Center Virtual Machine Manager Agent service is running, but the System Center Virtual Machine Manager service is not running, and if I try to start it, it fails with the error.
In the Event Log, I find this error entry which seems pretty useful.
Cluster network name resource ‘XXXVMM’ failed to create its associated computer object in domain ‘domain.com’ 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 ‘VMM-HV-CLUS01$’ has Create Computer Objects permissions. By default all computer objects are created in the same container as the cluster identity ‘VMM-HV-CLUS01$’.
– The quota for computer objects has not been reached.
– If there is an existing computer object, verify the Cluster Identity ‘VMM-HV-CLUS01$’ has ‘Full Control’ permission to that computer object using the Active Directory Users and Computers tool.
While looking in AD for this object, I also stumbled across a VMM computer object (who the hell knows where that come from) so I deleted that object as well. I am nearly 100% certain that is what caused my installation using VMM as my VMM Cluster Name to fail.
At the very bottom of this article it outlines how to troubleshoot issues with Cluster AD Accounts. The instructions are only slightly different for Server 2012, and it tells you how to grant only the permissions that you need.
With that done, I removed the VMM installation and tried it again, with the original VMM Cluster name (just VMM) and it worked fine, with no errors!