2016345612(Syncml(500) - Intune Compliance Policy Error

Craig Pennington 280 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.
171 questions
Microsoft Intune
Microsoft Intune
A Microsoft cloud-based management solution that offers mobile device management, mobile application management, and PC management capabilities.
5,365 questions
{count} votes

45 answers

Sort by: Most helpful
  1. Laurens Driessen 15 Reputation points
    2024-09-24T07:47:23.2533333+00:00

    Current situation:

    • So we have an Device Compliance Policy for W10/11 where Firewall is Enabled. (MarkDeviceNotCompliant = 1 Days). We use a Dynamic Security group with a DevicePhysicallds filter: "(device.devicePhysicalIds -any _ -startsWith "[OrderID]:User")". Hostnames are less then 15 characters.
    • We use GlobalProtect VPN, which will not work if the device is in de Not Compliant state and shows us the device does not comply with the Compliance Policy because the Edge account is not signed-in and synchronizing. Strangly all other apps work fine. We see that mostly new or reprovisioned with autopilot devices are getting the error on Firewall:

    "2016345612(Syncml(500): The recipient encountered an unexpected condition which prevented it from fulfilling the request)"

    So firstly, we checked the firewall on the devices, which state is Enabled and no errors on the device.
    Disabled the Firewall multiple times and performed multiple quickscans and Syncs after that. As mentioned as a solution on many forms. Sadly it only fixed it on one device.

    So we researched a bit more on the internet and came accross multiple actions we could try as follows:

    • Check Edge > logged on + sync > Sync device no result
    • Laptop login > Password
    • Recently changes password? > about 2 weeks (sometimes Lock device+ signin again works)
    • Defender Quick scan + Sync device no result
    • Sync from Settings > / work/school > No result
    • Disable PANGPS (Windows service for GlobalProtect VPN)
    • Check CPU time > 16h > Rebooted machine > Sync device no result
    • Powershell:

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

    &

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

    Lock/reboot:

    • Lock device and login with password > functional
    • Reboot device + sign-in with password > functional
    • Sync from Settings > / work/school and from company portal

    The strange thing is, we could fix the issue on two devices where we just had to Lock device and Sign in with Password instead of PIN code and sync the device. After that it came compliant.

    On another device we could fix the issue by performing a quickscan and a Sync. After we tried every step mentioned above and after that it came compliant.

    On again another device we could fix the issue, after trying everyting mentioned above, with the mentioned Powershell commands which perform a Sync.

    On again another device we could fix the issue after signing in with the Local Admin Password configured in Intune. Sync within that account and then sign-in again with the primary user.

    Further research:
    [https://learn.microsoft.com/en-us/mem/intune/protect/compliance-policy-create-windows#:~:text=Device%20Security-,Firewall%3A,-Not%20configured%20(](https://learn.microsoft.com/en-us/mem/intune/protect/compliance-policy-create-windows#:~:text=Device%20Security-,Firewall%3A,-Not%20configured%20()
    Checked if there is an GPO with a Firewall settings what could override the Intune policies > no GPO active as far as I could find.

    I also checked the IntuneManagementLogs if I could find something helpfull but sadly it did not pointed me in any direction.

    So, I really have no clue what the root cause of the issue is here because of the multiple actions that could fix the issue.

    2 people found this answer helpful.

  2. JuliusPIV 81 Reputation points
    2023-10-09T19:49:54.3666667+00:00

    I can confirm we are a Defender shop and seeing this as well, specifically for the Firewall setting within Device Compliance. It seems to resolve itself after a few hours, but OP mentions, it locks users out.

    1 person found this answer helpful.

  3. Abhay Kavaswala 5 Reputation points
    2023-10-12T15:54:31.3366667+00:00

    Facing the same issue here.

    1 person found this answer helpful.
    0 comments No comments

  4. Jan Gross 15 Reputation points
    2023-10-16T15:57:33.0133333+00:00

    Hello all,

    unfortunately, we have the same issue and all our computer names are up to 10 characters long. So this (renaming) will not be the solution for everybody.

    1 person found this answer helpful.
    0 comments No comments

  5. Efstratios Stratis 36 Reputation points
    2023-10-16T17:46:39.1+00:00

    Apparently intune thinks (defender firewall) real time or cloud protection setting is not enabled while in reality it is.

    As I mentioned before, retire the machine from intune, delete from azure, than try to reset windows on the machine, let it re enrol to both azure and intune and chances are the issue will be gone. No more compliance errors.

    Resetting machine apparently does not resolve the issue, that's just a workaround on win11 machines. MS need to fix that.

    Let me know if the above procedure helped.

    Thanks

    1 person 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.