very bad situation. We opened a ticket. The root cause is also the expired code signing certificate (April 12th 2021).
We asked if it will also impact the Pulse Secure Client L3 connections, perhaps tomorrow morning, but the answear was not really clear.
Same situation in the latest Version 9.1R11.1, the same certificate is used there.
Yes, I can also confirm that the HTML5 connections work and also via RDP or Terminal!
Is the HTML5 "standard" (aka using Guacamol server) running ?
Because on my side, Guacamol has never been functionnal.
Using advanced mode is running fine, but requires some extra licenses.
Until the fix is published you can change the date on the computer to 8th of April(not sure when the certificate expired). RDP client will work (tested).
Until the fix is published, you can change the date on the computer to 8th of April(not sure when the certificate expired). RDP client will work (tested).
Timeline for releases were added:
The following are the release timelines for the fixes,
Anyone think this is going to be a HotFix on the appliance side or is this going to require client side updates?
I have had zero success in finding a way to upgrade the software remotely when a user is not a local admin and with 500+ people this is going to be a nightmare.
It's a server-side upgrade. Upgrading the PCS to 9.1R11.x will push the fixed version of client binaries out to the user machines automatically when they connect to VPN post upgrade.
To allow non-admin users to upgrade or install the clients you can just push the Pulse Secure service on the computers (by GPO, PDQ Deploy, ...)