Narrow Search

Product Series
Can't find what you need?
Contact Us
Reset Search
 

Search Results

You searched for: lock down mode

KB40363 - Behavior of "Lock Down this connection" (also known as Lock Down Mode)
Pulse Secure Article - October 28, 2016
This article provides details about the requirements and how lock down mode works with Pulse Secure Desktop 5.2R5 and above.
KB43665 - Lock down mode exception rules feature
Pulse Secure Article - March 1, 2018
This article provides details about the lock down mode exception rules.
KB40503 - Connectivity to any resource fails when Pulse Secure Desktop client is installed and Lock Down Mode is enabled.
Pulse Secure Article - March 26, 2017
This article describes an issue where connectivity to resources fail (for ex. Windows logon (Winlogon), and anti-virus (AV) updates) when Pulse Secure Desktop client is installed and Lock Down Mode is enabled.
KB43679 - Best practices and known third-party issues with Pulse Desktop client with lock down mode feature
Pulse Secure Article - March 12, 2018
This article provides information about best practices and known third-party issues with Pulse Desktop Client with lock down mode feature.
KB43811 - Pulse Secure Desktop client cannot launch a configured session start-up script when lock down mode is enabled.
Pulse Secure Article - July 2, 2018
This article describes an issue where Pulse Secure Desktop client does not launch the session start-up script when lock down mode is enabled.
KB43828 - After lock down mode is enabled, Windows end user will receive the message of "SCNotification.exe has stopped working"
Pulse Secure Article - July 17, 2018
This article describes an issue where SCNotification (part of SCCM) will prompt a message of "SCNotification.exe has stopped working" after lock down mode is enabled for the Pulse Secure Desktop client.
KB44631 - After upgrading to macOS 11.0 (Big Sur), end users may receive Error 1205 "Failed to setup virtual adaptor" when Traffic Enforcement or Lock Down Mode are configured
Pulse Secure Article - November 13, 2020
After upgrading to macOS 11.0 (Big Sur) and above, end users may receive Error 1205 "Failed to setup virtual adaptor" when Traffic Enforcement or Lock Down Mode are configured.
KB43948 - Unable to reach any resources bound to the local loopback address when lock down mode is enabled with Pulse Secure Desktop client for macOS
Pulse Secure Article - November 26, 2018
This article describes an issue where end user is unable to reach the local loopback address when lock down mode is enabled with Pulse Secure Desktop client for macOS, but this does work with Pulse Secure Desktop client for Windows.
KB44242 - Lock down mode exception rules for Windows endpoints does not work after upgrading to Pulse Connect Secure 9.0R2 - 9.0R4.1 or 9.1R1 - 9.1R2
Pulse Secure Article - August 13, 2019
This article describes an issue where lock down mode exception rules for Windows endpoints does not work after upgrading to Pulse Connect Secure (PCS) 9.0R2 - 9.0R4.1 or 9.1R1 - 9.1R2.
KB43826 - After a successful connection with Pulse Secure Desktop Client is made and a VPN tunnel is created, network connectivity is blocked due to lock down mode is not lifted
Pulse Secure Article - July 16, 2018
This article describes an issue where the Pulse Secure Desktop client is able to make a successful connection to the Pulse Connect Secure (PCS) device, but network connectivity is blocked due to lock down mode is not lifted.
KB43848 - When lock down mode is enabled, Printer Spooler service cannot start with the error message " Windows could not start the Printer Spooler service on Local Computer. Error 0x800706b9: Not enough resources are available to complete this operation
Pulse Secure Article - August 3, 2018
This article describes an issue where the Printer Spooler service cannot start when lock down mode is enabled with Pulse Secure Desktop client.
KB43961 - "Lock down this connection" option is automatically disabled after selecting Save Changes in Pulse Connect Secure 9.0R3
Pulse Secure Article - December 7, 2018
This article describes an issue where selecting the checkbox for "Lock down this connection" in the Pulse connection set is automatically disabled after saving changes in Pulse Connect Secure 9.0R3.
KB43830 - Lock down exception does not work for Pulse Secure Desktop 9.0R2 client with the message of "Skipping lockdown exception [Exception_Name] as this is not supported for client platform"
Pulse Secure Article - July 17, 2018
This article describes an issue where lock down exceptions are configured on Pulse Connect Secure (PCS) device, but lock down exceptions are not accepted by the Pulse Secure Desktop client 9.0R2 and above.
KB43981 - VPN Only Access with resolvable address (location awareness rule) with more than one connection will cause the lock down firewall to start after the VPN tunnel is created with Pulse Desktop Client 9.0R1 / 5.3R6 and below
Pulse Secure Article - December 20, 2018
This article describes an issue where Pulse Desktop Client 9.0R1 / 5.3R7 and below will fail to connect to any resources after the VPN tunnel is created when one or more connections is configured with a location awareness rule.
KB43661 - After enabling lockdown mode with Pulse Secure Desktop client with Ivanti Device and Application control client installed, Windows endpoint experience slow performance (i.e. slow application load times and lagged response from mouse cursor)
Pulse Secure Article - February 27, 2018
This article describes an issue where Windows endpoints experience slow performance (i.e slow application load times, lagged response from mouse cursor, etc) after lockdown mode is enabled with the Pulse Secure Desktop client and Ivanti (formerly called L...