Moving machines around my network is often challenging, but hey – that’s why we do this right?
I’ve recently rebuilt my cluster, and it’s now entirely focused around SMB3 storage. While I did the rebuild, I moved my machines onto a 2012 R2 Hyper-V server that was a member server within the domain. Once I got my cluster fully working, I used SCVMM to move the machines back into the cluster and onto the SMB3 storage. All worked pretty well at that point. Naturally, I didn’t try to use the SCVMM machine to move itself onto the cluster, as I figured that just was not going to happen!
I shutdown the SCVMM Virtual Machine and instead used the Hyper-V Management Console on the server to move it into the Cluster via one of the cluster nodes. When I attempted to move it into the cluster, I got the error below indicating that it could not create the Prod-SC2012R2 folder or associated subfolders.
When I clicked Close, it then displayed the paths below – which happened to be the current paths of the machine.
I figured the easiest way to diagnose this was to try to open the folders myself from the console of the source server.
When I did, I found I could access them but could not create anything inside them. I had already previously given the computer accounts for my member server full control to the SMB3 share at both an NTFS level and a Share level. What I had missed however was giving my Domain Admins group full control permissions at the Share level. Once I did that, the machine moved quite happily over to the new cluster.
Hope this helps!