Deploy Remediations
In brief
The page replaces “Proactive Remediations” with “Remediations,” updates the admin center navigation path, and revises wording across requirements, scripting, privacy, and built-in package guidance.
What Intune admins need to know
Administrators should use the updated Remediations terminology and navigation when locating and deploying script packages.
This summary was assembled from the tracked documentation change. Verify important details in the full Microsoft Learn article.
Documentation change
The comparison below shows only the changed extract. Use the full-page view for complete context.
ms.collection:
- M365-identity-device-management
ms.subservice: apps
description: Learn more about Remediations in Microsoft Intune, including what Remediations are and view any prerequisites and licensing requirements.
Also, learn how to deploy built-in and custom remediation scripts, and learn how to monitor your scripts.ms.date:2025-09-08T00:2026-11-04T00:00:00.0000000Z ms.topic: how-to ms.reviewer: jocallah locale: en-us
Important
Proactive Remediations is renamed to Remediations and is available in the Microsoft Intune admin center at Devices > Manage devices > Scripts and remediations. All references to Proactive Remediations in this documentation are replaced with Remediations. However, theThe term Proactive Remediations might still appear in some blogs and other articles.
Remediations help you fix common support issues before end-users notice issues.
About Remediations
Remediations are script packages that can detect and fix common support issues on a user's device before theyusers even realize there's a problem. Remediations can help reduce support calls and tickets. You can create your own script package or deploy a built-in script package.
Each script package consists of a detection script, a remediation script, and metadata. When you use Intune, you can deploy these script packages and see reports on their effectiveness.
Prerequisites
Whether enrollingyou enroll devices viaby using Intune or Configuration Manager, Remediation scripting has the following requirements:
- Devices must be Microsoft Entra joined or Microsoft Entra hybrid joined and meet one of the following conditions:
Permissions
- For Remediations, the user needs permissions appropriate to their role under the Device configurations category. For more information, see Role-based access control for Microsoft Intune.
- An Intune Service Administrator
is required tomust confirm licensing requirements before using Remediations for the first time.
Script requirements
You can have up to 200 script packages.
A script package can contain a detection script
onlyor both a detection script and a remediation script.- A remediation script only runs if the detection script uses exit code
exit 1, meaning the issue was detected.
- A remediation script only runs if the detection script uses exit code
Ensure the scripts are encoded in UTF-8.
- In the Settings page of creating a script package, if the Enforce script signature check option is enabled,
thenmake sure that the scripts are encoded in UTF-8, not UTF-8 BOM (Byte Order Mark).
- In the Settings page of creating a script package, if the Enforce script signature check option is enabled,
The maximum allowed output size limit is 2,048 characters.
In the Settings page of creating a script package, if the Enforce script signature check option is enabled,
thenthe script runs using the device's PowerShell execution policy. The default execution policy for Windows client computers is Restricted. The default execution for Windows Server devices is RemoteSigned. For more information, see PowerShell execution policies.- Scripts built into Remediations are signed and the certificate is added to the Trusted Publishers certificate store of the device.
- When
usingyou use non-Microsoft scripts that are signed, make sure the certificate is in the Trusted Publishers certificate store. As with any certificate, the device must trust the certificate authority. - Scripts without Enforce script signature check use the Bypass execution policy.
Don't put reboot commands in detection or remediations scripts.
Don't include any type of sensitive information in
scripts (suchscripts, such aspasswords)passwords.Don't include personal data in
scriptsscripts.Don't use scripts to collect personal data from
devicesdevices.Always follow privacy best
practicespractices.
Deploy built-in script packages
There areUse the built-in script packages you can use to get started with Remediations. The Microsoft Intune Management Extension service gets the scripts from Intune and runs them. TheAssign the following built-in script packages just need to be assigned:packages:
- Update stale Group Policies
–. Stale Group Policies can lead to helpdesk tickets related to connectivity and internal resource access. - Restart Office Click-to-run service
–. When the Click-to-run service is stopped, Office apps fail tostart leadingstart, which leads to helpdesk calls.
To assign the script package:
- In the Microsoft Intune admin center, go to Devices > Manage devices > Scripts and remediations node, and select one of the built-in script packages.
- Select Properties, and then next to the Assignments heading, select Edit.
- Choose the groups you want to Assign to and any Excluded groups for the script package.
To change theScope tags, selectSelect Edit then Select scope tags to change the Scope tags.To change the schedule, selectSelect the ellipses and choose Edit tospecifychange the schedule. Specify yoursettings. Selectsettings and select Apply to save your changes.- When you're done, select Review + save.
Schedule options for assignments
When you configure the assignment of a script package, you can define how often the remediation runs by using one of the following Schedule options:
- Once
– Execute: Run the remediation one time only, at a specified date and time. - Hourly
–: Run the remediation on an hourly basis, with a configurable interval, like every n hours. The value must be less than 24 hours. - Daily
– Execute: Run the remediation daily at a specified time.
Execution behavior:behavior
- Remediations run based on the device's local time, by default. To schedule by Coordinated Universal Time, select Use UTC.
- If a scheduled run is missed, the remediation runs when the device is online, and as soon as possible.
For nonurgent or resource-heavy scripts, use less frequent schedules (such as every seven days) toTo reduce performance effects on thedevice.device, use less frequent schedules, such as every seven days, for nonurgent or resource-heavy scripts.
Performance recommendations
To reduce the effect of Remediations on device performance:
- Assign only the script packages that each device requires. Every script runs in PowerShell and consumes CPU and battery resources.
- Avoid resource-intensive scripts and frequent schedules. For nonurgent or resource-intensive scripts, use a less frequent schedule, such as every
7seven days. - Configure detection scripts to return stable, actionable results. Avoid values that change with every run, such as timestamps.
Create and deploy custom script packages
The Microsoft Intune Management Extension service gets the scripts from Intune and runs them. The service reruns the scripts are rerun every 24 hours. You can copy the provided scripts and deploy them, or you can create your own script packages. To deploy script packages, follow the instructions in the next section.
Copy the provided detection and remediation scripts
Copy the scripts from the PowerShell scriptsarticle.
- Script files whose names start with
Detectare detection scripts. Remediation scripts start withRemediate. - For a description of the scripts, see the Script descriptions.
- Script files whose names start with
Save each script by using the provided name. The name is also in the comments at the top of each script. Ensure the saved scripts are encoded in UTF-8.
- You can use a different script name, but it
wondoesn't match the name listed in the Script descriptions.
- You can use a different script name, but it
Deploy the script packages
Remediation scripts need to be encoded in UTF-8. Uploading these scripts rather than editing them directly in your browser helps ensure that the script encoding is correct so your devices can executerun them.
In the Microsoft Intune admin center, go to Devices > Manage devices > Scripts and remediations.
Choose the Create script package button to create a script package.
- Browse to the
.ps1file. - Choose the file and select Open to upload it.
The detection script must use exit code
exit 1if the target issue is detected. If there's any other exit code, the remediation script won'trun. Includingrun, including an empty output,sincebecause it results in an issue isn't found state. Review the Sample detection script for an example of exit code usage.You need the corresponding detection and remediation script to be in the same package. For example, the
Detect_Expired_User_Certificates.ps1detection script corresponds with theRemediate_Expired_User_Certificates.ps1remediation script.- Run script in 64-bit PowerShell: No
For information about enforcing script signature checks, see Script requirements.
- Browse to the
Select Next, then assign any Scope tags you need.
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.
Note
Run a remediation script on-demand (preview)
You can useUse the Run remediation device action to run a remediation script on-on demand tofor a single Windows device.
Prerequisites for running a remediation script on-demand
- Configure Remediations
must already be configuredbefore you can use a remediation scriptcan be used on-on demand. TheMake built-in or custom script packagesmust beavailable for users to run a remediationon-on demand.However, theyYou don't need tobe assignedassign them to a user or device.You can useUse Scope tags to limit which remediation script packages a user can see.Users must beBe an IntuneAdminsadmin or have a role with the Run remediationpermission (availablepermission, available under Remote tasks). During the public preview, the user must also have Organization:Read.Read.DevicesEnsure devices are online andable tocan communicate with Intune and Windows Push Notification Service (WNS) during the remote action.- The Intune Management Extension must be installed on devices. The installation is done automatically when a Win32 app, PowerShell script, or Remediation is assigned to a user or device.
How to run a Remediation script on-demand
- Sign in to the Microsoft Intune admin center.
NavigateGo to Devices > By platform > Windows>, and select a supported device.- On the device's Overview page, select ... > Run remediation (preview).
- In the Run remediation (preview) pane, select the Script package you want to run from the list. Select View details to see properties of the script
packagepackage, like detection and remediation script contents, description, and configured settings. - To run the remediation on-demand, select Run remediation.
Note
Only a singleYou can issue only one Run remediation device actioncan be issuedat a time for the same device. If you run multiple Run remediation device actions in a short period of time to a device, they can overwrite each other.- The device
will notdoesn't receive the Run remediation device action if the device is offline or can't successfully communicate with Intune or Windows Push Notification Service (WNS) when you send the deviceaction is sent.action.
Client policy retrieval and client reporting
The client retrieves policy for Remediation scripts at the following times:
After a restart of the device or Intune management extension service
After a user signs
intoin to the clientOnce every 8 hours
- The
88-hour script retrieval schedule is fixed based on when the Intune management extension service starts. User sign-ins don't alter the schedule.
- The
The client reports Remediation information at the following times:
When a script is set to run once, the client reports the results
are reportedafter the script runs.Recurring scripts follow a
sevenseven-day reporting cycle:- Within the first six days, the client reports only if a change occurs. The first time the script runs
would beis considered a change. - Every seven
daysdays, the client sends a report even if there wasn't a change.
- Within the first six days, the client reports only if a change occurs. The first time the script runs
Monitor your script packages
In the Microsoft Intune admin center, go to Devices > Manage devices > Scripts and remediations
, you. You can see an overview of your detection and remediation status.Select Device status to get status details for each device in your deployment. You can view the status of Remediations that are assigned or run on-demand to a device.
Sign in to the Microsoft Intune admin center.
NavigateGo to Devices > By platform > Windows>, and then select a supported device.Select Remediations in the Monitor section.
Known Issuesissues
When you apply filters such as "Author" or "Status,"Status, or usinguse the Export option on the Remediations page of Scripts and remediations, you include only the currently loaded script packages are included.packages. To include all scripts, scroll until the full list is loaded.
Note
@@ -11,8 +11,8 @@ ms.service: microsoft-intune ms.collection: - M365-identity-device-management ms.subservice: apps-description: Learn more about Remediations in Microsoft Intune, including what Remediations are and view any prerequisites and licensing requirements. Also, learn how to deploy built-in and custom remediation scripts, and learn how to monitor your scripts.-ms.date: 2025-09-08T00:00:00.0000000Z+description: Learn more about Remediations in Microsoft Intune, including what Remediations are and view any prerequisites and licensing requirements.+ms.date: 2026-11-04T00:00:00.0000000Z ms.topic: how-to ms.reviewer: jocallah locale: en-us@@ -45,7 +45,7 @@ platformId: cd2c24ef-bb7f-1486-9c01-85435be4937b Important
-**Proactive Remediations** is renamed to **Remediations** and is available in the Microsoft Intune admin center at **Devices** > **Manage devices** > **Scripts and remediations**. All references to Proactive Remediations in this documentation are replaced with **Remediations**. However, the term Proactive Remediations might still appear in some blogs and other articles.
+*Proactive Remediations* is renamed to *Remediations* and is available in the Microsoft Intune admin center at **Devices** > **Manage devices** > **Scripts and remediations**. All references to Proactive Remediations in this documentation are replaced with *Remediations*. The term *Proactive Remediations* might still appear in some blogs and other articles.
Remediations help you fix common support issues before end-users notice issues.
@@ -62,13 +62,13 @@ In this article, you learn how to:
## About Remediations
-Remediations are script packages that can detect and fix common support issues on a user's device before they even realize there's a problem. Remediations can help reduce support calls and tickets. You can create your own script package or deploy a built-in script package.
+Remediations are script packages that can detect and fix common support issues on a user's device before users even realize there's a problem. Remediations can help reduce support calls and tickets. You can create your own script package or deploy a built-in script package.
Each script package consists of a detection script, a remediation script, and metadata. When you use Intune, you can deploy these script packages and see reports on their effectiveness.
## Prerequisites
-Whether enrolling devices via Intune or Configuration Manager, Remediation scripting has the following requirements:
+Whether you enroll devices by using Intune or Configuration Manager, Remediation scripting has the following requirements:
- Devices must be Microsoft Entra joined or Microsoft Entra hybrid joined and meet one of the following conditions:
@@ -88,79 +88,84 @@ Remediations require users of the devices to have one of the following licenses: ### Permissions
- For Remediations, the user needs permissions appropriate to their role under the **Device configurations** category. For more information, see [Role-based access control for Microsoft Intune](../../fundamentals/role-based-access-control/overview).
-- An [Intune Service Administrator](/en-us/azure/active-directory/users-groups-roles/directory-assign-admin-roles#intune-service-administrator-permissions) is required to confirm licensing requirements before using Remediations for the first time.
+- An [Intune Service Administrator](/en-us/azure/active-directory/users-groups-roles/directory-assign-admin-roles#intune-service-administrator-permissions) must confirm licensing requirements before using Remediations for the first time.
### Script requirements
- You can have up to 200 script packages.
-- A script package can contain a detection script only or both a detection script and a remediation script.
+- A script package can contain a detection script or both a detection script and a remediation script.
+
- A remediation script only runs if the detection script uses exit code `exit 1`, meaning the issue was detected.
- Ensure the scripts are encoded in UTF-8.
- - In the Settings page of creating a script package, if the **Enforce script signature check** option is enabled, then make sure that the scripts are encoded in UTF-8, not UTF-8 BOM (Byte Order Mark).
+
+ - In the Settings page of creating a script package, if the **Enforce script signature check** option is enabled, make sure that the scripts are encoded in UTF-8, not UTF-8 BOM (Byte Order Mark).
- The maximum allowed output size limit is 2,048 characters.
-- In the Settings page of creating a script package, if the **Enforce script signature check** option is enabled, then the script runs using the device's PowerShell execution policy. The default execution policy for Windows client computers is **Restricted**. The default execution for Windows Server devices is **RemoteSigned**. For more information, see [PowerShell execution policies](/en-us/powershell/module/microsoft.powershell.core/about/about_execution_policies#powershell-execution-policies).
+- In the Settings page of creating a script package, if the **Enforce script signature check** option is enabled, the script runs using the device's PowerShell execution policy. The default execution policy for Windows client computers is **Restricted**. The default execution for Windows Server devices is **RemoteSigned**. For more information, see [PowerShell execution policies](/en-us/powershell/module/microsoft.powershell.core/about/about_execution_policies#powershell-execution-policies).
+
- Scripts built into Remediations are signed and the certificate is added to the **Trusted Publishers** certificate store of the device.
- - When using non-Microsoft scripts that are signed, make sure the certificate is in the **Trusted Publishers** certificate store. As with any certificate, the device must trust the certificate authority.
+ - When you use non-Microsoft scripts that are signed, make sure the certificate is in the **Trusted Publishers** certificate store. As with any certificate, the device must trust the certificate authority.
- Scripts without **Enforce script signature check** use the **Bypass** execution policy.
- Don't put reboot commands in detection or remediations scripts.
-- Don't include any type of sensitive information in scripts (such as passwords)
-- Don't include personal data in scripts
-- Don't use scripts to collect personal data from devices
-- Always follow privacy best practices
+- Don't include any type of sensitive information in scripts, such as passwords.
+- Don't include personal data in scripts.
+- Don't use scripts to collect personal data from devices.
+- Always follow privacy best practices.
## Deploy built-in script packages
-There are built-in script packages you can use to get started with Remediations. The **Microsoft Intune Management Extension** service gets the scripts from Intune and runs them. The following built-in script packages just need to be assigned:
+Use the built-in script packages to get started with Remediations. The **Microsoft Intune Management Extension** service gets the scripts from Intune and runs them. Assign the following built-in script packages:
-- **Update stale Group Policies** – Stale Group Policies can lead to helpdesk tickets related to connectivity and internal resource access.
-- **Restart Office Click-to-run service** – When the Click-to-run service is stopped, Office apps fail to start leading to helpdesk calls.
+- **Update stale Group Policies**. Stale Group Policies can lead to helpdesk tickets related to connectivity and internal resource access.
+- **Restart Office Click-to-run service**. When the Click-to-run service is stopped, Office apps fail to start, which leads to helpdesk calls.
To assign the script package:
-1. In the [Microsoft Intune admin center](https://go.microsoft.com/fwlink/?linkid=2109431), go to **Devices** > **Manage devices** > **Scripts and remediations** node, select one of the built-in script packages.
-2. Select **Properties**, then next to the **Assignments** heading, select **Edit**.
+1. In the [Microsoft Intune admin center](https://go.microsoft.com/fwlink/?linkid=2109431), go to **Devices** > **Manage devices** > **Scripts and remediations** node, and select one of the built-in script packages.
+2. Select **Properties**, and then next to the **Assignments** heading, select **Edit**.
3. Choose the groups you want to **Assign to** and any **Excluded groups** for the script package.
-4. To change the **Scope tags**, select **Edit** then **Select scope tags**.
-5. To change the schedule, select the ellipses and choose **Edit** to specify your settings. Select **Apply** to save your changes.
+4. Select **Edit** then **Select scope tags** to change the **Scope tags**.
+5. Select the ellipses and choose **Edit** to change the schedule. Specify your settings and select **Apply** to save your changes.
6. When you're done, select **Review + save**.
### Schedule options for assignments
-When you configure the assignment of a script package, you can define how often the remediation runs using one of the following **Schedule** options:
+When you configure the assignment of a script package, define how often the remediation runs by using one of the following **Schedule** options:
-- **Once** – Execute the remediation one time only, at a specified date and time.
-- **Hourly** – Run the remediation on an hourly basis, with a configurable interval, like every *n* hours. The value must be less than 24 hours.
-- **Daily** – Execute the remediation daily at a specified time.
+- **Once**: Run the remediation one time only, at a specified date and time.
+- **Hourly**: Run the remediation on an hourly basis, with a configurable interval, like every *n* hours. The value must be less than 24 hours.
+- **Daily**: Run the remediation daily at a specified time.
-#### Execution behavior:
+#### Execution behavior
- Remediations run based on the device's local time, by default. To schedule by Coordinated Universal Time, select **Use UTC**.
- If a scheduled run is missed, the remediation runs when the device is online, and as soon as possible.
-- For nonurgent or resource-heavy scripts, use less frequent schedules (such as every seven days) to reduce performance effects on the device.
+- To reduce performance effects on the device, use less frequent schedules, such as every seven days, for nonurgent or resource-heavy scripts.
### Performance recommendations
To reduce the effect of Remediations on device performance:
- Assign only the script packages that each device requires. Every script runs in PowerShell and consumes CPU and battery resources.
-- Avoid resource-intensive scripts and frequent schedules. For nonurgent or resource-intensive scripts, use a less frequent schedule, such as every 7 days.
+- Avoid resource-intensive scripts and frequent schedules. For nonurgent or resource-intensive scripts, use a less frequent schedule, such as every seven days.
- Configure detection scripts to return stable, actionable results. Avoid values that change with every run, such as timestamps.
## Create and deploy custom script packages
-The **Microsoft Intune Management Extension** service gets the scripts from Intune and runs them. The scripts are rerun every 24 hours. You can copy the provided scripts and deploy them, or you can create your own script packages. To deploy script packages, follow the instructions in the next section.
+The **Microsoft Intune Management Extension** service gets the scripts from Intune and runs them. The service reruns the scripts every 24 hours. You can copy the provided scripts and deploy them, or you can create your own script packages. To deploy script packages, follow the instructions in the next section.
### Copy the provided detection and remediation scripts
-1. Copy the scripts from the [PowerShell scripts](ref-remediation-scripts#powershell-scripts-for-remediations)article.
+1. Copy the scripts from the [PowerShell scripts](ref-remediation-scripts#powershell-scripts-for-remediations) article.
+
- Script files whose names start with `Detect` are detection scripts. Remediation scripts start with `Remediate`.
- For a description of the scripts, see the [Script descriptions](ref-remediation-scripts#script-descriptions).
-2. Save each script using the provided name. The name is also in the comments at the top of each script. Ensure the saved scripts are encoded in UTF-8.
- - You can use a different script name, but it won't match the name listed in the [Script descriptions](ref-remediation-scripts#script-descriptions).
+2. Save each script by using the provided name. The name is also in the comments at the top of each script. Ensure the saved scripts are encoded in UTF-8.
+
+ - You can use a different script name, but it doesn't match the name listed in the [Script descriptions](ref-remediation-scripts#script-descriptions).
### Deploy the script packages
-Remediation scripts need to be encoded in UTF-8. Uploading these scripts rather than editing them directly in your browser helps ensure that the script encoding is correct so your devices can execute them.
+Remediation scripts need to be encoded in UTF-8. Uploading these scripts rather than editing them directly in your browser helps ensure that the script encoding is correct so your devices can run them.
1. In the [Microsoft Intune admin center](https://go.microsoft.com/fwlink/?linkid=2109431), go to **Devices** > **Manage devices** > **Scripts and remediations**.
2. Choose the **Create script package** button to create a script package.
@@ -173,7 +178,7 @@ Remediation scripts need to be encoded in UTF-8. Uploading these scripts rather 2. Browse to the `.ps1` file.
3. Choose the file and select **Open** to upload it.
- The detection script must use exit code `exit 1` if the target issue is detected. If there's any other exit code, the remediation script won't run. Including an empty output, since it results in an *issue isn't found* state. Review the [Sample detection script](ref-remediation-scripts#script-descriptions) for an example of exit code usage.
+ The detection script must use exit code `exit 1` if the target issue is detected. If there's any other exit code, the remediation script won't run, including an empty output, because it results in an *issue isn't found* state. Review the [Sample detection script](ref-remediation-scripts#script-descriptions) for an example of exit code usage.
You need the corresponding detection and remediation script to be in the same package. For example, the `Detect_Expired_User_Certificates.ps1` detection script corresponds with the `Remediate_Expired_User_Certificates.ps1` remediation script.
@@ -185,7 +190,7 @@ Remediation scripts need to be encoded in UTF-8. Uploading these scripts rather - **Run script in 64-bit PowerShell**: No
For information about enforcing script signature checks, see Script requirements.
-6. Select **Next** then assign any **Scope tags** you need.
+6. Select **Next**, then assign any **Scope tags** you need.
7. 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](../../fundamentals/filters/overview).
Note
@@ -195,50 +200,50 @@ Remediation scripts need to be encoded in UTF-8. Uploading these scripts rather
## Run a remediation script on-demand (preview)
-You can use the **Run remediation** device action to run a remediation script on-demand to a single Windows device.
+Use the **Run remediation** device action to run a remediation script on demand for a single Windows device.
### Prerequisites for running a remediation script on-demand
-- Remediations must already be configured before a remediation script can be used on-demand.
-- The built-in or custom script packages must be available for users to run a remediation on-demand. However, they don't need to be assigned to a user or device. You can use **Scope tags** to limit which remediation script packages a user can see.
-- Users must be Intune Admins or have a role with the **Run remediation** permission (available under **Remote tasks**). During the public preview, the user must also have Organization: Read.
-- Devices are online and able to communicate with Intune and [Windows Push Notification Service (WNS)](../../fundamentals/endpoints#windows-push-notification-services-wns-dependencies) during the remote action.
+- Configure Remediations before you can use a remediation script on demand.
+- Make built-in or custom script packages available for users to run a remediation on demand. You don't need to assign them to a user or device. Use **Scope tags** to limit which remediation script packages a user can see.
+- Be an Intune admin or have a role with the **Run remediation** permission, available under **Remote tasks**. During the public preview, the user must also have **Organization: Read**.
+- Ensure devices are online and can communicate with Intune and [Windows Push Notification Service (WNS)](../../fundamentals/endpoints#windows-push-notification-services-wns-dependencies) during the remote action.
- The [Intune Management Extension](management-extension-windows) must be installed on devices. The installation is done automatically when a Win32 app, PowerShell script, or Remediation is assigned to a user or device.
### How to run a Remediation script on-demand
1. Sign in to the [Microsoft Intune admin center](https://go.microsoft.com/fwlink/?linkid=2109431).
-2. Navigate to **Devices** > **By platform** > **Windows** > select a supported device.
+2. Go to **Devices** > **By platform** > **Windows**, and select a supported device.
3. On the device's **Overview** page, select **...** > **Run remediation (preview).**
-4. In the **Run remediation (preview)** pane, select the **Script package** you want to run from the list. Select **View details** to see properties of the script package like detection and remediation script contents, description, and configured settings.
+4. In the **Run remediation (preview)** pane, select the **Script package** you want to run from the list. Select **View details** to see properties of the script package, like detection and remediation script contents, description, and configured settings.
5. To run the remediation on-demand, select **Run remediation**.
Note
-- Only a single **Run remediation** device action can be issued at a time for the same device. If you run multiple **Run remediation** device actions in a short period of time to a device, they can overwrite each other.
-- The device will not receive the **Run remediation** device action if the device is offline or can't successfully communicate with Intune or Windows Push Notification Service (WNS) when the device action is sent.
+- You can issue only one **Run remediation** device action at a time for the same device. If you run multiple **Run remediation** device actions in a short period of time to a device, they can overwrite each other.
+- The device doesn't receive the **Run remediation** device action if the device is offline or can't successfully communicate with Intune or Windows Push Notification Service (WNS) when you send the device action.
## Client policy retrieval and client reporting
The client retrieves policy for Remediation scripts at the following times:
- After a restart of the device or Intune management extension service
-- After a user signs into the client
+- After a user signs in to the client
- Once every 8 hours
- - The 8 hour script retrieval schedule is fixed based on when the Intune management extension service starts. User sign-ins don't alter the schedule.
+ - The 8-hour script retrieval schedule is fixed based on when the Intune management extension service starts. User sign-ins don't alter the schedule.
The client reports Remediation information at the following times:
-- When a script is set to run once, the results are reported after the script runs.
-- Recurring scripts follow a seven day reporting cycle:
+- When a script is set to run once, the client reports the results after the script runs.
+- Recurring scripts follow a seven-day reporting cycle:
- - Within the first six days, the client reports only if a change occurs. The first time the script runs would be considered a change.
- - Every seven days the client sends a report even if there wasn't a change.
+ - Within the first six days, the client reports only if a change occurs. The first time the script runs is considered a change.
+ - Every seven days, the client sends a report even if there wasn't a change.
## Monitor your script packages
-1. In the [Microsoft Intune admin center](https://go.microsoft.com/fwlink/?linkid=2109431), go to **Devices** > **Manage devices** > **Scripts and remediations**, you can see an overview of your detection and remediation status.
+1. In the [Microsoft Intune admin center](https://go.microsoft.com/fwlink/?linkid=2109431), go to **Devices** > **Manage devices** > **Scripts and remediations**. You can see an overview of your detection and remediation status.
[](media/deploy-remediations/remediations-report-overview.png#lightbox)
2. Select **Device status** to get status details for each device in your deployment.
@@ -254,12 +259,12 @@ To help you easily analyze returned outputs, use the **Export** option to save t You can view the status of Remediations that are assigned or run on-demand to a device.
1. Sign in to the [Microsoft Intune admin center](https://go.microsoft.com/fwlink/?linkid=2109431).
-2. Navigate to **Devices** > **By platform** > **Windows** > select a supported device.
+2. Go to **Devices** > **By platform** > **Windows**, and then select a supported device.
3. Select **Remediations** in the **Monitor** section.
-## Known Issues
+## Known issues
-When you apply filters such as "Author" or "Status," or using the **Export** option on the **Remediations** page of **Scripts and remediations**, only the currently loaded script packages are included. To include all scripts, scroll until the full list is loaded.
+When you apply filters such as *Author* or *Status*, or use the **Export** option on the **Remediations** page of **Scripts and remediations**, you include only the currently loaded script packages. To include all scripts, scroll until the full list is loaded.
Note
