Open in the explorer

Fail authentication requests when Kerberos armoring is not available

Faire échouer les demandes d’authentification lorsque le blindage Kerberos n’est pas disponible

Type
Computer
GPO path
Computer Configuration › Policies › Administrative Templates › System › Kerberos FR: Configuration ordinateur › Stratégies › Modèles d'administration › Système › Kerberos
Supported on
At least Windows Server 2012, Windows 8 or Windows RT FR: Au minimum Windows Server 2012, Windows 8 ou Windows RT
ADMX file
Kerberos.admx
Internal name
Kerberos/ClientRequireFast

Explanation

This policy setting controls whether a computer requires that Kerberos message exchanges be armored when communicating with a domain controller.

Warning: When a domain does not support Kerberos armoring by enabling "Support Dynamic Access Control and Kerberos armoring", then all authentication for all its users will fail from computers with this policy setting enabled.

If you enable this policy setting, the client computers in the domain enforce the use of Kerberos armoring in only authentication service (AS) and ticket-granting service (TGS) message exchanges with the domain controllers.

Note: The Kerberos Group Policy "Kerberos client support for claims, compound authentication and Kerberos armoring" must also be enabled to support Kerberos armoring.

If you disable or do not configure this policy setting, the client computers in the domain enforce the use of Kerberos armoring when possible as supported by the target domain.

French text from Windows 11 26H2

Ce paramètre de stratégie détermine si un ordinateur exige que les échanges de messages Kerberos soient blindés durant la communication avec un contrôleur de domaine.

Avertissement : lorsqu’un domaine ne prend pas en charge le blindage Kerberos à travers le paramètre de stratégie « Prendre en charge le contrôle d’accès dynamique et le blindage Kerberos », toutes les authentifications de ses utilisateurs échouent à partir des ordinateurs où ce paramètre de stratégie est activé.

Si vous activez ce paramètre de stratégie, les ordinateurs clients du domaine appliquent l’utilisation du blindage Kerberos uniquement durant les échanges de messages du service d’authentification (AS) et du service d’accord de tickets (TGS) avec les contrôleurs de domaine.

Remarque : la stratégie de groupe Kerberos Prise en charge du client Kerberos pour les revendications, l’authentification composée et le blindage Kerberos doit également être activée pour prendre en charge le blindage Kerberos.

Si vous désactivez ce paramètre de stratégie ou si vous ne le configurez pas, les ordinateurs clients du domaine appliquent l’utilisation du blindage Kerberos lorsque cela est possible, en fonction de la prise en charge par le domaine cible.

Use cases

Makes the computer require Kerberos armoring (FAST) for its AS and TGS exchanges with domain controllers. Armoring protects pre-authentication data from offline dictionary attacks and authenticates Kerberos errors, which stops a fake KDC from pushing the client down to NTLM or weaker cryptography.

Major risk: if the domain has not enabled “KDC support for claims, compound authentication and Kerberos armoring”, all user authentications fail from computers where this policy is on; they also fail if no Windows Server 2012 or later domain controller can be found. Deploy in order: KDC first, then client-side support (“Kerberos client support for claims…”), and only then this requirement.

Microsoft source: What's New in Kerberos Authentication

Registry

HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Policies\System\Kerberos\Parameters
Value name
RequireFast
StateValue written
EnabledREG_DWORD = 1
DisabledREG_DWORD = 0

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: Kerberos/ClientRequireFast
$k = 'HKLM:\Software\Microsoft\Windows\CurrentVersion\Policies\System\Kerberos\Parameters'
if (-not (Test-Path -Path $k)) { New-Item -Path $k -Force | Out-Null }
Set-ItemProperty -Path $k -Name 'RequireFast' -Value 1 -Type DWord

Disable

# Disable: Kerberos/ClientRequireFast
$k = 'HKLM:\Software\Microsoft\Windows\CurrentVersion\Policies\System\Kerberos\Parameters'
if (-not (Test-Path -Path $k)) { New-Item -Path $k -Force | Out-Null }
Set-ItemProperty -Path $k -Name 'RequireFast' -Value 0 -Type DWord

Revert to "Not configured"

# Revert to "Not configured": Kerberos/ClientRequireFast
$k = 'HKLM:\Software\Microsoft\Windows\CurrentVersion\Policies\System\Kerberos\Parameters'
Remove-ItemProperty -Path $k -Name 'RequireFast' -ErrorAction SilentlyContinue

Availability