Dual enrollment
This article describes Windows Hello for Business functionalities or scenarios that apply to:
- Deployment type: on-premises , hybrid
- Trust type: certificate trust
- Join type: domain join , Microsoft Entra hybrid join
Important
Dual enrollment does not replace or provide the same security as Privileged Access Workstations feature. Microsoft encourages organizations to use the Privileged Access Workstations for their privileged credential users. Organizations can consider Windows Hello for Business dual enrollment in situations where the Privileged Access feature can't be used. To learn more, see Privileged Access Workstations.
Dual enrollment enables administrators to perform elevated, administrative functions by enrolling both their nonprivileged and privileged credentials on their device.
By design, Windows doesn't enumerate all Windows Hello for Business users from within a user's session. Using the group policy setting, Allow enumeration of emulated smart card for all users, you can configure a device to enumerate all enrolled Windows Hello for Business credentials on selected devices.
With this setting, administrative users can sign in to Windows using their nonprivileged Windows Hello credentials for normal work flow such as email, but can launch Microsoft Management Consoles (MMCs), Remote Desktop Services clients, and other applications by selecting Run as different user or Run as administrator, selecting the privileged user account, and providing their PIN. Administrators can also take advantage of this feature with command-line applications by using runas.exe
combined with the /smartcard
argument. This enables administrators to perform their day-to-day operations without needing to sign in and out, or use fast user switching when alternating between privileged and nonprivileged workloads.
Important
You must configure a Windows computer for Windows Hello for Business dual enrollment before either user (privileged or non-privileged) provisions Windows Hello for Business. Dual enrollment is a special setting that is configured on the Windows Hello container during creation.
Configure Windows Hello for Business dual enrollment
Here are the steps to enable dual enrollment:
- Configure Active Directory to support Domain Administrator enrollment
- Configure dual enrollment using Group Policy
Configure Active Directory to support Domain Administrator enrollment
The designed Windows Hello for Business configuration gives the Key Admins
group read and write permissions to the msDS-KeyCredentialsLink
attribute. You provided these permissions at root of the domain and use object inheritance to ensure the permissions apply to all users in the domain regardless of their location within the domain hierarchy.
Active Directory Domain Services uses AdminSDHolder
to secure privileged users and groups from unintentional modification by comparing and replacing the security on privileged users and groups to match those defined on the AdminSDHolder object on an hourly cycle. For Windows Hello for Business, your domain administrator account might receive the permissions but they disappear from the user object unless you give the AdminSDHolder
read and write permissions to the msDS-KeyCredential
attribute.
Sign in to a domain controller or management workstation with access equivalent to domain administrator.
Type the following command to add the allow read and write property permissions for msDS-KeyCredentialLink attribute for the
Key Admins
group on theAdminSDHolder
object.dsacls "CN=AdminSDHolder,CN=System,DC=domain,DC=com" /g "[domainName\keyAdminGroup]":RPWP;msDS-KeyCredentialLink
where
DC=domain,DC=com
is the LDAP path of your Active Directory domain anddomainName\keyAdminGroup
is the NetBIOS name of your domain and the name of the group you use to give access to keys based on your deployment. For example:dsacls "CN=AdminSDHolder,CN=System,DC=corp,DC=mstepdemo,DC=net" /g "mstepdemo\Key Admins":RPWP;msDS-KeyCredentialLink
To trigger security descriptor propagation, open
ldp.exe
.Select Connection and select Connect... Next to Server, type the name of the domain controller that holds the PDC role for the domain. Next to Port, type 389 and select OK.
Select Connection and select Bind... Select OK to bind as the currently signed-in user.
Select Browser and select Modify. Leave the DN text box blank. Next to Attribute, type RunProtectAdminGroupsTask. Next to Values, type
1
. Select Enter to add this to the Entry List.Select Run to start the task.
Close LDP.
Configure dual enrollment with group policy
You configure Windows to support dual enrollment using the computer configuration portion of a Group Policy object:
Using the Group Policy Management Console (GPMC), create a new domain-based Group Policy object and link it to an organizational Unit that contains Active Directory computer objects used by privileged users.
Edit the Group Policy object from step 1.
Enable the Allow enumeration of emulated smart cards for all users policy setting located under Computer Configuration->Administrative Templates->Windows Components->Windows Hello for Business
Close the Group Policy Management Editor to save the Group Policy object. Close the GPMC.
Restart computers targeted by this Group Policy object.
The computer is ready for dual enrollment. Sign in as the privileged user first and enroll for Windows Hello for Business. Once completed, sign out and sign in as the nonprivileged user and enroll for Windows Hello for Business. You can now use your privileged credential to perform privileged tasks without using your password and without needing to switch users.