11-22-2019 12:03 AM
11-22-2019 12:03 AM
I have a device in intune, its not assigned. Im testing it to get the device in the Autopilot Device Enrollment profile (Deployment Profiles), the mainly problem is, that the device is N/A.
Is there a way to get the device in AD, without a HardwareHash?
11-22-2019 02:04 AM
UPDATE: Did add it in Azure AD (Domain Join), but now cant get the device in Windows Autopilot Deployment Program (Devices)
Does anyone have a solution for this?
11-22-2019 06:41 AM
@Amedian2019 as you are able to add the device in Autopilot, the device is also available in AAD.
The next step is getting the device in an AAD Security group, which can be done by following the instructions here https://docs.microsoft.com/en-us/intune/enrollment/enrollment-autopilot#create-an-autopilot-device-g...
Assign your deployment profile to the security group, give it some time and the profile should get assigned.
11-24-2019 11:07 PM
Ik leg het even in het Nederlands uit, de computer bestaat al, het systeem zit dan ook in Intune en onze AD.
Het probleem is, kunnen we een bestaande apparaat, in de Deployment Profiles krijgen? Zodat we zonder de HardwareHash uit te lezen, op afstand het apparaat in Autopilot kunnen starten.
11-25-2019 07:27 AM
@Amedian2019 I continue in English as i might be interesting for others :)
Yes in the Deployment profile you should set "Convert all targeted devices to Autopilot" to Yes and assign that profile to a security group which your existing device is member of.
That should register this existing device in AutoPilot.
11-25-2019 07:41 AM
11-27-2019 12:25 AM
@Amedian2019 That`s strange. I have seen this work in several tenants. That was always with User-Driven mode, but cannot imagine that this would not work for Self-Deploying.
Are you using hardware from one of the Autopilot supported vendors? If not the issue might be that the vendor isn`t able to provide the hardware hash.
Otherwise I think you should open a support case.