Use case: Remediating missing patches
This topic provides instructions on how to identify and remediate missing patches.
What do I need to get started?
- A user account with privileges to access either BMC Helix Automation Console or TrueSight Automation Console.
You do not require administrative privileges for this use case.
- A patch administrator must have imported patch catalogs from TrueSight Server Automation.
- A patch administrator must have defined Service Level Agreement deadlines and warning thresholds.
How to identify and remediate?
This describes the steps to identify and remediate missing patches.
1. Create and run a patch policy.
For details, see Working with patch policies.
2. View the policy scan results.
After a policy scans the assets, the results appear on the Manage Patch Policies page and on the Dashboard.
On the Manage Patch Policies page, you can view these results:
- Total number of assets scanned by the policy
- Date, time, and duration of the policy scan
- Number of assets that were scanned successfully or with warnings, and failed scans
- List of assets scanned by the policy and the number of missing and installed patches on these assets
- List of installed and missing patches for each scanned asset
- Logs for each asset, which contains errors and warnings
The Dashboard provides a consolidated graphical view of the patch compliance. On the Dashboard, you can view these results:
- Patch compliance percentage based on the number of patches installed and the number of missing patches
- Number of impacted assets by Service Level Agreement levels
- Number of impacted assets by patch severity
- Number of unique missing patches by their release age
- Patch remediation trend for the last six weeks
- Top 10 missing patches
3. Create an operation to remediate missing patches.
For details, see Working with operations.