If you've met those requirements, it should work. It's important to remember that the device tunnel requires your laptops to be running Windows 10 Enterprise edition andīe joined to a domain.
If you've deployed the Windows 10 Always On VPN device tunnel correctly it should establish a VPN connection before the user logs on. I've tried task scheduler and a specific script to run the vpn connectivity on logon but it appears either not all/some of the services don't start until after login for this to work? Has anyone found a functional way to enable VPN connectivity either from the lock screen or an alternative work-around to allow non-cached users to login, as the VPN would be connected prior to login? However, I've read elsewhere the only way someone got around this scenario as the VPN doesn'tĬonnect until login (for users who haven't already logged into that specific machine before, therefore have no cached credentials) - is to enable user switching and switch the user once cached credentials have logged in. Once a user account is cached, they shouldn't have any issues. The scenario we currently have, is where some PC's are being used elsewhere on sim-card connectivity. I've implemented Always-On-VPN and enabled device based authentication alongside client based, this element works fine without any problems.
#Windows 10 lock screen tunnel how to
Unsure if anyone has managed to identify how to do this fluidly.