Windows Server 2012 | Thomas Maurer

Last updated by Thomas Maurer at July 25, 2016.

Jul252016July 25, 2016July 25, 20160 Commentby Thomas Maurer

PowerShell One-liner to list IP Addresses of Hyper-V Virtual Machines

Posted in Cloud, Hyper-V, IT, Microsoft, Powershell, Virtualization, Web, Windows, Windows 10, Windows Server, Windows Server 2012, Windows Server 2012 R2, Windows Server 2016, Work

Here a very quick PowerShell command to list all the Virtual Network Adapters, including IP Addresses of Virtual Machines running on a Hyper-V Host.

Get-VM -ComputerName "Hyperv01" | Get-VMNetworkAdapter

1	Get-VM -ComputerName "Hyperv01" \| Get-VMNetworkAdapter

This will give you a list of all Virtual Machines running on Hyper-V Server called “HyperV01”

May312016May 31, 2016May 31, 20167 Commentsby Thomas Maurer

Windows Sysprep for Virtual Machines

Posted in Cloud, Hyper-V, IT, Microsoft, Powershell, Server Core, Virtualization, VMware, Web, Windows, Windows 10, Windows 8, Windows 8.1, Windows Server, Windows Server 2012, Windows Server 2012 R2, Windows Server 2016, Work

For using the same system image for different virtual machines or physical computer, Microsoft created a tool called sysprep.exe. Most people should be already familiar with that tool. If not here is the description:

Sysprep prepares a Windows installation (Windows client and Windows Server) for imaging, allowing you to capture a customized installation. Sysprep removes PC-specific information from a Windows installation, “generalizing” the installation so it can be reused on different PCs. With Sysprep you can configre the PC to boot to audit mode, where you can make additional changes or updates to your image. Or, you can configure Windows to boot to the Out-of-Box Experience (OOBE).

This is great so you can sysprep a virtual machine copy the VHD or VHDX file and use it for the first boot of different VMs. In Windows Server 2012 and Windows 8, Microsoft added an addition to sysprep called the mode switch “/mode:vm”. The mode:vm switch allows you to identify the Windows as a Virtual Machine and sysprep.exe will generalize a Virtual Hard Disk (VHD or VHDX) so that you can deploy the VHD as a VHD on the same Virtual Machine (VM) or hypervisor. You must deploy the VHD on a Virtual Machine (VM) or hypervisor with the same hardware profile. For example, if you created VHD in Microsoft Hyper-V, you can only deploy your VHD to Microsoft Hyper-V VMs with a matching hardware profile, and you can only run VM mode from inside a VM.

This will boost the performance and time for the virtual machine for the first startup and installation. This also work of course with virtual machines running on other hypervisors such as VMware or Xen.

Run the following command inside the Virtual Machine (You find sysprep.exe in the C:\Windows\System32\Sysprep folder):

sysprep.exe /oobe /generalize /shutdown /mode:vm

1	sysprep.exe /oobe /generalize /shutdown /mode:vm

Now you can copy the VHD or VHDX file from that virtual machine and use it for other VMs.

Feb162016February 16, 2016February 18, 20168 Commentsby Thomas Maurer

Basic Networking PowerShell cmdlets cheatsheet to replace netsh, ipconfig, nslookup and more

Posted in Cloud, Containers, Hyper-V, IT, Microsoft, Microsoft Azure, Nano Server, Powershell, Private Cloud, Virtualization, Windows, Windows 10, Windows 7, Windows 8, Windows 8.1, Windows Server, Windows Server 2012, Windows Server 2012 R2, Windows Server 2016, Work

Around 4 years ago I wrote a blog post about how to Replace netsh with Windows PowerShell which includes basic powershell networking cmdlets. After working with Microsoft Azure, Nano Server and Containers, Powershell together with networking becomes more and more important. I created this little cheat sheet so it becomes easy for people to get started.

Basic Networking Information with PowerShell

Get the IP Configuration (ipconfig with PowerShell)

Get-NetIPConfiguration

