Posts Tagged ‘Windows 8’

Windows Server 2012/R2 and NIC teaming modes and how to

April 2, 2012 8 comments

NIC teaming, the new feature of Windows 2012/R2, allows multiple network adapters on a computer to be placed into a team for the following purposes:

  • Bandwidth aggregation

– Traffic failover to prevent connectivity loss in the event of a network component failure


  • Generic or static teaming (IEEE 802.3ad draft v1): This mode requires configuration on the switch and the computer to identify which links form the team. Because this is a statically configured solution, no additional protocol assists the switch and the computer to identify incorrectly plugged cables or other errors that could cause the team to fail. This mode is typically supported by server-class switches.
  • Dynamic teaming (IEEE 802.1ax, LACP): IEEE 802.1ax uses the Link Aggregation Control Protocol (LACP) to dynamically identify links between the computer and a specific switch. This enables the automatic creation of a team and, in theory, the expansion and reduction of a team simply by the transmission or receipt of LACP from the peer network adapter. Typical server-class switches support IEEE 802.1ax, but most switches require manual administration to enable LACP on the port.
  • Switch independent: do not require that the team members connect to different switches, they merely make it possible.


  • It is manageable through both PowerShell and the GUI
  • Supported on various NIC types/vendors
  • You can team up to 32 NICs
  • Unlimited virtual interfaces
  • Multiple teaming modes
  • NIC teams can only be formed between homogenous NICs. So two 1GB NICs can be teamed, or two 10GB NICs can be teamed, but you cannot team a 1GB and 10GB NIC.
  • If the individual NIC  support Receive Side Scaling (RSS), the NIC team also supports RSS. Hence it is a good idea to team NICs  that support RSS. The resulting NIC team is also highly capable and does not lose any functionality.
  • If the individual NIC  supports RDMA, the resulting NIC team does NOT support RDMA. Given how Windows 8 SMB 2.2 natively supports RDMA without modifying applications, it is a bad idea to team NICs with RDMA capabilities, and where the interconnect (routers, etc) also supports RDMA

How to:

Using Powershell:

  • Static

New-NetLbfoTeam -Name “Team-Static” -TeamMembers NIC1,NIC2 -TeamingMode Static

  • Dynamic

New-NetLbfoTeam -Name “Team-Static” -TeamMembers NIC1,NIC2 -TeamingMode Lacp

  • Switch Independent

New-NetLbfoTeam -Name “Team-Independent” -TeamMembers NIC1,NIC2 –TeamingMode SwitchIndependent

More Power Shell Commands:

  • To get the Teaming proprieties and settings in PowerShell:


  • To get all of the PowerShell commands available for NetLBFO

Get-Command -Module NetLbfo

Using GUI:

  1. Open Server Manager.
  2. In the console tree, click Local Server.
  3. In the details pane, in the Properties section, click NIC Teaming Administration under Remote Desktop.
  4. In the NIC Teaming Window, select the NIC’s to team on the bottom right on the screen
  5. Right click and select add to new team
  6. In the new team window, provide the name of the nic team(e.g. team-static)
  7. Expand the additional properties and select the team mode
  8. click OK to finalise and create the nic team.

Now you are ready to create the Hyper-v Network Switch by using the NIC team.


Understanding SR-IOV in Hyper-V

March 27, 2012 1 comment
Categories: Virtualization Tags: , ,

Windows 8 Hyper-V : Powershell script to create vm’s based on csv file

March 3, 2012 Leave a comment

This is my first PowerShell 3.0 script to create Virtual Machine based on .csv file which contains the necessary information.

I created this script when in the Hands on Hyper-V PowerShell session at the MVP Global Summit, in Redmond.

Save the following .csv file ( I saved it on c:\vms )

OperatingSystem,MinimumMemoryMB,RecommendMemoryMB,BaseVhdPath Win7,512,1024,c:\VHD\7601.17514.101119-1850_x86fre_Enterprise_en-us_VL.vhd 2008R2,1024,2048,c:\VHD\WS2008R2_Enterprise_x64.vhd


Here is the Powershell script:


$vms=import-csv C:\vms\OperatingSystems.csv

