Netherlands: Software

Introductie Windows Server 2016

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

Contents of this Issue

Navigation

Page 48 of 173

41 C H A P T E R 2 | Compute As stated previously, you must shut down the VM and run the following Windows PowerShell command to upgrade the configuration version of the VM: PS C:\Users\Administrator> Update-VMConfigurationVersion vm02 Confirm Are you sure you want to perform this action? Performing a configuration version update of "vm02" will prevent it from being migrated to or imported on previous versions of Windows. This operation is not reversible. [Y] Yes [A] Yes to All [N] No [L] No to All [S] Suspend [?] Help (default is "Y"): Y PS C:\Users\Administrator> When checked again, the configuration version in Hyper-V Manager now has the value 6.0, as depicted in Figure 2-40. Figure 2-40: Upgraded version number Again, you can confirm this by using Windows PowerShell as follows: PS C:\Users\Administrator> Get-VM vm02 |Format-Table Name, Version Name Version ---- ------- vm02 6.0 As an aside, if you get any startup failure after a VM configuration version upgrade, try turning on secure boot and then run the following Windows PowerShell command: Set-VMFirmware -VMName "VMName" –SecureBootTemplate MicrosoftWindows The VM configuration version is successfully upgraded, which means the VM has access to new VM features introduced in Windows Server 2016 Technical Preview. Upgrade process considerations You need to be aware of several considerations before you upgrade the configuration version of a VM: You must shut down the VM before you upgrade the VM configuration version. The configuration version upgrade process is one way; that is, when you upgrade the configuration version of the VM from version 5.0 to version 6.0, you cannot downgrade, and, hence, afterward you cannot move the VM to a server running Windows Server 2012 R2. The Update-VMConfigurationVersion cmdlet is blocked on a Hyper-V cluster when the cluster functional level is Windows Server 2012 R2. You can still move the VM between all of the nodes in the Hyper-V cluster, however, when the cluster has a mix of both Windows Server 2012 R2 and Windows Server 2016 Technical Preview. New configuration file format After you have upgraded the VM configuration version as described in the previous section, the VM will use the new configuration file format. The new VM configuration file format uses the .vmcx extension for the VM's configuration data and the .vmrs extension for its runtime state data. The new format is a binary file format, which means that you cannot edit the file directly. The new configuration file format increases the efficiency of reading and writing the VM's configuration data, reduces the potential for data corruption in the event of a storage failure, and provides better overall efficiency. Figure 2-41 shows the new VM configuration file format, which uses the .vmcx extension for the VM's configuration data and the .vmrs extension for runtime state data.

Articles in this issue

Archives of this issue

view archives of Netherlands: Software - Introductie Windows Server 2016