Running a Guest from two Windows 10 User IDs.

[gbohn]

Hi;

I'm running Workstation 15.1 on a Windows 10 Host. I normally start a Guest locally (using the Workstation UI) and interact with it full-screen.

I would like to be able to start a Guest from one User-id, then Switch to another local Windows User (disconnecting from the original users Windows account and login as a different user) and be able to use/control the still running Guest from this other second user-id.

Both User IDs have access to the Guest virtual machines files (vmdk, vmx, etc.).

I tried this (including ending the launching Workstation UI while leaving the VM running from the first user-id), and the Guest VM doesn't show up in the User interface for Workstation on the second users Windows session.

I tried starting the Workstation UI program (in the first users Windows session) with the credentials of the second user and starting the Guest that way. But when switching over to the second user and launching the Workstation UI things still don't work.

I can (one at a time) start and control the Guest from either ID alone (only accessing it from the ID that started it).

Is there a way to control/use an instance of  a running guest from either ID?

Thanks;

[RDPetruska · Accepted solution]

You need to have the VM configured as a Shared VM in order to keep it running as a service, so both users can access it.

[gbohn]

Thanks, I tried this and was able to make it work.

It's too bad that this comes with a bunch of baggage... As best as I can tell you lose various capabilities

That is, access to local shared folders, copy and paste functionality, encrypted VMs, etc.

And you apparently have to put the files for all shared guest systems as folders under one directory. (So, limiting if you have several drives and large Guests).

(I've never user Shared VM's before, so maybe I'm just missing something).

[RDPetruska]

Yes, there are limitations on shared VMs.

Your other option is to not have the VM stay running between users, and have each user re-launch the VM when they log in.