The upcoming release of Hyper-V with Windows Server 8, dubbed Hyper-V “R3”, brings a lot of new features to the Microsoft virtualization stack. To many people’s surprise, these features can be delivered without additional management. While System Center Virtual Machine Manager 2012 will bring many new management features, the standalone Hyper-V configuration definitely should not be overlooked.
Like previous versions of Windows, adding Hyper-V is a role that is added to a host, and that is done via Server Manager. Server Manager on Windows Server 8 has a new feature that allows multiple servers to be managed in one interface, but Figure A shows Hyper-V being added to a single host:
Install Hyper-V role (click to enlarge)
Hyper-V does require a restart to make the role take effect on the host, so be sure that if you are planning to add this role, the momentary outage can be accommodated. This is especially of note should the Hyper-V Role be sent remotely through Server Manger to a different system or if PowerShell is used to suppress any options. Figure B shows that important step of adding the Hyper-V role:
Hyper-V Role Installation (click to enlarge)
When the server reboots, the Hyper-V role is enabled and ready to run virtual machines. While Hyper-V Manager on Windows Server 8 has not incurred an incredible number of changes, there are a few new features such as the virtual storage manager and virtual switch manager. Figure C shows the Hyper-V Manager for Windows Server 8.
Hyper-V Manager (click to enlarge)
Deploying the Hyper-V role on Windows Server 8 is rather straightforward as explained above. Do you have any plans to use Hyper-V on Windows Server 8 or on the current version with Windows Server 2008 R2? Share your comments below.