Hi Experts,
I am in the process of implementing Windows server 2012 and new features to my company, and have some questions related to design and best practices
My environment:
2 different sites, Windows 2008 R2 physical hosts, Hyper-V, Exchange 2010, Lync 2010, SCCM 2007 R2/SCOM 2007 R2 and allmost all MS technologies running
on different VMs across the 2 sites. Fiber channel and ISCSI for storage.
My proposed plan
1. Allocate new hardware compatible with Windows server 2012. Perform a clean OS installation of Windows server 2012.
2. Install Failover clustering feature and Hyper-V on each physical host to be deployed on each site
3. Enable Hyper-V replica between new Windows server 2012 physical host across sites
4. Perform a live migration from Windows server 2008 R2 physical hosts to new Windows server 2012 hosts
Questions:
1. Does it make any sense to you this high-level migration plan?
2. Should I join each new Windows server 2012 physical host to my Windows domain?
3. Since we do have all DCs in virtual, and deploying a new DC on a physical server is not an option. What is my best option to deploy new DC, and transfer all FSMO roles?
4. Do you have a step-by-step doc/blog to enable Hyper-V replica, and perform live migration from Windows server 2008 R2 host to a Windows server 2012 hyper-V host?
5. From all the MS technologies above mentioned, can you please provide a MS blog, doc, best practices to deploy on Windows server 2012 virtual environment?
6. Should I use Cluster shared volumes or the traditional cluster disk or quourum? pros and cons? best advice please
7. How many VMs should I deploy for each physical host? best practices?
8. Should I deploy one VM for each server role on each site to allow redundancy? For example. An Exchange 2010 CAS/HUB server one VM for each site, same for MB server role
Franki
