One way is to use an MDM provider using OMA-DM, as discussed earlier in the section VPNv2 CSP nodes. There are two ways to configure the ProfileXML VPNv2 CSP node in this deployment: You use ProfileXML in all the delivery methods this deployment describes, including Windows PowerShell, Microsoft Endpoint Configuration Manager, and Intune.
The ProfileXML schema matches the schema of the VPNv2 CSP nodes almost identically, but some terms are slightly different.
Rather than configuring each VPNv2 CSP node individually-such as triggers, route lists, and authentication protocols-use this node to configure a Windows 10 VPN client by delivering all the settings as a single XML block to a single CSP node. ProfileXML is a URI node within the VPNv2 CSP.
Either folder redirection must be disabled for %appdata%, or the auto-triggered VPN profile must be deployed in system context, to change the path in which the rasphone.pbk file is stored. Auto-triggered VPN connections will not work if folder redirection for %appdata% (C:\Users\username\AppData\Roaming) is enabled.
