At this point, the SQL team (or even before this point) punts it back to the server team.
The server team scratches their head, mumbles something about this working in Windows Server 2008 R2, and typically opens a case with Microsoft.
There is an issue I have seen repeatedly in the field since Windows Server 2012 and Windows Server 2012 R2 released.
It typically surfaces when attempting to add roles to Windows Failover Cluster.
There should be a VCO by the name of SQL1MSDTC, but no such object exists in AD.VMM is installed and the two boxes are clustered together and volumes on the Dell equallogic box are seen from the two dell boxes I can validate the cluster successfully but with the following warnings.Below are the warnings that are produced as a result of running the validation.The easiest method to solve this is to create a security group that has the Create Computer Objects permission at the OU level.When building a new Cluster, add the Cluster name (CNO) to the group.At this point in the Create Cluster Wizard, I can actually specify an OU if I wanted to, but I’m just going to do what I see in the field and specify the Cluster name.