Hyper V Core 2019 Export not working to Network Share

Question

Hi,

I am trying to export a VM from Hyper V Core 2019 to a Network Share.

I have followed this:- https://learn.microsoft.com/en-us/troubleshoot/windows-server/virtualization/error-0x80070005-export-vms

But I still get the general access denied error

Answer 1

I was able to solve the issue by using icals command to provide each sid access to shares

Answer 2

Hi Simranjeet Singh Grewal,

Here are a few troubleshooting steps you can try:

1. Ensure that the account you're using to perform the export has the necessary permissions to access the network share. You may need to grant the account explicit permissions to the share and/or the underlying file system.
2. Check that the network share is accessible from the Hyper-V host. You can test this by attempting to access the share from the command line using the "net use" command.
3. Verify that the network share is not currently in use by another process. If another process has a lock on the share, it may prevent the export from completing successfully.
4. Try exporting the VM to a local drive on the Hyper-V host to see if the issue is specific to exporting to a network share.

I hope these steps help you resolve the issue.

Answer 3

Hi,

Exporting a VM from Hyper-V Core 2019 to a network share can sometimes result in an "Access Denied" error (0x80070005), even after following the recommended troubleshooting steps. This problem is often related to permissions or network settings. Let's go through a structured approach to troubleshoot and hopefully resolve the issue.

Verify Network Share and NTFS Permissions

Ensure that the account used by Hyper-V to perform the export has the necessary permissions. This account is typically the one under which the Hyper-V service runs, often SYSTEM or a specific user account if configured differently.

• Share Permissions: On the network share, ensure that the Everyone group or the specific account Hyper-V runs under has Change and Read permissions at a minimum.
• NTFS Permissions: On the folder where the network share is located, the Hyper-V service account needs Modify permissions, which include read, write, execute, and delete capabilities.

Use a Hyper-V Administrator Account

If you're running the export command under your user account, ensure that your account is part of the Hyper-V Administrators group on the Hyper-V server. This provides sufficient privileges to perform exports.

Disable UAC (User Account Control) Remote Restrictions

Windows Server might block access to network shares from services running as SYSTEM. To check if this is the issue, you can temporarily disable these restrictions:

1. Open Registry Editor on the Hyper-V host.
2. Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System.
3. Create a new DWORD value named LocalAccountTokenFilterPolicy and set its value to 1.
4. Restart the server and try the export again.

Warning: This action decreases the security of the server by allowing full administrator tokens during remote connections. Use it as a temporary measure to diagnose the issue.

Explicitly Specify Credentials

Try specifying credentials explicitly when accessing the network share, to ensure that the correct permissions are used. You can do this by using the net use command before exporting the VM:

shell

net use \\NetworkShare\Path /user:domain\username password

Replace \\NetworkShare\Path with your network share path, and domain\username and password with the credentials that have access to the share.

Check Antivirus and Firewall Settings

Ensure that any antivirus or firewall running on the Hyper-V host or the network share server isn't blocking the export process. Temporarily disable these (if your policy allows) to rule out interference.

Verify Network Connectivity and Path

Ensure that the Hyper-V host has proper network connectivity to the share and that the share path is correctly specified. Typos or network issues can lead to access denied errors.

Log and Event Viewer

Check the Event Viewer on both the Hyper-V host and the server hosting the network share for any additional information that might point to the cause of the failure. Specifically, look under Windows Logs > System or Applications for related error entries.

Consider Using PowerShell

If you're not already, consider using PowerShell for the export operation. It might give you more control and better error output. Here's a basic command to export a VM:

powershell

Export-VM -Name "VMName" -Path "\\NetworkShare\Path"

If after following these steps you still encounter issues, it might be helpful to revisit the network share setup or consult with your network administrator to ensure there are no underlying network policies or configurations that might be causing the problem.