This move is possible because both Windows 10 and Windows Server 2016 are new systems, which can read the format of virtual machines exported from older configuration system versions (for Windows Server 2012 R2, the configuration system version is 5.0 while for Windows 10, it is 6.2). vmcx, which is supported only by Windows 10 and Windows Server 2016.Īs you may suppose, there is no problem when you import the virtual machine the opposite way round – from Windows Server 2012 R2 to Windows 10 (or to Windows Server 2016). So why are those files not visible in the wizard? The problem is related to the new format of a virtual machine configuration file, namely. In the Select Virtual Machine section, the virtual machine imported from Windows 10 host is not listed:Īs you can see in the screenshot below, the virtual machine files exist but the wizard doesn’t see them: To see what happens when you try to import such virtual machines, go to the Import Virtual Machine wizard and locate the folder with your virtual machine: Unluckily, along with the release of Windows 10, the export/import functionality has been restricted – in other words, it is no longer possible to perform export/import move of the virtual machine from Windows 10 to Windows Server 2012 R2. This scenario, however, may not work in all situations. The usual scenario would be to export the virtual machine from the local host and move it to the server host. When preparing a Hyper-V virtual machine, it is a good idea to create it and configure it on your own computer, and then implement it in the production environment.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |