Reset Search
 

 

Article

KB44540 - Workaround for Known Issues in Pulse Client 9.1R7.1 Release

« Go Back

Information

 
Last Modified Date7/20/2020 10:20 PM
Synopsis
This article describes the known issues in Pulse Client 9.1R7.1 and the suggested workarounds with targeted fix. 
Problem or Goal
Known Issues in Pulse Client 9.1R7.1 Release.
Cause
Solution
The following is a list of known issues in Pulse 9.1R7.1.  For any other issue, please open a support case.
 
PRS Number Issue / SymptomConditionWorkaroundTarget Fix
PRS-392383Pulse Client gets stuck at Host Checker when the endpoint has Pulse Secure Installer Service (PSIS) older than version 9.1R7.1 installed.Issue occurs when Host Checker with SAML authentication is configured and external browser is used for SAML authentication.Perform the actions when Pulse Client is launched in following ways:

•  Through a browser: Disable Host checker
•  SAML based Authentication: Use embedded browser or disable Host checker
•  Directly: No issue
•  If above workarounds cannot be implemented, use the new PSIS that is available separately.
Pulse 9.1R8 (Tentative for the week of July 20th)
PRS-389851Pulse Client UI reports “Pulse Secure service is not running”.Issue occurs when Pulse9.1R7 client is used with a PSIS older than version 9.1R7.1 and host checker is configured on the realm.Perform the actions when Pulse Client is launched in following ways:
•  Through a browser: Disable Host checker
•  SAML based Authentication: Use embedded browser or disable Host checker
•  Directly: No issue
•  If above workarounds cannot be implemented, use the new PSIS that is available separately.
Pulse 9.1R8 (Tentative for the week of July 20th)
Related Links
N/A
Attachment 1 
Created ByRaghu Kumar

Feedback

 

Was this article helpful?


   

Feedback

Please tell us how we can make this article more useful.

Characters Remaining: 255