Forum Discussion

m_krone's avatar
m_krone
Brass Contributor
Oct 15, 2019

Sync cannot be initialized 0x80190194

I have one device which cannot be synced since 2 month. I am getting the message: Sync cannot be initialized 0x80190194 Any idea about this?   Best regards, Miguel
Intune
Mobile Application Management (MAM)
Mobile Device Management (MDM)
  • RyanWilson's avatar
    RyanWilson
    Jan 28, 2020

    m_kroneI found a solution, hopefully this helps you

     

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\EnterpriseResourceManager\Tracked\[guid]

     

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Enrollments\[some guid which has the enrolment information]

     

    • removed both reg paths above
    • ran dsregcmd /leave
    • reboot device
    • ran AAD connect to provision device back into Azure AD
    • device now Hybrid joined again and registration date is todays date and time / MDM set to none
    • dsregcmd /status shows information is being pulled down, waiting for MDM URLs to populate
    • Info button on settings / user accounts has now disappeared
    • Rebooted device again after 10 minutes
    • Upon reboot the MDM URLs now populated
    • Event logs show device enrolled
    • Info button now available and sync status is successful
    • Intune policies applying
Jesse_Slocum's avatar
Jesse_Slocum
Copper Contributor

RyanWilson 

 

Thank you Sir, however I do not think this is working either because I am remote/vpn and/or this is an AutoPilot device.

 

It will not remove from AAD... I will delete it from AutoPilot and try this again. dsregcmd shows it is not in AAD but when I go to the web console the device is still there and managed.

RyanWilson's avatar
RyanWilson
Copper Contributor
Nov 19, 2020

Jesse_Slocum 

If the device is autopilot then yes remove the hardware hash from your tenant and remove the device from AAD and intune. Then try this the blog again if you still get the problem.

Thanks

  • DheenJaabir's avatar
    DheenJaabir
    Copper Contributor
    Jan 02, 2022
    It has been a sometime but I would like to drop this about the error. I have tested the same behavior in my labs as a part of a client deployment.

    This is because, the MDM and MAM Scoping were not set properly or it is moving downwards.

    If both MDM and MAM scope are set to All, - all the client computers that are not joined to azure or just domain joined will be given a MAM profile with the initial registration. This MAM profile must be removed after changing the scope.

    the easy solution is that we go to the work school - remove the account and reconnect the account. the sync issue would be resolved.

    Thanks, BR, DJ
  • Jesse_Slocum's avatar
    Jesse_Slocum
    Copper Contributor
    Nov 19, 2020

    RyanWilson 

     

    Thank you, it now shows in AAD as Hybrid Azure AD joined however, local registry has not updated nor is the device listed in Intune yet.

     

    Validated Registry that there is no other Enrollments listed as described in your post. Was not able to get your script to work but did a manual lookup in Registry for both values "SSPHyperLink" and then "http://go.microsoft.com/fwlink/?LinkId=255310" and neither returned results.

     

    Only error in Event Viewer is now MDM Push: Failed to renew WNS Push Channel for MDM Push Sessions. Result: (The system cannot find the file specified.).

     

    Have restarted the system multiple times and logged back into the VPN each time.

     

    Thoughts? We do not have pre-login setup or AOVPN at this time.

Resources