easily insert the VPN profile configuration XML markup into the ProfileXML CSP node. This is the method you’ll use to configure the Remote Access Always On VPN client by using Intune. Windows Management Instrumentation (WMI)-to-CSP bridge. The second method of configuring the ProfileXML CSP node is to use the WMI-to-CSP bridge—a WMI class called MDM_VPNv2_01—that can access the VPNv2 CSP and therefore the ProfileXML node. When you create a new instance of that WMI class, WMI uses the CSP to create the VPN profile. This is the method you use to configure the Remote Access Always On VPN client by using Windows PowerShell and System Center Configuration Manager. Even though these configuration methods differ, both require a properly formatted XML VPN profile. To use the ProfileXML VPNv2 CSP setting, you construct XML by using the ProfileXML schema to configure the tags necessary for the simple deployment scenario. For more details, see . In the section “Infrastructure requirements,” Table 1 provided an overview of the individual settings for the VPN client. Below is each of those required settings and its corresponding ProfileXML tag. You configure each setting in a specific tag within the ProfileXML schema, and not all of them are found under the native profile. For additional tag placement, see the ProfileXML schema. Connection type: Native IKEv2 ProfileXML element: Copy <NativeProtocolType>IKEv2</NativeProtocolType> Routing: tunneling ProfileXML element: Copy <RoutingPolicyType>SplitTunnel</RoutingPolicyType> Name resolution: Domain Name Information List and DNS suffix ProfileXML elements:
easily insert the VPN profile configuration XML markup into the ProfileXML CSP node. This is the method you’ll use to configure the Remote Access Always On VPN client by using Intune. Windows Management Instrumentation (WMI)-to-CSP bridge. The second method of configuring the ProfileXML CSP node is to use the WMI-to-CSP bridge—a WMI class called MDM_VPNv2_01—that can access the VPNv2 CSP and therefore the ProfileXML node. When you create a new instance of that WMI class, WMI uses the CSP to create the VPN profile. This is the method you use to configure the Remote Access Always On VPN client by using Windows PowerShell and System Center Configuration Manager. Even though these configuration methods differ, both require a properly formatted XML VPN profile. To use the ProfileXML VPNv2 CSP setting, you construct XML by using the ProfileXML schema to configure the tags necessary for the simple deployment scenario. For more details, see . In the section “Infrastructure requirements,” Table 1 provided an overview of the individual settings for the VPN client. Below is each of those required settings and its corresponding ProfileXML tag. You configure each setting in a specific tag within the ProfileXML schema, and not all of them are found under the native profile. For additional tag placement, see the ProfileXML schema. Connection type: Native IKEv2 ProfileXML element: Copy <NativeProtocolType>IKEv2</NativeProtocolType> Routing: tunneling ProfileXML element: Copy <RoutingPolicyType>SplitTunnel</RoutingPolicyType> Name resolution: Domain Name Information List and DNS suffix ProfileXML elements:
Remote%20Access%20Always%20On%20VPN%20Deployment%20Guide%20for%20Windows%20Server%202016%20and%20Windows%2010.docx