6.4 KiB
title, description, ms.author, ms.topic, ms.prod, ms.technology, author, ms.date
| title | description | ms.author | ms.topic | ms.prod | ms.technology | author | ms.date |
|---|---|---|---|---|---|---|---|
| Enroll a Windows 10 device automatically using Group Policy | Enroll a Windows 10 device automatically using Group Policy | maricia | article | w10 | windows | MariciaAlforque | 10/04/2017 |
Enroll a Windows 10 device automatically using Group Policy
Starting in Windows 10, version 1709 you can use a Group Policy to trigger auto-enrollment to MDM for Active Directory (AD) domain joined devices.
Requirements:
- AD-joined PC running Windows 10, version 1709
- Enterprise has MDM service already configured
- Enterprise AD must be registered with Azure AD
Tip
How to configure automatic registration of Windows domain-joined devices with Azure Active Directory
To verify if the device is Azure AD registered, run dsregcmd /status from the command line.
Here is a partial screenshot of the result:
The auto-enrollment relies of the presence of an MDM service and the Azure Active Directory registration for the PC. Starting in Windows 10, version 1607, once the enterprise has registered its AD with Azure AD, a Windows PC that is domain joined is automatically AAD registered.
Note
In Windows 10, version 1709, the enrollment protocol was updated to check whether the device is domain-joined. For details, see [MS-MDE2]: Mobile Device Enrollment Protocol Version 2. For examples, see section 4.3.1 RequestSecurityToken of the MS-MDE2 protocol documentation.
When the auto-enrollment Group Policy is enabled, a task is created in the background that initiates the MDM enrollment. The task will use the existing MDM service configuration from the Azure Active Directory information of the user. If multi-factor authentication is required, the user will get a prompt to complete the authentication. Once the enrollment is configured, the user can check the status in the Settings page.
In Windows 10, version 1709, when the same policy is configured in GP and MDM, the GP policy wins (GP policy is take precedence over MDM). In the future release of Windows 10, we are considering a feature that allows the admin to control which policy takes precedence.
For this policy to work, you must verify that the MDM service provider allows the GP triggered MDM enrollment for domain joined devices.
Configure the auto-enrollment Group Policy for a single PC
This procedure is only for illustration purposes to show how the new auto-enrollment policy works. It is not recommended for the production environment in the enterprise. For bulk deployment, you should use the Group Policy Management Console process.
Requirements:
- AD-joined PC running Windows 10, version 1709
- Enterprise has MDM service already configured
- Enterprise AD must be registered with Azure AD
-
Run GPEdit.msc
Click Start, then in the text box type gpedit.
-
Under Best match, click Edit group policy to launch it.
-
In Local Computer Policy, click Administrative Templates > Windows Components > MDM.
-
Double-click Auto MDM Enrollment with AAD Token.
-
Click Enable, then click OK.
A task is created and scheduled to run every 5 minutes for the duration of 1 day. The task is called " Schedule created by enrollment client for automatically enrolling in MDM from AAD."
To see the scheduled task, launch the Task Scheduler app.
If two-factor authentication is required, you will be prompted to complete the process. Here is an example screenshot.
-
To verify successful enrollment to MDM , click Start > Settings > Accounts > Access work or school, then select your domain account.
-
Click Info to see the MDM enrollment information.
If you do not see the Info button or the enrollment information, it is possible that the enrollment failed. Check the status in Task Scheduler app.
Task Scheduler app
-
Click Start, then in the text box type task scheduler.
-
Under Best match, click Task Scheduler to launch it.
-
In Task Scheduler Library, open Microsoft > Windows , then click EnterpriseMgmt.
To see the result of the task, move the scroll bar to the right to see the Last Run Result. Note that 0x80180026 is a failure message (MENROLL_E_DEVICE_MANAGEMENT_BLOCKED). You can see the logs in the History tab.
If the device enrollment is blocked, your IT admin may have enabled the Disable MDM Enrollment policy. Note that the GPEdit console does not reflect the status of policies set by your IT admin on your device. It is only used by the user to set policies.
Configure the auto-enrollment for a group of devices
Requirements:
- AD-joined PC running Windows 10, version 1709
- Enterprise has MDM service already configured (with Intune or a third party service provider)
- Enterprise AD must be integrated with Azure AD.
- Ensure that PCs belong to same computer group.
- Create a Group Policy Object (GPO) and enable the Group Policy Auto MDM enrollment with AAD token.
- Create a Security Group for the PCs.
- Link the GPO.
- Filter using Security Groups.
- Enforce a GPO link