Pulse Desktop Client. Release Notes PDC 5.3R4 Build Release, Build Published Document Version. 5.3R4, 1161 December,

Transcription

1 3 Pulse Desktop Client Release Notes PDC 5.3R4 Build 1161 Release, Build Published Document Version 5.3R4, 1161 December,

2 Pulse Secure, LLC 2700 Zanker Road, Suite 200 San Jose, CA 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 By downloading, installing or using such software, you agree to the terms and conditions of that EULA by Pulse Secure, LLC. All rights reserved 2

3 Contents Introduction...4 Interoperability and Supported Platforms...4 General Notes...4 Caveats, Important Changes, and Deprecated Features...4 Upgrade Paths...4 New Features in 5.3R4 Release...5 Product Codes (GUIDs) for SCCM Deployments in 5.3R4 Release...5 Fixed Issues in 5.3R4 Release...6 Known Issues in 5.3R4 Release...6 New Features in 5.3R3 Release...8 Product Codes (GUIDs) for SCCM Deployments in 5.3R3 Release...8 Fixed Issues in 5.3R3 Release...9 Known Issues in 5.3R3 Release...9 New Features in 5.3R2 Release Fixed Issues in 5.3R2 Release Known Issues in 5.3R2 Release New Features in 5.3R1 Release Fixed Issues in Current 5.3R1.1 Release Fixed Issues in 5.3R1 Release Known Issues in 5.3R1 Release Documentation Documentation Feedback Technical Support Revision History by Pulse Secure, LLC. All rights reserved 3

4 Introduction This release-notes document for the Pulse Secure desktop client version 5.3R4. This document provides a cumulative list of all enhancements, fixes and known issues for the 5.3R4 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 Secure s 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 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.3R4 Pulse Secure desktop client Beta program, please un-install the Beta 5.3R4 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 a March 10, 2015 Windows 7 Update in order to be able to accept and verify SHA-2-signed binaries properly. This Windows 7 update is described here and here. If this update is not installed (in other words if a Windows 7 machine has not received an OS update since March 10, 2015), then Pulse 5.3R1 and later will have reduced functionality (see PRS , 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 5.3Rx 5.2Rx 5.0Rx or 5.1Rx You can upgrade directly to 5.3R4. You can upgrade directly to 5.3R4. You can upgrade directly to 5.2Rx simply by installing the 5.2Rx update by Pulse Secure, LLC. All rights reserved 4

5 New Features in 5.3R4 Release The following table describes the major features that are introduced in this release. Pulse Desktop Client Release Notes Feature Pulse Linux Client Usability Improvements Support for Mac OS IPv6 Tunneling Windows Server Qualification The Pulse Linux client will now remain connected if the UI is closed. When the UI is re-launched, updated statistics are presented. The Pulse Secure client will now support IPv6 Split Tunneling feature for Mac OS. 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. Product Codes (GUIDs) for SCCM Deployments in 5.3R4 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 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-F A-A336-0A58CA993B24} Spanish - {AA3B7D0F-DAB6-46EC-AC84-600A599BF9B6} French - {9A0759AD-894C-4B2A-824A-57EE0609E210} Italian - {F998994E A1-84E2-2DB8801FCECF} Japanese - {23E4401D FC-99BE-170AEE127BFF} Korean - {9A1A4A11-514B-49E7-B816-E4C96F7E5C92} Polish - {5633C3AC A94-BD AC49CD} Chinese (China) - {ACED2067-7F09-4B02-AF06-F4F0842B188A} PulseSecure.x64.msi English - {84AB589C-1F5A-48AB-9070-A } Chinese (Taiwan) - {CAB4A270-6E7A-4950-B258-BED7613D41D3} German - {83C7F92B E-9B70-C60D8A431FD9} Spanish - {959D9EF1-31AB-44A3-AC73-826E F} French - {BDBFDB79-E6E A66F-2DF7FBAAE58A} Italian - {23DD1AE3-CAB6-4A25-9B6C-07621A60F5B8} Japanese - {7E1C21D7-87E B C55FF682} Korean - {82855F3C-7FC DA-F6DE5606CAEC} Polish - {17690ABC E B053744} Chinese (China) - {C870BB1E-E6A3-47F0-9FD8-D8775A8879C0} 2017 by Pulse Secure, LLC. All rights reserved 5

