Share via

2016345612(Syncml(500) - Intune Compliance Policy Error

Craig Pennington 265 Reputation points
2023-09-05T13:23:04.57+00:00

We have had this recurring issue for a long time now, and despite searching the error all over the place, there seem to be a lot of other IT professionals in the same boat, but no obvious answers.

The error is on the Anti-Virus setting on the default compliance policy.

2016345612(Syncml(500): The recipient encountered an unexpected condition which prevented it from fulfilling the request)User's image

The compliance policy in question is assigned to all users.

This is a very annoying issue as it stops users from being able to access any MSFT apps as it marks the device as non compliant.

we are forced to add users to the exclusion list of the policy until the error clears on it's own days/weeks later.

If anyone has any ideas on what could be the cause or any possible fixes, it would be greatly appreciated

Microsoft Intune Compliance
Microsoft Intune Compliance
Microsoft Intune: A Microsoft cloud-based management solution that offers mobile device management, mobile application management, and PC management capabilities.Compliance: Adhering to rules, standards, policies, and laws.
170 questions
Microsoft Intune
Microsoft Intune
A Microsoft cloud-based management solution that offers mobile device management, mobile application management, and PC management capabilities.
5,237 questions

43 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Aaron Murphy 25 Reputation points
    2024-05-09T17:39:03.67+00:00

    I have recently found that the following commands, in order, fix this issue fairly reliably (syncml issue on either Firewall or AV compliance)

    • Connect to MgGraph with Intune scopes

    Connect-MgGraph -scope DeviceManagementManagedDevices.PrivilegedOperations.All, DeviceManagementManagedDevices.ReadWrite.All,DeviceManagementManagedDevices.Read.All

    $device = Get-MgDeviceManagementManagedDevice -Filter "contains(deviceName,'<DEVICENAME>')"

    Sync-MgDeviceManagementManagedDevice -ManagedDeviceId $device.id

    • Trigger a compliance check via local process on PC (use remote shell or execute locally)

    Start-Process -FilePath "C:\Program Files (x86)\Microsoft Intune Management Extension\Microsoft.Management.Services.IntuneWindowsAgent.exe" -ArgumentList "intunemanagementextension://synccompliance"

    • Trigger a sync via local scheduled task on PC (use remote shell or execute locally)

    Get-ScheduledTask -TaskName “Schedule #3 created by enrollment client” | Start-ScheduledTask

    5 people found this answer helpful.
  2. Efstratios Stratis 36 Reputation points
    2023-10-09T13:36:44.87+00:00

    We have the same issue, no third party AV, laptops updated re-synched multiple times.

    It happens to Win11 laptops only!

    2 people found this answer helpful.
  3. Torben Eriksen - NTI A/S 10 Reputation points
    2024-09-11T09:31:21.14+00:00

    We have the same problem, 600 machines under Intune. Cant live with Microsofts neclect.

    I thought we could rely part of our security on Conditional Access requiring compliance.

    but with 5-10 false positives each month its not reliable

    FIRST i thought it only happend on Hybid joined computers or computers from acquired companies "joined EntraID as is" but we see it frequetly on "pure" Autopilot reshly picked up computers

    Great with the workaround - thanks!

    Cheers from Denmark

    PS: Can we upvote this or is there an article where Microsoft accept the fact that so many of us see this ?

    2 people found this answer helpful.
    0 comments
  4. Nick Eckermann 591 Reputation points
    2024-04-05T14:55:57.59+00:00

    Compliance delays on pre-provisioned devices have been an ongoing issue for us. My own view of what is happening at least for us. We have had multiple cased open going back to early 2023.

     

    Word on the street is updates are coming to Intune 2404 that will help alleviate some of the compliance delays on devices in error due to a transient state. I think the goal here was changes to the reporting of the transient state of the FW/AV components. Think SyncML500 errors. 

     

    Devices that are pre-provisioned and a delay occurs from user enrollments, think sitting for x days before enrollment, are impacted by the day 1 scheduled task not running every 3 minutes for 15 minutes / every 15min for 2 hours for syncing the device. These tasks are scheduled to run after enrollment but are created and started on the pre-provisioned day. When the user finishes the enrollment, they are not updated with the current date for the user enrollment so they don't seem to run any more to help get the device syncing and compliant like you would see on a user only enrollment. 

    \Microsoft\Windows\EnterpriseMgmt{enrollmentGUID}\Schedule #1 created by enrollment client

    \Microsoft\Windows\EnterpriseMgmt{enrollmentGUID}\Schedule #2 created by enrollment client

    https://learn.microsoft.com/en-us/mem/intune/configuration/device-profile-troubleshoot#policy-refresh-intervals

     

    We have noticed users that use Windows Hello for Business log into the device faster than the AV/FW services are fully working after a restart and the login scheduled task (\Microsoft\Windows\EnterpriseMgmt{enrollmentGUID}\Login Schedule created by enrollment client) to kick off a sync reports a transient syncml500 error for those components to Intune on the policy and since the devices have never been compliant, they do not follow the error state grace period and get marked non-compliant. Additional manual sync may be required to get out of this state. Since the scheduled day 1 tasks don't run it is a manual process. Or you may have to wait until the every 8 hour sync happens. \Microsoft\Windows\EnterpriseMgmt{enrollmentGUID}\Schedule #3 created by enrollment client

    https://learn.microsoft.com/en-us/mem/intune/protect/compliance-policy-create-windows#device-security

    https://learn.microsoft.com/en-us/mem/intune/protect/compliance-policy-monitor#device-behavior-with-a-compliance-setting-in-error-state

    2 people found this answer helpful.
    0 comments
  5. Denis Payne 171 Reputation points
    2024-08-14T14:54:10.4633333+00:00

    The below process has fixed InTune MDM not compliant due to 'antivirus syncml(500)' issue for me four times in a row, across 4 different Windows endpoints used by 4 different users.

    1. Install Company Portal app
    2. Use Company Portal app to run a sync
    3. From Intune run a sync for that endpoint
    4. Shutdown the Endpoint
    5. Wait a minute
    6. Power on the endpoint, logon, wait a minute
    7. If still not compliant repeat from step 2

    Had to do this four times on endpoint 1, endpoint 2 needed it done only once, endpoint 3 and 4 needed it done 3 times.

    2 people found this answer helpful.

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.