So to get started I'll give a bit of background on the Infrastructure we are currently working with.
We have:
2 x Hyper-V Hosts (Currently 2 for testing migrations, this will increase once we have a working platform)
2 x File Servers acting as storage nodes for VHD Storage
1 x Physical DC
The Hyper-V Hosts both have Server 2012 R2 Datacentre installed, the rest have Server 2012 R2 Standard installed and configured.
We currently have some VM's sitting on one host and I am in the process of simulations to make sure live migration is working between the two HV Hosts (This is a non-clustered setup), Everything is on the domain and i've been using a domain admin account to administer these servers for these simulations.
We plan on having VHD's stored on FS01 and FS02, basically our primary host is going to have all primary servers on and then those vhd's will be stored on FS01 and then all secondary/redundant servers are going to be on the second host and vhd's stored on FS02 - Simple enough?
I can perform Data migrations between both FS01 and FS02 using the Hyper-V Management tool on both hosts without any issues. The issue I am currently encountering is when I perform a migration of the "Virtual Machine Only". Now, this simulation works when the data for the VM is stored on either of the hosts using UNC pathway, no hiccups at all, I receive the below error when ever the data is stored on either FS01 or FS02 using again, UNC pathway (These VM's power on and work perfectly otherwise while hosted on FS01/02).
Error:
I've researched this quite a lot and have gone through countless solutions other people are having.
http://social.technet.microsoft.com/Forums/windowsserver/en-US/5780d041-4036-404e-9f33-8abe025bfe2b/hyperv-failed-to-create-external-configuration-store-general-access-denied-error-ox80070005?forum=winserverhyperv (Which
took me to the below link)
http://support2.microsoft.com/kb/2249906 (This solution didn't work, in fact i couldn't even get CMD to run the command)
Now, with THIS SOLUTION that I attempted I worked with adding all the hosts and FS01 (because nothing is on FS02 at the moment) in an attempt to get the VM Migration only working between hosts and still receive the same error.
As a testing option, I Moved the Data for the VM back to one of the hosts using UNC pathway and then performed a live migration to the other host no problems, then performed a data migration back to FS01 and that also worked. I don't particularly want to do this with production VM's as I have at least 6 x 780GB vhd's that need to be moved and this would move them more than once, obviously not ideal.
If someone is able to help me out, or at least point me in the right direction, that would be awesome!