POST UPDATED HERE
I wasn’t getting what i needed from the built in SCCM SSRS Reports. Admins were asking for it to be made easier to understand how bad the number of outstanding updates were for the systems they have ownership of. For example, how many of the outstanding updates are 0-30 days old or 60+ days old.
The attached report “should” clearly indicate how old the outstanding updates are. The parameters can be adjusted to fit your business SLA model for deploying updates.
The RDL also only contains one collection. Add your own collections to the report by modifying the COLLID parameter (you will need to know the Collection ID).
Default date parameters/columns are:-
0 – 30 Days Old
31 – 60 Days Old
61 Days and Older
There is also a column to show if the client requires a restart. Often pending restarts can affect new updates being installed.
*** Big thanks to Eswar Koneti @eskonr and Adam Gross @adamgrosstx for their collective SSRS Examples and SQL Ninja Skills ***
Hi Ben,
Thanks for the report.
Just one question.
After I installed Office 2016 x64 on a few PCs and patched them up, the report showed these machine were missing around 50 updates that were over 61 days and older old.
When I checked these machines in the builtin SUG reports on SCCM, it showed that they had been fully patched.
Where do you think your report is picking up these missing patches from?
Thanks.
Hi Ben,
Sorry, I’ve just realized that I was looking at the wrong collection when I ran the report.
The machines were indeed missing these updates as your report indicated.
Please disregard my last query. Thanks!
No problem, glad the report has helped you! Ben
Hi,
How can we filter only security and critical updates not all?
Check this other blog out, it will help you understand how we build the report so you can filter some of the classifications.
https://byteben.com/bb/sccm-software-compliance-report-filtered-by-update-classification-and-update-age/
Thank you.