Pulse Secure Desktop Client 5.0R3 (and higher) for windows contains an updated version of Windows Network driver.Updated NDIS Driver:
Pulse Secure Desktop Client for Windows includes a set of drivers that interface with the Windows Network Driver Interface Specification (NDIS) driver for communications with the endpoint’s network interface. Pulse Secure Desktop Client 5.0R2 and below included Network Driver Interface Specification (NDIS) 5 Intermediate (IM) Filter Driver called the (JNPRNA).
For Pulse Secure Desktop Client 5.0R3 and above, the NDIS5 compliant (JNPRNA) has been replaced with the NDIS6 compliant (JNPRNS) to support enhanced functionality that is available in Windows Vista and later Windows versions. JNPRNA will continue to be available on Windows XP endpoints. Pulse on all other Windows versions will use JNPRNS.
While no new features have been added as a direct result of upgrading the driver we expect better interoperability with newer Windows OS versions like Windows 8.0 and 8.1.
Pulse Secure Desktop Client 5.0R3 and above Deployment considerations:
You can deploy the Pulse Secure Desktop Client to endpoints from PCS using a Web Install or Out of Band Installation using MSI Installer or using your local organization’s standard software distribution method (such as Microsoft SMS/SCCM).. For details, please refer to PCS admin guide available on our support site https://pulsesecure.net/support/.
However, for Pulse Secure Desktop Client upgrade, one should use the same method of deployment as used during prior installation. Hence if the endpoint had pulse installed with the MSI package or previously upgraded with the MSI package, Pulse Secure Desktop Client 5.0R3 and above should be upgraded using MSI installer and if Web Install is used previously than the upgrade should use the Web-Install.
If the deployment method is ‘mixed’ or ‘unknown’, then the previous version of Pulse Secure client on the endpoint should be uninstalled and then re-installed via the preferred method.
As this version of Pulse contains a new driver version, it has gone through additional qualification cycles. We recommend that it be tested on your standard/corporate desktop environment for any corner-case issues/interoperability issues that may be specific to your environment before deploying it to your end users.Caveats:
If Pulse Secure Desktop Client was initially deployed or installed using the Web install method and Pulse 5.0R3 (or higher) is installed using the standalone install method (using MSI package) then the Pulse installer will not uninstall the legacy JNPRNA components installed during the Web Install methods. To remove the legacy JNPRNA components in such scenarios end-users will have to uninstall older version of Pulse before Pulse Secure Desktop Client is installed. However we don't expect any issues due to the legacy JNPRNA components and the newer JNPRNS components co-existing on the system.
JNPRNS does not support wired 802.1x for Odyssey Access Client (OAC). If OAC is already installed on the endpoint when you install Pulse 5.0R3, the new JNPRNS components will be installed to support Pulse, and the required legacy JNPRNA components will remain on the endpoint to support OAC functionality.