You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/automation/troubleshoot/update-management.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -33,13 +33,13 @@ Superseded updates are not being correctly indicated as declined so that they ca
33
33
34
34
When a superseded update becomes 100 percent not applicable, you should change the approval state of that update to **Declined**. To do this for all your updates:
35
35
36
-
1. In the Automation Account, select **Update Management** to view machine status. See [View update assessments](manage-update-multi.md#view-an-update-assessment).
36
+
1. In the Automation Account, select **Update Management** to view machine status. See [View update assessments](../manage-update-multi.md#view-an-update-assessment).
37
37
38
38
2. Check the superseded update to make sure that it is 100 percent not applicable.
39
39
40
40
3. Mark the update as declined unless you have a question about the update.
41
41
42
-
4. Select Computers and, in the Compliance column, force a rescan for compliance. See [Manage updates for multiple machines](manage-update-multi.md).
42
+
4. Select Computers and, in the Compliance column, force a rescan for compliance. See [Manage updates for multiple machines](../manage-update-multi.md).
43
43
44
44
5. Repeat the steps above for other superseded updates.
0 commit comments