6 Fixed Issues in 5.3R4 Release The following table lists issues that have been fixed and are resolved by upgrading to this release. PRS Release Note Login fails from Pulse when using a secondary auth server and the username is defined as <USER>. PRS Credential provider login fails with UPN if the authentication server is LDAP. PRS Pulse may fail to display the captive portal authentication page in specific scenarios. PRS Location awareness rules may not work as expected when network state changes quickly. PRS Client upgrade pop-up is not triggering if Always-on Pulse Client is enabled. PRS Pulse UI fails to start after forcefully being terminated on Linux. PRS Pulse for Linux may take an extended time to launch. PRS The connection status for Pulse may show an invalid state on Linux. PRS Pulse may fail to install from the web when using a self-signed certificate on macos clients. PRS dstermserv.exe may crash when launching an RDP session. Known Issues in 5.3R4 Release The following table lists known issues in 5.3R4 release. PRS PRS PRS PRS PRS PRS Host checker doesn't detect AVG antivirus on Windows Server Windows defender does not get detected when host checker is enabled on Windows Server PDC is not supporting IPv6 DNS server of SA if "device only" is selected in DNS search order with Split Tunneling. User needs to select other DNS searching order or IPv4 DNS server. From 5.3R4 release onwards, Pulse Secure Desktop client for Mac OSX is not supported for version 10.9 or below. User needs to upgrade Mac OSX to version or above. Pulse Application Launcher detects incorrect OS for Windows Server 2012 R2 and Windows Server by Pulse Secure, LLC. All rights reserved 6

7 PRS PRS PRS PRS PRS PRS PRS PRS PRS PRS Support for Windows Server 2012 is required in Endpoint Host checkers under OS check option. Displays error message WSCAPI.dll file is missing while downloading host checker.exe file on Windows Server 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. Displays wrong agent type in active users for Windows Server 2008, 2012 and 2016 when logged in through browser. Session Time Left does not get updated once PulseUI is relaunched. 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. Host Checker Compliance does not get updated after re-launching Linux Pulse Desktop Client. Connection status does not get displayed correctly upon manually terminating pulsesvc service, closing and re-launching Linux Pulse Desktop Client. Logging folder is missing in registry while installing Pulse Desktop Client on Windows 2016 server. During Machine authentication to CP transition, Pulse reports Error:1115. Enable the check box Use Desktop Credentials under the connection set. Connecting to Sign-In URL fails after PDC is upgraded from 5.3R3 to 5.3R4 without reboot. Re-start the machine after upgrade Or Terminate pulsesvc after upgrade 2017 by Pulse Secure, LLC. All rights reserved 7

8 New Features in 5.3R3 Release The following table describes the major features that are introduced in this release. Feature Support for Mac OS IPv6 ESP Pulse Linux Debian 9 support Pulse Linux 64bit binaries support Always on VPN exceptions Pulse Linux SAML Auth support 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. The Pulse Secure Linux client will now support Debian 9 operating system. The Pulse Secure Linux client will now support 64-bit package. The package consists of 64 bit binaries and libraries. 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. The Pulse Secure Linux client will now attempt to connect to Pulse Connect Secure by authenticating SAML servers. Product Codes (GUIDs) for SCCM Deployments in 5.3R3 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.3R3 of the desktop client for the given the architecture (32-bit or 64-bit) and locale (language environment). PulseSecure.x86.msi English - {B0CFE1C6-6A AFC7-62D9259D2EB5} Chinese (Taiwan) - {BA43A75F-B0A E0-E7FCFB6CF8B4} German - {509E9ADB B42C-2FE6ACA9EBBC} Spanish - { E-CD04-4B7D-B169-2FBB0C7C6602} French - {D98A6763-E980-48A9-BDCC-36B6AB4E8818} Italian - {563F2CC1-CED7-484D-87FB-B43CF83767C4} Japanese - {478B34A7-1E63-44AD-BC ED6751B3} Korean - {F8D79E BA4-81F5-904AD4B15F6D} Polish - {7164C2F4-CFE3-47CA BB30DE9EE23} Chinese (China) - {A4BB997A-B DEF-8E5D424D2658} PulseSecure.x64.msi English - {D5DE4E9C-D0E8-470B-8F5D-D4F8CA6DF85D} Chinese (Taiwan) - {3E A239-40DB D2B461AB12} German - {F49767B4-3A9A D-25EC88D6DCE9} Spanish - {EB B10-4D92-9E94-C3154DA8F9BF} French - {4FB8B D F-D833866F7E3D} Italian - {703F2140-6F10-4CEA-9BB B6D} Japanese - {7D0839B1-4CD0-473E-A872-7CB1EFBEE209} Korean - {F0CD2903-9E72-4C57-A91F-35187BF78122} Polish - {13FA4278-EE43-422E-BEF5-DE3EC5B6D87E}} 2017 by Pulse Secure, LLC. All rights reserved 8

