From cec0159439a48c31b76f9ccbd3b97ff3ec28ae25 Mon Sep 17 00:00:00 2001 From: ImranHabib <47118050+joinimran@users.noreply.github.com> Date: Fri, 19 Feb 2021 10:42:12 +0500 Subject: [PATCH] Update windows/security/identity-protection/hello-for-business/hello-hybrid-key-whfb-settings-pki.md Co-authored-by: mapalko --- .../hello-for-business/hello-hybrid-key-whfb-settings-pki.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/security/identity-protection/hello-for-business/hello-hybrid-key-whfb-settings-pki.md b/windows/security/identity-protection/hello-for-business/hello-hybrid-key-whfb-settings-pki.md index b00b4cc551..9773a3fe79 100644 --- a/windows/security/identity-protection/hello-for-business/hello-hybrid-key-whfb-settings-pki.md +++ b/windows/security/identity-protection/hello-for-business/hello-hybrid-key-whfb-settings-pki.md @@ -83,7 +83,7 @@ The certificate template is configured to supersede all the certificate template > [!NOTE] > The certificate for the CA issuing the domain controller certificate must be included in the NTAuth store. By default, the Active Directory Certificate Authority's root certificate is added to the NTAuth store. If you are using a multi-tier CA hierarchy or a third-party CA, this may not be done by default. If the Domain Controller certificate does not directly chain to a CA certificate in the NTAuth store, user authentication will fail. -The following PowerShell command can be used to check the NTAuth certificate: +The following PowerShell command can be used to check all certificates in the NTAuth store: ```powershell Certutil -viewstore -enterprise NTAuth