Hello Everybody,
Iam facing a strange behavior.
I have 2 sites with 2 distinct Failover Clusters in Windows Server 2012R2 Dtc Hyper-V using CSVs stored in a SAN. Each site has its physical domain controler.
Then I've virtualized and clustered a VM running a Windows Server 2012R2 Dtc core and promoted it as DC (on both sites). During a month no problem. But after I did the Windows updates in the VM I get an AD 1722 RPC error in the replication process.
I observed a strange behavior because my first virtualized DC (as clustered VM) is not able to ping the second virtualized DC (as a clustered VM) on the other site and vice and versa but is able to ping the rest of the networks.
To solve it I had to remove the both VMs from their respective failover cluster and I let it turn in the CSV volume and on one of the hypervisor of the failover cluster (on the both sites). After a reboot of the VMs the replication worked fine again.
I've read a lot of articles but I didn't found something recommending to not use DC as a clustered VM. As 2012R2 has a "AD-Less Cluster Bootstrapping" mode and having a physical DC running then normally it should work. Maybe I am wrong.
Please advise.