9 Chinese (China) - {8D80EE78-371F-486D-8E80-CE0C2CA98F25} Fixed Issues in 5.3R3 Release The following table lists issues that have been fixed and are resolved by upgrading to this release. PRS PRS PRS PRS PRS PRS PRS PRS Unable to access last IP address in Split Tunnel range with Windows clients. 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. Pulse Client 5.3R1 end user help doesn t have the localization for Pulse5.3R1 features. Active Users page does not capture the Mac OS version for Pulse connections. Pulse Client localization is not working for Windows8, Windows8.1 and Windows10. When layer 3 VPN is formed with Pulse Client, inaccurate statistics is sent to accounting server. Connection set xml import failing from 8.1Rx to.8.3r3. Proxy prompt with Pulse Secure client 5.2R8 when credential provider is configured. PRS Users are unable to reconnect if Pulse client connection doesn t succeed in several attempts within 5 minutes. PRS PRS PRS PRS PRS PRS PRS PRS PRS PRS PRS PRS First connection fails with error 1373 after upgrade to or reinstall of Pulse 5.2R8. Pulse Secure client will not alert users that an invalid PIN is entered in the New PIN prompt. Smartcard using Microsoft CSP are caching PIN. Corrupted characters are displayed in the Pulse Secure Desktop client UI. Windows Pulse - Unable to access last IP address in Split Tunnel range with Windows clients. Docker software's virtual adapter is getting identified as physical, breaking wireless suppression. Pulse Client disables wireless adapters and not re-enabling the adapter while wired connection is disconnected. Pulse 5.2R5 stuck at connecting and does not get the pre-sign-in notifications. Radius Auth passes even without username. NETLOGON failing if Pulse client is installed on Windows 10 devices. Pre-sign-in notification message does not get displayed when number of characters exceed 2883 characters. Pulse Linux runs cent OS commands on Ubuntu. Known Issues in 5.3R3 Release The following table lists known issues in 5.3R3 release by Pulse Secure, LLC. All rights reserved 9

10 PRS PRS PRS PRS PRS PRS PRS PRS PRS Unable to ping through the tunnels created by Pulse Secure Linux Client when installed on default installation of Ubuntu with Kernel version Upgrading the kernel to WSAM destination configured traffic does not go through WSAM tunnel, when accessed via Edge Browser. Access the resources via other browser e.g. Chrome or IE. Client upgrade pop-up is not triggering if existing client is installed through MSI and Always-on VPN is enabled on the PCS8.3R3. Uninstall the existing client and reinstall the new client. Prefer Smart Card option is not working when the client machine has user as well as smart card certificate. User needs to select the smart card certificate to establish the session. Pulse Secure Linux Client can be configured to authenticate to a SAML server. However, enabling Host Checker feature on SAML connections is not supported. Disable the Host Checker. 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. 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. Pulse Secure Linux Client not supported on Cent OS 6.4. Upgrade to latest Cent OS 6.X version. Pulse SAM is failing to tunnel the traffic, if absolute path or MD5 checksum added. Remove the absolute path or MD5 checksum. Displaying OK button as grayed out in the absence of PSAL on Windows 10 with Chrome browser. Click the Download button by Pulse Secure, LLC. All rights reserved 10

11 New Features in 5.3R2 Release The following table describes the major features that are introduced in this release. Feature Certificate Selection Mechanism - Phase 2 Proxy ordering for Pulse Client Support SHA2 in ESP mode The 5.2R5 Pulse Secure desktop client introduced two new features to improve the enduser 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 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. The Pulse Desktop Client for Mac, Windows, and Linux now supports ESP transport using the SHA256 HMAC algorithm. Fixed Issues in 5.3R2 Release The following table lists issues that have been fixed and are resolved by upgrading to this release. PRS PRS PRS PRS PRS Release Note 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). 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. Users may be able to add connections to the Pulse client incorrectly if the lockdown switch is enabled with the always-on VPN switch. Pulse after upgrade stuck in 'Connect requested - manual override' if connection-set configured after the upgrade is different from the one configured before upgrade. The Pulse client version number is not displayed in the about/info box on Linux. PRS It has been reported that the Pulse Secure Linux user fails after 1 or 3 rekeys. PRS Pulse Linux client packages are not downloadable from system->installers page. PRS PRS PRS PRS PRS PRS Older clients are not falling back to SSL when ESP transport mode Encryption type is set to AES256/SHA256. 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. Wireless suppression may not trigger as expected during reboot scenarios and the wired connection status changes. The Pulse client for Mac OS may interpret MTU settings incorrectly if path MTU discovery is interrupted. 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. The Pulse client does not honor proxy settings on initial connection, causing a delay in connection by Pulse Secure, LLC. All rights reserved 11