1	Get-NetIPConfiguration

List all Network Adapters

Get-NetAdapter

1	Get-NetAdapter

Get a spesific network adapter by name

Get-NetAdapter -Name *Ethernet*

1	Get-NetAdapter -Name Ethernet

Get more information VLAN ID, Speed, Connection status

Get-NetAdapter | ft Name, Status, Linkspeed, VlanID

1	Get-NetAdapter \| ft Name, Status, Linkspeed, VlanID

Get driver information

Get-NetAdapter | ft Name, DriverName, DriverVersion, DriverInformation, DriverFileName

1	Get-NetAdapter \| ft Name, DriverName, DriverVersion, DriverInformation, DriverFileName

Get adapter hardware information. This can be really usefull when you need to know the PCI slot of the NIC.

Get-NetAdapterHardwareInfo

1	Get-NetAdapterHardwareInfo

Disable and Enable a Network Adapter

Disable-NetAdapter -Name "Wireless Network Connection"
Enable-NetAdapter -Name "Wireless Network Connection"

1 2	Disable-NetAdapter -Name "Wireless Network Connection" Enable-NetAdapter -Name "Wireless Network Connection"

Rename a Network Adapter

Rename-NetAdapter -Name "Wireless Network Connection" -NewName "Wireless"

1	Rename-NetAdapter -Name "Wireless Network Connection" -NewName "Wireless"

IP Configuration using PowerShell

Get IP and DNS address information

Get-NetAdapter -Name "Local Area Connection" | Get-NetIPAddress

1	Get-NetAdapter -Name "Local Area Connection" \| Get-NetIPAddress

Get IP address only

(Get-NetAdapter -Name "Local Area Connection" | Get-NetIPAddress).IPv4Address

1	(Get-NetAdapter -Name "Local Area Connection" \| Get-NetIPAddress).IPv4Address

Get DNS Server Address information

Get-NetAdapter -Name "Local Area Connection" | Get-DnsClientServerAddress

1	Get-NetAdapter -Name "Local Area Connection" \| Get-DnsClientServerAddress

Set IP Address

New-NetIPAddress -InterfaceAlias "Wireless" -IPv4Address 10.0.1.95 -PrefixLength "24" -DefaultGateway 10.0.1.1

1	New-NetIPAddress -InterfaceAlias "Wireless" -IPv4Address 10.0.1.95 -PrefixLength "24" -DefaultGateway 10.0.1.1

or if you want to change a existing IP Address

Set-NetIPAddress -InterfaceAlias "Wireless" -IPv4Address 192.168.12.25 -PrefixLength "24"

1	Set-NetIPAddress -InterfaceAlias "Wireless" -IPv4Address 192.168.12.25 -PrefixLength "24"

Remove IP Address

Get-NetAdapter -Name "Wireless" | Remove-NetIPAddress

1	Get-NetAdapter -Name "Wireless" \| Remove-NetIPAddress

Set DNS Server

Set-DnsClientServerAddress -InterfaceAlias "Wireless" -ServerAddresses "10.10.20.1","10.10.20.2"

1	Set-DnsClientServerAddress -InterfaceAlias "Wireless" -ServerAddresses "10.10.20.1","10.10.20.2"

Set interface to DHCP

Set-NetIPInterface -InterfaceAlias "Wireless" -Dhcp Enabled

1	Set-NetIPInterface -InterfaceAlias "Wireless" -Dhcp Enabled

Ping with PowerShell

How to Ping with PowerShell

Test-NetConnection -ComputerName www.thomasmaurer.ch

1	Test-NetConnection -ComputerName www.thomasmaurer.ch

Get some more details from the Test-NetConnection

Test-NetConnection -ComputerName www.thomasmaurer.ch -InformationLevel Detailed

1	Test-NetConnection -ComputerName www.thomasmaurer.ch -InformationLevel Detailed

Ping multiple IP using PowerShell

1..99 | % { Test-NetConnection -ComputerName x.x.x.$_ } | FT -AutoSize

