Even on Windows 7 machines when we were able to get the VPN client to prompt the user to connect before the Windows Login prompt, the user could still simply click cancel and proceed to windows without forcing the VPN. Ultimately my customer is trying to ensure that when a user takes their laptop home and boots up / open the lid they are forced to connect to the VPN before they can do anything else (Unlock the laptop, etc.). however the client doesn't prompt the user to connect until they are already logged into Windows and the user can just keep cancelling the prompt and continue to use the laptop without the VPN being connected. I know with location awareness and auto connect you can force the client to prompt the user to authenticate and connect, etc. This is available on Windows 7 machines however I haven't seen an equivalent feature for Windows 10. 1- connect first to the vpn client with AD credential ( SDL), then to 'pass' the. we are working to avoid 2 times logins : one login/password to connect to the vpn, then the same for windows authentication. we are using endpoint security client with AD authentication.
Is there any way to force the Endpoint VPN to prompt for credentials and connect prior to the Windows Login prompt (either via boot-up or returning from sleep / standby mode). Push the windows Credentials to Endpoint Security client or vice versa.