I've used Network Connect before to create a different realm/sign in page/URL to allow the client to install, then load before the interactive windows login, allowing PCs to authenticate to a domain over the VPN. eg. under User Roles/VPN Tunneling using the "
I was going to do it the same way, but under Users/Junos Pulse I see you can add additional connections. The Default SA connection is set to "Automatically at user login." although I've disabled Auto-Launch in each user profile, so I'm a bit confused as to how this overlaps with the other policies.
Which is the correct place to install the client and embed the software, changing the GINA, so authentication do a remote domain can be done at the interactive windows logon?
Thanks for the clarification.
If you need the tunnel to be created when the machine starts (before windows logon), then you'll want to select either:
You can do this during the log in as well:
Automatically at user loginÑThis option enables Pulse client interaction with the credential provider software on the endpoint. The user credentials are used to establish the authenticated Pulse connection to the network, login to the endpoint, and login to the domain server.
For more details, you can refer to http://www.juniper.net/techpubs/en_US/uac5.0/topics/task/configuration/uac-access-control-connect-co...