Pulse Desktop Client · any subsequent Pulse desktop client releases. Important note: In order to run the Pulse Secure desktop client version 5.3R1 or later on a Windows 7 machine,

3

Pulse Desktop Client Release Notes

PDC 5.3R7, Build 1933

PDC (Linux) 5.3R7, Build 919

Release, Build

Published

Document Version

5.3R7, 1933

December 2018

7.2

© 2018 by Pulse Secure, LLC. All rights reserved 2


Pulse Secure, LLC

2700 Zanker Road, Suite 200

San Jose, CA 95134

https://www.pulsesecure.net

© 2018 by Pulse Secure, LLC. All rights reserved.

Pulse Secure and the Pulse Secure logo are trademarks of Pulse Secure, LLC in the United States. All other

trademarks, service marks, registered trademarks, or registered service marks are the property of their respective

owners.

Pulse Secure, LLC assumes no responsibility for any inaccuracies in this document. Pulse Secure, LLC reserves the

right to change, modify, transfer, or otherwise revise this publication without notice.

The information in this document is current as of the date on the title page.

END USER LICENSE AGREEMENT

The Pulse Secure product that is the subject of this technical documentation consists of (or is intended for use with)

Pulse Secure software. Use of such software is subject to the terms and conditions of the End User License

Agreement (“EULA”) posted at https://www.pulsesecure.net/support/eula. By downloading, installing or using such

software, you agree to the terms and conditions of that EULA.

https://www.pulsesecure.net/

https://www.pulsesecure.net/support/eula



Contents

Introduction .............................................................................................................................................................. 5

Interoperability and Supported Platforms ........................................................................................................ 5

General Notes .......................................................................................................................................................... 5

Caveats, Important Changes, and Deprecated Features ............................................................................... 5

Upgrade Paths ......................................................................................................................................................... 5

Product Codes (GUIDs) for SCCM Deployments in 5.3R7 Release .............................................................. 6

New Features in 5.3R7 Release ............................................................................................................................ 6

Fixed Issues in 5.3R7 Release ............................................................................................................................... 7



Known Issues in 5.3R6 Release ............................................................................................................................ 8



Known Issues in 5.3R5 Release ......................................................................................................................... 10

Noteworthy Changes in 5.3R4.2 ....................................................................................................................... 10

Product Codes (GUIDs) for SCCM Deployments in 5.3R4.1 Release ........................................................ 10

Fixed Issues in 5.3R4.1 Release ........................................................................................................................ 11

New Features in 5.3R4 Release ......................................................................................................................... 11

Product Codes (GUIDs) for SCCM Deployments in 5.3R4 Release ........................................................... 12

Fixed Issues in 5.3R4 Release ............................................................................................................................ 12



Product Codes (GUIDs) for SCCM Deployments in 5.3R3 Release ........................................................... 15







Fixed Issues in 5.3R1.1 Release ........................................................................................................................ 20



Documentation ..................................................................................................................................................... 24

Documentation Feedback ................................................................................................................................... 24

Technical Support ................................................................................................................................................. 24

Revision History ..................................................................................................................................................... 24





Introduction This release-notes document for the Pulse Secure desktop client version 5.3R7. This document provides a

cumulative list of all enhancements, fixes and known issues for the 5.3R7 client. If the information in the release

notes differs from the information found in the documentation set, follow the release notes.

The Pulse Secure desktop client provides a secure and authenticated connection from an endpoint device (either

Windows or Mac OS) to a Pulse Secure gateway (either Pulse Connect Secure or Pulse Policy Secure). For a

complete description of the capabilities of this desktop client, please see the online help within the desktop client

itself, or the Pulse Desktop Client Administration Guide (which can be found at Pulse Secures Technical Publications

site).

Interoperability and Supported Platforms Please refer to the Pulse Desktop Client Supported Platforms Guide for supported versions of operating systems,

browsers, and servers in this release.

General Notes Security-related issues are not normally covered in Pulse Secure release notes. To find more information security

advisories affecting Pulse Secure products, please refer to the Pulse Secure security advisory page.

Caveats, Important Changes, and Deprecated Features Please note that client upgrades are not supported to or from beta releases. As such, if you participated in the

5.3R7 Pulse Secure desktop client beta program, please uninstall the beta 5.3R7 client before attempting to install

any subsequent Pulse desktop client releases.

Important note: In order to run the Pulse Secure desktop client version 5.3R1 or later on a Windows 7 machine, the

machine must contain the March 10, 2015 Windows 7 Update in order to be able to accept and verify SHA2-signed

binaries properly. This Windows 7 update is described here. If this update is not installed, then Pulse 5.3R1 and later

will have reduced functionality (see PRS-337311, below). (As a general rule, Pulse Secure, LLC recommends that

client machines be kept current with the latest OS updates to maximize security and stability.)

Upgrade Paths The following table describes the tested upgrade paths.

Release Description

5.3Rx You can upgrade directly to 5.3R7

5.2Rx You can upgrade directly to 5.3R7

5.0Rx or 5.1Rx You can upgrade directly to 5.2Rx simply by installing the 5.2Rx update.

https://support.microsoft.com/en-us/kb/3033929



Product Codes (GUIDs) for SCCM Deployments in 5.3R7

Release Product Codes (GUIDs) for SCCM Deployments in 5.3R7 Release If you deploy the Pulse Secure desktop client using

System Center Configuration Manager (SCCM, formerly SMS), it can be helpful to know the Product Codes (GUIDs) of

