Reset Search



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"

« Go Back


Last Modified Date7/17/2018 11:05 PM
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.
Problem or Goal
After upgrade to Pulse Secure Desktop client 9.0R2 and above, lock down exceptions are pushed from the Pulse Connect Secure device to the client, but lock down exception are not accepted by the client.  In the debuglog.log, the following message will appear for the rule name:
ConnectionManagerService.cpp:2274 - 'ConnectionManagerService' Lockdown exception: Exception_Name
ConnectionManagerService.cpp:2288 - 'ConnectionManagerService' Skipping lockdown exception [Exception_Name] 
as this is not supported for client platform
This issue occurs when one of the following conditions are met:
  1. Pulse Connect Secure device has not been upgrade to 9.0R2
  2. Lock down exception rule is configured for the incorrect platform 
To help root cause the issue, review the Pulse Connect Secure configuration.
  1. Login to the admin UI
  2. Navigate to Users > Pulse Secure Client
  3. From the list, select the applicable connection set
  4. Under Lockdown mode exception rules, review the platform column and ensure the proper platform is configured
User-added image

Note: The selection between Windows, Mac and Any is only available in Pulse Connect Secure 9.0R2. If the option is not pushed to the Pulse Secure Desktop client, then it will default to a Windows rule.
Related Links
Attachment 1 
Created ByK. Kitajima



Was this article helpful?



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

Characters Remaining: 255