NC vs Pulse

[tech_dude_]

Exactly what is the different between NetConnect and Pulse?

Is Pulse something I should be loking at moving to (from NetConnect), and if so, why?

Any special "gotchas" I should be aware of, or do we just enable pulse?

[dcvers_]

One gotcha is the backward compatibility. Newer version of the Pulse client work with older versions of the appliance software but not all features are always fully support. For example newer versions of the user client won't work with older appliance software if host checker is enabled. So in some cases you will need to do a full appliance upgrade.

[zanyterp_]

With 7.4/4.0 and later, yes, there is an option to suppress the splash message AND manual connection. It will always start when the system launches, but it won't show the Pulse splash screen nor try to auto-connect.

[zanyterp_]

You should work on deploying Pulse rather than Network Connect unless there is a need for NC (eg FIPS or SVW support). If it's not possible to move right now, it should be evaluated for use case settings.

The only major gotcha with Pulse is that if you roam between WiFi access points or need to otherwise repeat the DHCP DORA process, it can take up to 10 min for this to complete (unless you disable the Juniper Networks Agent while on the LAN)

[stine_]

One other difference is that the NC client only starts when launched by the browswer (or opened by the user.)  The pulse client gets installed (on Windows 7) to run at Windows Login whether your users intend to connect, or not.

[stine_]

Fortunately, I run Fedora.

Also, I wouldn't make a blanket change to Pulse until the installer acts more friendly (i.e. NOT installing the app to auto-start on login, unless there's a new option on the SA/MAG to disable this abhorent behaviour.)

[jayLaiz_]

Pulse has evolved since it was initially developed.

Pulse can do location awareness,machine authentication, be backward and upward compatible to SA/MAG firmware version.If whole client is installed and not just SA/MAG components can connect to IC,SRX devices.Connect automatically when user signs into desktop

You can add multiple connections to Pulse to be able to connect to multiple SA/MAG devices worldwide.

As far as configuration is concerned ,same as NC other than selecting Junos pulse under the user role.

Under User's tab, need to setup a component set and connection set but a default one exists which makes it work witjout any configuration there. Location awareness, credential provider, machine auth etc can be confiured when defining a new connection.

Admin guide will have more detailed information.

So Pulse is the way to go forward.

Regards,

Jay

[Kita_]

Here is a comparsion chart between Pulse and NC:

http://www.juniper.net/techpubs/en_US/junos-pulse4.0/topics/reference/a-c-c-nc-comparing.html

[papageno_]

SVW works with Network Connect, while SVW and Pulse are not inter-operable

HTH

[braker_]

Also, Pulse is a standalone client with no dependencies on browser version or Java.

And, Pulse is not version bound to the SA/Mag firmware the way that NC is. Platform firmware and Pulse version can be upgraded independently.