Quantcast
Channel: System Center Dudes
Viewing all articles
Browse latest Browse all 410

Monitor and identify SCCM Maintenance Windows

$
0
0

During a recent SCCM Assessment, I encountered a customer having hundreds of Maintenance Windows. I had to identify which collection and which devices were assigned those SCCM Maintenance Windows.

SCCM has only 1 built-in report for Maintenance Windows monitoring (Maintenance windows available to a specified client).

This report lists all maintenance windows that are applicable to a specified client. This is fine but what if I need to have the maintenance window on multiple clients or collections? It would also be nice to have a list of all collection on which there’s maintenance window applied.

Free SCCM Maintenance Windows Report

SQL to the rescue ! We’ve built 2 free SCCM Maintenance Window reports:

The first report lists all SCCM Maintenance Windows per device.

SCCM Maintenance Windows Report

You can use the report parameter to filter a specific machine name or collection.

SCCM Maintenance Windows Report

The second report list all SCCM Maintenance Windows per collection.

SCCM Maintenance Windows Report

You can use the report parameter to filter a specific collection or a specific maintenance window name.

SCCM Maintenance Windows Report

Both reports are linked together so that you can navigate between them by clicking on the collection name or maintenance windows name.

You can download this free reports by visiting our product page. The Configuration Manager – Maintenance Windows contain both report and are available in the Report / Configuration Manager section.

We hope this report will help you to easily identify your maintenance window!

Note: There is a rating embedded within this post, please visit this post to rate it.

Share this Post

The post Monitor and identify SCCM Maintenance Windows appeared first on System Center Dudes.


Viewing all articles
Browse latest Browse all 410

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>