mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-16 15:27:22 +00:00
Merge pull request #7290 from MicrosoftDocs/main
Publish 10/19/2022 3:30 PM PT
This commit is contained in:
commit
08b3b28774
@ -15,13 +15,14 @@ appliesto:
|
||||
- ✅ <b>Windows 11</b>
|
||||
- ✅ <b>Hybrid deployment</b>
|
||||
- ✅ <b>Key trust</b>
|
||||
- ✅ <b>Cloud Kerberos trust</b>
|
||||
---
|
||||
|
||||
# Deploying Certificates to Key Trust Users to Enable RDP
|
||||
# Deploy Certificates to Key Trust and Cloud Kerberos Trust Users to Enable RDP
|
||||
|
||||
Windows Hello for Business supports using a certificate as the supplied credential when establishing a remote desktop connection to a server or other device. For certificate trust deployments, creation of this certificate occurs at container creation time.
|
||||
|
||||
This document discusses an approach for key trust deployments where authentication certificates can be deployed to an existing key trust user.
|
||||
This document discusses an approach for key trust and cloud Kerberos trust deployments where authentication certificates can be deployed to an existing WHFB user.
|
||||
|
||||
Three approaches are documented here:
|
||||
|
||||
@ -77,7 +78,7 @@ Three approaches are documented here:
|
||||
1. Tick **Microsoft Software Key Storage Provider**
|
||||
1. Set the Request hash to **SHA256**
|
||||
|
||||
1. On the **Security** tab, add the security group that you want to give **Enroll** access to. For example, if you want to give access to all users, select the **Authenticated** users group, and then select Enroll permissions for them .
|
||||
1. On the **Security** tab, add the security group that you want to give **Enroll** access to. For example, if you want to give access to all users, select the **Authenticated** users group, and then select Enroll permissions for them.
|
||||
|
||||
1. Click **OK** to finalize your changes and create the new template. Your new template should now appear in the list of Certificate Templates.
|
||||
|
||||
@ -87,7 +88,7 @@ Three approaches are documented here:
|
||||
|
||||
1. Execute the following command:
|
||||
|
||||
certutil -dstemplate \<TemplateName\> \> \<TemplateName\>.txt
|
||||
`certutil -dstemplate \<TemplateName\> \> \<TemplateName\>.txt`
|
||||
|
||||
Replace \<TemplateName\> with the Template name you took note of earlier in step 7.
|
||||
|
||||
|
@ -8,8 +8,8 @@ author: vinaypamnani-msft
|
||||
manager: aaroncz
|
||||
ms.collection: M365-security-compliance
|
||||
ms.topic: conceptual
|
||||
ms.date: 02/14/2022
|
||||
ms.reviewer:
|
||||
ms.date: 10/19/2022
|
||||
ms.reviewer: jmunck
|
||||
ms.technology: windows-sec
|
||||
---
|
||||
|
||||
@ -55,7 +55,7 @@ No. SCM supported only SCAP 1.0, which wasn't updated as SCAP evolved. The new t
|
||||
| Name | Build | Baseline Release Date | Security Tools |
|
||||
| ---- | ----- | --------------------- | -------------- |
|
||||
| Windows 11 | [22H2](https://techcommunity.microsoft.com/t5/microsoft-security-baselines/windows-11-version-22h2-security-baseline/ba-p/3632520) <br> | September 2022<br>|[SCT 1.0](https://www.microsoft.com/download/details.aspx?id=55319) |
|
||||
| Windows 10 | [21H2](https://techcommunity.microsoft.com/t5/microsoft-security-baselines/security-baseline-for-windows-10-version-21h2/ba-p/3042703) <br> [21H1](https://techcommunity.microsoft.com/t5/microsoft-security-baselines/security-baseline-final-for-windows-10-version-21h1/ba-p/2362353) <br> [20H2](https://techcommunity.microsoft.com/t5/microsoft-security-baselines/security-baseline-final-for-windows-10-and-windows-server/ba-p/1999393) <br> [1809](https://techcommunity.microsoft.com/t5/microsoft-security-baselines/security-baseline-final-for-windows-10-v1809-and-windows-server/ba-p/701082) <br> [1607](/archive/blogs/secguide/security-baseline-for-windows-10-v1607-anniversary-edition-and-windows-server-2016) <br>[1507](/archive/blogs/secguide/security-baseline-for-windows-10-v1507-build-10240-th1-ltsb-update)| December 2021<br>May 2021<br>December 2020<br>October 2018<br>October 2016 <br>January 2016 |[SCT 1.0](https://www.microsoft.com/download/details.aspx?id=55319) |
|
||||
| Windows 10 | [22H2](https://techcommunity.microsoft.com/t5/microsoft-security-baselines/windows-10-version-22h2-security-baseline/ba-p/3655724) <br> [21H2](https://techcommunity.microsoft.com/t5/microsoft-security-baselines/security-baseline-for-windows-10-version-21h2/ba-p/3042703) <br> [21H1](https://techcommunity.microsoft.com/t5/microsoft-security-baselines/security-baseline-final-for-windows-10-version-21h1/ba-p/2362353) <br> [20H2](https://techcommunity.microsoft.com/t5/microsoft-security-baselines/security-baseline-final-for-windows-10-and-windows-server/ba-p/1999393) <br> [1809](https://techcommunity.microsoft.com/t5/microsoft-security-baselines/security-baseline-final-for-windows-10-v1809-and-windows-server/ba-p/701082) <br> [1607](/archive/blogs/secguide/security-baseline-for-windows-10-v1607-anniversary-edition-and-windows-server-2016) <br>[1507](/archive/blogs/secguide/security-baseline-for-windows-10-v1507-build-10240-th1-ltsb-update)| October 2022<br>December 2021<br>May 2021<br>December 2020<br>October 2018<br>October 2016 <br>January 2016 |[SCT 1.0](https://www.microsoft.com/download/details.aspx?id=55319) |
|
||||
Windows 8.1 |[9600 (April Update)](/archive/blogs/secguide/security-baselines-for-windows-8-1-windows-server-2012-r2-and-internet-explorer-11-final)| October 2013| [SCM 4.0](/previous-versions/tn-archive/cc936627(v=technet.10)) |
|
||||
|
||||
<br />
|
||||
|
@ -28,6 +28,7 @@ The Security Compliance Toolkit consists of:
|
||||
- Windows 11, version 22H2
|
||||
- Windows 11, version 21H2
|
||||
- Windows 10 security baselines
|
||||
- Windows 10, version 22H2
|
||||
- Windows 10, version 21H2
|
||||
- Windows 10, version 21H1
|
||||
- Windows 10, version 20H2
|
||||
|
Loading…
x
Reference in New Issue
Block a user