4.5 KiB
title, description, keywords, ms.prod, ms.mktglfcycl, ms.sitesec, ms.pagetype, author, ms.localizationpriority, ms.author, ms.date
| title | description | keywords | ms.prod | ms.mktglfcycl | ms.sitesec | ms.pagetype | author | ms.localizationpriority | ms.author | ms.date |
|---|---|---|---|---|---|---|---|---|---|---|
| Validate Active Directory prerequisites (Windows Hello for Business) | How to Validate Active Directory prerequisites for Windows Hello for Business | identity, PIN, biometric, Hello, passport | w10 | deploy | library | security, mobile | DaniHalfin | high | daniha | 07/27/2017 |
Validate Active Directory prerequisites
Applies to
- Windows 10
This guide only applies to Windows 10, version 1703 or higher.
The key registration process for the On-prem deployment of Windows Hello for Business needs the Windows Server 2016 Active Directory schema. The key-trust model receives the schema extension when the first Windows Server 2016 domain controller is added to the forest. The certificate trust model requires manually updating the current schema to the Windows Server 2016 schema. If you already have a Windows Server 2016 domain controller in your forest, you can skip the next step.
Manually updating Active Directory uses the command-line utility adprep.exe located at <drive>:\support\adprep on the Windows Server 2016 DVD or ISO. Before running adprep.exe, you must identify the domain controller hosting the schema master role.
Discovering schema role
To locate the schema master role holder, open and command prompt and type:
Netdom query fsmo | findstr -i “schema”
The command should return the name of the domain controller where you need to adprep.exe. Update the schema locally on the domain controller hosting the Schema master role.
Updating the Schema
Windows Hello for Business uses asymmetric keys as user credentials (rather than passwords). During enrollment, the public key is registered in an attribute on the user object in Active Directory. The schema update adds this new attribute to Active Directory.
Sign-in to the domain controller hosting the schema master operational role using Enterprise Admin equivalent credentials.
- Open an elevated command prompt.
- Type
cd /d x:\support\adprepwhere x is the drive letter of the DVD or mounted ISO. - To update the schema, type
adprep /forestprep. - Read the Adprep Warning. Type the letter C and press Enter to update the schema.
- Close the Command Prompt and sign-out.
Create the KeyCredential Admins Security Global Group
The Windows Server 2016 Active Directory Federation Services (AD FS) role registers the public key on the user object during provisioning. You assign write and read permission to this group to the Active Directory attribute to ensure the AD FS service can add and remove keys are part of its normal workflow.
Sign-in a domain controller or management workstation with Domain Admin equivalent credentials.
- Open Active Directory Users and Computers.
- Click View and click Advance Features.
- Expand the domain node from the navigation pane.
- Right-click the Users container. Click New. Click Group.
- Type KeyCredential Admins in the Group Name text box.
- Click OK.
Create the Windows Hello for Business Users Security Global Group
The Windows Hello for Business Users group is used to make it easy to deploy Windows Hello for Business in phases. You assign Group Policy and Certificate template permissions to this group to simplify the deployment by simply adding the users to the group. This provides them the proper permissions to provision Windows Hello for Business and to enroll in the Windows Hello for Business authentication certificate.
Sign-in a domain controller or management workstation with Domain Admin equivalent credentials.
- Open Active Directory Users and Computers.
- Click View and click Advanced Features.
- Expand the domain node from the navigation pane.
- Right-click the Users container. Click New. Click Group.
- Type Windows Hello for Business Users in the Group Name text box.
- Click OK.