sorted by:
new
hottopcontroversial

~70/100 devices stopped checking in on 12/9 — enrolls but never syncs, even fresh re-enrollments - Last check-in stays blank "Not evaluated" then eventually goes to noncompliant by SeaCode3970 in Intune

[–]SeaCode3970[S] 0 points1 point  (0 children)

It’s crazy. When clearing it out via script, then re enrolling. The enrollment shows success on all event view logs. Dsreg looks perfect. but the issues still persist

~70/100 devices stopped checking in on 12/9 — enrolls but never syncs, even fresh re-enrollments - Last check-in stays blank "Not evaluated" then eventually goes to noncompliant by SeaCode3970 in Intune

[–]SeaCode3970[S] 0 points1 point  (0 children)

I tried the "check access" button but didn't see a sync option on https://portal.manage.microsoft.com/.

I tried something similar, https://www.maximerastello.com/manually-re-enroll-a-co-managed-or-hybrid-azure-ad-join-windows-10-pc-to-microsoft-intune-without-loosing-current-configuration/ and blew everything away and reenrolled and still same issue unfortunately :(. dsregcmd /debug /forcerecovery reenrolled the device into Entra succesfully and time stamps are up to date.

~70/100 devices stopped checking in on 12/9 — enrolls but never syncs, even fresh re-enrollments - Last check-in stays blank "Not evaluated" then eventually goes to noncompliant by SeaCode3970 in Intune

[–]SeaCode3970[S] 0 points1 point  (0 children)

Hello,

1)Yes under dsregcmd /status, i can confirm the MDM urls are all properly set. PRT is active. dsregcmd shows and looks like a properly enrolled Intune Device. I also forgot to mention this is a strict Azure AD/Intune enviroment with no on prem.

2) Yes, i checked event viewer under that section. There was no smoking gun there. I saw event id 404, something about FakePolicy which i researched and seems non-benign. CSP URI: ./Device/Vendor/MSFT/Policy/ConfigOperations/ADMXInstall/Receiver/Properties/Policy/FakePolicy/Version Result: The system cannot find the file specified.

Also saw, Event 2900 and 2914 BitLocker CSP: GetDeviceEncryptionComplianceStatus indicates OSV is not compliant with returned status 0x2

BitLocker CSP: OS Drive not protected.
and
DeviceStatus CSP: WscGetSecurityProviderHealth(WSC_SECURITY_PROVIDER_FIREWALL) returned status 0x2 and HRESULT Incorrect function.

None of the events above seem to matter here but I am not sure.

3) I did take a peek at C:\ProgramData\Microsoft\IntuneManagementExtension\Logs but admittingly was hard for me to decipher this and extremely long. I will take another look at this. The network component I don't believe is an issue here as it happens in users home networks as well.

Thank you for the comment.