To resolve this issue, please upgrade to the following Pulse Desktop Client releases:
- Pulse Desktop Client 9.1R1
- Pulse Desktop Client 9.0R5 (Tentative week of 17th September 2019)
The latest Pulse Desktop Client will accept either platform attribute (of win or windows) without having to make any changes to Pulse Connect Secure configuration.
Workaround:
If upgrading the Pulse Desktop Client is not possible, create new lock down mode exception rules for Windows Platform. When new lock down mode exception rules are added to the Connection Set, the platform parameter will be
win, not
windows.
{
direction: "outbound"
local-ip-addresses: "*"
local-ports: ""
name: "TestLockdownPolicy-new"
platform: "win"
program: ""
program-hash: ""
protocol: "TCP"
remote-ip-addresses: "*"
remote-ports: "4334"
}
Note: A reboot of the end user machine will be required after applying the workaround to download the new connection set.