Pulse Secure desktop client installation bundles. SCCM uses these codes to determine whether products are already

installed. The table below gives the product codes for version 5.3R7 of the desktop client for the given the

architecture (32-bit or 64-bit) and locale (language environment).

PulseSecure.x86.msi

• English - {75412CBD-74DC-4EDF-B5A9-FE5D5FE91F58}

• Chinese (Taiwan) - {FE7F6FD8-DF38-49AC-A6BD-C9A0BB90A47E}

• German - {2826246A-F54D-4677-91F2-42B15C265D2D}

• Spanish - {38BC32D2-8607-4140-989B-ADCAC71B8119}

• French - {7242221B-9782-44E8-BF3D-211D41D51958}

• Italian - {7606439C-8B80-4FAC-9DCB-E04B288E26F4}

• Japanese - {BC341E45-1E60-44B2-95C5-9F9F097FDF51}

• Korean - {CFA791C3-65B4-431E-A00A-A128BE293DEA}

• Polish - {9832DA66-E63E-47F0-B278-E8215FD049B4}

• Chinese (China) - {F123DC5B-541D-48CE-89CC-79FC812FDE0B}

PulseSecure.x64.msi

• English - {56E99116-391C-41D1-90C3-DB863006FB37}

• Chinese (Taiwan) - {4A7DF6A1-8B29-4A63-8ACE-05CBE6C5B928}

• German - {DB8B3A8B-76B5-41D2-8054-D94F8E386B62}

• Spanish - {03F5A7AE-A800-44E9-A159-9B253ECDA22A}

• French - {3E67D8BF-02BC-4615-848B-BF1257113F9C}

• Italian - {D89E246E-C91B-4D3C-AB73-94AB7C85BECA}

• Japanese - {0D0CBE9B-CD5A-4EFB-BE22-5204F021AA6C}

• Korean - {63C8B4B6-87FA-415A-B6D8-F4AD55B95600}

• Polish - {BC2E61A9-316D-4A8B-9E5E-0D63105D86FF}

• Chinese (China) - {F0ADB856-8101-487C-9D02-1995B789E35F}

New Features in 5.3R7 Release The following table describes the major features that are introduced in this release.

Feature Description

64-bit binary for macOS

clients

The macOS client of Pulse desktop client is now a 64-bit binary, following the advice of Apple.

