Haven’t been here enough. Too busy working ;)
So, I have embarked on the decision making adventure of choosing ESX 3.5 or Hyper-V for my new internal playground. The playground is a shiny new ML370. I have dual booted it with Beta Hyper-V and a trial of ESX 3.5 (more on exactly how that was accomplished later if I get time).
Not having Virtual Center and not intending to pop the cash for it, I am evaluating ESX using the VMware Infrastructure Client, which leads me to Hyper-V.
I installed Server Core per Microsoft’s recommendations. I did all the standard things to get Server Core on-line and accessible via RDP. I added the Hyper-V role. The recommendations I see tell me to install a full copy of Windows Server 2008 on another server - install the Hyper-V Role - and then manage the Server Core Hyper-V host machine from remote. Sounds easy and I have multiple other installations of Windows Server 2008.
Here is the rub — none of those machines is Hyper-V compliant. In fact one is a vintage 1999 PII 400MHz workstation with 768MB of memory! Try to install the Hyper-V role on any of these and I get a message to the effect that the machine is not Hyper-V compliant.
I just need the management tools not the whole package and it occurred to me that the Hyper-V package should be made up of components like the Web Server role. Oclist does not expose these but a little snooping found this list:
Microsoft-Hyper-V
Microsoft-Hyper-V-Common-Drivers
Microsoft-Hyper-V-Guest-Integration-Drivers
Microsoft-Hyper-V-Management-Clients
Microsoft-Hyper-V-Server-Drivers
The problem is solved with a single command: ‘ocsetup Microsoft-Hyper-V-Management-Clients’ run on the remote machine — in my case, that ancient PII. Let this command finish and the mmc snap-in for Hyper-V-Manager should appear as well as the shortcut in administrative tools. Be careful, the package name seems to be case sensitive.
So much for the assembler programmer’s solution, you can also use:
Add Features>
Remote Server Administration Tools>
Remote Administration>
Hyper-V Tools
and get the same result.
And there is the answer to ‘Where is adminpak.msi in Windows Server 2008. It is there in the form of the Server Manager. We just get to add the snap-ins one-at-a-time now or check all the boxes and do it once.
If you are bored, figure out the package name and install it with ocsetup.
Nick
Comments