In Windows 10 version 1809 and earlier, it's important to capture the hardware hash and create an Autopilot device profile before you connect a device to the internet. From the Desktop using Settings > AccountsĮach of these methods is described below.During OOBE by using the Diagnostics Page (Windows 11 only).Using Microsoft Endpoint Configuration Manager.The following methods are available to harvest a hardware hash from existing devices: In both Intune Administrator and role-based access control methods, the administrative user also requires consent to use the Microsoft Intune PowerShell enterprise application. Autopilot device management requires only that you enable all permissions under Enrollment programs, except for the four token management options. You can also create a custom Autopilot device manager role by using role-based access control. Azure Active Directory Premium subscriptionĭevice enrollment requires Intune Administrator or Policy and Profile Manager permissions.Windows Autopilot registration overview.For more information about registration, see: This article provides step-by-step guidance for manual registration. Other methods (PKID, tuple) are available through OEMs or CSP partners. So, this process is primarily for testing and evaluation scenarios.ĭevice owners can only register their devices with a hardware hash. Capturing the hardware hash for manual registration requires booting the device into Windows. You can perform Windows Autopilot device registration within your organization by manually collecting the hardware identity of devices (hardware hashes) and uploading this information in a comma-separated-values (CSV) file.
0 kommentar(er)
