Small Business Susan

P to Ving with the Sysinternals tool

http://technet.microsoft.com/en-us/sysinternals/ee656415.aspx


Testing this out.  Have a HP ML370G4 that has a physical install of SBS 2003 on a raid/hardware system.  Have a HyperV on an HP ML370G6.  In a test run (where I screwed up because I didn’t understand that I needed to ensure I copied the VOLUME which included both an Exchange data drive and a data data drive) I booted up the resulting VHDs and they didn’t BSOD with the move.


Mind you they had ghosted nics so that’s to be totally expected, and easily removed from the machine and then a rerun of the CEICW and that box was basically a running system.

How to remove ghost nics on vmware machines that have been P2Ved « Ramblings of a semi sane person:
http://secadmin.wordpress.com/2009/02/11/how-to-remove-ghost-nics-on-vmware-machines-that-have-been-p2ved/


Step 1: Open up a command prompt


Step 2: Type – “SET DEVMGR_SHOW_NONPRESENT_DEVICES=1″ and hit


Step 3: Type – “START DEVMGMT.MSC” and hit


Step 4: Once the Device Manger opens to the “View” menu and select “Show Hidden Devices”. Expand the Network Interface portion of the device tree and you should be able to remove the phantom NIC.

I’m doing it again as I need the second volume copied, and it will want reactivation in three days because I just ripped it off the hardware it was tied to, but it appears to do a physical to virtual without causing a bsod.  I’ll do a longer blog post explaining the process tomorrow.


The other thing you can use this for (assuming the proper XP movable licenses) is that you can PtoV and make a real XP that XP Mode underneath that Windows 7.  Kinda kewl huh?



2 comments ↓

  • #   Ben Krause on 11.05.09 at 6:05 am     

    Another tool that does this (a little more automated) is the System Center Virtual Machine Manager (SCVMM).

    I had used it once before to P to V an SBS 2003 box to a Hyper-V machine running Server 2008. It captured the entire system, shut down the old system and started the new one for me without any troubles.

    Recently I did the same thing to P to V a 2003 server to a Server 2008 32but running Virtual Server 2005 R2. I had some troubles this time but it was related to TCPOffloading being enabled on the server 2008. Once turned off it went flawlessly.

    I think you can use SCVMM as a trial to get the conversion done, then use Virtual Server 2005 R2 to manage it.


  • #   John Currie on 11.05.09 at 8:15 am     

    SBS 2008 is even finckier with this as it only want 1 NIC.

    I removed the ghost nics through the registry, rebooted and ran the “fix my network” wizard.

    This was a P2V and is now running in production.