Merge branch 'main' of https://github.com/MicrosoftDocs/windows-docs-pr into arm-dep
Before Width: | Height: | Size: 59 KiB |
Before Width: | Height: | Size: 74 KiB |
Before Width: | Height: | Size: 31 KiB |
Before Width: | Height: | Size: 4.1 KiB |
Before Width: | Height: | Size: 4.5 KiB |
Before Width: | Height: | Size: 28 KiB |
Before Width: | Height: | Size: 305 KiB |
Before Width: | Height: | Size: 217 KiB |
Before Width: | Height: | Size: 9.8 KiB |
Before Width: | Height: | Size: 6.0 KiB |
Before Width: | Height: | Size: 20 KiB |
Before Width: | Height: | Size: 145 KiB |
Before Width: | Height: | Size: 318 KiB |
Before Width: | Height: | Size: 23 KiB |
Before Width: | Height: | Size: 11 KiB |
Before Width: | Height: | Size: 135 KiB |
@ -286,9 +286,12 @@ One of the things we’ve heard from you is that it’s hard to know when you’
|
||||
|
||||
## Remote Desktop with Biometrics
|
||||
|
||||
Azure Active Directory and Active Directory users using Windows Hello for Business can use biometrics to authenticate to a remote desktop session.
|
||||
Windows Hello for Business supports using a certificate deployed to a Windows Hello for Business container as a supplied credential to establish a remote desktop connection to a server or another device. This feature takes advantage of the redirected smart card capabilities of the remote desktop protocol.
|
||||
Users using earlier versions of Windows 10 could authenticate to a remote desktop using Windows Hello for Business but were limited to using their PIN as their authentication gesture. Windows 10, version 1809 introduces the ability for users to authenticate to a remote desktop session using their Windows Hello for Business biometric gesture.
|
||||
|
||||
To get started, sign into your device using Windows Hello for Business. Bring up **Remote Desktop Connection** (mstsc.exe), type the name of the computer you want to connect to, and click **Connect**. Windows remembers that you signed using Windows Hello for Business, and automatically selects Windows Hello for Business to authenticate you to your RDP session. You can also click **More choices** to choose alternate credentials. Windows uses facial recognition to authenticate the RDP session to the Windows Server 2016 Hyper-V server. You can continue to use Windows Hello for Business in the remote session, but you must use your PIN.
|
||||
Azure Active Directory and Active Directory users using Windows Hello for Business in a certificate trust model, can use biometrics to authenticate to a remote desktop session.
|
||||
|
||||
To get started, sign into your device using Windows Hello for Business. Bring up **Remote Desktop Connection** (mstsc.exe), type the name of the device you want to connect to, and select **Connect**. Windows remembers that you signed using Windows Hello for Business, and automatically selects Windows Hello for Business to authenticate you to your RDP session. You can also select **More choices** to choose alternate credentials. Windows uses biometrics to authenticate the RDP session to the Windows device. You can continue to use Windows Hello for Business in the remote session, but in the remote session you must use the PIN.
|
||||
|
||||
See the following example:
|
||||
|
||||
|
@ -106,5 +106,5 @@ The VM host CPU must also meet Windows 11 [processor requirements](/windows-hard
|
||||
## See also
|
||||
|
||||
[Windows minimum hardware requirements](/windows-hardware/design/minimum/minimum-hardware-requirements-overview)<br>
|
||||
[What's new in Windows 11 overview](windows-11-whats-new.md)
|
||||
[What's new in Windows 11 overview](/windows/whats-new/windows-11-overview)
|
||||
|
||||
|