deepblue/windows-itpro-docs
1
0
Fork 0
mirror of https://github.com/MicrosoftDocs/windows-itpro-docs.git synced 2025-06-18 11:53:37 +00:00
Code Issues Actions 3 Packages Projects Releases Wiki Activity

Fix compatibility issues with Windows Hello for

Browse Source 
Business certificates
This commit is contained in:
Paolo Matarazzo
2023-12-08 08:57:15 -05:00
parent aec99d31b9
commit 5a9a43c363
1 changed files with 11 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

18
windows/security/identity-protection/hello-for-business/rdp-sign-in.md
View File

@ -203,16 +203,18 @@ After the certificate is obtained, users can RDP to any Windows devices in the s
## Compatibility ## Compatibility
While users appreciate the convenience of biometrics, and administrators value the security, you may experience compatibility issues with applications and Windows Hello for Business certificates. In such scenarios, you can deploy policy setting to revert to the previous behavior for the users needing it. While users appreciate the convenience of biometrics, and administrators value the security, you may experience compatibility issues with applications and Windows Hello for Business certificates. In such scenarios, you can deploy a policy setting to revert to the previous behavior for the users needing it.
## User experience 2 ### Use Windows Hello for Business certificates as smart card certificates
After the certificate is obtained, users can RDP to any Windows devices in the same Active Directory forest as the user's Active Directory account. If you enable this policy setting, applications use Windows Hello for Business certificates as smart card certificates. Biometric factors are unavailable when a user is asked to authorize the use of the certificate's private key. This policy setting is designed to allow compatibility with applications that rely exclusively on smart card certificates.
1. Open the Remote Desktop Client (`mstsc.exe`) on the client where the authentication certificate is deployed If you disable or don't configure this policy setting, applications don't use Windows Hello for Business certificates as smart card certificates, and biometric factors are available when a user is asked to authorize the use of the certificate's private key.
1. Attempt an RDP session to a target server
1. Use the certificate credential protected by your Windows Hello for Business gesture to authenticate | | Path |
> [!VIDEO https://learn-video.azurefd.net/vod/player?id=b6e1038d-98b5-48dc-8afb-65523d12cfaf] |--|--|
| **CSP** | `./Device/Vendor/MSFT/PassportForWork/{TenantId}/Policies/`[UseHelloCertificatesAsSmartCardCertificates][WIN-1]|
| **GPO** | **Computer Configuration** > **Administrative Templates** > **Windows Components** > **Windows Hello for Business** |
<!-- links --> <!-- links -->
@ -224,3 +226,5 @@ After the certificate is obtained, users can RDP to any Windows devices in the s
[MEM-6]: /mem/intune/protect/certificate-authority-add-scep-overview [MEM-6]: /mem/intune/protect/certificate-authority-add-scep-overview
[HTTP-1]: https://www.powershellgallery.com/packages/Generate-CertificateRequest [HTTP-1]: https://www.powershellgallery.com/packages/Generate-CertificateRequest
[WIN-1]: /windows/client-management/mdm/passportforwork-csp#devicetenantidpoliciesusehellocertificatesassmartcardcertificates