Skip to content

Commit a231610

Browse files
committed
revised the explanation.
1 parent cf13cb5 commit a231610

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/automation/automation-tutorial-update-management.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -117,7 +117,7 @@ Under **New update deployment**, specify the following information:
117117

118118
For descriptions of the classification types, see [Update classifications](automation-view-update-assessments.md#update-classifications).
119119

120-
* **Updates to include/exclude** - Opens the Include/Exclude page. Updates to be included or excluded are on separate tabs by specifying the KB Article ID numbers. When specifying one or more ID numbers, you need to remove or un-check all classifications with the update deployment.
120+
* **Updates to include/exclude** - Opens the Include/Exclude page. Updates to be included or excluded are on separate tabs by specifying the KB Article ID numbers. When specifying one or more ID numbers, you need to remove or un-check all classifications with the update deployment. This ensures that no other updates are included in your update package when specifying update IDs.
121121

122122
> [!NOTE]
123123
> It's important to know that exclusions override inclusions. For instance, if you define an exclusion rule of `*`, Update Management installs no patches or packages, as they're all excluded. Excluded patches still show as missing from the machine. For Linux machines, if you include a package that has a dependent package that has been excluded, Update Management doesn't install the main package.

0 commit comments

Comments
 (0)