SA40312 - September 22 2016 OpenSSL Security Advisory
KB21953 - Pulse Connect Secure (PCS) JumpStation
TSB43810 - EOL notification for Pulse Secure’s Network Connect (NC) client and Windows Secure Application Manager (WSAM) client software features
KB40602 - After disabling SMBv1, Pulse Connect Secure / Pulse Policy Secure device is unable to join the domain or end users are no longer able to authenticate
KB40627 - Compatibility issues between Cisco Media Services and Pulse Secure Desktop client on Windows 8.1/10
SA44114 - 2019-04: Out-of-Cycle Advisory: Pulse Desktop Client and Network Connect improper handling of session cookies (CVE-2019-11213)
KB40318 - Impact / Changes between V3 and V4 OPSWAT SDK
KB44113 - Pulse iOS client : Unable to connect with proxy PAC using Pulse Secure Mobile client for iOS 126.96.36.199829
KB43851 - Original DNS settings are not properly restored on the physical adapter after the tunnel is destroyed with Pulse Secure Desktop client
KB40126 - How to use the Pulse Secure Linux CLI client.
What would you like to know?
< Back to search results
KB40324 - How to migrate from Network Connect to Pulse desktop
Last Modified Date
10/14/2016 9:30 AM
This article provides access to the PDF version of the complete guide for migrating from Network Connect to Pulse desktop.
Problem or Goal
Click to download the
How to Migrate Network Connect to Pulse Desktop Client
guide in PDF format. The guide is also attached to this KB and can be downloaded by clicking on the PDF attached below.
NC to Pulse migration guide.pdf
Was this article helpful?
Please tell us how we can make this article more useful.