deepblue/windows-itpro-docs
1
0
Fork 0
mirror of https://github.com/MicrosoftDocs/windows-itpro-docs.git synced 2025-06-20 04:43:37 +00:00
Code Issues Actions 3 Packages Projects Releases Wiki Activity

update VPN path

Browse Source
This commit is contained in:
jdeckerMS
2016-10-05 13:27:08 -07:00
parent 0a9989db86
commit 5c0fd59550
3 changed files with 12 additions and 12 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
windows/keep-secure/vpn-auto-trigger-profile.md
View File

@ -34,7 +34,7 @@ The app identifier for a desktop app is a file path. The app identifier for a UW
You can configure a domain name-based rule so that a specific domain name triggers the VPN connection.
Name-based auto-trigger can be configured using the VPNv2//*ProfileName*/DomainNameInformationList/dniRowId/AutoTrigger setting in the [VPNv2 Configuration Service Provider (CSP)](https://msdn.microsoft.com/library/windows/hardware/dn914776.aspx).
Name-based auto-trigger can be configured using the VPNv2/*ProfileName*/DomainNameInformationList/dniRowId/AutoTrigger setting in the [VPNv2 Configuration Service Provider (CSP)](https://msdn.microsoft.com/library/windows/hardware/dn914776.aspx).
There are four types of name-based triggers:
@ -61,7 +61,7 @@ When a device has multiple profiles with Always On triggers, the user can specif
This feature configures the VPN such that it would not get triggered if a user is on a trusted corporate network. The value of this setting is a list of DNS suffices. The VPN stack will look at the DNS suffix on the physical interface and if it matches any in the configured list and the network is private or provisioned by MDM, then VPN will not get triggered.
Trusted network detection can be configured using the VPNv2//*ProfileName*/TrustedNetworkDetection setting in the [VPNv2 CCSP](https://msdn.microsoft.com/library/windows/hardware/dn914776.aspx).
Trusted network detection can be configured using the VPNv2/*ProfileName*/TrustedNetworkDetection setting in the [VPNv2 CCSP](https://msdn.microsoft.com/library/windows/hardware/dn914776.aspx).
## Configure app-triggered VPN

12
windows/keep-secure/vpn-name-resolution.md
View File

@ -31,7 +31,7 @@ There are 3 types of name matches that can set up for NRPT:
- Any resolution should attempt to first resolve with the proxy server/DNS server with this entry
NRPT is set using the **VPNv2//*ProfileName*/DomainNameInformationList** node. This node also configures Web proxy server or domain name servers.
NRPT is set using the **VPNv2/*ProfileName*/DomainNameInformationList** node. This node also configures Web proxy server or domain name servers.
[Learn more about NRPT](https://technet.microsoft.com/library/ee649207%28v=ws.10%29.aspx)
@ -40,7 +40,7 @@ NRPT is set using the **VPNv2//*ProfileName*/DomainNameInformationList** node. T
This setting is used to configure the primary DNS suffix for the VPN interface and the suffix search list after the VPN connection is established.
Primary DNS suffix is set using the **VPNv2//*ProfileName*/DnsSuffix** node.
Primary DNS suffix is set using the **VPNv2/*ProfileName*/DnsSuffix** node.
@ -50,7 +50,7 @@ Primary DNS suffix is set using the **VPNv2//*ProfileName*/DnsSuffix** node.
You can also configure *persistent* name resolution rules. Name resolution for specified items will only performed over VPN.
Persistent name resolution is set using the **VPNv2//*ProfileName*/DomainNameInformationList//*dniRowId*/Persistent** node.
Persistent name resolution is set using the **VPNv2/*ProfileName*/DomainNameInformationList//*dniRowId*/Persistent** node.
@ -66,9 +66,9 @@ The fields in **Add or edit DNS rule** in the Intune profile correspond to the X
| Field | XML |
| --- | --- |
| **Name** | **VPNv2//*ProfileName*/DomainNameInformationList//*dniRowId*/DomainName** |
| **Servers (comma separated)** | **VPNv2//*ProfileName*/DomainNameInformationList//*dniRowId*/DnsServers** |
| **Proxy server** | **VPNv2//*ProfileName*/DomainNameInformationList//*dniRowId*/WebServers** |
| **Name** | **VPNv2/*ProfileName*/DomainNameInformationList//*dniRowId*/DomainName** |
| **Servers (comma separated)** | **VPNv2/*ProfileName*/DomainNameInformationList//*dniRowId*/DnsServers** |
| **Proxy server** | **VPNv2/*ProfileName*/DomainNameInformationList//*dniRowId*/WebServers** |
## Related topics

8
windows/keep-secure/vpn-routing.md
View File

@ -21,13 +21,13 @@ Network routes are required for the stack to understand which interface to use f
In a split tunnel configuration, routes can be specified to go over VPN and all other traffic will go over the physical interface.
Routes can be configured using the VPNv2//*ProfileName*/RouteList setting in the [VPNv2 Configuration Service Provider (CSP)](https://msdn.microsoft.com/library/windows/hardware/dn914776.aspx).
Routes can be configured using the VPNv2/*ProfileName*/RouteList setting in the [VPNv2 Configuration Service Provider (CSP)](https://msdn.microsoft.com/library/windows/hardware/dn914776.aspx).
For each route item in the list the following can be specified:
- **Address**: VPNv2//*ProfileName*/RouteList//*routeRowId*/Address
- **Prefix size**: VPNv2//*ProfileName*/RouteList//*routeRowId*/Prefix
- **Exclusion route**: VPNv2//*ProfileName*/RouteList//*routeRowId*/ExclusionRoute
- **Address**: VPNv2/*ProfileName*/RouteList//*routeRowId*/Address
- **Prefix size**: VPNv2/*ProfileName*/RouteList//*routeRowId*/Prefix
- **Exclusion route**: VPNv2/*ProfileName*/RouteList//*routeRowId*/ExclusionRoute
Windows VPN platform now supports the ability to specify exclusion routes that specifically should not go over the physical interface.