IPsec Tunnel Endpoints
Points de terminaison de tunnels IPsec
Explanation
Specifies the IPv6 addresses of the endpoints of the Internet Protocol security (IPsec) tunnels that enable DirectAccess. NCA attempts to access the resources that are specified in the Corporate Resources setting through these configured tunnel endpoints.
By default, NCA uses the same DirectAccess server that the DirectAccess client computer connection is using. In default configurations of DirectAccess, there are typically two IPsec tunnel endpoints: one for the infrastructure tunnel and one for the intranet tunnel. You should configure one endpoint for each tunnel.
Each entry consists of the text PING: followed by the IPv6 address of an IPsec tunnel endpoint. Example: PING:2002:836b:1::836b:1.
You must configure this setting to have complete NCA functionality.
Indique les adresses IPv6 des points de terminaison de tunnels IPsec qui activent DirectAccess. L’Assistant Connectivité réseau tente d’accéder aux ressources spécifiées dans le paramètre Ressources d’entreprise via les points de terminaison de tunnels configurés.
Par défaut, l’Assistant Connectivité réseau utilise le même serveur DirectAccess que la connexion de l’ordinateur client DirectAccess. Dans les configurations par défaut de DirectAccess, il existe généralement deux points de terminaison de tunnels IPsec : l’un pour le tunnel d’infrastructure et l’autre pour le tunnel intranet. Vous devez configurer un point de terminaison pour chaque tunnel.
Chaque entrée se compose du texte PING: suivi de l’adresse IPv6 d’un point de terminaison de tunnel IPsec. Exemple : PING:2002:836b:1::836b:1.
Vous devez configurer ce paramètre pour que la fonctionnalité NCA soit complète.
Registry
HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\NetworkConnectivityAssistant\DTEs- Value name
- not defined in the ADMX
Enable / disable values: not defined in the ADMX (see the options below).
PowerShell
PowerShell commands that write to the registry what the policy would write. Values in angle brackets (<…>) must be replaced.
Writing directly to the registry bypasses Group Policy: if a GPO manages this value, it will be rewritten at the next gpupdate; otherwise the value stays in place (the "tattooing" effect). Prefer a GPO or, locally, LGPO.exe. Run PowerShell as administrator for HKLM. Some policies need a restart or gpupdate /force.
Enable
# Enable: nca/DTEs
$k = 'HKLM:\SOFTWARE\Policies\Microsoft\Windows\NetworkConnectivityAssistant\DTEs'
if (-not (Test-Path -Path $k)) { New-Item -Path $k -Force | Out-Null }
# DTEs
$values = @('<value1>', '<value2>') # Replace the values with your own
foreach ($v in $values) { Set-ItemProperty -Path $k -Name $v -Value $v -Type String }Disable
# Disable: nca/DTEs
# No value is written in the "Disabled" state (nothing defined in the ADMX)Revert to "Not configured"
# Revert to "Not configured": nca/DTEs
$k = 'HKLM:\SOFTWARE\Policies\Microsoft\Windows\NetworkConnectivityAssistant\DTEs'
# names to adapt
# Remove-ItemProperty -Path $k -Name '<name1>' -ErrorAction SilentlyContinueOptions (1)
| Label | Control | Registry value | REG type | Constraints / details |
|---|---|---|---|---|
| DTEsSystèmes DTEDTEs_Control | List (table)list | SOFTWARE\Policies\Microsoft\Windows\NetworkConnectivityAssistant\DTEsNumbered values (1, 2, 3…) · additive | REG_SZ (values under the key) |