1	1..99 \| % { Test-NetConnection -ComputerName x.x.x.$_ } \| FT -AutoSize

Tracert

Tracert with PowerShell

Test-NetConnection www.thomasmaurer.ch –TraceRoute

1	Test-NetConnection www.thomasmaurer.ch –TraceRoute

Portscan with PowerShell

Use PowerShell to check for open port

Test-NetConnection -ComputerName www.thomasmaurer.ch -Port 80
Test-NetConnection -ComputerName www.thomasmaurer.ch -CommonTCPPort HTTP

1 2	Test-NetConnection -ComputerName www.thomasmaurer.ch -Port 80 Test-NetConnection -ComputerName www.thomasmaurer.ch -CommonTCPPort HTTP

NSlookup in PowerShell

NSlookup using PowerShell:

Resolve-DnsName www.thomasmaurer.ch
Resolve-DnsName www.thomasmaurer.ch -Type MX -Server 8.8.8.8

1 2	Resolve-DnsName www.thomasmaurer.ch Resolve-DnsName www.thomasmaurer.ch -Type MX -Server 8.8.8.8

Route in PowerShell

How to replace Route command with PowerShell

Get-NetRoute -Protocol Local -DestinationPrefix 192.168*
Get-NetRoute -InterfaceAlias Wi-Fi

New-NetRoute –DestinationPrefix "10.0.0.0/24" –InterfaceAlias "Ethernet" –NextHop 192.168.192.1

Get-NetRoute -Protocol Local -DestinationPrefix 192.168*

Get-NetRoute -InterfaceAlias Wi-Fi

New-NetRoute –DestinationPrefix "10.0.0.0/24" –InterfaceAlias "Ethernet" –NextHop 192.168.192.1

NETSTAT in PowerShell

How to replace NETSTAT with PowerShell

Get-NetTCPConnection
Get-NetTCPConnection –State Established

1 2	Get-NetTCPConnection Get-NetTCPConnection –State Established

NIC Teaming PowerShell commands

Create a new NIC Teaming (Network Adapter Team)

New-NetLbfoTeam -Name NICTEAM01 -TeamMembers Ethernet, Ethernet2 -TeamingMode SwitchIndependent -TeamNicName NICTEAM01 -LoadBalancingAlgorithm Dynamic

1	New-NetLbfoTeam -Name NICTEAM01 -TeamMembers Ethernet, Ethernet2 -TeamingMode SwitchIndependent -TeamNicName NICTEAM01 -LoadBalancingAlgorithm Dynamic

SMB Related PowerShell commands

Get SMB Client Configuration

Get-SmbClientConfiguration

1	Get-SmbClientConfiguration

Get SMB Connections

Get-SmbConnection

1	Get-SmbConnection

Get SMB Mutlichannel Connections

Get-SmbMutlichannelConnection

1	Get-SmbMutlichannelConnection

Get SMB open files

Get-SmbOpenFile

1	Get-SmbOpenFile

Get SMB Direct (RDMA) adapters

Get-NetAdapterRdma

1	Get-NetAdapterRdma

Hyper-V Networking cmdlets

Get and set Network Adapter VMQ settings

Get-NetAdapterVmq
# Disable VMQ
Set-NetAdapterVmq -Enabled $false
# Enable VMQ
Set-NetAdapterVmq -Enabled $true

Get-NetAdapterVmq

# Disable VMQ

Set-NetAdapterVmq -Enabled $false

# Enable VMQ

Set-NetAdapterVmq -Enabled $true

Get VM Network Adapter

Get-VMNetworkAdapter -VMName Server01

1	Get-VMNetworkAdapter -VMName Server01

Get VM Network Adapter IP Addresses

(Get-VMNetworkAdapter -VMName NanoConHost01).IPAddresses

1	(Get-VMNetworkAdapter -VMName NanoConHost01).IPAddresses

Get VM Network Adapter Mac Addresses

(Get-VMNetworkAdapter -VMName NanoConHost01).MacAddress

1	(Get-VMNetworkAdapter -VMName NanoConHost01).MacAddress

