This blog will explain how to enable and install the Hyper-V role on Windows Server 2012. You can click on the pictures for a larger version of the picture.

 

(note: this blog was created with Windows Server 2012 Release Candidate but the screenshots will probably still be valid for the final version that is now available)

 

I am running Windows 2012 RC Bare Metal on my laptop on a separate Intel SSD. The boot time was impressive.

 

Assuming you have installed Windows 2012 you will start with the new Server Manager once the server has started.

 

The new Server Manager is a big improvement over the Windows 2008 R2 Server Manager, Microsoft did a good job on improving it.

 

To start with adding the Hyper-V role click on ‘Add roles and features’ in the Server Manager

 

 

After that some basic information is displayed, click on ‘Next’ to continue

 

 

On the next screen you have to choose if you want to do a role-based and feature-based installation or a Remote Desktop services installation. For now choose the role-based and feature based installation, I will cover the Remote Desktop Services part in an upcoming blog that I am still working on.

 

 

Choose if you want to select a Server from the server pool or Select a virtual hard disk. For my test environment I selected the local server installation that I am using.

 

 

After that the list of selectable roles will appear. Select the ‘Hyper-V’ role and click ‘Next’

 

 

After that a pop-up box will appear that indicated that some features are required to add the Hyper-V role.

Click on ‘Add features’ to select the required management components. Then click ‘Next’ to continue with adding the Hyper-V role.

 

 

The next screen will inform you that some choices will have to made before the Hyper-V role can be added. Click on ‘Next’ to continue.

 

 

Select the network adapter that you want to use with Hyper-V and click ‘Next’

 

 

The next screen will ask if you want to use the ability the send/receive Live migrations with this Server. Live Migration without the need for Shared Storage is one if the awesome new features in Hyper-V 3.0. I might want to give this a try so for now I will enable this feature and select the less-secure authentication method as this will be easiest way to try this from a 2nd Hyper-V server that might not be in my domain.

 

 

Next select the location where you want to store the virtual hard disks and the configuration data. Separating the Virtual Disks and the configuration data differs from Hyper-V R2/2.0 where all data was stored in one folder. Personally I do not think that the ProgramData folder and User folder would be the most convenient places for the configuration data and for the virtual disks. I changed this to a new Hyper-V folder on my D: drive and created a separate folder in the Hyper-V folder for Virtual Disks and for Configuration.

 

 

On the next screen you can select if you want the Server to automatically reboot if required (this option is new compared to Server 2008 R2)

Then finally the ‘Install’ button is no longer grayed out and you click this finalize the Hyper-V installation.

On my test machine two reboots where required before I could logon again.

 

 

After the two reboots the Server Manager will indicate that the installation succeeded and that you can click on ‘Close’ to end the Hyper-V installation.

 


Hyper-V is now listed in the Server Manager on the left part of screen where all installed roles will be added.

 

 

For some reason the Hyper-V management console has now been added to the Metro UI. I do not see the benefits or use case for enabling the Metro UI on a Server by default. The Metro UI should only be installed after adding features that extend the desktop experience.

 

 

You are now ready to deploy new Virtual Machines with Hyper-V 3.0 on Windows Server 2012.

 

 

For the Windows Server 2012 series I am also working installing Active Directory and on installing Remote Desktop Services. I will publish these soon.