SA40312 - September 22 2016 OpenSSL Security Advisory
KB21953 - Pulse Connect Secure (PCS) JumpStation
KB40627 - Compatibility issues between Cisco Media Services and Pulse Secure Desktop client on Windows 8.1/10
KB25581 - Pulse Secure Desktop (Windows or macOS) client is intermittently disconnecting for multiple users at random intervals
KB40318 - Impact / Changes between V3 and V4 OPSWAT SDK
SA40168 - [Pulse Secure] March 1st 2016 OpenSSL Security Advisory
KB28732 - [PPS/MAG-PCS, Pulse Secure Desktop Client] Upgrading ESAP in an L2 authentication environment
KB21481 - How is the Network Connect / Pulse Secure Desktop adapter MTU (Maximum Transmission Unit) calculated?
KB9218 - What client side logs are required when I open a Network Connect (NC) or Pulse Secure Client VPN case?
KB9216 - What executable(s) must be allowed to run in order for Pulse Secure Desktop client or Network Connect client to launch/connect?
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.