This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Device control scanning becomes inactive automicatlly

We've had this issue ever since we put up this policy. We have a Group for restricted device access with the "Device control scanning" enabled, however for some of the computers in that group it shows up as "Differs from policy" and "Device control scanning" Inactive.  We can go in there and manually comply with "Group Device control policy" and it will be fine but the next morning the same issue happens.  This has been an ongoing issue not sure if anyone else have had this issue.  We've tried recreating th policy, using the default policy as enabled, etc, but nothing seems to work.

:47271


This thread was automatically locked due to age.
Parents
  • Hello Rullah,

    if it is more or less reproducible the an Agent trace might give some insight. Just the Agent trace is required and the place where the policies are compared can easily be found in the logs. I once had a case where the "live" policy contained a blank (leading or trailing, can't remember) which was stripped when the policy was saved locally. After a restart the comparison failed ...

    Christian

    :47679
Reply
  • Hello Rullah,

    if it is more or less reproducible the an Agent trace might give some insight. Just the Agent trace is required and the place where the policies are compared can easily be found in the logs. I once had a case where the "live" policy contained a blank (leading or trailing, can't remember) which was stripped when the policy was saved locally. After a restart the comparison failed ...

    Christian

    :47679
Children
No Data