Which Windows PowerShell cmdlet should you run?

You have a server named Server1 that runs Windows Server 2012.
You plan to enable Hyper-V Network Visualization onServer1.
You need to install the Windows Network Virtualization Filter Driver on Server1.
Which Windows PowerShell cmdlet should you run?

You have a server named Server1 that runs Windows Server 2012.
You plan to enable Hyper-V Network Visualization onServer1.
You need to install the Windows Network Virtualization Filter Driver on Server1.
Which Windows PowerShell cmdlet should you run?

A.
Set-NetVirtualizationGlobal

B.
Set-NetAdapterVmq

C.
Add-WindowsFeature

D.
Enable-NetAdapterBinding



Leave a Reply 4

Your email address will not be published. Required fields are marked *

5 × three =


MCSE

MCSE

http://technet.microsoft.com/en-us/library/jj130913.aspx

The Enable-NetAdapterBinding cmdlet enables binding of a protocol or filter to the network. By default this cmdlet operates on the protocols and filters visible in the Windows UI Network Adapter properties pages. Note: Enabling some adapter bindings can automatically disable other network adapter bindings.

sneed

sneed

Hyper-V Network Virtrtualization runs multiple virtual networks on a physical network. And each virtual
network operates as if it is running as a physical network. The The Set- NetAdaptercmdlet sets the basic
properties of a network adapter such as virtual LAN (VLAN) identifier (ID) and MAC address. Thus if you add
the binding parameter to the command then you will be able to install the Windows Network Virtualization
Filter Driver.
Step one:
Enable Windows Network Virtualization (WNV). This is a binding that is applied to the NIC that you External
Virtual Switch is bound to. This can be a physical NIC, it can be an LBFO NIC team. Either way, it is the
network adapter that your External Virtual Switch uses to exit the server.
This also means that if you have multiple virtual networks or multiple interfaces that you can pick and choose
and it is not some global setting.
If you have one External Virtual Switch this is fairly easy:
$vSwitch = Get-VMSwitch -SwitchType External
# Check if Network Virtualization is bound
# This could be done by checking for the binding and seeing if it is enabled ForEach-Object -InputObject
$vSwitch {
if ((Get-NetAdapterBinding -ComponentID “ms_netwnv” -InterfaceDescription
$_.NetAdapterInterfaceDescription).Enabled -eq $false){ # Lets enable it
Enable-NetAdapterBinding -InterfaceDescription $_.NetAdapterInterfaceDescription -ComponentID
“ms_netwnv”
}}

Cleber

Cleber

D – Enable-NetAdapterBinding