|
2 | 2 | title: Tutorial - Proactive remediations |
3 | 3 | titleSuffix: Microsoft Endpoint Manager |
4 | 4 | description: A tutorial on using Proactive remediations to enhance the user |
5 | | -ms.date: 03/07/2022 |
| 5 | +ms.date: 07/05/2022 |
6 | 6 | ms.prod: configuration-manager |
7 | 7 | ms.technology: configmgr-analytics |
8 | 8 | ms.topic: tutorial |
@@ -120,9 +120,24 @@ Proactive remediation scripts need to be encoded in UTF-8. Uploading these scrip |
120 | 120 |
|
121 | 121 | For information about enforcing script signature checks, see [Script requirements](#bkmk_requirements). |
122 | 122 | 1. Click **Next** then assign any **Scope tags** you need. |
123 | | -1. In the **Assignments** step, select the device groups to which you want to deploy the script package. When you're ready to deploy the packages to your users or devices, you can also use filters. For more information, see [Create filters in Microsoft Intune](../intune/fundamentals/filters.md). |
| 123 | +1. In the **Assignments** step, select the device groups to which you want to deploy the script package. When you're ready to deploy the packages to your users or devices, you can also use filters. For more information, see [Create filters in Microsoft Intune](../intune/fundamentals/filters.md). |
124 | 124 | 1. Complete the **Review + Create** step for your deployment. |
125 | 125 |
|
| 126 | +## <a name="bkmk_prs_policy"></a> Client policy retrieval and client reporting |
| 127 | + |
| 128 | +The client retrieves policy for proactive remediations scripts at the following times: |
| 129 | + |
| 130 | +- After a restart of the device or Intune management extension service |
| 131 | +- After a user signs into the client |
| 132 | +- Once every 8 hours |
| 133 | + - The 8 hour script retrieval schedule is fixed based on when the Intune management extension service starts. The schedule isn't altered by user sign ins. |
| 134 | + |
| 135 | +The client reports proactive remediation information at the following times: |
| 136 | + |
| 137 | +- When a script is set to run once, the results are reported after the script runs. |
| 138 | +- Recurring scripts follow a 7 day reporting cycle: |
| 139 | + - Within the first 6 days, the client reports only if a change occurs. The first time the script runs would be considered a change. |
| 140 | + - Every 7 days the client sends a report even if there wasn't a change. |
126 | 141 |
|
127 | 142 | ## <a name="bkmk_prs_monitor"></a> Monitor your script packages |
128 | 143 |
|
|
0 commit comments