Sign in
 
HomeWindows Server 2012Windows Server 2008 R2Windows Server 2003LibraryForums
Windows Server TechCenter >
> 
> 
WS2008R2 AD DS VM Migration

Answered WS2008R2 AD DS VM Migration

  • Wednesday, November 28, 2012 10:26 PM
     
     
    Sign In to Vote
    0
    My organization (a small group) is trying to move our (only) domain controller from an old server to our new one. The domain controller is a Windows Server 2008 R2 Standard virtual machine running on Hyper-V. We are simply trying to move the VM from one Hyper-V host to another. We have migrated other VM's with no problem. The domain controller, however, will not start after migration and won't authenticate anything. Does anyone know why this is happening and how to migrate successfully? Any advice is appreciated.
     

All Replies

  • Thursday, November 29, 2012 8:56 AM
     
     
    Sign In to Vote
    0

    Hi,

    How did you migrate the virtual machine ?export then import or copy the VHD file onto the other hote.
    the best way to migrate active directory is to create new virtual machine as second active directory and then migrate the FSMO roles and finally demote the old one via dcpromo command.


    Best regards Bourbita Thameur Microsoft Certified Technology Specialist: Windows Server 2008 R2,Server Virtualizaton

     
  • Thursday, November 29, 2012 6:17 PM
     
     
    Sign In to Vote
    0

    Thanks for the quick reply. We exported then imported the vm.

    I like your idea about creating a new Active Directory vm and migrating roles. I will try this and get back to you. However, we had problems before when creating a second domain controller. When I added a second domain controller, it broke the first domain controller. The first domain controller would not allow us to logon with any credentials. I ended up seizing the master roles for it on the second dc. I know this is getting off topic for the thread, but do you know what may have caused this?

     
  • Friday, November 30, 2012 9:05 AM
     
     
    Sign In to Vote
    0

    hi

    Have you turned off the first server to avoid conflict with the second server imported?

    Note that after seizing the fsmo role the old server must not be running again

    Best regards Bourbita Thameur Microsoft Certified Technology Specialist: Windows Server 2008 R2,Server Virtualizaton

     
  • Friday, November 30, 2012 1:09 PM
     
     Answered
    Sign In to Vote
    1

    hi

    Have you turned off the first server to avoid conflict with the second server imported?

    Note that after seizing the fsmo role the old server must not be running again

    Best regards Bourbita Thameur Microsoft Certified Technology Specialist: Windows Server 2008 R2,Server Virtualizaton

    That is not true. You can run or keep old DCs after the FSMO transfer.

    If you are planning to add additional DCs, you wont be to maintain the same IP and name during the transition period.

    However, your issues sounds like a VM networking related issue.  Not a DC.  After the hyper-v host migration, did you check the IP address? VM can ping the default gateway?

    Santhosh Sivarajan | Houston, TX

    Migrating from 2008 to Windows Server 2012
    http://www.sivarajan.com/

    FaceBook Twitter LinkedIn SS Tech Forum

    This posting is provided AS IS with no warranties,and confers no rights.

     
  • Friday, November 30, 2012 2:55 PM
     
     Answered
    Sign In to Vote
    1

    Hi santhash Sivarajan,

    I'm not talking about fsmo migration , but the VM migration using export and import option in hyper-v.

    I'm agree with you if it was fsmo migration you shouldn't turn off any DC.

    Best regards Bourbita Thameur Microsoft Certified Technology Specialist: Windows Server 2008 R2,Server Virtualizaton

     
  • Sunday, December 02, 2012 8:13 PM
     
     Answered
    Sign In to Vote
    2

    The fully supported way to do it is the following:

    • Create a new VM and promote it as a DC / DNS / GC server
    • Transfer FSMO roles to the new DC: http://support.microsoft.com/kb/255690/
    • Demote the old VM (You have to check that everything is fine for DCs health and AD replication. This could be done using dcdiag and repadmin tools)

    Of course, once you demote the old VM, you will be able to rename the new DC and re-use the old IP.

    This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

     
  • Tuesday, December 04, 2012 3:50 AM
     
     
    Sign In to Vote
    0
    Thanks for the help. I transferred the FSMO roles as everyone has suggested, but kept the original DC for redundancy. They're both on the same physical host so that kind of defeats the purpose, but we will move them later. Both DC's seem to be working well. Thank you all again for your help.
    • Edited by Mevry Tuesday, December 04, 2012 3:51 AM
    •