Access Denied trying to convert P2V on Hyper-V

[veriatech]

Hello,

I am trying to convert a physical machine to a virtual Hyper-V machine and am running into Access is denied upon authentication. Can someone please help? I've already tried opening firewall ports (WMI - port 135, etc.) to no avail. Below is a copy of my logfile. TIA!

The log file name: 'logs\V2V_Log-20221215-081451.log' (PID 156232)
12/15 8:14:51.017 16f34 Facility ???INFO: CV2V_ConverterApp::InitInstance: SetDllDirectory: C:\Program Files\StarWind Software\StarWind V2V Converter\lib
12/15 8:14:51.017 16f34 Facility ???INFO: CV2V_ConverterApp::InitInstance: File Version: 9.0.1.268
12/15 8:14:51.026 16f34 Facility ???INFO: CV2V_ConverterApp::InitInstance: Load language IDR_XML_ENGLISH
12/15 8:14:51.026 16f34 Facility ???INFO: CV2V_ConverterApp::InitInstance: Set current language English
12/15 8:14:51.029 16f34 Facility ???INFO: CPS_V2V_Converter::CPS_V2V_Converter: Version MajorVersion 6, MinorVersion 3, BuildNumber 9600
12/15 8:14:51.032 16f34 Facility ???INFO: WrapperHyperV::WrapperHyperV: LoadLibrary C:\Windows\system32\wbem\wmiutils.dll - e2650000
12/15 8:14:51.033 16f34 Facility ???INFO: WrapperHyperV::WrapperHyperV: LoadLibrary C:\Windows\system32\wbem\wmiutils.dll - e2650000
12/15 8:14:56.296 16f34 Facility ???INFO: ICPPage::OnWizardNext: SetActivePage - eTypeP2V
12/15 8:14:59.058 16f34 Facility ???INFO: ICPPage::OnWizardNext: SetActivePage - eVolumeSelectVM
12/15 8:15:02.226 16f34 Facility ???INFO: ICPPage::OnWizardNext: SetActivePage - eLocationTo
12/15 8:15:06.020 16f34 Facility ???INFO: ICPPage::OnWizardNext: SetActivePage - eHYPERVConnectionTo
12/15 8:15:24.421 16f34 Facility ???INFO: WrapperHyperV::connect: Host - \\192.168.2.10\root\virtualization\v2
12/15 8:15:24.448 16f34 Facility ???ERROR: WrapperHyperV::connect: pLoc->ConnectServer \\192.168.2.10\root\virtualization\v2 - 0x80070005
12/15 8:15:24.448 16f34 Facility ???ERROR: WrapperHyperV::failResultToStr: Last Error - Access is denied.
(0x80070005)
12/15 8:15:24.448 16f34 Facility ???ERROR: VMConverter::HyperVConverter::Connection: connect fail - 0x80070005
12/15 8:15:25.944 16f34 Facility ???WARNING: CPPHYPERVConnectionTo::onNext: connect Access is denied.
(0x80070005)

[yaroslav (staff)]

Can you please try disabling the firewall?
Please see this post on firewall ports https://forums.starwindsoftware.com/vie ... v2v#p32208. I just want to be sure all the necessary firewall ports are open.

[veriatech]

Thank you for your reply! I have tried several things already, including disabling firewall, adding the required ports to be open on TCP & UDP (135, 443, 445) all to no available.

Furthermore, my configuration consists of Windows Server 2012 R2 (physical machine) and Windows Server 2022 (hyper-v host). I am trying to migrate the Windows Server 2012 R2 to the hyper-v host as a VM. Also of note, there is no domain in my network. We only operate in a WORKGROUP configuration.

EDIT: I am going to guess the reason is that I chose Windows Server 2022 as my host OS for my new Hyper-V server. There are likely new configuration parameters which Win Srv 2022 requires that no one knows about yet, or at least I cannot find them. Perhaps I need to scale back to using Win Srv 2019 so that I can get this project done ASAP.

Thanks so much for any help at all!

[veriatech]

It appears to me that a Domain / Active Directory network is a requirement in order to be able to perform P2V ops. Correct me if I am wrong. Currently, our configuration only consists of standalone servers. I am running into brick walls as a result. Please let me know if my analysis is correct. Thank you!

[yaroslav (staff)]

No, you do not need the domain account. Can you try P2V converting Windows Server 2016 or 2019 VM for testing?
The Access denied error means that some constrained communications between the source and the destination.

[veriatech]

What sort of possible "constrained communications" do you think it could be? Are you saying I should upgrade my Windows Server 2012 R2 to 2016 before performing the migration? Is it possible to convert a Windows Server 2012 R2 physical machine to a virtual machine hosted on a Windows Server 2019 hyper-v server?

[yaroslav (staff)]

There could be something on the network level.
Can you try doing VM migration from your target server to a destination one?
Try converting it to a VM on Windows Server 2016. Then, do VM migration to 2022.

This issue is likely to be related to infrastructure, not P2V Conversion.

[veriatech]

That is a good suggestion. I currently have the new server connected to a higher end HP 2920 managed gigabit ethernet switch. Perhaps there is something on the HP 2920 that is blocking the P2V connection to Hyper-V. It is also worth noting that I am also unable to connect to the new Hyper-V server from the Hyper-V Management Console on the Windows Server 2012 (the one I am trying to convert). I will work on modifying the network infrastructure (HP 2920 switch) or just eliminate it as a possibility all together and keep us posted here. Thanks so much for your help!

[veriatech]

So much for that theory. It is NOT a network infrastructure issue. I completely removed the HP 2920 managed switch from the equation and instead, implemented a plain basic unmanaged gigabit switch and am still getting an Access Denied error message when trying to connect to the remote Hyper-V server. And just to re-iterate, the server I am trying to migrate (convert) is a Windows Server 2012 RS and the server I am trying to migrate to is a Windows Server 2019 system (with Hyper-V installed). Does anyone have any other ideas?

[yaroslav (staff)]

Greetings,

Thank you for your update. Can you try migrating the VM from the Windows Server 2012R2 host to Windows Server 2019 one?

[veriatech]

I have an update: I was able to upgrade my PHYSICAL Windows Server 2012 R2 to Windows Server 2016. Then, I tried again. I am STILL getting the Access Denied error message. At this point, the firewall is completely turned off on my Windows Sever 2019 (Hyper-V) server. I was, however, now able to remotely connect to my Hyper-V manager (on the 2019 server) from the 2016 server. I had to enter a different username and password since my 2019 Hyper-V is connected to a domain. Do you have any other ideas for me to try?

[veriatech]

Question: What Hyper-V services are required to be running on the target Hyper-V server in order for Starwind to be able to communicate?

[yaroslav (staff)]

It should be running.
Also, did you try performing Hyper-V VM move?