Forum Discussion
Windows 10 automatic enrollment on a new device
Aside from the troubleshooting steps in the article, make sure the account signing on to Windows is synchronized to Azure AD and has permissions to auto-enroll devices. The scheduled task created by the GPO uses that account for authentication.
In my lab, I have had cases where a user did not sign on during the 24 hour period the scheduled task runs for and had to wait until the GPO refreshed and created the task again. In those cases, a gpupdate /force worked so long as the user had local administrator permissions.
Other than that, you wait.
They are Hybrid Azure AD Joined with a GPO and i wonder if there is any faster way to make this happen then just wait or logging in with the users credentials under "accounts". running a gpupdate /force is not helping either.
Aside from the troubleshooting steps in the article, make sure the account signing on to Windows is synchronized to Azure AD and has permissions to auto-enroll devices. The scheduled task created by the GPO uses that account for authentication.
In my lab, I have had cases where a user did not sign on during the 24 hour period the scheduled task runs for and had to wait until the GPO refreshed and created the task again. In those cases, a gpupdate /force worked so long as the user had local administrator permissions.
Other than that, you wait.