12 PRS Release Note Certificate authentication using Pulse Secure Command-line Launcher will not work. PRS Wireless suppression is not disabled after the wired connection is removed. PRS The Pulse client help files localization data is missing. PRS 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. PRS PRS PRS PRS PRS Windows Pulse - Unable to access last IP address in Split Tunnel range with Windows clients. 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.. 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. 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. Pulse WSAM fails to connect when Credential Guard is enabled on a Windows 10 Redstone 2 client. WSAM tunnel not establish in windows 10 with credential guard by Pulse Secure, LLC. All rights reserved 12

13 New Features in 5.3R1 Release The following table describes the major features that are introduced in this release. Feature Minimum client Version Enforcement IPv6 support for 802.1x authentication - Windows and MAC VPN only Access (Windows) IPv6 Spilt Tunneling for Windows Pulse Linux Support for Debian Systems 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. 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 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. 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. 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 Current 5.3R1.1 Release The following table lists issues that have been fixed and are resolved by upgrading to this release. PRS PRS PRS Release Note Unable to load captive portal properly when captive portal page uses any technology above IE7. Lock/unlock mode switching doesn't happen in some scenarios. Captive portal redirection is not working with Canada Starbucks by Pulse Secure, LLC. All rights reserved 13

14 Fixed Issues in 5.3R1 Release The following table lists issues that have been fixed and are resolved by upgrading to this release. Release Note PRS PRS PRS PRS PRS Always on VPN doesn't work on 32 bit machines. Pulse Linux: OpenSSL Security Advisory. Location awareness rules are not taken into consideration when "VPN only access" is turned on. VPNOnlyAccess doesn't kick in the firewall after reboot when the connection is not marked as automatic. OpenSSL Security Advisory. PRS Error while installing Pulse desktop client in Linux Debian 8. PRS PRS Rebranding required for "ConfigureInstaller" file of Pulse Secure Desktop Client-5.2R3. 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. PRS PRS PRS PRS PRS PRS PRS Pulse client 5.3R1 End user help doesn t have the Localization for Pulse5.3R1 Features. Certificate Authentication is failing on MacOS when "Always Trust" option is enabled on the client machine. 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. Active Users page does not capture the Mac OS version for Pulse connections. Sometimes Disconnect is taking more time on MacOS. Restart Pulse service. Pulse client is not going for auto connect after signing out from the browser when AlwyasOn-VPN is enabled. User can connect back using browser. Pre-sign-in notification message not being displayed when number of characters exceed 2883 characters by Pulse Secure, LLC. All rights reserved 14

15 With OPSWAT V4 SDK when remediation action is going for turn on RTP, in Pulse UI displaying Update in Progress. PRS PRS PRS PRS PRS PRS PRS PRS Inconsistency may observe when using certificate authentication on cent OS 6.4. The setup client alert message which display during the minimum client enforcement is not localized.. Pulse client Localization is not working for Windows8, windows8.1 and Windows10. Minimum client enforcement feature is not supported for Pulse5.1Rx and older clients. 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 Upgrading Pulse from 5.2R5 (or prior) to 5.2R6 on Linux shows "downgrading". Pulse Desktop Client installation via browser failing for few Win7 Professional machines. Direct MSI installer instead of browser for pulse desktop client. 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 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.2R by Pulse Secure, LLC. All rights reserved 15

16 Modify description for Lock down this connection to "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." Documentation Pulse documentation is available at Documentation Feedback We encourage you to provide feedback, comments, and suggestions so that we can improve the documentation. You can send your comments to Technical Support When you need additional information or assistance, you can contact Pulse Secure Global Support Center (PSGSC): Call us at (toll-free USA) For more technical support resources, browse the support (website Revision History The following table lists the revision history for this document. Table 6 Revision History Revision Date 5.0 December, R4 Update 4.1 October, R3 Update 4.0 October, R3 Update 3.0 June, R2 Update 2.0 May, R1.1 Update 1.0 March, 2017 Initial Publication 5.3R by Pulse Secure, LLC. All rights reserved 16