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
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
KB40318 - Impact / Changes between V3 and V4 OPSWAT SDK
KB40430 - How to switch an Active Directory authentication server instance from Legacy mode to Standard mode
Updated: Junos Pulse App Removed - TSB16705 - Notification on Removal/Unpublish of Junos Pulse Mobile Client for iOS 220.127.116.11589 and Android 18.104.22.168337 by the end of September 2015 from the respective App Stores
KB28810 - Java-based Pulse Secure components fail to run or launch on Safari
KB40126 - How to use the Pulse Secure Linux CLI client.
KB28876 - Pulse Secure Desktop running in FIPS mode on an endpoint running McAfee Application Control can cause a self-test failure
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.