many other attributes that can be used to uniquely identify the device.

details about when the ID was generated.

The hardware hash contains details about the device, such as: It's also possible to do identify a device with a harvesting process that collects the device's hardware hash from within a running Windows installation. As previously mentioned, this step is ideally done by the hardware vendor (OEM, reseller, or distributor) automatically associating the device with an organization.

To identify a device with Windows Autopilot, the device's unique hardware hash must be captured and uploaded to the service. Importing devices is the process of uploading a comma-separated-values (CSV) file that contains device information such as the model and serial number in order to manually add devices.Įnrolling a device is the process of adding devices to Intune. This process can be automated for new enterprise devices manufactured by OEMs that are Windows Autopilot partners.Īdding a device is the process of registering a device with the Windows Autopilot service, (if it is not already registered) and associating it to a tenant ID. The following terms are used to refer to various steps in the registration process: Termĭevice registration happens when a device's hardware hash is associated with the Windows Autopilot service.

Reseller, distributor, or partner registration.

For more information about the ways in which devices can be registered with Windows Autopilot, see the following overview topics: If devices meet certain requirements, they can also be configured for automatic registration with Windows Autopilot. Registration can also be performed within your organization by collecting the hardware identity from new or existing devices and uploading it manually. An OEM or other device provider uses the registration authorization process to perform device registration on your behalf.

Ideally, both of these processes are performed by the OEM, reseller, or distributor from which the devices were purchased.

The device is associated to an Azure tenant ID.

The device's unique hardware identity (known as a hardware hash) is captured and uploaded to the Autopilot service.

Successful registration requires that two processes are complete: Before deploying a device using Windows Autopilot, the device must be registered with the Windows Autopilot deployment service.

Vmix 14 manual registration