04-24-2012 09:10 AM
We have been using Network Connect for quite a few years and it works well for our users who travel all over, and the ESP to SSL fallback works great for sites that may only allow HTTPS and HTTP traffic out of their network.
What are the reasons that we would want to switch from Network Connect to Pulse? We are planning on upgrading to 7.2R1.1 and not sure if we should stick with Network Connect, or move to Pulse 3.\
04-29-2012 06:48 PM
You have all the information that you require in this link:
Hope that helps.
Please mark this post as 'accepted solution' if this answers your question that way it might help others as well, a kudo would be a bonus thanks
05-04-2012 06:25 AM
Was the link helpful?
Do you have any more questions?
If the link I gave helped you decide, may I ask you to please mark this post as 'accepted solution' if this answers your question that way it might help others as well, a kudo would be a bonus thanks
05-08-2012 07:12 AM
Pulse will also be replacing NC in the future, here is a older link for the same question
05-08-2012 12:16 PM - edited 05-08-2012 12:18 PM
It is really your call based on your user need; are there specific items you like about one or the other?
Pulse looks interesting for the ability to automatically detect if on the company network or external and automatically login if you save your password. We have been using Network Connect with Host Checker for years without any problems and it has been really stable. I am not sure if we will run into application compatibility issues or stability issues with Pulse 3.0.1 on 7.2R1.1.
It would require less testing to stick with Network Connect, but Pulse does appear to have some nice features. Staying with network connect would also make it easier for our end users since it wouldn't require additional training or documentation to use.
Has anyone run into problems with certain applications or network traffic not working properly with pulse, or any stability issues? We are running Windows 7 x64.