![]() ![]() I think this is all consistent with your recommendations, but If you see a hole in this thought process please let me know. Vmware fusion 8.5 purchase upgrade#Then I should able to upgrade windows to Win 10 and complete the migration with no gaps in compatibility along the way. Once I have 11.5 woking I can migrate to Mojave and everything will remain compatible. Vmware fusion 8.5 purchase install#11.5 is compatible with the two operating systems I now use (High Sierra and Windows 7) so I should be able to install it and operate with the current configurations on my computer. Therefore the logical choice which takes a bigger step up than I was considering in my original question, but which I believe you are recommending in your latest response, is to go all the way to Fusion 11.5 as the first step in my migration. They are also compatible with Windows 10圆4. If you want to keep using VMware Fusion 8.5 you will probably need to purchase a second license. The question is whether VMware Support can still issue licence keys for versions that far back. Producer is fully the gaming groove your experience, allowing material for crafting very first Moog mixer, audio editor, to hit tunes from HDTV, camcorder. This makes their recommendation to me to buy 11.5 and downgrade the license to 10.x a non-starter for the upgrade of my OS.įurther, when I went to the interactive VM Ware compatibility guide (/resources/compatibility), I found that each of the Fusions 10.x, 11.1.x and 11.5 are said to be compatible with Windows 7圆4 which is what I have now. VMware Fusion licence keys are tied to the major version number, so you would need a different licence key to use an older major version of VMware Fusion. Buy VMware Fusion 8.5 - Cheapest price - 49.95 The shovelware and crapware that Parallels pushes on you, even via advertisements with the application that you paid for. Fusion 11.1.1 and 11.5 are compatible with Mojave, but 10.x is not. KB 208571 says what you say: Fusion 10.x through 11.5 are all compatible with High Sierra (10.13.6 is what I have). 'As informed, this issue with latest version of VMware Tools 10.1.5 has already been reported to the concerned team' Here are the steps for fixing the current issue with VMware Tools 10.1.5 and Fusion 8.5. ![]() Since I was getting confusing answers from the sales people at VMWare, I went to two VM references. PS: Of course you can also use my backup product ( ) for making the VM backup, but the steps above will work fine. If anything goes wrong you at least have a backup that you can fall back on. make a copy of that virtual machine to an external disk shut down VMware Fusion - not strictly required, but recommended as it makes it very certain no files are left open The correct way to make a backup of your VM is to: Even VMware suggest you to exclude VMs from backing up via Time Machine (see VMware Knowledge Base or for more details see ) Please do not trust Time Machine with your VM backups as it isn't reliable for that kind of backup. However I would add one more step: Make a backup of your VM before you start any of the upgrades. Your suggested upgrade path is the one I would suggest and is afaict the best order. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |