Windows 10: Shared VMs are back (temporarily) in VMware Workstation 6.1.0

In the new release of VMware workstation Pro (16.1.0) , the previously removed feature "Shared VMs" is back. I guess that it wasn't just me that was bent about that feature being removed.

VMware states that the feature is deprecated but it will remain through the lifetime of the version 16.x release.

Ironically, I've moved a bunch of VMs over to Hyper-V because of that very feature missing.

:)

 

Wow - VMware has killed off Shared VMs in VMware Workstation 16

One of the great features in VMware workstation was the ability to create Shared VMs. There were several good things about these VMs, only one of which was that they could start automatically without having to log onto the host system.

In VMware Workstation 16 that feature was simply abruptly removed with nothing but a one line sentence in the release notes stating that this feature has reached end of life.

This must have been some sort of knee jerk reaction because they didn't even remove all references to the feature in their version 16 User Guide and a clean install of VMware Workstation still installs the VMware Workstation Server service used for Shared VMs.

I guess that I may be going back to Hyper-V!

 

VmWare Workstation 12.5.9: how to share folders between VMs?

Sorry but
- not true for Mint
- not true for Mac
- not true for Win7.
It can be true for some old NAS devices however see 1st post:
"I need to run a CMD command in a VM that would need the access of Windows folder from another VM."









Completely hijacked thread.. sigh
Apologies to butterfly.

 

VmWare Workstation 12.5.9: how to share folders between VMs?

omg, are my sins really so big?

See the pictures below.
10.20.30.69 - notebook, vmware host
10.20.30.72 - virtual machine at bridged segment at notebook, acts as smb server
10.20.30.64 - miditower, vmware host
192.168.183.133 - virtual machine at nat segment at miditower, acts as smb client
Established smb connection from 192.168.183.133 to 10.20.30.72 through two vmware hosts. Absolutely no problem at all.

No, apologies. Not obliged to give networking trivia lessons.

In the case the problem lies in hostname-to-ipaddress translation, you can use either ip addresses in net use command (optionally with dhcp reservations for servers) or dynamic name service. Beyond the scope of our discussion.

Enough.