I need guidance on fixing "General access denied error (0x80070005)" when moving a VM between Hyper-V hosts, and also creating a new virtual hard disk, from an administrative workstation.
Scenario:
Hyper-V host servers "Host1" and "Host2" and Storage server "Nas1" are all connected by both a 1G and a separate 10G network.
All 3 servers are Windows Server 2012 R2 with a 1G and a 10G NIC, the administrative workstation "Wks1" is Windows 8.1 Enterprise (actually, a VM), all are joined to domain "acme.local".
What is the best method to make Host1 and Host2 use the 10G network to connect to the share on Nas1?
On the domain controller, I added static DNS records mirroring the 1G network, adding a "z" to the host name, using a different subnet designation. Example: all "1G" hosts use addresses in 192.168.1.0 range, all "10G"
network hosts use addresses in the 10.1.1.0 range. So where Host1 is 192.168.1.18, then zHost1 is 10.1.1.18, an so on.
All the host machines using shared storage are configured to use the common share: \\zNas1\vm
(I know upper-case is ignored in host names, I use upper-case letters here for readability)
From Wks1, when I try to create a new .VHD disk-file, I get the error:
The server encountered an error tyring to create the virtual had disk.
The system failed to create '\\zNas1\vm\disks\test1.vhd':
General access denied error (0x80070005).
I get a similar message when trying to move a VM:
Failed to get the disk information.
Account does not have permission to open attachment.
Failed to get the disk information.
'': account does not have permission required to open attachment '\\zNas1\vm\disks\wks2.vhd'
Error: 'General access denied error' (0x80070005). (Virtual machine ID)
Oddly, I can click "Close" on the pop-up, then "Next" throught the wizard choosing the otions to move the machine but NOT the storage, and the VM will move just fine, as long as I use the options "Move the virtual machine's data
by selecting where to move the items" and "Move the virtual machine's items to different locations" then de-selecting the .VHD file(s).
From Wks1, I can create a new .VHD disk-file using the 1G network, example: '\\Nas1\vm\disks\test1.vhd'
These same problems occur when using Hyper-V management tool on the servers, if I try to "pull" a VM from the other server, I can only "push" a vm to get it to move without any problems.
I have tried wide-open permissions on the "\\Nas1\vm" share and directory structure, example: EVERYONE,RWX.
I tried adding Wks1 to the "delegation" tab in AD.
Where can I find what the CORRECT permissions should be on the Nas1 share, directories, and the .VHD file (including, what should the "owner" be)?
Or am I going about it wrong in trying to tell Hyper-V to access the .VHD disk-files on the shared storage using the 10G network?
Thanks in advance for you help!!
---Jay R O
