Dell laptop runs OOBE several months after being registered and used
We have a Dell Vostro laptop that has started to bring up the Autopilot oobe after login and connected to Wi-Fi, this is several months after first configuration and monitoring with Intune. it started when the end user visited a colleague. It initially stuck on the ESP screen with no access to the internet, we used the accessibility button to connect to local Wi-Fi. We rebooted via a hard power reset and it ended up at the final section on the ESP page after the user used her pin to login, also same after email address to login. It doesn’t complete the OOBE process and let her get to her desktop. Remotely Intune EndPoint manager can monitor and restart the system. Has anyone had this? Intune Support have collected logs and compared with another Autopilot device and gives Intune a clean bill of health! User is couriering me the laptop as Intune Support feel it is either a Windows issue or a hardware one. Suggestions welcome Paul
Windows 365 Administrator built-in role getting 401 unauthorized when enrolling devices
I'm trying to enroll new devices using the get-windowsautopilotinfo script. For this task, I'm trying to use a user assigned with the built-in role "Windows 365 Administrator", which is a new role. https://learn.microsoft.com/en-us/azure/active-directory/roles/permissions-reference#windows-365-administrator Based on the above article, the role has the "microsoft.directory/devices/create" action, with description "Create devices (enroll in Azure AD)". It even says the role can "Enroll and manage devices in Azure AD, including assigning users and policies". But when I execute get-windowsautopilotinfo -online in Windows 10 OOBE Powershell, and login with the Windows 365 Admin. user, I encounter the following error: add-autopilotimportedevice: system.net.http.httprequestexception: 401 unauthorized Anyone else encounter the same problem? Should I just wait a few months for Microsoft to fix the role? 🙂 I've tried waiting 24 hours after assigning the role, same error. It might be unlikely a delay-related issue, a few seconds after assigning the Intune Admin. role, the script executes flawlessly. I've also tried 2 users, 2 separate devices, same error.
