The home Hyper-V server is running away merrily. I have noticed that the 7200rpm drives are definitely not up to scratch when I perform relatively intense procedures, like creating a fixed VHD and installing an OS in another VM using an ISO mounted on the local filesystem…still, it gets there in the end and at least I don’t need industrial cooling and soundproofing.
As I previously wrote, to set up the environment so that I can test various System Center products, the parent partition on the Hyper-V system really needed to be a member of a domain. The setup of that went well and hasn’t presented any issues so far.
The next step was remote management. Of course I can do everything from the local console, but it’s always good to have other options (especially when that option has a nice 23″ screen attached!). Normally, the steps to get remote management of a domain system from a non-domain source can be tricky, but in this scenario all is made sweetness and light by the technical wonder that is John Howard. No, not our former PM, but rather the Senior Program Manager with the Hyper-V team in Redmond – check out his blog here.
John has written a utility called “Hyper-V Remote Management Configuration Utility”, or HVRemote for short, which is available for download from MSDN.
All you need is HVRemote downloaded to both the client machine and the server, and with the 10-second guide on the HVRemote page you’ll be up and away with probably only just one reboot. Amazing! And if I sound gushy it’s because I have set up remote management before the existence of HVRemote, and believe me it was no fun.
So if sorting out remote access to/from a Hyper-V server is on the cards – start and finish with HVRemote. Seriously, I’d expected this to take me a while, and it ended up being all sorted within 5 minutes.
THAT’S the sort of technical problem I like 🙂