Auto MDM Enroll: Device Credential (0x1), Failed (The system tried to delete the JOIN of a drive that is not joined.)

Gustavo Henrique Gomes Silva 1 Reputation point
2021-08-26T19:56:12.42+00:00

I'm joining devices per GPO in Intune. I'm using the Intune standalone license. And I'm having this mistake. I tried to configure by device credential and user credential and the same error.

126888-capture.png

Microsoft Intune Enrollment
Microsoft Intune Enrollment
Microsoft Intune: A Microsoft cloud-based management solution that offers mobile device management, mobile application management, and PC management capabilities.Enrollment: The process of requesting, receiving, and installing a certificate.
1,254 questions
0 comments

5 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Adien Pant 5 Reputation points
    2023-04-09T07:01:08.7433333+00:00

    I am using E3 AND E3 MOBILITY AND SECURITY but I am getting same error and I tried to see setting from Intune portal they are correct and I checked the windows version also that is correct too. can anyone suggest.

    1 person found this answer helpful.
  2. Nick Hogarth 3,436 Reputation points
    2021-08-26T20:51:44.38+00:00

    How long has it been trying to enroll for? Sometimes it can take up to a day. Do you have autoenrollment groups configured and an Azure ad premium license assigned? Do you have any enrollment restrictions blocking Windows 10 MDM in Intune?

    0 comments
  3. Lu Dai-MSFT 28,356 Reputation points
    2021-08-27T02:33:43.697+00:00

    @Anonymous Thanks for posting in our Q&A.

    For this issue, we appreciate your help to collect some information:
    1.Make sure the windows device is Windows 10, version 1709 or later.
    2.Make sure MDM user scope is set to "All" and MAM user scope is set to "None" in Devices > Windows > Windows enrollment > Automatic Enrollment in intune portal.
    126982-image.png

    3.Make sure allow windows MDM in Enroll devices > Enrollment restrictions.
    126991-image.png

    4.Run "dsregcmd /status" from the command line. Confirm that if both "AzureAdJoined" and "DomainJoined" are set to YES. And SSO State section displays "AzureAdPrt" as YES.

    If there is anything update, feel free to let us know.

    If the response is helpful, please click "Accept Answer" and upvote it.
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

  4. Randy Buckman 1 Reputation point
    2021-09-24T16:16:19.053+00:00

    I'd like to see if there's any upate to this also.

    I'm getting similar 76 events with a slightly different error code.

    Auto MDM Enroll: Device Credential (0x1), Failed (Unknown Win32 Error code: 0x80192f76)

    Comanagementhandler.log stating that:

    This device is enrolled to an unexpected vendor, it will be set in co-existence mode.

    There has never been another MDM solution so the error is unclear.

    0 comments
  5. Leonard Palad 1 Reputation point
    2022-07-20T03:44:39.647+00:00

    This is how I managed to fix this error for me:

    purchased (trial) the Microsoft 365 Business Premium

    • (The error message from the add. portal>azure active directory>Mobility (MDM and MAM) that I need to use a 'premium' subscription, so I used the trial business premium., then waited for a few minutes., 'bingo', I managed to bypass the error message, and in the event viewer, I got the below message.

    MDM Session: OMA-DM session ended with the status: (The operation completed successfully.).

    222561-capture.jpg

    222506-capture1.jpg

    Hope this helps.

    Cheers
    Leonard
    P.S. too many IT certifications to mention :-)

    0 comments