Please see KB43768 (https://kb.pulsesecure.net/articles/Pulse_Secure_Article/KB43768) for more

information.

https://en.wikipedia.org/wiki/System_Center_Configuration_Manager

https://kb.pulsesecure.net/articles/Pulse_Secure_Article/KB43768



Fixed Issues in 5.3R7 Release The following table lists issues that have been fixed and are resolved by upgrading to this release.

Problem Report

Number Release Note

PRS-368112 The Wi-Fi selector is not available on Windows 10.

PRS-365294 Pulse Desktop Client with lockdown enabled causes SC Notification error when SCCM

client is reboot.

PRS-365277 Location awareness with more than one connection will cause lockdown firewall to start

after VPN tunnel is created

PRS-364732 Pulse Desktop Client fails to authenticate with timeout error with Smart card

authentication after connecting to SAML IDP.

PRS-359099 Pulse Connect Secure administrator failed to modify the default Pulse UI fields for the

Pulse Secure desktop client on Mac.

PRS-363917 Lock-down mode is being invoked as soon as the tunnel is disconnected.

PRS-368828 Pulse desktop client is not a 64-bit binary. Starting with 5.3R7, this is rectified.







PulseSecure.x86.msi

• English - {9F7F010D-3137-4496-970F-D77A61CE8E92}

• Chinese (Taiwan) - {0A5C6955-DBF0-45B1-86AA-764796E1E242}

• German - {4364E854-A123-477C-A449-BE449234C38F}

• Spanish - {8257F724-857C-485B-AB59-8153C6474F44}

• French - {C536CD19-6DCE-4213-9490-AAF803D28D1A}

• Italian - {676D27AE-7A80-4CDD-A59F-984DDE9167FA}

• Japanese - {A1B8DD60-6205-423E-B382-2F08C8A056CD}

• Korean - {973E6C6D-FD55-4F86-A4D4-5B4219BC52E4}

• Polish - {3E79280F-0496-4349-883A-0551BD0C1760}

• Chinese (China) - {661366E6-BA87-455D-A0FF-6B8BF4824749}

PulseSecure.x64.msi

• English - {20ECE8AB-3378-4A41-83C8-5DA3037F6135}

• Chinese (Taiwan) - {96A73EF7-9190-491A-9192-C9BC51A9E7F8}

• German - {A4601489-F449-4BE7-86DB-7F1F734FBDD3}

• Spanish - {07D14C14-E045-4B5E-8BFD-12A49F9718A2}

• French - {7F354847-C4AB-4CB5-A816-4A11B4556EA2}

• Italian - {566C5056-4D5C-41E7-AAB1-54DEAA333467}




• Japanese - {86666C25-D29A-4E1C-9720-0706A1826ACD}

• Korean - {301053C8-E7E0-4DA2-B714-27950F2FF6DA}

• Polish - {23F1E38D-4D11-46E6-8296-3B4D85EBB011}

• Chinese (China) - {1DA0C832-FAD9-4EF0-A787-E0E6C2D4A820}

Fixed Issues in 5.3R6 Release The following table lists issues that have been fixed and are resolved by upgrading to 5.3R6 release.

Problem Report

Number Release Note

PRS-359407 DNS settings are not getting removed from physical adapter when switched from LAN to

Wi-Fi.

PRS-359720 Pulse Secure client fails to install on a Windows client with Cisco AnyConnect is installed

PRS-360082 The Pulse Linux client may fail to set the MTU to 1400 (instead setting it to 1500, which

prevents data transport)

PRS-360810 Domain login fails when lockdown mode is enabled in Pulse Secure client.

PRS-362066 Pulse Secure client fails to install correctly when Cisco AnyConnect is present on 32-bit

Windows-based systems

PRS-357647 Startup script launch fails when lockdown is enabled on the Pulse Secure client

configuration.

PRS-362394 The DNS client service may fail when Pulse and CrowdStrike are installed on the same

client system

Known Issues in 5.3R6 Release The following table lists known issues in 5.3R6 release.

Problem Report

Number Description

PRS-358500

Symptom:

Traffic enforcement enabled for IPv4 and IPv6 does not work as expected (existing

connections are not disconnected) on macOS clients when split tunneling is disabled and

route enforcement has tunnel priority

Work Around:

None









PulseSecure.x86.msi

• English - {557686F0-9C00-456F-AED6-41ABF3DE1A0D}

• Chinese (Taiwan) - {5097458C-7123-4CC6-A922-E9D30ABA7C68}

• German - {A7ECCB9A-7C33-48A1-8B41-99241981C694}

• Spanish - {63B3A6EF-E06B-4EFE-B31F-03B050395A8A}

• French - {B1173DAC-89DB-42B2-BF3A-E76623C5C7D4}

• Italian - {6941EE03-BCD5-49A5-A8E6-506393701B5C}

• Japanese - {9D738495-1190-4A4B-A84C-87DA06F4B9DA}

• Korean - {56E241BC-EC02-4B28-91BC-A1580D6CFD8F}

• Polish - {49992ED7-8182-451E-8D1E-C046BF1F11C4}

• Chinese (China) - {414423AF-C621-464C-83B5-DAD29A5506BE}

PulseSecure.x64.msi

• English - {35A74498-5DA0-4DBC-A91F-C89BEA8090AF}

• Chinese (Taiwan) - {807CAE61-8B55-4C2A-9325-E6A6A8B21311}

• German - {310965FE-CD7D-4938-B514-B10B38FC5C2A}

• Spanish - {8E8581D9-F436-4730-A81C-19DFE9C76B01}

• French - {037FBB49-928E-4BEF-AE0D-6845C4930EC5}

• Italian - {57C5E233-2737-4AE6-9E32-89F6659045A4}

• Japanese - {C0C20283-E5F6-4394-A47C-69B9044AE825}

• Korean - {567D6927-B924-4BE3-A0A2-87A912C6F558}

• Polish - {FEF7D1F8-0ED9-484F-8F43-59074FFC6332}

• Chinese (China) - {6CD7E733-17DE-4D39-8001-C7B87E75D0A4}


Problem Report

Number Release Note

PRS-360377 If lockdown is enabled for a Pulse connection with dual authentication enabled AND the user

cancels the secondary authentication prompt, lockdown is disabled and placed in "Manual

override".

PRS-360116 Pulse may fail to upgrade from legacy Juniper branded versions OR fail to upgrade if a Juniper

branded version was installed previously and removed outside the add/remove programs

interface.

PRS-359667 Secondary authentication may fail if the username is defined as <USERNAME> due to a greyed out

"Connect" button.

PRS-359563 L2 connections may fail while attempting to connect to a proxy server where proxy server is not

configured.




Problem Report

Number Release Note

PRS-357156 The exit (退出) text for Pulse on the Windows system tray is incorrectly rendered as EDIT (编辑)

when using Simplified Chinese.

PRS-354316 When a user needs to change the password and the password change fails due to not complying

with password policy, the message is truncated to one word on Japanese language.

PRS-353990 Junos Pulse is recorded in events logs even when using a Pulse Secure-branded client.

PRS-352103 Wireless suppression fails to operate correctly with Docker virtual adapters.

PRS-361800 User accounts may be locked earlier than expected when using credential provider-based login

with Pulse.

PRS-355666 Username and password are the default login option for credential provider. Starting with this

release, Pulse will prompt for the last used authentication type.


Problem Report

Number Description

PRS-361314

Symptom:

Pulse splash screen displays incorrect copyright details.

Work Around:

None

Noteworthy Changes in 5.3R4.2 This release is pertaining to only Pulse Linux Client installer package, this release does not contain any Windows or

Mac installers. Please refer to this KB for more information on this release.

Product Codes (GUIDs) for SCCM Deployments in 5.3R4.1

Release If you deploy the Pulse Secure desktop client using System Center Configuration Manager (SCCM, formerly SMS), it

can be helpful to know the Product Codes (GUIDs) of Pulse Secure desktop client installation bundles. SCCM uses

these codes to determine whether products are already installed. The table below gives the product codes for

version 5.3R4.1 of the desktop client for the given the architecture (32-bit or 64-bit) and locale (language

environment).

PulseSecure.x86.msi

• English - {E936D7F2-D9B3-494E-8433-67A2A496ACF0}

• Chinese (Taiwan) - {50D5B6B2-397A-4263-86D0-B544563DF437}

• German - {19D01EF1-495B-4408-BE2D-2623663E3E78}

• Spanish - {E35A4AD9-C8DE-4497-860D-FD4D8701676B}

http://kb.pulsesecure.net/articles/Pulse_Security_Advisories/SA43620




• French - {FDF388E0-F73E-46EB-BF85-1E32E778B8B4}

• Italian - {B18A7C8B-83D6-466C-B670-94694366EE36}

• Japanese - {0E108D40-D961-43FD-83C3-33FE1E30D22D}

• Korean - {38EC7596-3F7E-4A53-AADA-60436472DC77}

• Polish - {39C6C1E1-2044-42AC-90F9-69BA80120A05}

• Chinese (China) - {5D70528D-C693-412F-91E6-D7C962EE18A4}

PulseSecure.x64.msi

• English - {BCA8F252-3DA1-4578-B5A0-FC75197FAF0B}

• Chinese (Taiwan) - {4DE549CA-7E07-4CAD-819D-8DB94C382592}

• German - {EFAD87D6-0C07-405D-A99D-D41496D54A45}

• Spanish - {75A7426D-CCC9-4F4B-BA32-6473E7296A5F}

• French - {756B5940-48F6-42B8-827D-8A269ED1C8A1}

• Italian - {719E5A4B-380B-436C-849D-A4CA86EBBDA4}

• Japanese - {17BCA951-EEA2-4088-B05B-06EDF1D4FFAB}

• Korean - {B35E97C6-E56D-4B34-A8EF-0194ED77AEEE}

• Polish - {92F5605D-1748-4968-BE89-665EE52F048B}

• Chinese (China) - {AF627E88-3993-4302-8202-9DE795F1D343}

Fixed Issues in 5.3R4.1 Release The following table lists issues that have been fixed and are resolved by upgrading to 5.3R4.1 release.

Problem

Report

Number

Release Note

PRS-359258 After installing January 3, 2018 Microsoft Patches, Pulse client connections fail when Host Checker is

applied. For more information refer KB43600

New Features in 5.3R4 Release The following table describes the major features that are introduced in 5.3R4 release.

Feature Description

Pulse Linux Client Usability

Improvements

The Pulse Linux client will now remain connected if the UI is closed. When the UI is re-launched,

updated statistics are presented.

Support for Mac OS

IPv6 Tunneling The Pulse Secure client will now support IPv6 Split Tunneling feature for Mac OS.

Windows Server Qualification The Pulse Secure client will now support for Windows Servers.

Note: From 5.3R4 release onwards, Pulse Secure Desktop client for Mac OSX is not supported for version

10.9 and below.

http://kb.pulsesecure.net/articles/Pulse_Secure_Article/KB43600







version 5.3R4 of the desktop client for the given the architecture (32-bit or 64-bit) and locale (language

environment).

PulseSecure.x86.msi

• English - {D712EFCD-ADB6-4DE9-937C-DA9A67BF1CC6}

• Chinese (Taiwan) - {125F39E0-39F3-4DAE-A19C-A3B25D8A53BA}

• German - {AF09449C-F838-419A-A336-0A58CA993B24}

• Spanish - {AA3B7D0F-DAB6-46EC-AC84-600A599BF9B6}

• French - {9A0759AD-894C-4B2A-824A-57EE0609E210}

• Italian - {F998994E-5652-47A1-84E2-2DB8801FCECF}

• Japanese - {23E4401D-0104-49FC-99BE-170AEE127BFF}

• Korean - {9A1A4A11-514B-49E7-B816-E4C96F7E5C92}

• Polish - {5633C3AC-8050-4A94-BD66-835252AC49CD}

• Chinese (China) - {ACED2067-7F09-4B02-AF06-F4F0842B188A}

PulseSecure.x64.msi

• English - {84AB589C-1F5A-48AB-9070-A09833457177}

• Chinese (Taiwan) - {CAB4A270-6E7A-4950-B258-BED7613D41D3}

• German - {83C7F92B-0124-419E-9B70-C60D8A431FD9}

• Spanish - {959D9EF1-31AB-44A3-AC73-826E0829893F}

• French - {BDBFDB79-E6E6-4476-A66F-2DF7FBAAE58A}

• Italian - {23DD1AE3-CAB6-4A25-9B6C-07621A60F5B8}

• Japanese - {7E1C21D7-87E2-4791-B623-2530C55FF682}

• Korean - {82855F3C-7FC9-4418-98DA-F6DE5606CAEC}

• Polish - {17690ABC-0021-4855-83E9-22922B053744}

• Chinese (China) - {C870BB1E-E6A3-47F0-9FD8-D8775A8879C0}


Problem Report

Number Release Note

PRS-357492 Login fails from Pulse when using a secondary auth server and the username is defined as

<USER>.

PRS-357368 Credential provider login fails with UPN if the authentication server is LDAP.

PRS-357338 Pulse may fail to display the captive portal authentication page in specific scenarios.

PRS-355525 Location awareness rules may not work as expected when network state changes quickly.

PRS-354193 Client upgrade pop-up is not triggering if Always-on Pulse Client is enabled.

PRS-358159 Pulse UI fails to start after forcefully being terminated on Linux.




Problem Report

Number Release Note

PRS-357972 Pulse for Linux may take an extended time to launch.

PRS-357964 The connection status for Pulse may show an invalid state on Linux.

PRS-357286 Pulse may fail to install from the web when using a self-signed certificate on macOS clients.

PRS-357887 dsTermServ.exe may crash when launching an RDP session.


Problem Report

Number Description

PRS-358397

Symptom:

Host checker doesn't detect AVG antivirus on Windows Server 2016.

Work Around:

None

PRS-358395

Symptom:

Windows defender does not get detected when host checker is enabled on Windows

Server 2016.

Work Around:

None

PRS-357472

Symptom:

PDC is not supporting IPv6 DNS server of SA if "device only" is selected in DNS search

order with Split Tunneling.

Work Around:

User needs to select other DNS searching order or IPv4 DNS server.

PRS-358153

Symptom:

From 5.3R4 release onwards, Pulse Secure Desktop client for Mac OSX is not supported

for version 10.9 or below.

Work Around:

User needs to upgrade Mac OSX to 10.10 version or above.

PRS-356847

Symptom:

Pulse Application Launcher detects incorrect OS for Windows Server 2012 R2 and

Windows Server 2016.

Work Around:

None

PRS-357941

Symptom:

Support for Windows Server 2012 is required in Endpoint Host checkers under OS check

option.

Work Around:

None

PRS-357735

Symptom:

Displays error message ‘WSCAPI.dll file is missing’ while downloading host checker.exe file

on Windows Server 2012.

Work Around:

None

PRS-356967

Symptom:

Agent type is displayed as Windows Pulse Secure instead of Windows Server 2012 R2,

2016, once tunnel has been established in PCS active users page.

Work Around:

None

PRS-356794

Symptom:

Displays wrong agent type in active users for Windows Server 2008, 2012 and 2016 when

logged in through browser.



Problem Report

Number Description

Work Around:

None

PRS-357966

Symptom:

Session Time Left does not get updated once PulseUI is relaunched.

Work Around:

None

PRS-358002

Symptom:

Session Idle Timeout and Max. Session Length warnings do not get displayed during an

active session if Pulse Linux Desktop Client is in closed state.

Work Around:

None

PRS-358519

Symptom:

Host Checker Compliance does not get updated after re-launching Linux Pulse Desktop Client. Work Around:

None

PRS-358045

Symptom:

Connection status does not get displayed correctly upon manually terminating pulsesvc service,

closing and re-launching Linux Pulse Desktop Client.

Work Around:

None

PRS-358640

Symptom:

Logging folder is missing in registry while installing Pulse Desktop Client on Windows 2016

server.

Work Around:

None

PRS-358115

Symptom:

During Machine authentication to CP transition, Pulse reports Error:1115.

Work Around:

Enable the check box “Use Desktop Credentials” under the connection set.

PRS-358699

Symptom:

Connecting to Sign-In URL fails after PDC is upgraded from 5.3R3 to 5.3R4 without reboot.

Work Around:

• Re-start the machine after upgrade

Or

• Terminate pulsesvc after upgrade


Feature Description

Support for Mac OS IPv6

ESP

The Pulse Secure Mac OS will now support IPv6 tunnel between Pulse Connect Secure

(PCS) and Pulse Secure Desktop Client (PDC) in ESP (Encapsulating Security Payload)

mode.

Pulse Linux Debian 9

support The Pulse Secure Linux client will now support Debian 9 operating system.

Pulse Linux 64bit binaries

support

The Pulse Secure Linux client will now support 64-bit package. The package consists of 64

bit binaries and libraries.

Always on VPN exceptions

The Pulse client will now allow admin user to configure exception rules for which traffic

needs to be exempted if user has applied Lock-Down mode.

Note: This feature is for Windows users only.



Feature Description

Pulse Linux SAML Auth

support

The Pulse Secure Linux client will now attempt to connect to Pulse Connect Secure by

authenticating SAML servers.





version 5.3R3 of the desktop client for the given the architecture (32-bit or 64-bit) and locale (language

environment).

PulseSecure.x86.msi

• English - {B0CFE1C6-6A54-4165-AFC7-62D9259D2EB5}

• Chinese (Taiwan) - {BA43A75F-B0A4-4612-91E0-E7FCFB6CF8B4}

• German - {509E9ADB-3106-4202-B42C-2FE6ACA9EBBC}

• Spanish - {9905079E-CD04-4B7D-B169-2FBB0C7C6602}

• French - {D98A6763-E980-48A9-BDCC-36B6AB4E8818}

• Italian - {563F2CC1-CED7-484D-87FB-B43CF83767C4}

• Japanese - {478B34A7-1E63-44AD-BC55-9070ED6751B3}

• Korean - {F8D79E28-9279-4BA4-81F5-904AD4B15F6D}

• Polish - {7164C2F4-CFE3-47CA-8508-9BB30DE9EE23}

• Chinese (China) - {A4BB997A-B252-4523-8DEF-8E5D424D2658}

PulseSecure.x64.msi

• English - {D5DE4E9C-D0E8-470B-8F5D-D4F8CA6DF85D}

• Chinese (Taiwan) - {3E320436-A239-40DB-8697-82D2B461AB12}

• German - {F49767B4-3A9A-4212-846D-25EC88D6DCE9}

• Spanish - {EB963665-9B10-4D92-9E94-C3154DA8F9BF}

• French - {4FB8B159-373D-4056-870F-D833866F7E3D}

• Italian - {703F2140-6F10-4CEA-9BB4-739344899B6D}

• Japanese - {7D0839B1-4CD0-473E-A872-7CB1EFBEE209}

• Korean - {F0CD2903-9E72-4C57-A91F-35187BF78122}

• Polish - {13FA4278-EE43-422E-BEF5-DE3EC5B6D87E}}

