New Windows 10 VM - will not connect to portal

[charliegil]

I work as a consultant at a company using GP (5.2.11-10).  I have numerous virtual machines (Windows 10, 7, and Xp) to support development, and they all will connect to the portal.  The customer has a well defined installation process (trivial):

1) go to this link to download the correct version (32 or 64bit) then install;

2) set the portal to xyz.  Value isn't relevant, it's all set to the same thing;

3) connect.  At this point, I'm prompted for my login, I go through two factor authentication;

4) connected.

I've done this many times.  Turning to my new Windows 11 Pro laptop, I am in the process of moving everything to virtual machines.  I want the main laptop to be as clean as possible.  Install VMWorkstation, create a Windows 10 machine, all updates.  Download GP client, install.  Issues:

1) I cannot change my user account unless I enable the client.  Seems counterintuitive, but okay.  For some reason, this installation has defaulted to my virtual machine login.  I need my customer's login, so I change it.

2) I refresh the connection it just spins.

3) I stop and restart GP, it has reverted to my local user. 

Okay, fine.  I top GP in the VM.  Go back to the base Windows 11 laptop, install GP.  Works as expected.  Yes, the network is operational in the vm.

Any ideas?
In fact, I'm typing this on my main development laptop.  I

[charliegil · Accepted solution]

I knew this would happen.  Company puts up LIVEcommunity as a teaser.  No support whatsoever.  VMware is just as bad.  Please, God, give me PulseSecure.