Fix: Adding special permissions to the cluster computer object failed

Scenario

You have two or more 2012 R2 up-to-date nodes and want to create new failover cluster. Logged user is Domain Admin.

You install the required features:

Install-WindowsFeature FailoverClustering -IncludeManagementTools

Run validation tests and it’s green:

Test-Cluster -Node node1,node2

Run cluster creating:

New-Cluster -Name TestCluster -Node node1,node2 -StaticAddress 192.168.1.100 -NoStorage

and you receive:

Adding special permissions to the computer object failed. Trying to add ‘Full-Access’ permissions for security principal to computer object CN=,OU=,DC=,DC= failed. Verify that the user running create cluster has permissions to update the computer object in Active Directory Domain Services. The parameter is incorrect.

  • Steps for prestaging required objects don’t work too.
  • Changing user rights or adding new user for cluster creating  –>  no luck
  • No time synchronization issues between nodes and DCs
  • Networks are configured properly
  • Validation tests are all “green”
  • Firewall is disabled

Solution

1. Create new computer object for cluster name (Go to ADUC –> your OU –> new –> computer)

cluster creating error 1

3. Turn on view with advanced features

cluster creating error 3

4. Right click on CNO (computer object for new cluster) and go to Security tab –> select Advanced

cluster creating error 4

5. Click on “Disable Inheritance” (for 2012/2012 R2) or clear “Allow inheritable permissions from parent to propagate to this object and all the child objects” (2008/2008R2) and “Remove all inherited permissions from this object”

cluster creating error 5

6. Right click on the new cluster name and disable it (prestaged computer object from step 1)

cluster creating error 2

7. Go back to the failover cluster wizard and try to create cluster again

HP P2000 G3 MSA Array Systems – Microsoft Windows 2012 Cluster Validation Test Returns Persistent Reservation Errors

Issue

While performing the cluster validation test on Microsoft Windows 2012, the test returns persistent validation warnings like the ones provided below:

msa

Failure. Persistent Reservation not present on Test Disk 0 from node Server.XXXXX.net after successful call to update reservation holder’s registration key 0xb.

Failure. Persistent Reservation not present on Test Disk 1 from node Server.XXXXX.net after successful call to update reservation holder’s registration key 0x10000000b.

Test Disk 0 does not support SCSI-3 Persistent Reservations commands needed to support clustered Storage Pools.
Some storage devices require specific firmware versions or settings to function properly with failover clusters.
Please contact your storage administrator or storage vendor to check the configuration of the storage to allow it to function properly with failover clusters.

Test Disk 1 does not support SCSI-3 Persistent Reservations commands needed to support clustered Storage Pools.
Some storage devices require specific firmware versions or settings to function properly with failover clusters.
Please contact your storage administrator or storage vendor to check the configuration of the storage to allow it to function properly with failover clusters.

Solution

Microsoft Windows 2012 and Microsoft Windows 8 introduce the feature called Storage Spaces (Windows Virtual Disks), the storage spaces feature does not support volumes presented using any kind of RAID controllers including the HP P2000 G3 MSA Array Systems.

As part of the Cluster validation process Microsoft Windows 2012 also runs a Storage Spaces test. As the Storage Spaces feature does not support the P2000 volumes the Cluster Validation test will include the warnings shown on the issue section of this article, however; the warnings do not cause the Cluster Validation test, as the warnings are only related to the Storage Spaces feature.

This is the normal behavior and it is not related to any issues on the HP P2000 G3 MSA Array Systems, it is just a warning to remind that the Storage Spaces feature does not support RAID based storage devices, and can be safely ignored.

Source