I hope you enjoyed it and the post was helpful, if you think something important is missing, please add it in the comments.

Jan112016January 11, 2016January 11, 20160 Commentby Thomas Maurer

Change Hyper-V VM Switch of Virtual Machines using PowerShell

Posted in Cloud, Hyper-V, IT, Microsoft, Powershell, Private Cloud, Virtualization, Web, Windows, Windows 10, Windows Server, Windows Server 2012, Windows Server 2012 R2, Windows Server 2016, Work

This is one of the first post of a short blog series with some simple PowerShell scripts and oneliners for Hyper-V. One this is how you can connect a Virtual Network Adapter of a Hyper-V Virtual Machine to another Virtual Switch.

This is very simple, with this command you can see all the Network Adapters of the Virtual Machine and to which Switch they are connected:

Get-VM "VM01" | Get-VMNetworkAdapter

1	Get-VM "VM01" \| Get-VMNetworkAdapter

With this command you can connect it to another Switch:

Get-VM "VM01" | Get-VMNetworkAdapter | Connect-VMNetworkAdapter -SwitchName "NewSwitch"

1	Get-VM "VM01" \| Get-VMNetworkAdapter \| Connect-VMNetworkAdapter -SwitchName "NewSwitch"

Now of course you can also do this for all Virtual Machines running on a Hyper-V host:

Get-VM | Get-VMNetworkAdapter

Get-VM | Get-VMNetworkAdapter | Connect-VMNetworkAdapter -SwitchName "NewSwitch"

Get-VM | Get-VMNetworkAdapter

Get-VM | Get-VMNetworkAdapter

Get-VM | Get-VMNetworkAdapter | Connect-VMNetworkAdapter -SwitchName "NewSwitch"

Get-VM | Get-VMNetworkAdapter

Jul302015July 30, 2015July 30, 20151 Commentby Thomas Maurer

Move multipe Hyper-V Virtual Machines with Live Storage Migration via Windows PowerShell

Posted in Cloud, Hyper-V, IT, Microsoft, Powershell, Private Cloud, Virtualization, Web, Windows Server, Windows Server 2012, Windows Server 2012 R2, Work

Well I was working in on a Private Cloud Deployment where we had some temporary storage for our Hyper-V Virtual Machines and after we got the right storage ready, which was btw a Windows Server Scale-Out File Server Cluster running with Storage Spaces and DataON JBOD chassis, we had to migrate the storage of all virtual machines running on our Hyper-V hosts. Since Windows Server 2012 offers Live Storage Migration which allows us to move the Virtual Machine to a different storage location without downtime we would use that. But if you have to move around 20 virtual machines you think twice if you want to move that via the Hyper-V Manager GUI or Windows PowerShell.

Here is a pretty simple PowerShell foreach loop which moves the storage of all virtual machines running on the Hyper-V host.

#New Storage Location
$StoragePath = "\\SMB01\VMs01\"
#VMs which will be migrated Get-VM will migrate all VMs
$VMs = Get-VM

Foreach ($VM in $VMs) {
$VMStorage = $StoragePath + $VM.Name
Write-Host "Moving VM:" $VM.name "to" $VMStorage
Move-VMStorage -VMName $VM.name -DestinationStoragePath $VMStorage
}

#New Storage Location

$StoragePath = "\\SMB01\VMs01\"

#VMs which will be migrated Get-VM will migrate all VMs

$VMs = Get-VM

Foreach ($VM in $VMs) {

$VMStorage = $StoragePath + $VM.Name

Write-Host "Moving VM:" $VM.name "to" $VMStorage

Move-VMStorage -VMName $VM.name -DestinationStoragePath $VMStorage

}

May252015May 25, 2015May 25, 20151 Commentby Thomas Maurer

Cisco UCS supports Consistent Device Naming (CDN)

Posted in Cisco, Cloud, Hardware, Hardware, Hyper-V, IT, Microsoft, Network, Powershell, Private Cloud, Server, UCS, Virtualization, Web, Windows Server, Windows Server 2012, Windows Server 2012 R2, Work