foreach ($vm in $vms) {

#this command creates the VM with the recommend memory

New-VM -Name $vm.operatingsystem -MemoryStartupBytes $vm.RecommendedMemoryMB

# this command set’s the minimum memory for the OS

Set-Vm -Name $vm.operatingsystem -MemoryMinimumBytes $vm.MinimumMemoryMB

#how cool is the new command to extract the path and join to a new string…

$vhpath= join-path (Split-Path $vm.basevhdpath -Parent) -ChildPath ($vm.operatingsystem+’Diff.vhdx’)

#this command create a new differencing disk and attach it to a vm

New-VHD –ParentPath $vm.BaseVhdPath –Path $vhdpath -Differencing Add-VMHardDiskDrive -VMName $vm.operatingsystem -Path c:\vhd\Diff.vhdx




Client Hyper-V in Windows 8

March 1, 2012 2 comments

Client Hyper-V is the same computer virtualization technology previously available in Windows Server. In Windows 8 Consumer Preview, the technology is now built into the non-server version of Windows, often called the “desktop” version because it does not run on server-class hardware.
Because Client Hyper-V in Windows 8 Consumer Preview is the same technology as server Hyper-V IT Pros and developers do not need to learn any new tools or commands. You can move virtual machines (VMs) from Client Hyper-V to server Hyper-V. For example, you can build a “test lab” infrastructure hosted entirely on your laptop or desktop machine and export the VMs you create and test from your laptop into production.

Windows PowerShell scripts for managing virtual machines that you create using Client Hyper-V are fully compatible in with Windows Server 8 Hyper-V.

There a few features included in Windows Server 8 Hyper-V that are not included in Client Hyper-V. These include: the remote FX capability to virtualize GPUs (software GPU in RDP 8), Live VM migration, Hyper-V Replica, SR-IOV networking, and synthetic fiber channel.

HARDWARE : Hyper-V requires a 64-bit system that has Second Level Address Translation (SLAT). GB RAM is required. The RAM on your Client Hyper-V machine is allocated and de-allocated dynamically as required by the VMs. You can run several VMs on a Client Hyper-V machine (also called a “host”) that has the minimum 4GB of RAM, but you will need additional RAM for 5 or more VMs, depending on the RAM requirements for each VM.

Client Hyper-V supports server Hyper-V’s “Live Storage Move” capability. This means you can use your VMs fairly independent of the underlying storage. You can move VMs to and from one local drive to another, to a USB stick, or to a remote file share without needing to stop the VM.

To Enable using GUI:

  1. On the Control Panel click “Programs”, and then click “Programs and Features”
  2. Click “Turn Windows features on or off”
  3. Click “Hyper-V”, and then click “OK”, and then click “Close”
To Enable using Powershell :
Enable-WindowsOptionalFeature –FeatureName Microsoft-Hyper-V -Restart

Important :

    You must restart your machine, not just reboot, to complete installation

For more info: Windows 8 Client Hyper-V wiki page (FWLINK) (

Windows 8 Consumer Preview are now live

March 1, 2012 Leave a comment

The Windows 8 Consumer Preview bits are now live. Everything you need to know, including links and information about the download is on the Springboard Series for Windows 8 on TechNet. Also, the Windows 8 TechNet forums are now live.


Hyper-V. New Linux Integration Services 3.2

December 3, 2011 6 comments

This release includes the following features:

  • Synthetic Mouse Support: Finnaly ! The virtualized mouse device is no longer bound to the VMConnect window, and can now be used with a RDP session, which means that you no longer need to install a separate package to get integrated mouse support, and will not have to worry about the mouse being captured by the virtual machine.
  • Merged Device Drivers: We now present a single device driver for both IDE and SCSI devices (hv_storvsc).
  • Windows 8 Fix: The synthetic network device (hv_netvsc) can now be used with a Windows 8 host, eliminating the hang on boot that was previously seen.
  •  SCVMM Fix: This release fixes the issue as described inKB2586286.
  •  Improved Setup Experience: Users now only need to run (as root) to automatically detect the correct architecture and install the appropriate drivers

In addition, :

  • The driver applied to guest virtual machines running Red Hat Enterprise Linux Server 6.1 (architecture x 86 and x 64) and CentOS 6.0 (architecture x 86 and x 64). For earlier version should be used components integration version 2.1
  • In fact, it’s modified drivers in the Linux kernel 3.2, but can work with the Linux kernel 2.6.32, shipped with Red Hat and CentOS

BIG NOTE: Microsoft is working with the sponsors of the Linux distros and in the future a list of officially supported distributions will be expanded.

You can download them directly from here:

Running Windows 8 Preview as Hyper-V Windows 2008R2 Virtual Machine

October 13, 2011 Leave a comment

If you are planning to run Windows 8 as a Virtual Machine under your current Hyper-V Windows 2008R2 server, here is an update   that enables the Windows Developer Preview or Windows Server Developer Preview to be hosted in a Hyper-V virtual machine on Windows Server 2008 R2:


Without this hotfix you may experience one or more of the following issues:

  • The Windows Developer Preview or Windows Server Developer Preview virtual machine stops responding.
  • The Windows Server 2008 R2 host computer displays a stop error message and restarts automatically. This behavior brings down all other running virtual machines together with the host computer