When you deploy software updates using SCCM/configmgr to clients ,patch status will be sent back to SCCM site.It is always good to know the Last state ID's and its state names for custom reporting.
Below are the available Last state ID's and State Names.
These state IDs do exist in SQL View called v_GS_PatchStatusEx .
| LastState | LastStateName |
| 0 | No Status |
| 101 | Failed |
| 102 | Reboot pending |
| 105 | Install Verified |
| 107 | Preliminary Success |
couple of Patch Compliance reports based on laststate/Laststatename are
SCCM Patch Compliance Progress report: http://eskonr.com/2009/10/patch-status-compliancesoftware-updates-report-in-sms-sccm/
Software Update Compliance Status on Specific Collection : http://eskonr.com/2009/09/report-for-software-update-report-for-software-update-compliance/
SCCM monthly Patch statistics report http://eskonr.com/2011/10/sccm-monthly-patch-statistics-reports-to-the-management-in-a-simplified-manner/
1 Comment
Pingback: SCCM ConfigMgr Compliance status of client for multiple software update groups | Eswar Koneti Blog