Forum Discussion

RonaldvdMeer's avatar
RonaldvdMeer
Iron Contributor
Dec 11, 2019

Device restrictions conflict

We have a conflict in our device restrictions after we change another setting in that profile. In the Windows Defender settings we have set 'Time to perform a daily quick scan'. After setting a ano...
Intune
Degerlunden's avatar
Degerlunden
Brass Contributor
Jan 07, 2020

RonaldvdMeer 

Same problem here as well. Hope Microsoft notices this thread and propose a solution.

//Markus

Christian_Hemken's avatar
Christian_Hemken
Copper Contributor
Jan 29, 2020

I see the same situation at one of my customers. Has anyone tried not to use the gui, but work directly with the Defender CSP via Custom policies? I am not sure, if its a bug on the backend or something wrong with the csp that are underlying. 

Kind Regards,

Chris

  • Paul McDonald's avatar
    Paul McDonald
    Copper Contributor
    Jan 29, 2020

    Christian_Hemken I've worked with MS on this for quite a while now and we've tried all sorts (GUI, Custom CSP, PowerShell), still not resolved as we speak

    I was told a fix for this would be in the 2001 service release, it wasn't. Still seeing a conflict

    • Christian_Hemken's avatar
      Christian_Hemken
      Copper Contributor
      Jan 29, 2020

      Paul McDonald Thanks a lot for the answer. I will also open a call with MS to (hopefully) increase the pressure.

      Best,

      Chris

      • RonaldvdMeer's avatar
        RonaldvdMeer
        Iron Contributor
        Feb 01, 2020

        Christian_Hemken The is was fix last evening

        Device Restriction policy setting reports may be inaccurate
        IT202581, Microsoft Intune, Last updated: January 31, 2020 10:57 PM
        Start time: December 16, 2019 1:00 PM, End time: January 31, 2020 8:45 PM
        Status
        Service restored
        User impact
        Admins may have received inaccurate data from their Device Restriction policy setting reports.
         
        Is this post helpful?
         
        Latest message View history
        Title: Device Restriction policy setting reports may be inaccurate User Impact: Admins may have received inaccurate data from their Device Restriction policy setting reports. More info: Policy settings delivered to devices were applying as expected. This issue only impacted reporting. The inaccuracy may have occurred in the "Type of system scan to perform" setting in Device Restrictions. The policy may have appeared to fail even when it successfully applied. Final status: We've confirmed with a subset of affected users that the Device Restriction policy setting reports are now calculating data correctly. Users will have to wait for their device to check-in before Device Restriction policy settings reports are calculated correctly. Admins can force a check-in and recalculation by modifying the title of the Device Restriction policy and point protection policy, then saving these changes. Scope of impact: Your organization was affected by this event, and any admin may have noticed that their Device Restriction policy reports were inaccurate. Start time: Monday, December 16, 2019, 1:00 PM (12:00 PM UTC) End time: Friday, January 31, 2020, 8:45 PM (7:45 PM UTC) Root cause: A recent update introduced a code regression in the affected environment, which was causing policy setting reports to return inaccurate results. Next steps: - We're reviewing our update procedures during our development and testing cycles to better identify similar issues with policy report calculation in the future. This is the final update for the event.

Resources