Netherlands: Software

Introductie Windows Server 2016

Issue link: http://hub-nl.insight.com/i/692748

Contents of this Issue

Navigation

Page 47 of 173

40 C H A P T E R 2 | Compute VM configuration version The VM upgrade process has changed in Windows Server 2016 Technical Preview. In the past, when you imported VMs to a new version of Hyper-V, they were automatically upgraded. However, it was not always easy to identify which VMs were imported from a previous version of Hyper-V and which were newly created. That's because the VM configuration version upgrades automatically with the host upgrade. The real challenge, however, was that you couldn't roll back the VM to a previous version of the VM configuration. The VM configuration version determines with which versions of Hyper-V the VM's configuration, saved state, and snapshot files are compatible. In Windows Server 2016 Technical Preview, the VM configuration version upgrade process is no longer automatic. This makes it possible for you to move the VM to a server running an earlier version of Hyper-V, such as Windows Server 2012 R2. In that case, you do not have access to new VM features until you manually update the VM configuration version. All VM capabilities remain compatible such as live migration, storage live migration, and dynamic memory. Hence, upgrading a VM is now a manual operation that is separate from upgrading the physical host. It is important to note that when you upgrade the configuration version of the VM, you cannot downgrade it. If you use VMs that were created with Windows Server 2012 R2, you will not have access to new VM features until you manually update the VM configuration version. VMs with configuration version 5.0 are compatible with Windows Server 2012 R2 and can run on both Windows Server 2012 R2 and Windows Server 2016 Technical Preview. VMs with configuration version 6.0 are compatible with Windows Server 2016 Technical Preview but will not run on Hyper-V running on Windows Server 2012 R2. Upgrading the configuration version To upgrade the configuration version, shut down the VM and, at an elevated Windows PowerShell command prompt, type the following command: Update-VmConfigurationVersion vmname or vmobject. To check the configuration version of the VMs running on Hyper-V, from an elevated command prompt, run the following command: Get-VM * | Format-Table Name, Version To illustrate the configuration version upgrade process, the following example determines the VM configuration version imported from a host running Windows Server 2012 R2 and then shows how to upgrade its configuration version. In this case, as expected, the configuration version of the VM is 5.0 as indicated in Hyper-V Manager (see Figure 2-39). Figure 2-39: VM version number You can confirm this by using Windows PowerShell as follows: PS C:\Users\Administrator> Get-VM vm02 |Format-Table Name, Version Name Version ---- ------- vm02 5.0

Articles in this issue

Archives of this issue

view archives of Netherlands: Software - Introductie Windows Server 2016