Intune Management Extension missing after AutoPilot Reset

Copper Contributor

We're testing the AutoPilot Reset as an easy way to reset devices between users as simply as possible. The reset itself is working, but after resetting and logging in, the Intune Maganament Extension / Engine service is missing from services. Configuration profiles still get applied (power settings, bitlocker, lock screen image etc), but powershell scripts don't run and Win32 apps don't get reinstalled after the reset. The apps and scripts are assigned to the same device groups as the configuration profiles that work and the device is autopilot registered with the self-deploying scenario. If I do a clean installation from Windows 10 Education ISO with autopilot enrollment the extension works properly and apps get installed.


The advanced diagnostic MDM report lists under Managed applications ONLY Modern Apps and the status of all of them is Failed. The Win32 apps are not listed in the report.


I'd like to be able to use the AutoPilot reset since compared to installing from ISO, wiping or fresh starting, it'll retain the Computer name which is a huge help not having to rename them by hand after resetting (I'm working at a university and we might reset 300 shared devices at a time before the new semester starts).


This problem only seems to affect the AutoPilot Reset. Doing a fresh start doesn't break the Intune Management Extension and everything works, BUT I have to rename the computers. It's also important for our dynamic groups that the devices have specific names, so using the serial/random name templates don't do for us.


@Michael Niehaus here I have to give a suggestion to Microsoft: Add the ability to force the device names from Intune or Azure AD in a way that reinstalled computers with the same serial number automatically get the old name if they have been registered in AAD/Intune earlier and have not been deleted. This should be possible since AutoPilot registered devices retain the AAD Device Object through clean installs and resets, once the hardware hashes have been imported.


Another suggestion: Automatically merge/replace Intune device objects with the same serial number at re-enrollment. Currently if I reinstall a computer, let's say, 10 times and it's autopilot registered, It'll appear in Intune 10 times even though it'll only appear in Azure AD once. I don't see the point having the device's old copies in Intune as they have no more effect after the AutoPilot enrollment creates a new device in Intune and attaches the computer to it. Currently I use the automatic deletion of devices not used in a while, but that still leaves the 300 duplicate laptops for at least three months lying around our MDM unless I manually delete them with PowerShell.


Kind Regards,

Benjamin Pettinen

University of Helsinki

0 Replies