• Chinese (China) - {8D80EE78-371F-486D-8E80-CE0C2CA98F25}





Problem Report

Number Description

PRS-352308 Unable to access last IP address in Split Tunnel range with Windows clients.

PRS-353395 If user does not remember the issued smart card or if the issued smart card is not working. Use

alternative user certificate (client authentication) issued to login.

In current scenario, even though it is issued, it is not listed or it does not allow user to connect, if there

is any “smart card log on eku” cert is there in personal store. Hence user is blocked.

PRS-350819 Pulse Client 5.3R1 end user help doesn’t have the localization for Pulse5.3R1 features.

PRS-348889 Active Users page does not capture the Mac OS version for Pulse connections.

PRS-348782 Pulse Client localization is not working for Windows8, Windows8.1 and Windows10.

PRS-350525 When layer 3 VPN is formed with Pulse Client, inaccurate statistics is sent to accounting server.

PRS-351019 Connection set xml import failing from 8.1Rx to .8.3R3.

PRS-355601 Proxy prompt with Pulse Secure client 5.2R8 when credential provider is configured.

PRS-354262 Users are unable to reconnect if Pulse client connection doesn’t succeed in several attempts within 5

minutes.

PRS-354016 First connection fails with error 1373 after upgrade to or reinstall of Pulse 5.2R8.

