Forum Discussion
Solved
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
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
Hi
You may need to remove the token settings to pull down new settings, follow this article i posted awhile back:
https://www.inittogether.uk/2019/12/04/windows-10-device-not-enrolling-into-intune-mdm-after-admt-migration/
Check out the steps at the bottom regarding removing settings files.
Thanks
Ryan
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
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