##Weird one here… Hyper-V Replica issue:
Hyper-V could not replicate changes for virtual machine ‘MikroRMM’:
The server name or address could not be resolved (0x00002EE7).
(Virtual Machine ID 722E9124-A917-4AD4-AC0D-0AEAA0C95686)
… did some poking around, got here for a workaround:
http://blogs.technet.com/b/virtualization/archive/2013/04/08/hyper-v-replica-name-resolution-of-internationalized-server-domain-names.aspx
But while waiting for GPEdit to launch ( Separate Issue 🙂 ) I just threw records in each (primary/replica)’s host file for the appropriate opposite server.
#####Example Host File Entry:
C:\Users\cstgeorge>type c:\Windows\System32\drivers\etc\hosts
….
192.168.254.60 mikrovserver2 mikrovserver2.mikrodots.org
Once hard coded in the Hosts file, replication resumed without issue.
Obvi, there is a deeper issue to be addressed, but this will get you going in a pinch!