PRS-353451 Pulse Secure client will not alert users that an invalid PIN is entered in the New PIN prompt.

PRS-338029 Smartcard using Microsoft CSP are caching PIN.

PRS-352472 Corrupted characters are displayed in the Pulse Secure Desktop client UI.

PRS-350978 Windows Pulse - Unable to access last IP address in Split Tunnel range with Windows clients.

PRS-352103 Docker software's virtual adapter is getting identified as physical, breaking wireless suppression.

PRS-351793 Pulse Client disables wireless adapters and not re-enabling the adapter while wired connection is

disconnected.

PRS-351063 Pulse 5.2R5 stuck at connecting and does not get the pre-sign-in notifications.

PRS-350824 Radius Auth passes even without username.

PRS-350048 NETLOGON failing if Pulse client is installed on Windows 10 devices.

PRS-347649 Pre-sign-in notification message does not get displayed when number of characters exceed

2883 characters.

PRS-349498 Pulse Linux runs cent OS commands on Ubuntu.




Problem Report

Number Description

PRS-355466

Symptom:

Unable to ping through the tunnels created by Pulse Secure Linux Client when installed on default

installation of Ubuntu 15.04 with Kernel version 3.19.0-15.

Work Around:

Upgrading the kernel to 3.19.0-84.

PRS-339882

