Update windows/security/identity-protection/hello-for-business/hello-deployment-guide.md

Co-Authored-By: Nicole Turner <39884432+nenonix@users.noreply.github.com>
This commit is contained in:
Reece Peacock
2019-08-08 08:22:54 +02:00
committed by GitHub
parent 95c023cbe6
commit 1a874f9fe9

View File

@ -55,7 +55,7 @@ The trust model determines how you want users to authenticate to the on-premises
* The certificate-trust model is for enterprise that *do* want to issue end-entity certificates to their users and have the benefits of certificate expiration and renewal, similar to how smart cards work today.
* The certificate trust model also supports enterprises which are not ready to deploy Windows Server 2016 Domain Controllers.
For additional information regarding directory sync, including hybrid deployments (Azure Active Directory) using cert and key trusts models see [Hybrid Windows Hello for Business Prerequisites](https://docs.microsoft.com/windows/security/identity-protection/hello-for-business/hello-hybrid-cert-trust-prereqs#directory-synchronization) and [Hybrid Key trust Windows Hello for Business Prerequisites](https://docs.microsoft.com/windows/security/identity-protection/hello-for-business/hello-hybrid-key-trust-prereqs#directory-synchronization).
For additional information about directory sync, including hybrid deployments (Azure Active Directory) see the Hybrid Windows Hello for Business [certificate trust prerequisites](hello-hybrid-cert-trust-prereqs.md#directory-synchronization) and [key trust prerequisites](hello-hybrid-key-trust-prereqs.md#directory-synchronization).
>[!NOTE]
>Remote Desktop Protocol (RDP) does not support authentication with Windows Hello for Business key trust deployments. RDP is only supported with certificate trust deployments at this time. See [Remote Desktop with Biometrics](hello-features.md#remote-desktop-with-biometrics) to learn more.