Hello everyone,

In October last year, Microsoft exempt Windows Server Technical Preview 1 bits together System Center technical preview and Windows 10 technical preview.

On Monday, May 4, 2015 and during the Ignite Conference, Microsoft exempt Windows Server 2016 Technical Preview 2 bits together System Center Technical Preview 2.

Windows 10 is scheduled for release on July 29thth An update to Windows 10 is available through Windows Update, so make sure to book a free upgrade by completing the registration and you have enough bandwidth to download the update.

As we can see, 2015 will be an exciting year, however, the final release of Windows Server 2016 and System Center is only in 2016! When? don’t ask me i don’t know …

In today’s blog post, we’ll look at the new features in PowerShell’s Hyper-V in Windows Server 2016 Technical Preview 2 vs. Technical preview 1.

Hyper-V The PowerShell module includes several significant features that extend its use, improve its usability, and allow you to fully manage, automate, and manage your Hyper-V environment.

Hyper-V PowerShell module in Windows Server 2016 TP1 comes with 186 PowerShell cmdlets.

If we look at the PowerShell in Windows Server 2016 TP2 and calculate Hyper-V available cmdlets.

As you can see, Hyper-V 2016 TP2 has 204 cmdlets compared to 186 cmdlets in Hyper-V 2016 TP1, so we have 18 new cmdlets so far. Moment

One important note to note is that starting with Windows Server 2016 TP2 and Windows 10, Microsoft will ship two Hyper-V PowerShell modules in internal versions 1.1 and 2.0 to help manage Hyper-V hosts 2012, 2012 R2, and 2016.


What are these new cmdlets? Let’s compare the Hyper-V 2016 TP1 and TP2 modules side by side and examine the difference.

I will use Compare object cmdlet, but before you can do this, you must capture the XML file with all Hyper-V PowerShell cmdlets on the WS2016 TP1 and TP2 hosts.

TP1 host: Get-Command Module Hyper-V | Export-Clixml C: HyperV-TP1-Compare.xml

TP2 host: Get-Command Module Hyper-V | Export-Clixml C: HyperV-TP2-Compare.xml


The result above is a table that tells you what is different. Each PowerShell cmdlet in the reference series (HyperV-TP1-Comapre.xml), but not in the separation set (HyperV-TP2-Compare.xml), is <= LED (indicating that the cmdlet is on the left side only). However, if the cmdlet is on a Hyper-V TP2 computer but not on a TP1 reference computer, it has => an indicator, which in this case is 18 new cmdlets and 6 updated cmdlets on the right. Finally, PowerShell cmdlets that fit in both sets are not included in the differential output.

All previous PowerShell cmdlets that are available in Windows Server 2012 R2 and 2016 TP1 Hyper-V are also available in Windows Server Technical Preview 2 in addition to:


Dive in and discover what these new cmdlets will bring to Hyper-V 2016 in TP2.


Trust is the biggest barrier to cloud services. In Microsoft Windows Server 2016, they are working hard on the Hyper-V kernel platform to start offering these warranties. Even if you trust or don’t trust your IT administrator, no one can access your information!

Virtual TPM (Trusted Platform Module) can be injected into a virtual machine. You can then enable BiLocker on the virtual machine and protect your data from non-virtual machines. So you can now have a virtual machine running on someone else’s Hyper-V server or someone else’s infrastructure, and you know you only have access to that data.

For the deployment side, this can be done through an Active Directory certificate or a TPM certificate, in which case the TPM certificate requires that the TPM version 2.0 chip be installed on the physical host.

For demonstration purposes only, you can add a virtual TPM to a virtual machine as follows:this is not safe):

1. Enable Hyper-V 2016 TP2
2. Install-WindowsFeature – Name Isolated-UserMode
3. Restart the Hyper-V host
4. Create a Gen2 virtual machine
5. Install the guest operating system, enable Remote Desktop, and then shut down the virtual machine.
6. Run the following cmdlets to configure the virtual TPM:

7. Start the virtual machine, vTPM should appear in the Guest operating system in Device Manager

