Cannot unlock Windows Server 2003 after P2V


1. You use disk2vhd to perform P2V conversion of Windows Server 2003


2. Disk2VHD created an VHD successfully

3. You attach this VHD to newly created virtual machine (Generation 1, host 2012 in my case) and start VM

4. Unfortunately, you notice that mouse and keyboard are not captured and ctrl+alt+delete doesn’t unlock guest OS. This is because of there are no integration services inside guest OS. RDP+console access are not working too. Network adapter is not available = no RDP to guest OS.



1. Download and install VMware vCenter Converter Standalone

2. Convert source machine to vmdk


3. Convert vmdk to vhd using 2Tware

2tware converter

4. Attach VHD to VM and start VM.

Now Ctrl+alt+delete works + keyboard is captured. Insert ISO with integration services, install, restart VM and now mouse is available too.

12 thoughts on “Cannot unlock Windows Server 2003 after P2V”

  1. Thanks for this solution. However now I am stuck at installing integration services. It just does not finish the Installing Windows Driver Framework phase. Maybe you have a solution for that ?

      1. So just to let you know I’ve managed to successfully virtualize this last server. I will provide the steps I have taken as my contribution. Perhaps it will be helpful for someone.

        Firstly, after several attempts, I have managed to unlock OS without using VMware Standalone converter. I ran sfc /scannow on the physical server with the original Windows media inserted. In addition I ran disk2vhd from the console not from the rdp session. It worked, but I do not know which one of these two steps helped.

        Secondly, I was still struggling with the installation of IS. So I went to safe mode and ran msconfig. Disabled all the startup programs and all non Microsoft services. After reboot installation of the Integration Services was successful. I assume the problem was with LANdesk services.


    1. Glad to hear that you have successfully figured it out.

      I’ve heard about impacts of some non-microsoft services but I’ve never faced with trouble like you had. Troubleshooting steps were right . I could add 1 more extra step: deep diving into logs to finally spot a cause of issue

      Thanks for your comment. It can be very helpful for someone
      Have a great day and virtualization!).

  2. Hi Roman, I did all the steps but when I start the VM, I get a blue Windows screen of death.
    The conversion from VHD to VMDK and from VMDK to VHD completed sucessfully.
    Is that another way to solve unlock problem with 2003 vm ?


          1. Hi, let me explain…
            My source machine is a physical windows Server 2012 R2 hyper-v. I used Disk2vhd to perform p2v conversion. The conversion finished without any problem, but when I imported it to hyper-v, anything works on the VM, ctrl alt del doesn’t unlock the vm. neither mouse and keyboard are captured nor network virtual swith.
            So I did a conversion to VMDK (completed without any problem) and to VHD again (completed without any problem) as this article. I’m thinking on give up and try to do this p2v conversion with windows backup.

            1. I’m not sure about Windows Server backup. Have you tried to change VM settings? (disk controllers and etc.) + you have an option to convert from vhdk to vhd using VMM converter ps module
              Import-Module "C:\Program Files\Microsoft Virtual Machine Converter\MvmcCmdlet.psd1"
              ConvertTo-MvmcVirtualHardDisk -SourceLiteralPath c:\vmdkfolder\test.vmdk -VhdType DynamicHardDisk -VhdFormat vhdx -destination c:\vhdfolder

              Or StarWind V2V
              If you still getting issues, write me directly (contact me page)

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: