Recently Changed Policy Settings Not Taking Effect

Recently Changed Policy Settings Are Not Being Applied At Policy Run

Changes made to a policy will need to be recognized by local device agents.  Ensuring there is a scan of each device in between policy changes and policy run will be the best practice.

Symptoms

Changes were made to a policy within 24 hours of a scheduled or manual run don't apply the changes made to the policy.  

Example

• Device targeting
• Manual approval / rejection
• Schedule changes

Steps to resolution

• Running a manual scan (refresh) of all devices associated with the policy will ensure that each Agent will utilize the most up-to-date settings for the policy.
• Devices are set to scan at least every 24 hours.  If there has been at least that much time in between a policy change and the policy run then no additional action needs to be taken.