Of course not included in this list but supported is Windows 10 Always On VPN. Microsoft doesn’t provide an exhaustive list of supported solutions but there are some third-party solutions that are expected to work. We need to establish the connection from the Windows 10 login screen using the Network Sign-in option. This is the reason for the VPN connection prior to the user logging in. As a new machine, the user has never logged on before so we don’t have a cached credential for them to use.
To work, the solution must use device authentication and not user authentication. Hybrid Windows Autopilot VPN compatibility
To work with Windows Autopilot, however, you need to make sure that the VPN solution being deployed is going to be compatible with Hybrid Windows Autopilot. I’m not going to dwell on that for this post as we have another one in the works talking about some of the Microsoft options for VPN focusing on security. Deploying VPN via Microsoft Intuneĭeployment of a VPN connection, software package, or other type of VPN connection via Intune is not new: we’ve had this option for some time.
How does it do the VPN connection you ask? Well through your Microsoft Intune Configuration Profiles of course. The way it works, to get 100% remotely deployable Hybrid Windows Autopilot devices is like this skip the check during the deployment for domain connectivity until the device is able to establish a VPN connection. With the introduction of support for Hybrid Windows Autopilot over VPN (Bring Your Own VPN as the Microsoft documentation calls it) the game has changed. For devices which are Hybrid Azure AD Joined via Active Directory, Windows Autopilot could fail as it required the device to have line-of-sight to a Domain Controller to perform the Domain Join operation. Windows Autopilot until now has only worked 100% remotely for Azure AD Joined devices.
0 kommentar(er)
