I’ve learned a lot of things from building a Hyper-V server, many of which I thought I already knew.
The most important thing is Plan, plan, plan, and plan some more. I went into this with an overall idea of what I wanted to do– build a virtual lab, so I can work on my Microsoft Certifications — however, I realized after building the PC, installing HyperV and setting a virtual Active Directory domain, I didn’t plan things out very well. The biggest problem came when I tried to daisy chain two routers, so I could run a virtual DHCP server on the first router instead of using the built-in DHCP server, and using the second router as a basic access point. It did not turn out so well after spending hours fighting with configurations. It turned out to be a issue with the virtual network switch for the virtual clients/servers — I did not assign it a static IP address, so the DHCP server was not assign addresses to any on virtual clients; I believe the ethernet cable wasn’t firmly connected too.
Here are my lessons, thus far, in no particular order:
* Plan the deployment in depth.
* If using HyperV in a workgroup environment – follow the directions by John Howard here (http://blogs.technet.com/b/jhoward/archive/2008/03/28/part-1-hyper-v-remote-management-you-do-not-have-the-requested-permission-to-complete-this-task-contact-the-administrator-of-the-authorization-policy-for-the-computer-computername.aspx)
* Don’t forget to set the correct firewall exceptions on both server and the managing computer, if you are not using RD.
ex: netsh advfirewall firewall set rule group=”Windows Firewall Remote Management” new enable=yes
Some MMC snap-ins and their rule group for netsh:
MMC snap-in — Rule Group
Event Viewer Remote — Event Log Management
Services Remote — Service Mangement
Shared Folders — File And Print Sharing
Task Scheduler — Remote Scheduled Tasks Mangement
Reliability and Performance — Performance Logs and Alerts, File and Print Sharing
Windows Firewall with Advanced Security — Windows Firewall Remote Management
* When installing RSAT, use Wusa.exe from the command prompt instead of double-clicking on the file.
* Use a RAID setup for virtual machine files. There is a serious disk I/O bottleneck when working with a single hard drive.
* Use Server 2008 R2 Core instead of a Full install for the best performance.