I'm not entirely clear what you meant by "isolated non network environment" . . . how I interpreted this, is that you have no network connected to the machine [VMware Workstation Host], and therefore, the users on the 'legacy systems' will not have access to the network !

If you wish to make sure that users cannot physically connect the machine to the network, then would suggest, blocking up the RJ45 connector; remove any network interfaces (Ethernet/Wi-Fi); disable the Hosts Operating System network Adapters; remove VMware's Virtual network externally facing interfaces.

As far as I aware VMware Workstation is not designed around multi-users access, and as such some services may require the appropriate level of permissions for the currently logged on user to function correctly.  Therefore, you would have to experiment . . . with quite a bit of trial and many errors, and you're on your own.

It's not entirely clear what your requirements are, or the Host Operating System . . . but you might consider looking into Microsoft's Kiosk-mode, I've used it for other applications, but have absolutely no idea if this works with VMware Workstation.

Hi,

This feature existed, but was removed in VMware Workstation 16.0

It's still in the documentation though...

https://docs.vmware.com/en/VMware-Workstation-Pro/16.0/com.vmware.ws.using.doc/GUID-8A64D0EF-CB0E-4C...

--
Wil

| Author of Vimalin. The virtual machine Backup app for VMware Fusion, VMware Workstation and Player |
| More info at vimalin.com | Twitter @wilva

I was hoping that I could have the host machine on the network, but ensure that the guest legacy machines was never connected to the network.

Any idea if this could be achieved by using the Player instead of the workstation?

I discovered this as well, but in 16 it only allows me to set a password for powering the guest up.
I was hoping could use this feature...

Any idea why this has veen removed?

@HeiniGut wrote: I was hoping that I could have the host machine on the network, but ensure that the guest legacy machines was never connected to the network.

In that case you may have a couple of options, one related to VMware Workstation/Player, and, or the other to the 'legacy guest' itself [operating system unknown] . . . 

VMware: In the legacy guests Virtual Machine Setting - Hardware tab, Remove the 'Network Adapter'

Legacy Guest: from within the legacy guests operating system, disable the network interface/s, and restrict access to it.

Hi,

There's currently no way to limit that kind of thing with VMware Workstation (Pro or Player).

You'll have to ask VMware on why they remove features. They don't always tell us why they do something

The only solution I see is to use another product. If you want to stay with VMware then look into vSphere and perhaps VMware Horizon. But of course those are completely different products and it means running VM's on a remote server, not locally.

--
Wil

| Author of Vimalin. The virtual machine Backup app for VMware Fusion, VMware Workstation and Player |
| More info at vimalin.com | Twitter @wilva

I have tried setting NTFS rights on the vmx file, but I cant open a guest unless the user has full access to the file, and then VMware resets the security settings back to Authenticated users Full Control

Do you have any suggestions for another product that can do this?

Is anyone from VMware monitoring this forum, who can explain why they have removed the restrict funtion?

---

@HeiniGut wrote: Do you have any suggestions for another product that can do this?

---

Suggest that you refer @wila comment above "If you want to stay with VMware then look into vSphere and perhaps VMware Horizon"