Hello. Thanks for posting. Unfortunately I don’t have a resolution, but can related to your problem. I’m confused and a bit frustrated to say the least. At any rate, I have been trying to work through two issues, which the second issue overlaps a bit with your efforts:
- Restoring browser-based logins
- Restoring working upgrade prompt via PDC (Pulse Desktop Client) logins
With regard to your experience, I think whatever Pulse Client version has the radio/option button selected when navigating to Users > Pulse Secure Client > Components is the current active one. I wish it was a little more evident on the UI. But, I have the same experience as you, when I have an older version of PDC on a Windows endpoint and login to the 9.1R11.5 PCS device, I do get prompted for the upgrade, but then NOTHING after I click “Upgrade”. I was sure hoping that the upgrade prompt was going to be resolved in 9.1R11.5, but that does not appear to be the case.
For your 9.1R11.4 issues... I see in in the release notes for 9.1R11.4 there is a known issue - (PRS-400668):
Symptom: Pulse Desktop Client (PDC) always displays upgrade prompt even when client version on the endpoint and the server are same. Clicking on upgrade prompt performs no action (Cosmetic/UI issue).
Condition: Occurs when the Pulse Desktop Client has Symantec signed binaries and the PCS on which it is hosted (9.1R11.3/ 9.1R10.2/ 9.1R9.2/ 9.1R8.4) is signed by Digicert.
Workaround: Disable End-point upgrade on Pulse Connect Secure (PCS). Enable again only when a higher version of PDC is activated on PCS and let the users trigger the client upgrade through the browser.
For my situation, I am testing PCS 9.1R11.5. And I will add though that I have Pulse Client package 9.1R10 as my active client package (my company’s current standard), so my testing has been trying to get the upgrade prompt to upgrade my 9.1R7 client to 9.1R10 in my testing. But I don’t think the client version matters; as you indicate I think it’s a bug or two with 9.1R4 and 9.1R5.
I think your steps are correct though. If you are wanting to run PCS 9.1R5 and for clients to have PDC 9.11R5, then yea, upgrade the appliance, activate the new PDC, and ensure the “Enable web installation and automatic upgrade of Pulse Secure clients" option is checked. Historically that has worked, but seems to be bug(s) with the latest versions.
I probably didn’t state anything in here you didn’t already know, but know you are aren’t the only one having issues. I’ll likely be opening a support case and see what the best path forward is.
