I had a customer ask me the other day about statistics on the various home pages (system status, software updates and software distribution) specifically with how the software update node in the console gets updated with the total counts of software updates that are installed, not installed, required, unknown, etc. This is something I had not really looked into before.
The home page summarization process is unique depending on the feature. There are three major categories of summarization that occurr. The first is system status, followed by software updates and software distribution. The focus here is on software updates. In this particular instance, software updates has a summarization schedule of 4 hours. This means that its 4 hours out of date when it comes to reporting the compliance of software update deployment. This can cause some confusion when reports are run. There is a relatively easy way to work around this. The following screen shot shows the ability to run a summarization on the fly:
When do run a manual summarization process, you will want to monitor the following logs:
statmgr.log – responsible for writing all status messages to the site database. This will show any outstanding svf files that need to be processed.
smsdbmon.log – records database changes
statesys.log – responsible for state message processing and activity. This log indicates the stored procedures that are run to summarize software update compliance.
If you take a look at the below screenshot, you will see the stored procedure SUM_Update Status Summarizer that is responsible for ensuring that statistics relating to software updates are updated against what is in the SCCM Site database.
Once the summarization SP is complete, you will want to refresh the console at the root. You will see the latest date/time stamp when the process has completed as shown below: