Let me start by saying, I've followed just about every guide I can find on delegation and permissions and virtually everything works just fine except for this...

I created a VM using Server 2012 R2 Hyper-V. That server was created on, stored on and exported to a Server 2012 R2 File Server, all using my workstation (Windows 8.1) to remotely manage the Hyper-V server. That should be proof that delegation works perfectly fine (being able to create a VM and export it on the SMB share remotely, right?)

My user account, workstation computer account, and the Hyper-V server account all have full rights to the SMB share (NTFS and Share Permissions). To clarify further, my user account is a domain admin.

However, when I go to import the exact same machine that I JUST exported successfully I get the error: Hyper-V did not find virtual machines to import from location '\\FS01\Hyper-V\Exports\Server2012R2\' - The folder '\\FS01\Hyper-V\Exports\Server2012R2\' could not be found. You might not have permission to access it.

Here are some outputs to show that I've, hopefully, configured everything correctly:

PS C:\Windows\system32> Get-SmbDelegation FS01
WS
HV02
PS C:\Windows\system32> Get-SmbDelegation HV02
WS

WS:
Get-WSManCredSSP
The machine is configured to allow delegating fresh credentials to the following target(s): wsman/*.domain.local

HV02:
Invoke-Command -ComputerName HV02 -ScriptBlock {Get-WSManCredSSP}
The machine is configured to allow delegating fresh credentials to the following target(s): wsman/FS01.domain.local

This computer is configured to receive credentials from a remote client computer.

FS01:
Invoke-Command -ComputerName FS01 -ScriptBlock {Get-WSManCredSSP}
The machine is not configured to allow delegating fresh credentials.
This computer is configured to receive credentials from a remote client computer.

I should also not that it works fine if I remote desktop to the HV02 server and do the import.

• Edited by MysticRyuujin Thursday, May 01, 2014 10:52 AM

Bump

Hi ,

Maybe the following article is helpful

http://blogs.technet.com/b/heyscriptingguy/archive/2012/11/14/enable-powershell-quot-second-hop-quot-functionality-with-credssp.aspx

Best Regards

Elton Ji

i had the same problem copy the vm mine folder with all the files and do the import vm on the folder you copyed and it will imporet her fine with the wizard 

• Edited by Guy Rubinger Sunday, May 04, 2014 2:59 PM

Nope, it was not helpful. As you can see from my Get-WSManCredSSP output I've already configured CredSSP for all three devices. If I didn't I shouldn't be able to export to begin with, correct?

The one part in the article that I did see was:
When making the PS Session, ensure that I use the FQDN of the remote server. (This is true because I specified the delegate computer as *.mydomain.net. If I had specified the delegate computer as Sql1.mydomain.net, I would not need the FQDN.)

However, specifically adding HV02.domain.local and FS01.domain.local didn't change the outcome. Nor did specifying \\FS01.domain.local instead of \\FS01

Also, I don't know of any way to use the PowerShell argument "-Authentication CredSSP" with the Hyper-V Manager...

Finally, I tried to copy the exported VM folder to a totally different folder and that, of course, didn't magically work.

• Edited by MysticRyuujin Monday, May 05, 2014 1:14 AM

Hi MysticRyuujin,

Sorry for the delay .

One more thing I want to check is wether the export and import path is same .

Such as you exported the VM to path : \\FS01\Hyper-V\Exports\Server2012R2   then you used the same path to import the VM   .

Afer you export the VM to the folder , there will be a new subfolder named for the VM's name .

If the VM's name is  " test " , then your import path is  : \\FS01\Hyper-V\Exports\Server2012R2\test

Best Regards

Elton Ji

Elton,

Yes, I can export to both the \\FS01\Hyper-V\Exports and the FQDN \\FS01.domain.local\Hyper-V\Exports\

I am aware that another folder gets created under the export path that is the name of the VM however, it doesn't make any difference what path I put into the Import path, it still fails with the same error. I have tried every combination of Short Name/FQDN for both Export and Import.

Again this all works perfectly fine if I remote desktop to the Hyper-V Server and do the import from the Hyper-V Manager there. It only doesn't work if I use the Hyper-V Manager from my workstation (using the exact same steps).

• Edited by MysticRyuujin Thursday, May 08, 2014 6:18 AM

Hi MysticRyuujin,

I tested that issue and  I'm trying to involve someone familiar with this topic to further look at it.

Thanks for your understanding.

Best Regards

El

Elton Ji,

So you're seeing the same issue that I am? It's not just me? I appreciate your help very much and I will patiently await a reply...

Thank You!

Does anyone else have any ideas? <- Bump

I have the exact same problem and I am stuck not being able to figure this out. What's worse, the Hyper-V host is a server core install and I can't just run Hyper-V Manager there for the time being as a work around. I really need to figure this problem out.