P2V migration to Hyper-V failing

[Technician334]

I did not find any helpful fixes while searching these forums for this problem.

I have a Windows Server 2011 (On the domain) that I'm performing a migration on - Physical to Virtual

The data is supposed to be going into a format Hyper-V can use on a new Windows Server 2019 which is being used as a VMHOST (Not on a domain)

I'm receiving the error (0x80070005) Access is Denied when on the screen that asks to enter Microsoft Hyper-V Server connection parameters (hostname, username, password)
I've confirmed I'm using the correct user name and password. It's a local admin on the VMHOST machine
input looks like this
hostname: vmhost-computer-name-here
user:vmhost-name\local-admin-name
password: correct password

I checked event viewer on the VMHOST and can confirm that the Server 2011 is successfully authenticating to it using those credentials when Starwind attempts to make the connection, however I can also see that the connection is immediately destroyed after the successful logon. I'm unsure if this is normal or not

I have turned both firewalls off, ran the program as Admin, made sure I can RDP between devices (using same credentials), made sure I can move a file from one server to the other server manually

At this point I think it is a permissions issue, but I'm open to try other fixes. Are there specific permissions the local admin on the VMHost needs to be given for this to work? Does the Server 2011 need some special permission to access the VMHOST?

[yaroslav (staff)]

Windows Server 2011

Do you mean Windows Server 2012? Is it R2?
Try performing a Hyper-V migration to Windows Server 2019. Also try P2V conversion of a disk.

[Technician334]

Windows Server 2011

Do you mean Windows Server 2012? Is it R2?
Try performing a Hyper-V migration to Windows Server 2019. Also try P2V conversion of a disk.

It's an SBS 2011 (Small Business Server) so the OS is Small Business Server 2011 Standard

[yaroslav (staff)]

Thanks for your update!
I am not sure if SBS is suitable for P2V. Did you try the Hyper-V VM move between 2019 and SBS 2011?

[Technician334]

Thanks for your update!
I am not sure if SBS is suitable for P2V. Did you try the Hyper-V VM move between 2019 and SBS 2011?

We have decided to go with a backup plan of using Starwind to do P2V to a file on the local machine and then move that over the network to the new VMHOST. It should work for what we need since all we really need is to convert the physical machine to a virtual image that Hyper-V can use to run it as a VM

[yaroslav (staff)]

Hi,

I am not sure if SBS is tested with StarWind V2V Converter. Could you please convert the disk into VMDK. Could you please tell me how big is the disk?

[ebayironman]

If you create a share with permissions for everyone on the destination server, then map as a local drive letter on Physical server you are trying to P2V, it will work.
There is some kind of permissions issue with using older versions of Windows to try to remotely manage Hyper-V or VMWare on newer OS server.
I spent a bit of time trying to resolve the issues and gave up. As doing the whole physical disk to one .vhdx wrote to a mapped network drive works.

[yaroslav (staff)]

Thanks for your update.