The clustered role {0} has a value other than NULL for the property "AntiAffinityClassNames." The value of this property is {1}. In the event of a failover, the failover manager will attempt to fail the clustered role to a node that is not hosting another clustered role with the same value in AntiAffinityClassNames. This value can take higher priority over the Preferred Owners List for the clustered role. As an example, if it is preferable that a clustered file server fail over to a node that is not hosting another clustered file server, you can give the clustered file server the same value for AntiAffinityClassNames. When one of the clustered file servers fails, the failover manager will try to fail it over to a node that is not already hosting a file server.
The Cluster-Aware Updating clustered role has been moved or failed over {0} times during the Updating Run, which indicates ...
The clustered disks could not be enumerated or could not be put into cluster maintenance mode. Check the System event log ...
The clustered RD Connection Broker server for the cluster {0} is not a part of the server pool. Add the server {1} to the ...
The clustered role will not be started because the resources may need additional configuration. Finish configuration, and ...
The clustered role {0} has a value other than NULL for the property "AntiAffinityClassNames." The value of this property ...
The clustered virtual machine '{0}' is no longer available on computer '{1}'. The virtual machine may have been moved, taken ...
The cmdlet "{0}" or the alias "{1}" cannot be present when "{2}","{3}","{4}" or "{5}" keys are specified in the session configuration ...
The cmdlet cannot be run because the required migration manifests are missing. Verify that the dlmanifests folder exist at ...
The cmdlet cannot be run because the required migration manifests are missing. Verify that the replacementmanifests folder ...