deepblue/windows-itpro-docs
1
0
Fork 0
mirror of https://github.com/MicrosoftDocs/windows-itpro-docs.git synced 2025-05-13 05:47:23 +00:00
Code Issues Actions 2 Packages Projects Releases Wiki Activity

Fixes for device registration page

Browse Source
This commit is contained in:
Mike Stephens 2017-09-04 08:30:46 -07:00
parent 343daf1530
commit dd6b49e747
1 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
windows/access-protection/hello-for-business/hello-hybrid-cert-trust-devreg.md
View File

@ -13,7 +13,7 @@ localizationpriority: high
# Configure Device Registration for Hybrid Windows Hello for Business
**Applies to**
- Windows 10
- Windows 10
> [!div class="step-by-step"]
[Configure Active Directory >](hello-hybrid-cert-whfb-settings-ad.md)
@ -30,7 +30,7 @@ Use this three phased approach for configuring device registration.
1. [Configure devices to register in Azure](#configure-azure-for-device-registration)
2. [Synchronize devices to on-premises Active Directory](#configure-active-directory-to-support-azure-device-syncrhonization)
3. [Configure AD FS to use cloud devices](#configure-ad-fs-to-use-azure-registered-devices)
>!NOTE
>[!NOTE]
> Before proceeding, you should familiarize yourself with device regisration concepts such as:
>* Azure AD registered devices
>* Azure AD joined devices
@ -51,7 +51,7 @@ Azure Active Directory is now configured for device registration. Next, you need
To use Windows Hello for Business with Hybrid Azure AD joined devices, you must first upgrade your Active Directory schema to Windows Server 2016.
>!IMPORTANT
>![IMPORTANT]
>If you already have a Windows Server 2016 domain controller in your forest, you can skip **Upgrading Active Directory to the Windows Server 2016 Schema** (this section).
#### Identify the schema role domain controller
@ -106,7 +106,7 @@ If your AD FS farm is not already configured for Device Authentication (you can
![Device Registration](images/hybridct/device1.png)
>Note: The below commands require Active Directory administration tools, so if your federation server is not also a domain controller, first install the tools using step 1 below. Otherwise you can skip step 1.
>[!NOTE]The below commands require Active Directory administration tools, so if your federation server is not also a domain controller, first install the tools using step 1 below. Otherwise you can skip step 1.
1. Run the **Add Roles & Features** wizard and select feature **Remote Server Administration Tools** -> **Role Administration Tools** -> **AD DS and AD LDS Tools** -> Choose both the **Active Directory module for Windows PowerShell** and the **AD DS Tools**.
@ -118,7 +118,7 @@ If your AD FS farm is not already configured for Device Authentication (you can
`PS C:\> Initialize-ADDeviceRegistration -ServiceAccountName "<your service account>" `
3. On the pop-up window hit Yes.
>Note: If your AD FS service is configured to use a GMSA account, enter the account name in the format "domain\accountname$"
>[!NOTE]If your AD FS service is configured to use a GMSA account, enter the account name in the format "domain\accountname$"
![Device Registration](images/hybridct/device3.png)
@ -141,7 +141,7 @@ If you plan to use Windows 10 domain join (with automatic registration to Azure
`PS C:>Import-Module -Name "C:\Program Files\Microsoft Azure Active Directory Connect\AdPrep\AdSyncPrep.psm1" `
>Note: if necessary, copy the AdSyncPrep.psm1 file from your Azure AD Connect server. This file is located in Program Files\Microsoft Azure Active Directory Connect\AdPrep
>[!NOTE]If necessary, copy the AdSyncPrep.psm1 file from your Azure AD Connect server. This file is located in Program Files\Microsoft Azure Active Directory Connect\AdPrep
![Device Registration](images/hybridct/device6.png)