I have run into an odd problem with using pre-staged Virtual Computer Objects with Cluster Aware Updating.
If I either allow the Configure Self-Updating Options Wizard create the object or pre-create a brand new, unique Virtual Computer Object, the wizard will complete successfully.
If I try to use a specific name which conforms with our existing naming standard, it fails with "Unable to create the CAU clustered role because a Network Name resource could not be created."
I know it's not a rights issue because the wizard will create a new Virtual Computer Object if I don't choose the "I have a prestaged computer object for the CAU clustered role" option. Also, if I create another Virtual Computer Object with a different name, it works even without granting Full Control privileges to the new Virtual Computer Object.
Steps I have tried that have failed:
- I have deleted and recreated the pre-staged computer object and granted Full Control permissions to the Cluster Name Object. Object is in the same Organization Unit as the Cluster Name Object.
- Pre-staged Virtual Computer Object in both a disabled and enabled state.
- Complete the Configure Self-Updating Options Wizard without a pre-stated computer object. Then remove the self-updating feature from the cluster. I have noticed that the Virtual Computer Object is removed as part of this process, but the DNS entries remain. I delete them manually.
Any insights into what is checked and validated as part of using the pre-staged computer object option would be most appreciated.