How to properly move a virtual DC from a standalone Hyper-V to a Failover Cluster? We have the same scenario with Exchange 2010 SP3. Help, please.


hi,

i need guidance here, please.

we have standalone hyper-v running windows 2008 r2 datacenter hosting virtual dc , virtual exchange 2010 sp3 server. have failover cluster running windows 2012 std , want move both vms standalone cluster. both vms running windows 2008 r2 std.

what proper way move dc?

what proper way move exchange 2010?

any special considerations based upon information?

how can avoid usn problems?

thanks in advanced. 

what proper way move dc? 

you have four options:

  1. shut down virtual domain controller, pick virtual hard disk , base new highly-available virtual domain controller on it.
  2. export , import virtual domain controller stand-alone hyper-v server onto hyper-v cluster
  3. upgrade the windows server 2008 r2-based hyper-v server windows server 2012 , perform a shared-nothing live migration for virtual domain controller
  4. create additional domain controller same active directory domain on hyper-v cluster, transfer fsmo roles , demote virtual domain controller on stand-alone hyper-v server.

how can avoid usn problems?

when environment features 1 domain controller not encounter usn rollbacks or usn bubbles due moving or migrating domain controllers. (you can encounter these problems backups, though)

however, please note, microsoft recommends running @ least 2 domain controllers per active directory domain.



Windows Server  >  Hyper-V



Comments

Popular posts from this blog

Edit Group Policy

Hyper-V VM not reaching OS 'Logon' screen

DNS question...