In the past, I have rolled out the Installer Service package as a Group Policy via Active Directory to all my laptop clients.
But we still get errors with NC. Completely random type stuff too. Mostly 2379x errors.
I also tried to find a way to STOP pushing the network connect client actively.
I would prefer to "Roll-out" the client by myself via software distribution.
This would also grant more security as I am able to define the computers the client is installed onto.
Using unwanted devices to open up a vpn tunnel would be more difficult for a regardless user because the client will not be pushed automatically.
The suggested way by juniper was to use a hostchecker to test if network connect is installed and then to enable the role for network connect itself. But why should I use the hostchecker if not really needed in my eyes.
I hope Juniper will integrate a way to STOP pushing the client AND to give us some more options when installing the network connect client with command line switches (f.e. after installation of the network connect client it doesn't starts minimized!!)