Likewise for other software installed in the VM: There is a chance that applications could see that the hardware has changed and demand that you reactivate/relicense to keep using it.įinally, keep in mind that Windows 7 is out of support, and Microsoft has made clear that they will not necessarily be supporting Windows 7 on the latest CPUs, so there might be some inherent risk in running Windows 7 on a very new host. I don't recall precisely how fussy Windows 7 is with its product activation. If there is a change of CPU, the guest OS will be able to see that. Choosing 'Moved' will ensure that your virtual machine's network identity (MAC address) is kept unchanged Choosing 'Copied' will generate a new MAC address – which would allow the 'source' and 'destination' VMs to coexist on the same network without interfering with each other.īe aware that you might need to re-activate the Windows guest OS if it feels that too much hardware has changed. If you do not plan to power on the VMs anymore on the old host, choose 'Moved', even if you actually copied them. When you start using the VM on the new host, Workstation Player will probably ask whether the VM was moved or copied. If a snapshot is copied, Workstation Player might warn you about changed CPU capabilities when you try to resume the VM on the new host, and the guest OS might potentially crash if you continue anyway. Again, we try to keep that compatibility as close to 100% as we can, but sometimes it is simply not possible – particularly when CPU vendors start removing features from their newer CPUs! If your VMs are suspended, I would advise resuming the VMs on the old host (if possible) and shutting them down normally before copying it over. If your new host has a different CPU or GPU model, there is some risk in moving a suspended virtual machine (which is effectively 'still running') from one host to another. Regarding optimizing the VMs for the migration: The VM's file formats are all compatible across that range of versions.

We don't always get that compatibility 100% right, but we would generally expect that a Windows guest with a reasonably 'normal' configuration, migrating from Player 5 (from 2012) to the latest Workstation Player 15.5, should not encounter any specific issues. We aim to maintain VM compatibility across product versions to the highest degree possible.

Vmware workstation player 15 guide