Let’s check the default ConfigMgr Software Updates Reports. There are thirty-one (31) out of box reports available as part of Configuration Manager SSRS reports. Learn how to create deploy New Software Update (a.k.a patching/patch deployment) Patch Package using ConfigMgr.
There are other useful hardware related reports outside ConfigMgr software updates reports. Also, you can learn How to Launch ConfigMgr Reports from the previous post here.
If you have trouble opening default SCCM reports, you can refer to Fix Report Server cannot Open a Connection Error ConfigMgr. Let’s also learn how to create a New Database for SSRS Reporting Service.
Requirements
Make sure you have all the following are in place to access the ConfigMgr Software Updates(a.k.a patching/patch deployment) default reports.
- Reporting Services Point is installed.
- SSRS reports are working fine.
- Make sure you have appropriate permissions to launch reports from Console and SSRS URL.
Launch ConfigMgr Client Reports
Let’s learn how to launch Software Updates default reports from console.
- Launch Console
- Navigate to \Monitoring\Overview\Reporting\Reports.
- Sort the reports with Category.
- Right-click on the related reports “Software Updates“.
- Select the RUN option.
Introduction
Let’s understand the different software update categories available in the software update section. There are five (5) categories available in SSRS default reports.
| Software Update Category |
|---|
| Software Updates – A Compliance |
| Software Updates – B Deployment Management |
| Software Updates – C Deployment States |
| Software Updates – D Scan |
| Software Updates – E Troubleshooting |
Software Updates – A Compliance
The reports in Software Updates – A Compliance category of reports that help to identify the compliance status of Software Update.
| Software Updates – A Compliance |
| Compliance 1 – Overall compliance |
| Compliance 2 – Specific software update |
| Compliance 3 – Update group (per update) |
| Compliance 4 – Updates by vendor month year |
| Compliance 5 – Specific computer |
| Compliance 6 – Specific software update states (secondary) |
| Compliance 7 – Computers in a specific compliance state for an update group (secondary) |
| Compliance 8 – Computers in a specific compliance state for an update (secondary) |
| Compliance 9 – Overall health and compliance |
Software Updates – B Deployment Management
The reports in Software Updates – B Deployment Management category of reports that help to identify the Software Update Deployment details.
| Software Updates – B Deployment Management |
| Management 1 – Deployments of an update group |
| Management 2 – Updates required but not deployed |
| Management 3 – Updates in a deployment |
| Management 4 – Deployments that target a collection |
| Management 5 – Deployments that target a computer |
| Management 6 – Deployments that contain a specific update |
| Management 7 – Updates in a deployment missing content |
| Management 8 – Computers missing content (secondary) |
Software Updates – C Deployment States
Let’s get more details about Deployment States of Software Update deployments (a.k.a patching/patch).
| Software Updates – C Deployment States |
| States 1 – Enforcement states for a deployment |
| States 2 – Evaluation states for a deployment |
| States 3 – States for a deployment and computer |
| States 4 – Computers in a specific state for a deployment (secondary) |
| States 5 – States for an update in a deployment (secondary) |
| States 6 – Computers in a specific enforcement state for an update (secondary) |
This report returns all deployments that contain all of the software updates defined in a specified software update group.
Software Updates – D Scan
Let’s get more details about Software Updates Scan related details.
| Software Updates – D Scan |
| Scan 1 – Last scan states by collection |
| Scan 2 – Last scan states by site |
| Scan 3 – Clients of a collection reporting a specific state (secondary) |
| Scan 4 – Clients of a site reporting a specific state (secondary) |
This report returns the enforcement states for a specific software update (a.k.a patching/patch deployment) deployment, which is typically the second phase of a deployment assessment. For the overall progress of software update installation, use this report in conjunction with “States 2 – Evaluation states for a deployment“.
Software Updates – E Troubleshooting
Let’s find out some Software Updates (a.k.a patching/patch deployment) Troubleshooting related reports.
| Software Updates – E Troubleshooting |
| Troubleshooting 1 – Scan errors |
| Troubleshooting 2 – Deployment errors |
| Troubleshooting 3 – Computers failing with a specific scan error (secondary) |
| Troubleshooting 4 – Computers failing with a specific deployment error (secondary) |
This report returns the scan errors at the site and a count of computers that are experiencing each error.