Symptom:

WSAM destination configured traffic does not go through WSAM tunnel, when accessed

via Edge Browser.

Work Around:

Access the resources via other browser e.g. Chrome or IE.

PRS-354193

Symptom:

Client upgrade pop-up is not triggering if existing client is installed through MSI and

Always-on VPN is enabled on the PCS8.3R3.

Work Around:

Uninstall the existing client and reinstall the new client.

PRS-356219

Symptom:

Prefer Smart Card option is not working when the client machine has user as well as smart

card certificate.

Work Around:

User needs to select the smart card certificate to establish the session.

PRS-355316

Symptom:

Pulse Secure Linux Client can be configured to authenticate to a SAML server. However, enabling

Host Checker feature on SAML connections is not supported.

Work Around:

Disable the Host Checker.

PRS-355909

Symptom:

When older clients try to connect to a PCS device which is configured with Encryption type

as ESP SHA2 and ESP Transport only as enabled on a server, client fails to establish the

session.

Work Around:

Disable the ESP Transport only option till all the clients upgraded to latest Pulse client

build. Re-enable the option, once all the clients are upgraded.

PRS-355560

Symptom:

Pulse Secure Linux Client not supported on Cent OS 6.4.

Work Around:

Upgrade to latest Cent OS 6.X version.

PRS-355721

Symptom:

Pulse SAM is failing to tunnel the traffic, if absolute path or MD5 checksum added.

Work Around:

Remove the absolute path or MD5 checksum.

PRS-356770

Symptom:

Displaying OK button as grayed out in the absence of PSAL on Windows 10 with Chrome

browser.

Work Around:

Click the Download button.




Feature Description

Certificate

Selection

Mechanism -

Phase 2

The 5.2R5 Pulse Secure desktop client introduced two new features to improve the end-

user experience during certificate authentication. There was no administrative-console

option to enable this feature back in 5.2R5. In 5.3R2, a new PCS console option has been

introduced for the PCS admin to configure this feature.

• Improved automatic certificate-selection algorithm

• Ability to prefer smart-card certificates over other certificates

Proxy ordering for

Pulse Client

The Pulse client will now attempt to connect through the system proxy and then fallback

to direct connection rather than attempt a direct connection and fallback to check for

proxy configuration detail.

Support SHA2 in

ESP mode The Pulse Desktop Client for Mac, Windows, and Linux now supports ESP transport using the

SHA256 HMAC algorithm.


Problem Report

Number Release Note

PRS-353586

The Pulse Desktop Client for Mac may fail to disconnect completely if an invalid URL is configured

(requiring stopping and starting the service to recover access).

PRS-353082

If a manual connection is created in the Pulse client after importing a config file and then the user

connects on the manual connection to a gateway that pushes down a lockdown configuration, the

Pulse client stays in “Connect Requested” state.

PRS-353064

Users may be able to add connections to the Pulse client incorrectly if the lockdown switch is enabled

with the always-on VPN switch.

PRS-352901

