Over the past few days I have been attempting to setup Hyper-V replication. I run through the wizard keeping most settings default I get a general access denied error message.
Here is the environment:
2 VM host machines running Server 2012 Data Center (clustered)
1 Server 2012 Standard as a SMB file server for hosting the VHD and VM files.
1 Server 2012 Standard for storing the replication VHDs (clustered, but only one machine in this cluster because replication from 1 Hyper-V cluster must replicated to a replication broker in another cluster.)
I have 6 VMs running and a Replication Broker (co-srv-hvrepb) in the Hyper-V cluster(co-srv-hvtest) and the purpose is to replicate the VHD files to the Replication Broker (co-srv-hvrep) on the replication cluster (co-srv-hvreplication)
When I set up the replication I set the replica server to co-srv-hvrep, the authentication is set to use kerberos through port 80 (firewalls disabled on all machines), I leave the VHD files selected, I only use the last recovery point and set the initial replication to begin over the network and start immediately. When I click finish to start the replication I get an error message that says "Hyper-V failed to enable replication for virtual machine 'co-srv-epo': General access denied error (0x80070005). (Virtual Machine ID 44A94B70-7B4D-49B8-9E42-E645CB180388)"
I have triple checked the permission settings on the hosts and have set all of my different servers and cluster services to full control on all file shares for the VMs. On my replication broker co-srv-hvrep, I have the authentication to use kerberos and have used the setting for allowing any authenticated server and also tried the option for *.domainname.com
When I was setting this all up I had some permission problems that were in the administrative log on co-srv-hvtest, but now I am not seeing anything in this log anymore indicating the cause of why this is failing.
I have even attempted to use procmon as a last resort to find where access is being denied but I have not been able to track it down with procmon either.
This is our last major obstacle before rolling out Hyper-V in our environment.