mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-18 20:03:40 +00:00
Corrected Two Spelling Errors
This commit is contained in:
@ -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).
|
||||
|
||||
You can use the **dsregcmd.exe** command to determine if your device is registered to Azure Active Directory.
|
||||

|
||||

|
||||
|
||||
### CRL Distribution Point (CDP)
|
||||
|
||||
@ -264,7 +264,7 @@ Steps you will perform include:
|
||||
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.
|
||||
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**.
|
||||

|
||||
5. In the new **Certificate** dialog box, click the **Details** tab. Click **Copy to File**.
|
||||

|
||||
|
Reference in New Issue
Block a user