Get-VHD failing with access denied when querying remote VHDs on SMB 3.0 shares

Question

I'm out of ideas on this one. I'm attempting to do a Get-VHD to retrieve VHD info for some Guests that are using SMB 3.0 shares to remotely store their VHDs and I cannot remotely run the powershell command at all without getting  Error: 'General Access
denied error' (0x80070005)'. Command running locally on the machine hosting the guest works fine.
Here is the Hyper-V Setup - Host is Server 2012 datacenter, guests are 2012 or 2008 R2 boxes. Storage server is Server 2012, domain is 2008 R2 functionality level if it matters, powershell version 3.0
Host1 --> Guest(1) --> {LAN}--> StorageServer --> Share --> VHD
Make sense? pretty easy, normal setup. The Host has full access NTFS rights on the share and all files, including the VHDs. As does my AD account. All on the same domain. If I RDP into Host1 I can retrieve everything just fine. However, the following methods
will not work to retrieve VHD info of any Guest running on their VHDs off the share (get-vhd works if Guests have their VHDs on locally attached storage).
1.) Enter-PsSession Host1 and then attempt get-vhd
2.) Invoke-Command
3.) import module/hyper-v management tools on client then running get-vhd
4.) Executing GetVirtualHardDiskInfo method in WMI (http://msdn.microsoft.com/en-us/library/cc136797%28VS.85%29.aspx) to retrieve the job which results in same error message.
5.) Even attempting test-path $pathToVHD on the host will result in Access Denied error.
If I check the storage server hosting the VHDs I see some normal access requests come across on my Domain account followed a few seconds later by a null sid/anonymous requests which of course are denied. I have no idea why on earth they are coming across
as null SIDs/anonymous requests but this seems to be the root of the issue. Is it trying to regenerate my credentials or something to access the VHD and failing? If so, is there a way to fix it?

Answer 1

Yeah I thought about that too and that isn't the problem in this particular case (also PSSession takes care of the RSAT/HyperV problem). If it was Scenario #1 wouldn't work and scenario #4 would.
Again, this works fine:
Scenario #1 (works)
1.) Remote computer running PS 3.0 (win 7 desktop in this case) enter-pssession Host1
2.)  Get-VHD $VHDOnLocalDirectAttachedStorage (Host1 is running guest)
Scenario #2 (works)
1.) RDP to Host1
2.) Get-VHD $VHDOnSMBShare (host1 is running guest)
Scenario #3 (breaks)
1.) On remote computer enter-pssession Host1
2.) Get-VHD $VHDOnSMBShare (host1 is running guest)
Scenario #4 (breaks):
1.) RDP to Host2 server 2012 running Hyper-v with RSAT installed
2.) Get-VHD $VHDOnSMBShare -ComputerName RemoteHost
Scenario #5 (works):
1.) Enter-Psession Host2
2.) Get-VHD $VHDOnHost1LocalStorage -ComputerName Host1