![]() Microsoft Intune is changing how BitLocker resets occur for reused Windows Autopilot devices in the September (2309) service release. Update to BitLocker Recovery Key Process for Windows Autopilot Select the device that you want to unblock and the select the Unblock button at the top of the page. Under Windows Autopilot Deployment Program, select Devices. In the Windows | Windows devices screen, select Windows enrollment. In the Devices | Overview screen, under By platform, select Windows. In the Home screen, select Devices in the left hand pane. Sign in to the Microsoft Intune admin center. This update only works for OEMs that aren't within the OEM list and doesn't work on the fix pending status. This change in 2310 enables a button in the Autopilot devices section in Intune to manually unblock those devices. This behavior could cause problems if the device needed to be reset or redeployed. This block means that the device could go through self-deployment mode once and then get blocked from doing it again. Customers using these manufacturers were still subjected to the one-time self-deployment mode block. ![]() Starting in 2310, we're making an update to the self-deployment mode for manufacturers that have not opted-in to attesting to removal of Autopilot refurbished devices. Unblock fix pending state for self-deploying mode for disabled OEMs The error codes also include more details on why the device failed to upload, whether the device is assigned to another tenant, or the device already registered to the tenant. If a device couldn't be imported, a notification shows the import error along with the specific lines of the CSV file that received the error. ![]() The 2310 release of Intune adds more clarity to the manual hardware hash upload in the console. In this article Updates to error message for manual device uploads
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |