Really, if you are going to migrate off 2003 to a newer Microsoft platform , bypass 2008 , 2008 R2 , 2012 and go straight for 2012 R2. The Time you are going to invest in the migration, you may as well go directly to the stable product that is 2012 R2
Virtualisation Support in Hyper-V and WMware 5.1 for Domain Controllers
With Server 2012 came the ability for the domain controller to understand it was virtualised. (AKA VM-Generation ID support ) This means with things like snapshotting a DC and rolling back the snapshot, the Domain Controller will know it has been rolled back and not try and continue servicing AD requests, or talk to the other Domain Controllers
Three important document’s to read and understand:
With 2012 cam a new version of DHCP. Gone is the need to do split scopes. DHCP HA can be setup in two ways
- Load sharing mode, where two DHCP servers are clustered together and serve the clients
- Hot standby mode, where you can setup one DHCP server to be the active node and fail back to a standby DHCP server. This can be a many to one relations ship, e.g. 4 remote sites can have the active node and they all fall back to one Standby DHCP server at Head Office.
2012 was just the start of it, there are 24 more DHCP cmdlets with 2012 R2 for example. PowerShell just makes an admins life easier