Yesterday I posted about Cisco UCS supporting RDMA (SMB Direct) with firmware version 2.2(4b)B. Walter Dey, former Cisco Distinguished Engineer at Cisco informed me not only about the RDMA feature he also showed me that Cisco UCS now supports Consistent Device Naming which was introduced with Windows Server 2012. Consistent Device Naming (CDN) allows Ethernet interfaces to be named in a consistent manner. This makes Ethernet interface names more persistent when adapter or other configuration changes are made. To use CDN in Cisco UCS you need to run firmware version 2.2(4b)B. This will help to make it a lot easier to identify network interfaces used with Windows Server 2012 R2 and Hyper-V.

May242015May 24, 2015May 25, 20151 Commentby Thomas Maurer

Cisco UCS supports RoCE for Microsoft SMB Direct

Posted in Cisco, Cloud, Hardware, Hyper-V, IT, Microsoft, Network, Powershell, Private Cloud, Server, UCS, Virtualization, Web, Windows Server, Windows Server 2012, Windows Server 2012 R2, Windows Server 2016, Work

As you may know we use SMB as the storage protocol for several Hyper-V deployments using Scale-Out File Server and Storage Spaces which adds a lot value to your Hyper-V deployments. To boost performance Microsoft is using RDMA or SMB Direct to accelerate Storage network performance.

RDMA over Converged Ethernet (RoCE) allows direct memory access over an Ethernet network. RoCE is a link layer protocol, and hence, it allows communication between any two hosts in the same Ethernet broadcast domain. RoCE delivers superior performance compared to traditional network socket implementations because of lower latency, lower CPU utilization and higher utilization of network bandwidth. Windows Server 2012 and later versions use RDMA for accelerating and improving the performance of SMB file sharing traffic and Live Migration. If you need to know more about RDMA or SMB Direct checkout my blog post: Hyper-V over SMB: SMB Direct

With Cisco UCS Manager Release 2.2(4), Cisco finally supports RoCE for SMB Direct. It sends additional configuration information to the adapter while creating or modifying an Ethernet adapter policy.

Guidelines and Limitations for SMB Direct with RoCE

SMB Direct with RoCE is supported only on Windows Server 2012 R2.
SMB Direct with RoCE is supported only with Cisco UCS VIC 1340 and 1380 adapters.
Cisco UCS Manager does not support more than 4 RoCE-enabled vNICs per adapter.
Cisco UCS Manager does not support RoCE with NVGRE, VXLAN, NetFlow, VMQ, or usNIC.
You can not use Windows Server NIC Teaming together with RMDA enabled adapters in Windows Server 2012 and Windows Server 2012 R2 or you will lose RDMA feature on these adapters.
Maximum number of queue pairs per adapter is 8192.
Maximum number of memory regions per adapter is 524288.
If you do not disable RoCE before downgrading Cisco UCS Manager from Release 2.2(4), downgrade will fail.

Checkout my post about Hyper-V over SMB:

Tag: Windows Server 2012

PowerShell One-liner to list IP Addresses of Hyper-V Virtual Machines

Windows Sysprep for Virtual Machines

Basic Networking PowerShell cmdlets cheatsheet to replace netsh, ipconfig, nslookup and more

Basic Networking Information with PowerShell

IP Configuration using PowerShell

Ping with PowerShell

Tracert

Portscan with PowerShell

NSlookup in PowerShell

Route in PowerShell

NETSTAT in PowerShell

NIC Teaming PowerShell commands

SMB Related PowerShell commands

Hyper-V Networking cmdlets

Change Hyper-V VM Switch of Virtual Machines using PowerShell

Move multipe Hyper-V Virtual Machines with Live Storage Migration via Windows PowerShell

Cisco UCS supports Consistent Device Naming (CDN)

Cisco UCS supports RoCE for Microsoft SMB Direct

Guidelines and Limitations for SMB Direct with RoCE

About

Follow Me

Sponsor

Sponsor

Sponsor

Sponsor