Issues enrolling computers that auto log in with a generic account into Intune

Kyle Salce 1 Reputation point
2022-07-19T12:23:03.577+00:00

Hello,

I was looking for help with an issue I'm having currently. I'm currently in the process of enrolling all of the computers in the company into Intune. It has been going relatively smooth for the most part but am currently running into an issue enrolling some of our generic computers such as digital signage computers which auto login with a generic user account. I'm currently using a DEM account along with a provisioning package to enroll those type of computers but for some reason, some of them seem to not fully enroll. I see there's a placeholder listing for it in Intune but the device name looks like an Object ID along with the date of enrollment and the device ownership shows as unknown. What is weird is some of them do end up fully enrolling eventually but others stay in that state. Below are screenshots of what I'm talking about. I did hop on one of the computers that is not fully enrolling and I noticed there a sync error when it tries to sync policies with Intune. The error says "The sync could not be initiated (0x80190190)". I'm assuming this has something to do with it but I'm not sure what to do to correct it. I'm also attaching a screenshot of that as well. Any help would be greatly appreciated.

222280-intuneunknowndevice.png
222259-intunedevicesyncstatus.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,207 questions
0 comments No comments
{count} votes

6 answers

Sort by: Most helpful
  1. Crystal-MSFT 40,381 Reputation points Microsoft Vendor
    2022-07-20T01:00:29.293+00:00

    @Kyle Salce , For our issue, we can wait some more time to see if the device information will be updated.

    For the error "The sync could not be initiated (0x80190190)", most are caused with the previously enrolled information. If the device information is still incorrect after waiting some time, we can choose one affected device and try the following steps to see if it works:

    1. Delete the devices records in both Intune and Azure AD.
    2. Remove the following registry keys on the device.
      HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\EnterpriseResourceManager\Tracked[guid]
      HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Enrollments[some guid which has the enrolment information]
    3. Reboot the device and enroll again to see if it works.

    However, if the issue still persists, please check the event log under Applications and Services Logs > Microsoft > Windows > DeviceManagement-Enterprise-Diagnostic-Provider > Admin to see if there's any error related.

    Please try the above suggestion and if there's any update, feel free to let us know.


    If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
    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.

    0 comments No comments

  2. Kyle Salce 1 Reputation point
    2022-07-20T13:36:16.903+00:00

    Hello,
    Thanks for the reply back. Unfortunately I have tried that solution already and had no luck. It still does not enroll fully after trying to reenroll after deleting those registry keys. I did look in the event viewer and found multiple instances of the error below:

    222640-intunemdmeventviewererror.png


  3. Kyle Salce 1 Reputation point
    2022-07-28T00:56:07.397+00:00

    Hi sorry for the delay in responding. There are no other errors that show in event viewer. That is the only error that shows every single time the sync fails. There are also no conflicting service plans.

    None of these generic accounts have EMS licensing assigned to them but I was told by Microsoft Support that a DEM account can be used to enroll these computers with a provisioning package so I'm not sure why it's not working.


  4. Kyle Salce 1 Reputation point
    2022-08-11T14:44:07.377+00:00

    Hello,
    Sorry for the delay in response. I am able to log in manually with the DEM account on the machine and enroll the computer that way no problem. However, we have over 100 generic computers that I would essentially need to do this with which is not practical whatsoever. Also after I manually log into the computer with the DEM account and enroll it, it will not sync in Intune at all after the machine is logged back in with the generic account. I was able to enroll a machine 3 weeks ago using the DEM account and since I've enrolled it, it has not sync'd in Intune at all after I relogged it back in with the generic account. Based off this, does this mean that the computer will not sync with Intune unless the user account that is currently logged in is licensed with an EMS license? I was under the impression that as long as the device was enrolled with a DEM account, any user can log into it afterwards and it'll still be able to sync policies in Intune. I was even told that by Microsoft support but that does not seem to be the case at all.

    0 comments No comments

  5. Jason Sandys 31,116 Reputation points Microsoft Employee
    2022-08-11T18:05:06.863+00:00

    Can you please define "generic account"? Is this a local account, an AD account, or an AAD account?

    Do you have device-based licensing for these systems?

    0 comments No comments