KB9216 - What executable(s) must be allowed to run in order for Pulse Desktop client or Network Connect client to install/launch/connect/upgrade?
KB44572 - How to increase the size of the Pulse Desktop client debug log on Windows operating systems
KB44792 - How to remove old client side components via Stand-Alone Pulse Desktop Client to resolve the Pulse Desktop Client Upgrade issue?
KB44815 - The limitation with the Length of EAP packets when connecting Pulse desktop Clients.
KB44037 - How to use jamcommand to Import connections to Pulse Desktop Client?
KB44898 - Basic Paths and troubleshooting in Mac OS respective to PSAL and Pulse Desktop Client features
SA44114 - 2019-04: Out-of-Cycle Advisory: Pulse Desktop Client and Network Connect improper handling of session cookies (CVE-2019-11213)
KB21481 - How is the Network Connect / Pulse Secure Desktop adapter MTU (Maximum Transmission Unit) calculated?
KB25230 - How to install the 32-bit Network Connect client on 64-bit Linux platforms
KB26755 - How to migrate configurations from an existing SA-x000 / SA-x500 to a new MAG device
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.