Pulse after upgrade stuck in 'Connect requested - manual override' if connection-set configured after

the upgrade is different from the one configured before upgrade.

PRS-349934

The Pulse client version number is not displayed in the about/info box on Linux.

PRS-350871

It has been reported that the Pulse Secure Linux user fails after 1 or 3 rekeys.

PRS-352239

Pulse Linux client packages are not downloadable from system->installers page.

PRS-347455

Older clients are not falling back to SSL when ESP transport mode Encryption type is set to

AES256/SHA256.

PRS-351297

The Pulse client for Linux displays erroneous “Security policies not met” if multiple Host Checker

policies or rules are configured and the user meets some while failing others.

PRS-351457

Wireless suppression may not trigger as expected during reboot scenarios and the wired connection

status changes.

PRS-349571 The Pulse client for Mac OS may interpret MTU settings incorrectly if path MTU discovery is

interrupted.

PRS-349661 Certificate authentication may fail if the client certificate does not have the EKU field configured AND

the connection store has not been updated to use either AUTO or LEGACY certificate selection

algorithms.

PRS-351212

The Pulse client does not honor proxy settings on initial connection, causing a delay in connection.



Problem Report

Number Release Note

PRS-351102

Certificate authentication using Pulse Secure Command-line Launcher will not work.

PRS-347066

Wireless suppression is not disabled after the wired connection is removed.

PRS-350819

The Pulse client help files localization data is missing.

PRS-347923

The Pulse client logs incorrectly identifies Windows 10 clients as Windows 8.

Known Issues in 5.3R2 Release The following table lists Known issues in 5.3R2 release.

Problem Report

Number Description

PRS-352308

Symptom:

Windows Pulse - Unable to access last IP address in Split Tunnel range with Windows

clients.

Work Around:

None

PRS-353330

Symptom:

If the connection set is replaced during session establishment, the user may see error 1135 “Remote

access already provided by another connection”. Issue is observed in corner cases were pulse takes

more time to disconnect.

Work Around:

None.

PRS-353395

Symptom:

If user forgot the issued smart card / it’s not working there should be alternative user certificate

(client authentication) issued which can be used for login, but in current scenario even though it is

issued it is not listed /not allow user to connect in scenario if there is any “smart card log on eku”

cert is there in personal store hence user is blocked.

Work Around:

Check the cert mmc snapin, mmc->add snap-> certificates -> check personal->certificates

