Most people think that the process to migrate a virtual machine from one host that is running a previous version of Hyper-V, to another one with a newer version, is simply done by the export and import process, as shown in the previous task. In the past this would have been wrong, but this is the experience that Microsoft wants to provide for Windows Server 2016. During previous migrations, you may have noticed some strange behavior in the VMs you migrated, such as mouse integration, slow performance, and some other issues.

With Windows Server 2016, Microsoft has changed its strategy when it comes to Integration Services, no longer are the Integration Service versions so heavily matched to the host version. The focus is now on applying updates to the VM if there is a requirement to update the VM. This has the added benefit that the person responsible for managing the Hyper-V host isn't necessarily responsible for updating...