Introducing
IntroducingWindowsServer2016_ebook
IntroducingWindowsServer2016_ebook
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
VM configuration version<br />
The VM upgrade process has changed in Windows Server 2016. In the past, when you imported VMs<br />
to a new version of Hyper-V, they were automatically upgraded. However, it was not always easy to<br />
identify which VMs were imported from a previous version of Hyper-V and which were newly created.<br />
That's because the VM configuration version upgrades automatically with the host upgrade.<br />
The real challenge, however, was that you couldn't roll back the VM to a previous configuration<br />
version. The VM version determines with which versions of Hyper-V the VM’s configuration, saved<br />
state, and snapshot files are compatible. In Windows Server 2016, the VM configuration version<br />
upgrade process is no longer automatic. This makes it possible for you to move the VM to a server<br />
running an earlier version of Hyper-V, such as Windows Server 2012 R2. In that case, you do not have<br />
access to new VM features until you manually update the VM configuration version.<br />
All VM capabilities remain compatible, such as live migration, storage live migration, and dynamic<br />
memory. Hence, upgrading a VM is now a manual operation that is separate from upgrading the<br />
physical host. It is important to note that when you upgrade the configuration version of the VM, you<br />
cannot downgrade it. If you use VMs that were created with Windows Server 2012 R2, you will not<br />
have access to new VM features until you manually update the VM configuration version.<br />
VMs with configuration version 5.0 are compatible with Windows Server 2012 R2 and can run on both<br />
Windows Server 2012 R2 and Windows Server 2016. VMs with configuration version 6.0 are compatible<br />
with Windows Server 2016 but will not run on Hyper-V running on Windows Server 2012 R2.<br />
The following table lists the supported versions of the configuration version on Windows:<br />
Hyper-V host Windows version<br />
Windows 10 Anniversary Update 8.0, 7.1, 7.0, 6.2, 5.0<br />
Windows Server 2016 Technical Preview 7.1, 7.0, 6.2, 5.0<br />
Windows 10 build 10565 or later 7.0, 6.2, 5.0<br />
Windows 10 builds earlier than 10565 6.2, 5.0<br />
Windows Server 2012 R2 5.0<br />
Windows 8.1 5.0<br />
Supported VM configuration versions<br />
Upgrading the configuration version<br />
To upgrade the configuration version, shut down the VM and, at an elevated Windows PowerShell<br />
command prompt, type the following command:<br />
Update-VmConfigurationVersion vmname or vmobject.<br />
To check the configuration version of the VMs running on Hyper-V, from an elevated command<br />
prompt, run the following command:<br />
Get-VM * | Format-Table Name, Version<br />
To illustrate the configuration version upgrade process, the following example determines the VM<br />
configuration version imported from a host running Windows Server 2012 R2 and then shows how to<br />
upgrade its configuration version. In this case, as expected, the configuration version of the VM is 5.0<br />
as indicated in Hyper-V Manager (see Figure 2-14).<br />
Figure 2-14: VM version number<br />
22 CHAPTER 2 | Software-defined datacenter