delete manually all certs having intended purpose ("smart card logon set), deleting these do not

cause any issues as whenever any required smartcard is plugged in the one belong to them will be

enumerated automatically and now since there is "no smart card log on" cert, client authentication

cert will be higher rank and allowed to connect if present single it uses it silently if > 1 it prompts for

choose.

PRS-353063

Symptom:

Pulse WSAM fails to connect when Credential Guard is enabled on a Windows 10 Redstone 2 client.

Work Around:

None

PRS-

353158

Symptom:

WSAM tunnel not establish in windows 10 with credential guard.

Work Around:

None




Feature Description

Minimum client

Version

Enforcement

It allows to easily force end users to upgrade their clients to some specified minimum

version. If a client that is older than a certain version is used to connect to the Pulse

Connect Secure gateway, the end user is prompted to upgrade their client, rejecting which

the connectivity is denied.

IPv6 support for

802.1x

authentication -

Windows and MAC

This feature is to enable Pulse Desktop client to authenticate Pulse Policy Secure with

802.1x L2 connection over both IPV4 and IPV6 on both Wired and Wireless networks.

VPN only Access

(Windows)

VPN only access is an extension to our existing ‘Always ON’ VPN and adds flexibility to the

function, by letting users be in control of when they want to access the VPN. When a user

is not connected to the VPN, all network access is blocked. When a user needs to access

something on the network, they must sign into the VPN, and in successfully doing so, get

the network access allowed by IT.

IPv6 Spilt

Tunneling for

Windows

Pulse VPN now allows accessing both IPv4 and IPv6 corporate resources from IPv4 and

IPv6 endpoints. It enables client to access both corporate network and local network at

the same time. The network traffic designated are directed to tunnel interface for

corporate network by configuring route policies, whereas other traffics are sent to direct

interface.

Pulse Linux

Support for

Debian Systems

In spirit of providing broad platform support for our customers, we have now added

Debian Linux as a validated platform, to an existing list if supported Linux platforms.

Windows 10

Redstone support Complete support for Windows 10 Redstone.

Certificate

authentication in

Pulse Linux It allows secure and seamless user experience when setting up VPN tunnel.

Fixed Issues in 5.3R1.1 Release The following table lists issues that have been fixed and are resolved by upgrading to this release.

Problem Report

Number Release Note

PRS-

352314

Unable to load captive portal properly when captive portal page uses any technology above

IE7.

PRS-

351760 Lock/unlock mode switching doesn't happen in some scenarios.

PRS-

352098 Captive portal redirection is not working with Canada Starbucks.




Problem Report

Number Release Note

PRS- 350488 Always on VPN doesn't work on 32-bit machines.

PRS- 350394 Pulse Linux: OpenSSL Security Advisory.

PRS- 350070 Location awareness rules are not taken into consideration when "VPN only access" is

turned on.

PRS- 350356 VPNOnlyAccess doesn't kick in the firewall after reboot when the connection is not

marked as automatic.

PRS- 349481 OpenSSL Security Advisory.

PRS- 349585 Error while installing Pulse desktop client in Linux Debian 8.

PRS- 344703 Rebranding required for "ConfigureInstaller" file of Pulse Secure Desktop Client-5.2R3.

PRS- 347982 Branding Tools contains incorrect data in PulseResource_JA.txt for label.

Known Issues in 5.3R1 Release The following table lists Known issues in 5.3R1 release.

Problem Report

Number Description

PRS-350819

Symptom:

Pulse client 5.3R1 End user help doesn’t have the Localization for Pulse5.3R1 Features.

Work Around:

None

PRS-350486

Symptom:

Certificate Authentication is failing on MacOS when "Always Trust" option is enabled on

the client machine.

Work Around:

Select “Use System Defaults” instead of “Always Trust” option on endpoint which is the

default option. Navigate to Keychain Access->Login->select the certificate->right click-

>get info and choose “Use System Defaults “on endpoint.

PRS-348889

Symptom:

Active Users page does not capture the Mac OS version for Pulse connections.

Work Around:

None

PRS-350643

Symptom:

Sometimes Disconnect is taking more time on MacOS.

Work Around:

Restart Pulse service.

PRS-349190

Symptom:

Pulse client is not going for auto connect after signing out from the browser when

AlwyasOn-VPN is enabled.

Work Around:

User can connect back using browser.

PRS-347649

Symptom:

Pre-sign-in notification message not being displayed when number of characters

exceed 2883 characters.

Work Around:

None

PRS-344718 Symptom:

With OPSWAT V4 SDK when remediation action is going for turn on RTP, in Pulse UI



Problem Report

Number Description

displaying Update in Progress.

Work Around:

None

PRS-343837

Symptom:

Inconsistency may observe when using certificate authentication on cent OS 6.4.

Work Around:

None

PRS-350759

Symptom:

The setup client alert message which display during the minimum client enforcement is

not localized.

Work Around:

None.

PRS-348782

Symptom:

Pulse client Localization is not working for Windows8, windows8.1 and Windows10.

Work Around:

None

PRS-350759

Symptom:

Minimum client enforcement feature is not supported for Pulse5.1Rx and older clients.

Work Around:

None

PRS- 350525

Symptom:

Inaccurate statistics sent to accounting server when layer 3 VPN is formed with Pulse

client.

Condition:

Accounting bytes updated in LMDB cache is not correct, there by showing wrong accounting bytes

Work Around:

None

PRS- 347284

Symptom:

Upgrading Pulse from 5.2R5 (or prior) to 5.2R6 on Linux shows "downgrading".

Work Around:

None

PRS- 351198

Symptom:

Pulse Desktop Client installation via browser failing for few Win7 Professional machines.

Work Around:

Direct MSI installer instead of browser for pulse desktop client.

PRS-351019

Symptom:

Connection set xml import failing from 8.1Rx to .8.3R1.

Condition:

• Import from 8.1R10 or 8.1R11 to 8.3R1

• Import from 8.2R5 to 8.3R1, import fails if 8.3R1 has a new connection with

the same connection name as in 8.2R5

Work Around:

• Import binary or add below option tag with mentioned content in xml file

under each connection and import it to 8.3R1.

<option>

<name>Lock down this connection</name>

<description>Network access is limited until this connection is established.

This option is available only when the Always-on Pulse Client option or VPN

only access option on the connection set is checked</description>

<tag>connection-lock-down</tag>

<bool-type>

<value>false</value>

</bool-type>

</option>

• Import from 8.2R5 to 8.3R1, import fails if 8.3R1 has a new connection with

the same connection name as in 8.2R5.

Modify description for Lock down this connection to "Network access is

limited until this connection is established. This option is available only when



Problem Report

Number Description

the Always-on Pulse Client option or VPN only access option on the

connection set is checked."



Documentation Pulse documentation is available at https://www.pulsesecure.net/techpubs/.

Documentation Feedback We encourage you to provide feedback, comments, and suggestions so that we can improve the documentation.

You can send your comments to [email protected].

Technical Support When you need additional information or assistance, you can contact “Pulse Secure Global Support Center (PSGSC):

• https://www.pulsesecure.net/support

• [email protected]

Call us at 1- 844-751-7629 (toll-free USA)

For more technical support resources, browse the support (website https://www.pulsesecure.net/support).

Revision History The following table lists the revision history for this document.

Table Revision History

Revision Date Description

7.2 December 2018

PRS-368112 added in “Fixed Issues

in 5.3R7 Release” section.

PRS-359407 is added in “Fixed Issues

in 5.3R6 Release” section as carried

over information from 5.3R6 Pulse

Secure Desktop Client Release

Notes.

7.1 November 2018 5.3R7 Update

7.0 July 2018 5.3R6 Update

6.1 May, 2018 5.3R5 Update

6.0 April, 2018 5.3R5 Update

5.2 January, 2018 5.3R4 Update



5.0 December, 2017 5.3R4 Update

4.1 October, 2017 5.3R3 Update

4.0 October, 2017 5.3R3 Update

3.0 June, 2017 5.3R2 Update

2.0 May, 2017 5.3R1.1 Update

1.0 March, 2017 Initial Publication – 5.3R1

http://www.pulsesecure.net/techpubs/

mailto:[email protected]

https://www.pulsesecure.net/support

mailto:[email protected]

https://www.pulsesecure.net/support

Documents

Pulse Desktop Client · any subsequent Pulse desktop client releases. Important note: In order to run the Pulse Secure desktop client version 5.3R1 or later on a Windows 7 machine,