The other day I had the bright idea to setup a quick lab to practice some Server 2008 and Active directory functions. I chose Hyper-V as my virtualization platform primarily because I have a descent amount of experience with ESXi and it is always good to try something new.
First I hopped over to the Hyper-V site and downloaded the standalone version of Hyper-V Server 2008 R2 and installed it on an old desktop that was at least new enough to support VT in the BIOS. Everything went well and it installed on the antiquated hardware just fine. (This was the last thing that went smoothly with this project)
This Technet Article was my primary resource for the installation. The article is very well written as long as you pay close attention to server vs client in the instructions. I have no doubt that if both machines are in the same domain then this is a ten minute job and you are up and running. Unfortunately if you are in a mixed environment of workgroups and domains or do not have a DC to authenticate against the task gets much harder. Be prepared for multiple permissions errors while trying to run Hyper-V Manager on the client.
Here are the lessons I learned the hard way –
- The client can not be running Server 2008. It must be Server 2008 R2 or Windows 7
- It is much harder to setup if the client is a member of a domain and the server is in a workgroup. If possible use computers in the same domain or workgroup. (This is more of an issue in a lab environment)
- This 10 Second guide to using the HVRemote.wsf script was more helpful then the original article.
- Sometimes the journey is more important then the destination.
Here is the snippet of text that finally fixed the permissions issues I was having…..