In this blog post,I will show you ,how to know /monitor the clients with software update scan status results .
For patch management,all Configmgr Managed clients should do successful software update scan else,client will not be able to get updates from SCCM and thus ,SUP compliance go down the SLA.
I looked at the default reports to check if there is any such report to get count of clients that performed successful scan ,not successful scan and how many do not even report anything about scan.
I come up with nice SSRS Report gives you count of clients with success SU Scan,Failed and client that do not report anything.
All the counts in the report have linked report means,you can get list of clients for troubleshooting why they failed.
Software update scan results stored in v_updatescanstatus ,with LastErrorCode='0' considered as success and rest are considered as failed.
Download the RDL files from TechNet Gallary,uploaded all the reports to your SSRS Folder (make sure you uploaded all these files into same folder as they are linked) and change the data source before you run them.
Note:All these reports filtered with criteria DATEDIFF(dd,sys.Last_Logon_Timestamp0,GetDate()) <30 (computers did not logged into domain during last 30 days will not be reflected in this report ,I feel that ,no point looking at these computers since they are not on the network) and no other filters added like OU limitation /Server limitation etc. If at all you want,you can customize the RDL File.
Uploaded to your folder:
Software Update Scan Results:
Linked report- List of client SUScan Failed:
List of Client NoSUScan:
This report includes clients with no sccm client and you are required to get the client install on all computers with client=No.
Hope this report will help you to get some idea how the client are doing with respect to Soft update Scan ,from this point,you can start troubleshooting the failed clients.
Feel Free to share your feedback via comments section .
Pingback: Troubleshoot client side software updates issue. | system center experts
I follow your blogs very closely and you do a great job with your blogs. I have got couple of quick questions. I have setup a test sccm 2012 r2 environment with two test clients with win server 2012 r2 version. Configured SUP and both the test clients have sccm agent installed with all components existing.
1.After sync When I go to ‘all software updates’ I see required as '0' for all patches. I am not sure if this is a problem with my client agent installation or if all the patches are up to date on my test machines. Is there any way to check this?
2.I tried deploying a patch manually to test the client. I could not see the patch getting deployed. I tried triggering the policies on client manually but no luck . All I see is enumerable updates = 0.
3.One more thing which I want to mention is "Specify intranet MS update service location" was not configured by default . Would this be configured when the client gets installed automatically ? or do we manually setup a group policy. I did this manually here.
4. To test the client further I used your rdl file “List of clients nosusscan” . Strangely my two client machines appeared in this even after having sccm client installed on it. Why would this happen does it indicate corrupt client? When I used list of suss can filed rdl I get no results.
At this moment i am really not sure if clients are up to date with all patches and that is the reason it showing required = 0 or if there is any problem with my client installations on these machines. Is there a way to check if my sccm client is healthy ?
Thank you in advance
I do not understand very well the difference between your reports, and the OOTB report "Scan 1 - Last scan states by collection". Could you explain it further?
default reports do not provide any additional information like last software update scan,last hardware inventory etc. Did you run the reports available on the blog compared to default reports ?
Please ignore my previous comment.
It is actually for below link.
i downloaded the zip file from Technet gallary,imported the reports into SSRS folder,change the data source and run the report.it works fine for me.
No errors at all.
you can edit the RDL,copy the sql code from app dataset and execute it to see if anything wrong.
Thank you for this !
I was looking for this report specifically, unfortunately it is throwing me below error (both the reports).
An error has occurred during report processing. (rsProcessingAborted)
Query execution failed for dataset 'App'. (rsErrorExecutingCommand)
For more information about this error navigate to the report server on the local server machine, or enable remote errors
I have changed the datasource as mentioned & still getting this error. When the query is ran individually, it is executing & displaying results.
Any help around this will be much appreciated.
I installed these reports in my home lab and they work great!
Thanks Eswar for the reports.
Looks Good. I am going to test it now.Thanks ESWAR
Let me know the feedback