Quick Environment Configuration:
At the moment we have two domain controller's (Primary: Windows Server 2003 and a replicating partner that is a physical Windows Server 2012). We are a small office with 20 AD users. The Domain Functional Level and Forest Functional levels are both at Windows Server 2003. The Windows Server 2003 server holds all the FSMO roles.
AD Upgrade Path:
Add a second VM as a new Windows Server 2012 DC. Move the FSMO roles to the other physical Windows Server 2012 DC. Demote and remove the Windows Server 2003 machine.
I have a Windows 2012 Standard Hypervisor with one Exchange 2010 VM running on it. There are a total of 4 physical NICs on this server. I enabled NIC teaming using two NICs as members of the team. The Hypervisor NIC is segregated and is not part of the team. So I now have one physical NIC left right now.
I have a virtual switch configured by the name of VM Switch (Team) which uses the NIC team. I thought I'd mention this just in case.
VM installation options on Hypervisor:
I am contemplating adding the third physical NIC as part of the existing NIC team (VM Switch (Team)) which is currently dedicated to the sole Exchange Server 2010 or create another virtual switch dedicated for the newly created Windows Server 2012 DC. I like the idea of having separate dedicated virtual switches isolating the traffic destined for each VM, but then again it might not be necessary or overkill.
Referencing the disk storage allotted to the new domain controller, I am thinking the most simplistic approach is using one sole virtual disk to create the VM to house the NTDS.dit, logfiles, and SYSVOL folder. Not sure about best practices on this right now. Looking for the simplest setup as possible,
Any advice and supporting documentation is greatly appreciated.