Initial Server Setup with Microsoft® Windows Server® 12 Beta and the Dell™ PowerEdge™ R710

This blog post was originally written by Aditi Satam and Michael Schroeder.

Comments are welcome! To suggest a blog topic or make other comments, contact

With the announcement of Windows Server 2012 Beta, we explored some of the common setup tasks that are configured before deploying any applications or workloads on the PowerEdge R710. 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 embedded Broadcom 5709 network cards on the R710 and attach the system to our test domain.

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

Step 1: Launch PowerShell v3.0 with Administrator Privileges

After the Beta installation is complete, select the Windows PowerShell icon from the taskbar. Make sure PowerShell is running with Administrator privileges as noted in the title bar below. Using the $Host command, we can confirm that we have version 3.0 of PowerShell installed:


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 run the following cmdlet:

Rename-Computer -NewName Win8-HV3 -Restart

Step 3: Configure NIC Ports with a Static IP Address

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

Next we’ll configure the first Broadcom 5709 NIC port with a new IP address. To add a static address, we will first disable dhcp then assign a static IP address.

Here are the commands:

Set-NetIPInterface -InterfaceAlias “Wired Ethernet Connection” –Dhcp Disabled

New-NetIPAddress -InterfaceAlias “Wired Ethernet Connection” –Ipv4Address 10.X.X.XX –PrefixLength 8

Step 4: Set DNS Client for Domain Name Resolution

Now that the IP address is established, we must also set our DNS client for proper domain name resolution using:

Set-DnsClientServerAddress -InterfaceAlias “Wired Ethernet Connection” -ServerAddresses 10.XX.XXX.XXX


Step 5: Add the PowerEdge R710 Server to the Domain

Now that we’re on the network, let’s join the R710 to the domain. A restart is needed for the changes to take effect. Simply run the following Windows® PowerShell™ command:

Add-Computer -DomainName OSEDEV.local -Credential osedev\administrator -Restart

Step 6: Verify and Modify Windows Roles and Features

To get a list of all of the Windows roles and features available run Get-WindowsFeature

Add a new Windows role or feature with Add-WindowsFeature -Name Hyper-V -Restart

To confirm that the role or feature was installed run the following:

Get-WindowsFeature | ? installed


If you have had previous experience with Windows PowerShell™ v2, you will quickly discover that PowerShell v3.0 is packed with a great number of networking related cmdlets and many others to help you quickly configure your 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.

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!