maybe someone is running / has expirience with this combination :
Thin Client with JunOS Pulse or Network Connect ?
Unfortunately, either will work and we can't answer which is best for your environment. Pulse may be the best option as you have potential for more flexibility, especially if you will be using the IC, WX, or other features of Pulse.
Use some of the below data to make a decision.
1. A few more minor options than Pulse (multiple modes of split tunnel, start script and stop script, etc)
2. Better cross platform support from end user perspective (windows/mac/linux)
1. Single client that can interface with multiple Juniper products (smaller footprint on client and easier to manage compared to having multiple client components)
In the end these are two different approaches to the same requirement i.e. providing layer 3 type of connectivity to remote users and as other forum users mentioned the factor that would weigh in the most is 'What works best in your environment?'