Related Articles

KB45104 - How to Deep Clean Pulse Desktop Client in Windows and MAC OS

SA44114 - 2019-04: Out-of-Cycle Advisory: Pulse Desktop Client and Network Connect improper handling of session cookies (CVE-2019-11213)

KB25230 - How to install the 32-bit Network Connect client on 64-bit Linux platforms

KB44792 - How to remove old client side components via Stand-Alone Pulse Desktop Client to resolve the Pulse Desktop Client Upgrade issue?

KB44037 - How to Use Jamcommand to Import Connections to Pulse Desktop Client/Ivanti Secure Access Client

KB21481 - How is the Network Connect / Pulse Secure Desktop adapter MTU (Maximum Transmission Unit) calculated?

KB25451 - Network Connect error message: 'The Network Connect session timed out. (nc.windows.apps.23790)'

KB40157 - "Failed to connect to (PCS_URL) error 110" with Pulse Desktop Client (Linux)

KB44815 - The limitation with the Length of EAP packets when connecting Pulse desktop Clients.

KB40514 - How to configure certificate authentication with Pulse Desktop Client for Linux

< Back to search results

Article

KB40324 - How to migrate from Network Connect to Pulse desktop

« Go Back

Information

Last Modified Date	10/14/2016 9:30 AM

Synopsis

This article provides access to the PDF version of the complete guide for migrating from Network Connect to Pulse desktop.

Problem or Goal

Cause

Solution

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.

Related Links

Attachment 1	NC to Pulse migration guide.pdf

Created By	Karen Mayberry