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

Corrected Two Spelling Errors

Browse Source
This commit is contained in:
Thomas Raya
2019-10-08 10:18:05 -07:00
committed by GitHub
parent cecc4f7028
commit 94a1c0b512
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
windows/security/identity-protection/hello-for-business/hello-hybrid-aadj-sso-base.md
View File

@ -44,7 +44,7 @@ If you upgraded your Active Directory schema to the Windows Server 2016 schema a
A fundamental prerequisite of all cloud and hybrid Windows Hello for Business deployments is device registration. A user cannot provision Windows Hello for Business unless the device from which they are trying to provision has registered with Azure Active Directory. For more information about device registration, read [Introduction to device management in Azure Active Directory](https://docs.microsoft.com/azure/active-directory/devices/overview). A fundamental prerequisite of all cloud and hybrid Windows Hello for Business deployments is device registration. A user cannot provision Windows Hello for Business unless the device from which they are trying to provision has registered with Azure Active Directory. For more information about device registration, read [Introduction to device management in Azure Active Directory](https://docs.microsoft.com/azure/active-directory/devices/overview).
You can use the **dsregcmd.exe** command to determine if your device is registered to Azure Active Directory. You can use the **dsregcmd.exe** command to determine if your device is registered to Azure Active Directory.
![dsregcmd outpout](images/aadj/dsregcmd.png) ![dsregcmd output](images/aadj/dsregcmd.png)
### CRL Distribution Point (CDP) ### CRL Distribution Point (CDP)
@ -264,7 +264,7 @@ Steps you will perform include:
1. Sign-in a domain controller using administrative credentials. 1. Sign-in a domain controller using administrative credentials.
2. Open the **Run** dialog box. Type **certlm.msc** to open the **Certificate Manager** for the local computer. 2. Open the **Run** dialog box. Type **certlm.msc** to open the **Certificate Manager** for the local computer.
3. In the navigation pane, expand **Personal**. Click **Certificates**. In the details pane, double-click the existing domain controller certificate includes **KDC Authentication** in the list of **Intended Purposes**. 3. In the navigation pane, expand **Personal**. Click **Certificates**. In the details pane, double-click the existing domain controller certificate includes **KDC Authentication** in the list of **Intended Purposes**.
4. Click the **Certification Path** tab. In the **Certifcation path** view, select the top most node and click **View Certificate**. 4. Click the **Certification Path** tab. In the **Certification path** view, select the top most node and click **View Certificate**.
![Certificate Path](images/aadj/certlm-cert-path-tab.png) ![Certificate Path](images/aadj/certlm-cert-path-tab.png)
5. In the new **Certificate** dialog box, click the **Details** tab. Click **Copy to File**. 5. In the new **Certificate** dialog box, click the **Details** tab. Click **Copy to File**.
![Details tab and copy to file](images/aadj/certlm-root-cert-details-tab.png) ![Details tab and copy to file](images/aadj/certlm-root-cert-details-tab.png)