p2v of win 2k3 sbs for hyper-v

Posted on 2012-09-07
Last Modified: 2012-09-10
I have a win 2k3 sbs SP2 standalone server that i'd like to virtualize on new hardware.

The server runs AD, DHCP, TIME, DNS and some local programs.  It is the only domain controller.

I know there are big concerns with migrating Domain Controllers to virtual so want to be sure.

I have a pretty small network (10 computers or so).  
My plan is to do the following.
1. Turn off every computer in the office
2. Use Microsoft disk2vhd tool to make a vhd of the server
3. Turn on the new virtualization server and create the new VM from the VHD
4. start up the office computers (but don't startup the old server)

Is there anything special that I have to do to the original server before running the disk2vhd?  I have successfully done it once and it started up fine in the new VM hardware (minus a network connection to avoid conflicts) so it would seem not.

Would there be any potential problems if the new server that is hosting the VMs was initially joined to the domain?  I'm just picturing issues that may arise from the host server authenticating to one of it's VMs.

Thanks in advance for your help!
Question by:colin911
    LVL 20

    Accepted Solution

    Your plan makes sense. However, I would add couple of things:

    - Do not joint the Hyper-V server to the domain even after p2v: if the only DC is hosted in a domain member Hyper-V, you could find yourselft in a situation where you are unable to log on the server

    - When you do the P2V make sure that once the new virtualized DC is up you never bring up the old unvirtualized server. I would suggest the following: after doing P2V and attaching the VHD file, keep the virtual NIC disconnected until you fix all driver issues and the Integration Services on the new VM.
    LVL 95

    Assisted Solution

    by:Lee W, MVP
    Agree with spaperov.

    Other small note, DCs as VMs is no problem.  HOWEVER, you do NOT want to create snapshots of DCs in multi-DC environments.  Doing so can cause SERIOUS corruption of AD if the snapshot is ever restored.  A single DC environment shouldn't be a problem, though workstations may end up having to be rejoined to the domain.

    Author Closing Comment


    Featured Post

    IT, Stop Being Called Into Every Meeting

    Highfive is so simple that setting up every meeting room takes just minutes and every employee will be able to start or join a call from any room with ease. Never be called into a meeting just to get it started again. This is how video conferencing should work!

    Join & Write a Comment

    Few best practices specific to Network Configurations to be considered while deploying a Hyper-V infrastructure. It may not be the full list, but this could be a base line. Dedicated Network: Always consider dedicated network/VLAN for Hyper-V…
    Citrix XenApp, Internet Explorer 11 set to Enterprise Mode and using central hosted sites.xml file.
    Windows 8 came with a dramatically different user interface known as Metro. Notably missing from that interface was a Start button and Start Menu. Microsoft responded to negative user feedback of the Metro interface, bringing back the Start button a…
    With the advent of Windows 10, Microsoft is pushing a Get Windows 10 icon into the notification area (system tray) of qualifying computers. There are many reasons for wanting to remove this icon. This two-part Experts Exchange video Micro Tutorial s…

    729 members asked questions and received personalized solutions in the past 7 days.

    Join the community of 500,000 technology professionals and ask your questions.

    Join & Ask a Question

    Need Help in Real-Time?

    Connect with top rated Experts

    16 Experts available now in Live!

    Get 1:1 Help Now