P to V conversions of Window server

 Yes, we are still doing the occasional P to V conversion from hardware Windows Server to Hyper-V VM!

You can still use Mark Russinovich's PtoV converter to do this, Sysinternals Disk2VHD.

After you have done the P-toV the hardware, create a new VM in Hyper-V using Generation 1 machines.

When booting, you need to create a BCD / Boot partition. Boot into recovery mode using the same Windows Server ISO, and boot to the CD/DVD. Select Recover and Command Prompt.

Then type:

bootrec /fixmbr

bootrec /fixboot

bootrec /rebuildbcd

After that, you can boot again to the C drive.


Comments

Post a Comment

Popular posts from this blog

"The SNMP Service is ignoring the manager because its name could not be resolved." in Windows Server Event log.

 Interesting SNMP service problem on Windows. Since installing KB5051979 on Windows Server 2022 Standard, we can no longer use the SNMP service. The server no longer responds to SNMP requests from the management server <Server name>. Message in Event log on the problem server:- "The SNMP Service is ignoring the manager <Server name> because its name could not be resolved." The manager <Server name> CAN be pinged and resolved with DNS, also reverse lookup works. ............. Turns out, the GPO applying the policy for the names in the SNMP service had a fault. Re-created the GPO with the names again, and it worked.
Read more

Server Manager will not start, error .NET Framework: "This application requires one of the following versions of the .NET Framework:"

Server Manager will not start on Windows Server 2019 after installing ADConnect. Error ServerManager.exe: This application could not be started. .NET Framework: "This application requires one of the following versions of the .NET Framework:xxxxx Do you want to install .NET framework now?" Of course it's already installed automatically on the server, so if you try and install it again you can't, error "already installed". Try the .NET repair package, can't repair the install. Try dsim.exe to install the package, error "Microsoft .NET Framework is already part of this installation". .NET Runtime version : 4.0.30319.0 - This application could not be started.This application requires one of the following versions of the .NET Framework:  v4.0.30319 The answer is to re-create the registry entries deleted when you installed ADConnect:- [HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\.NETFramework\v4.0.30319] "AspNetEnforceViewStateMac"=dw...
Read more