Testing deploying MS Always on VPN Profile to W10 1703 with Force tunneling. Looking at this document for settings
https://docs.microsoft.com/en-us/windows/client-management/mdm/vpnv2-csp
I have two settings that are in this document but missing from 1703
ByPassForLocal and RegisterDNS
1. The VPN Entry has the box "Register this Connection's Address" unticked. Although there is a profile setting above it is not implemented so I need to get around it. Has anyone resolved it. I can see you can use set-dns PowerShell command but only when the VPN connection is active so this is hard to manage through an SCCM job. Without this box ticked the home router's IP address is registered on our DNS server rather than the correct VPN IP address.
2. Found with Forcetunnel that the VPN entry needs to have Proxy setting in order to allow traffic out. Again there is a setting in profileXLM "ByPassForLocal" but it is not active yet - so although I can enter the Proxy/Manual/Server entry which is fine without that bypass box ticked nothing works - again has anyone hit/resolved this?
Ian Burnell, London (UK)