From b26cd411da421394212feb6afa580fdba13d8e8e Mon Sep 17 00:00:00 2001 From: Jake Grandlienard <57494526+jakeg-pki@users.noreply.github.com> Date: Mon, 19 Jul 2021 12:15:53 -0500 Subject: [PATCH] Update hello-deployment-rdp-certs.md Removed space between - and dsaddtemplate. From certutil - dsaddtemplate \.txt to certutil -dsaddtemplate \.txt --- .../hello-for-business/hello-deployment-rdp-certs.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/windows/security/identity-protection/hello-for-business/hello-deployment-rdp-certs.md b/windows/security/identity-protection/hello-for-business/hello-deployment-rdp-certs.md index 64ccdffe62..bafde6afc2 100644 --- a/windows/security/identity-protection/hello-for-business/hello-deployment-rdp-certs.md +++ b/windows/security/identity-protection/hello-for-business/hello-deployment-rdp-certs.md @@ -105,7 +105,7 @@ Three approaches are documented here: 1. Update the certificate template by executing the following command: - certutil - dsaddtemplate \.txt + certutil -dsaddtemplate \.txt 1. In the Certificate Authority console, right-click **Certificate Templates**, select **New**, and select **Certificate Template to Issue** @@ -206,4 +206,4 @@ After adding the certificate using an approach from any of the previous sections 1. Open the Remote Desktop Client (%windir%\system32\mstsc.exe) on the Hybrid AAD-Joined client where the authentication certificate has been deployed. 1. Attempt an RDP session to a target server. -1. Use the certificate credential protected by your Windows Hello for Business gesture. \ No newline at end of file +1. Use the certificate credential protected by your Windows Hello for Business gesture.