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(198.4, 77%, 29%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ETH%3C/text%3E%3C/svg%3E)
I have a problem joining my Windows 10 laptop to my AAD domain. AAD Domain join results in an "oops something went wrong - error caaa2000c. AAD audit logs show the device as being successfully registered, immediately followed by successfully unregistered. I am a Global Admin.
The device was originally Hybrid-Joined although AD has now been decommissioned. I have removed the device from both Intune and Azure AD but this has not resolved the problem. The Device was originally registered for AutoPilot but I have also removed this registration to try and resolve this issue. I have also turned off MFA temporarily on my user account as the local device logs indicate a "user interaction required" issue.
Have ran the enrollment troubleshooter tool and this reports everything is in order for a Domain Join to happen. I've also tried dsregcmd /leave force and dsregcmd /join force, which hasn't worked either.
I don;t know what else to do - I have googled the hell of this issue and tried everything I have come across!
![](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(291.2, 54%, 38%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EDG%3C/text%3E%3C/svg%3E)
Ok, so we had this issue for a period of 2 months in our environment. During whole of that period we had an active ticket with Microsoft and there were no solutions recommended that were helpful. I have a strong feeling that it had to do something with updates, but there was no way of proving it. After that 2-month period, the solution was to run sysprep/generalize on the machines and it helped. Apparently although the machines were clean with the vanilla image of Windows, somehow there were some information regarding previous users left in the background.
Hi,
Do you get any error codes?0x8xxx something? Can you export the logs from the Windows 10 device and upload here or onedrive from the device - User Device Registration. logs in the event logs.
Hi Marshaljs,
Thanks for responding. I think I have resolved the issue (not had chance to test yet) I'll outline what I believe to be the issue in case it is useful for anyone else.
So, I created myself another admin account and tried using that to join the device to the AAD domain. This went without a hitch. I tried joining a different device with my old account, which failed. So the problem is something to do with my specific user account rather than the device as I had been surmising previously.
Went through my account config closely. Found that I (possibly someone else) had removed my account from our main Intune enrolment group, this didn't resolve the issue but looking through the Audit logs noticed I was being blocked through a compliance policy. I have resolved this but have not had chance to verify whether this has resolved the issue. Fingers crossed.
![](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(281.6, 17%, 37%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EGM%3C/text%3E%3C/svg%3E)
@Trevor Hopkins Thank you for sharing the detailed steps, definitely error code was unique, appreciate you sharing the steps which helped to resolve the issue, will help community facing similar issue.
@Trevor Hopkins I'm glad that you were able to resolve your issue and thank you for posting your solution so that others experiencing the same thing can easily reference this! Since the Microsoft Q&A community has a policy that "The question author cannot accept their own answer. They can only accept answers by others ", I'll repost your solution in case you'd like to "Accept " the answer.