1 person found this helpful
10.15 is now officially out and upgrades are starting.
Is there an ETA on a 64-bit naclient?
Unfortunately, it's against vendor policies to commit to any ETAs. But I would be expecting this issue to be resolved in future NSX-V releases.
Does anyone know if there is any work around available in order to connect to the Edge SSL VPN without using NAclient until that gets updated?
It's been about a month now since Catalina was released ... and VmWare had plenty of warning before... This is really pathetic, VmWare.... and they can't even make a guess when they'll fix it. I guess they don't see Mac clients as important to their business.
If I had the choice, I'd never use VmWare for anything again, but our data center uses their VPN with this proprietary client, and there is no other way to get in.
Most of our developers shut off Mac auto-upgrades before it was too late, but one now has to run Linux in a VirtualBox (not going to use VmWare for anything) guest machine, share his working directory to the guest OS, and run naclient inside the guest, in order to be able to push his work to our secure repo.
That is a very awkward workaround, and he had to fight with it over file permissions between the host OS and the guest OS in both directions.
We run a tenant vDC and most of the users are not really tech savy at all, so it's not possible to use a 3rd party client to VPN into the NSX?
Using virtual box and all that seems a little bit out of scope for this one user that was hasty enough to update his OS..