Share via


V2V a Domain controller?

Question

Monday, September 12, 2011 2:03 PM

Can you V2V a domain controller?  Currently we are in the process of moving from VMware to Hyper V, both of our domain controllers are Windows 2008 R2 and they are virtualized on VMware.

I have moved about a 25 VM's so far using V2V, by taking them offline, copy the .vmx and vmdk files into the library and run the conversion.  It has worked well but I am wondering if there are any issues using this process for the Domain Controllers.

 

Thanks!

Thanks, -Lindy

All replies (7)

Monday, September 12, 2011 3:25 PM âś…Answered | 1 vote

Well, v2v is supported.

However, check that you meet the requirements in this V2V guide: http://technet.microsoft.com/en-us/library/cc793147.aspx

Kristian (Virtualization and some coffee: http://kristiannese.blogspot.com )


Monday, September 12, 2011 2:15 PM

I ran into an issue when i was restoing a VHD file which happened to be a Domain Controller.

I was getting a lot of issues.

If they are only dc's, why not dcpromo them down (one at a time), move them, dcpromo back up.

That is what I would do.

just my 0.02 :)


Monday, September 12, 2011 2:50 PM

I normally drive careful when it comes to conversion of domain controllers, though it`s supported to do P2V and V2V.

If they are only domain controllers, you could run dcpromo on a new vm, and transfer the roles.

Kristian (Virtualization and some coffee: http://kristiannese.blogspot.com )


Monday, September 12, 2011 2:52 PM

They are DNS, DHCP, TS License server...and domain controllers.Thanks, -Lindy


Monday, September 12, 2011 2:53 PM

restoring as in from a backup?Thanks, -Lindy


Monday, September 12, 2011 3:37 PM

i mentioned backup as a starting point of using a "replacement" vhd.

anyways, i would suggest using a combination of all the above.

dcpromo 2 new dcs on hyper-v, transfer roles.

dcpromo down current to keep, dhcp and ts.

and potentially v2v the now member servers.

again my 2 cents


Monday, September 12, 2011 9:11 PM

What I am going to do is......

  • Move all of the FSMO roles to one DC.
  • Back both up with DPM.
  • Shutdown the DC with no FSMO roles.
  • Take a SAN based snapshot of the one I am going to move.
  • Copy it to the library server via the vcenter app.
  • Convert it and bring it online.

 

If it works then I will move the FSMO roles and do the same ot the remaining server.  I can imagine it would not especially if it is off.  Also I will have a few restore options, start it up on VMware again, DPM restore, SAN snapshot.

 

Thanks!

Thanks, -Lindy