Note that the virtual machine console license is not available for the secure virtual machine, so you must access the virtual machine through RDP.


Microsoft released step by step Installation and Verification Guide for Windows Server for Windows 2016 TP2 (build # 10074) and System Center VMM for secure fabric hosts and secure virtual machines. You can download the complete guide from here.

Enable-VMConsoleSupport, Disable-VMConsoleSupport

VM console support is for the user interface that is part of USB specification external peripherals, limited functionality at the moment, but it seems we are able to connect and plug direct HID devices into a foreign operating system.


Get-VHDSet, Optimize-VHDSet

There is a new type of VHD file that Microsoft introduced in Windows Server 2016 TP2 VHD series (VHDS) and is required for some new shared VHDX functions. The shared VHDX file still exists, so if you already have guest clusters that use the VHDX file, you can continue to use those VHDX files for the guest clusters. However, you cannot make an online size and host-based backup. The good news is that Microsoft provides tools to quickly and easily upgrade from VHDX to VHDS file so you can take advantage of it.



Get-VHDSnapshot, Delete-VHDSnapshot

Get-VHDSnapshot and Delete VHDSnapshot used to manage a new shared VHD configuration file (VHDS). Limited functionality at this time.


New-VMGroup, Get-VMGroup, Rename-VMGroup, Delete-VMGroup, Add-VMGroupMember, Delete-VMGroupMember

VM group cmdlets are intended to group multiple virtual machines into a single group, for example, a three-tier application that consists of a background database, a mid-level application, and a front-level web server, or if you want to manage a group of virtual machines together.

You must first create a new group and select the group type (VMCollectionType or ManagementCollectionType)


Next, you can start adding virtual machines to the group using Add-VMGroupMember / Remove-VMGroupMember. Limited functionality at this time.

Get-VMHostCluster, Set-VMHostCluster

Microsoft provides a single view of the entire Hyper-V cluster through WMI. You can manage an entire Hyper-V cluster as if it were just one big Hyper-V server.

So, for example, with Get a VM, if you actually point it to one Hyper-V host, you get all the virtual machines on that host, but if you point it to the Hyper-V cluster, what happens will return all the virtual machines in it to the cluster, so you can take the output and mount it to all the different PowerShell commands , which makes it much easier to get started in a Hyper-V cluster with PowerShell.

Get-VMHostCLuster –ClusterName -Credential $ Cred

Set-VMHostCluster -ClusterName -SharedStoragePath SOFS SHARE1

Start-VMTrace, Stop-VMTrace

VMTrace is targeted to trace virtual machines based on different information levels such as (Error, Info, Warning, Verbal, Off).


Add-VMSwitchTeamMember, Set-VMSwitchTeam, Get-VMSwitchTeam, Remove-VMSwitchTeamMember

When we create Teaming vSwitch on Windows Server 2012 / R2, we first create the LBFO team (New-NetLbfoTeam), and it creates a new connected adapter in the system, and finally we connect the adapter to Hyper-V vSwitch. However, in Windows Server 2016 TP2, Microsoft introduced a new group mode called SwitchEmbeddedTeaming, this allows us to simply connect all the physical adapters directly to the Hyper-V virtual switch, and then the virtual switch internally handles the traffic between these adapters from inside the switch, so the virtual switch handles that traffic in and out more efficiently.

First, you need to create a new vSwitch and enable Switch Embedded Teaming as follows:

Note: Note that this does not work in the current version (build 10074). HyperV_PoSh_TP2-17


Upgrading a virtual machine version requires shutting down the virtual machine and performing a manual upgrade. This is a one-way process, so you can do this through either PowerShell or the Hyper-V Manager console. To update a virtual machine configuration file through PowerShell, run the following cmdlet from Advanced Windows PowerShell:


If you want to automate the virtual machine upgrade process, check this send.

I will update this blog post as soon as Technical Preview 3 appears!

entry: This is the current release of the technical preview #10744 compile, so we have to wait and see the changes in the next bits …

Next time … Enjoy the weekend!

– Charbel


Please enter your comment!
Please enter your name here