Page has been moved.

Initial Hyper-V Role Setup with Microsoft® Windows Server® 2012 Beta and the Dell™ PowerEdge™ R810

This blog post was originally written by Michael Schroeder.

Microsoft Windows Server 2012 was previously known as Windows Server “8”.  Comments are welcome! To suggest a blog topic or make other comments, contact

With the announcement of the Windows Server 2012 Beta, we explored some of the common setup tasks that are implemented while deploying the Hyper-V Role on the PowerEdge R810. With the initial setup of our server, we decided to walk through some of the new Windows® PowerShell™ v3.0 cmdlets in Windows Server 2012 Beta to help configure the initial steps for setting up Hyper-V on the PowerEdge R810.

The following steps are a good reference to use when setting up and testing your PowerEdge systems with Windows Server 2012 Beta. 

Step 1: Enable the required hardware settings

The Windows Server 2012 Beta Hyper-V role requires the following hardware features:

  • Hardware-assisted Virtualization - Intel Virtualization Technology
  • Hardware-enforced Data Execution Prevention (DEP) – Intel Execute Disable (XD) bit.

After pressing F2 to enter the System BIOS, locate the following options and ensure they are both set to “Enabled”:

“Processor Settings” -> “Virtualization Technology”

“Processor Settings” -> “Execute Disable”

Note: Additional BIOS details can be found by highlighting a particular setting then selecting F1 for help.

After the hardware settings are established, the GUI installation of Windows Server 2012 Beta can then be completed.

Step 2: Rename the System

Now we’ll rename the system to something more appropriate for use in our lab. A restart is needed for the name change to take place. We’ll use a new PowerShell cmdlet to make this change. Open Windows PowerShell from the taskbar, and then run the following cmdlet:

Rename-Computer -NewName WIN12HV02 -Restart

Step 3: Configure Network Settings

Let’s list all the available Network Adapters (NICs) using the Get-NetAdapter cmdlet.

The following four sample commands can be used for manually configuring the IP address for your NIC. If you’re using DHCP, you can skip this step.

Set-NetIPInterface -InterfaceAlias “Wired Ethernet Connection” -DHCP Disabled

Remove-NetIPAddress -InterfaceAlias “Wired Ethernet Connection” -AddressFamily IPv4 -Confirm:$false

New-NetIPAddress -InterfaceAlias “Wired Ethernet Connection” -AddressFamily IPv4 -IPv4Address -PrefixLength 24 -Type Unicast
Set-DnsClientServerAddress -InterfaceAlias “Wired Ethernet Connection” -ServerAddresses

Step 4: Enable the Hyper-V Role

While you can enable Hyper-V through the familiar Server Manager, you can also do so very quickly via PowerShell. After adding the Hyper-V role a system restart is needed to complete the installation. Run the following cmdlet to add the Hyper-V role and restart the system:

Add-WindowsFeature –Name Hyper-V -IncludeManagementTools -Restart

To confirm the Hyper-V role was installed successfully, run the following PowerShell command to list all the installed roles and features on the system:

Get-WindowsFeature | ? Installed 

Step 5: Configure a Hyper-V Virtual Switch

Next, we’ll create and configure an external virtual switch and connect one of our Broadcom 5709 NIC ports to it to allow for external host communication between virtual machines (VMs) and other hosts on our network. We’ll leave another NIC port free for Remote Desktop management of the host.

Step 6: Create the First VM

Now we can create the first VM with PowerShell then open the Hyper-V Manager to configure the VHD details or any other settings we would like configured on the VM. At this point, the VM’s OS can be installed and configured with any desired workload.

As you can see, Windows Server 2012 Beta is packed with a great number of cmdlets to help you quickly configure your Roles and Features on PowerEdge systems. These new PowerShell cmdlets save you a great deal of time when building out your solutions and are also very intuitive to script for your automated needs. We hope you found this walkthrough helpful.  

Because Windows Server 2012 Beta is a pre-release product still in active development, all features are of course subject to change. Dell does not provide any support for this pre-release software and it is not recommended for use in a production environment. Feel free to check out the new features of the Beta release on your test servers and let us know what you think. Stay tuned for more blogs from the Dell OS Engineering team.