This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(179.20000000000002, 86%, 27%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMP%3C/text%3E%3C/svg%3E)
Hello community.
I previously created a question, but it no longer matches the problem and I would like to rephrase and ask a new question.
We use the Provision Package to join the on-prem device to Azure AD.
The problem is that the device immediately deletes itself as soon as it joins AAD.
If you try to add a device manually, an error occurs:
Error 8018000a: “Something went wrong. The device is already enrolled. You can contact your system administrator with the error code 8018000a.
We migrated some devices earlier (test). We did NOT have problems if we used the ISO downloaded from Microsoft. And we had problems with devices on which the system is installed from a different ISO.
We made SYSPREP
"%WINDIR%\system32\sysprep\sysprep.exe /generalize /shutdown /oobe" and right after that the device connected (Provision Package worked).
The essence of the problem: we have almost all devices installed with an ISO with which there is a problem. It's very hard to sysprep during migration. The entire migration process is fully automated.
I would like to know what needs to be changed in the system so that such a problem does not arise? Which system ID is critical during device join, how does Azure AD determine which system is added and which is not? Is it possible to use a simple script to fix this?
Hello
@Mountain Pond , I will be working on this issue and come back ASAP.
Great to hear about that @Mountain Pond . What were the differences between both ISO?
The problem is not with the ISO. The problem is that the device was previously registered.
@Mountain Pond Yes I understan that, however "We did NOT have problems if we used the ISO downloaded from Microsoft. And we had problems with devices on which the system is installed from a different ISO". Was the latter customized. If so, how?
The problem is not with the ISO.
I made sure that my account I was testing with didn't have Intune auto enrollment permissions.
I had no problems with this. As soon as I connected the work profile, the device was registered in Azure AD and that's it.
But after I allowed my account to automatically add the device to Intune. I started having problems too.
For some reason, if a user adds a worker account and it has auto enrollment permissions. That device will NOT appear in Intune, but something changes in the system itself, as if the device is already in Intune.
Therefore, repeated attempts to add a device to Intune end in an error.
Two workarounds: disable autoenrollment in Intune, or clean up the registry before joining to Azure AD. Or manually disable all work profiles on the device.
This seems to be a known issue and unfortunately no one has fixed it yet in MS.
Hello @Mountain Pond , my understanding is that registering a device works w/o problems but once you try to join (or register too?) the device with auto-enrollment enabled you will hit the 'DeviceAADJoin' failed with '0x8018000A' error. Thus, they won't get added to Azure AD or to intune but Intune registry entries will appear on the device. Is that correct?
The entry in the registry appears at the time of registration of the device. During the connection, it interferes and an error occurs because of it.