A couple builds ago, Microsoft added a cool new column to the ConfigMgr console.\u00a0 It is really cool but I wanted to more with it.\u00a0 I wanted pending reboot collections and reports.\u00a0 Now I want to share what I found and did.<\/p>\n
The Pending Reboot information can be found in the ConfigMgr DB as part of the v_CombinedDeviceResources view.\u00a0 This view has a lot of cool info, but we are interested in ClientState.\u00a0 ClientState is\u00a0 what lets us know if there is a reboot pending.<\/p>\n
There are\u00a0five main states:
\n0 = No reboot Pending
\n1 = Configuration Manager
\n2 = File Rename
\n4 = Windows Update
\n8 = Add or Remove Feature<\/p>\n
Now, if you look at that view, you will notice that there are more than those five listed.\u00a0 Two of my biggest ClientState values are 12 and 13.\u00a0 That is because the five are bit flags and your system may have multiple reasons for needing a reboot.<\/p>\n
By looking at the message in the console and comparing it to the ClientState value, I determined these additional ClientState values are the various main states added together.<\/p>\n
1 – Configuration Manager
\n2 – File Rename
\n3 – Configuration Manager, File Rename
\n4 – Windows Update
\n5 – Configuration Manager, Windows Update
\n6 – File Rename, Windows Update
\n7 – Configuration Manager, File Rename, Windows Update
\n8 – Add or Remove Feature
\n9 – Configuration Manager, Add or Remove Feature
\n10 – File Rename, Add or Remove Feature
\n11 – Configuration Manager, File Rename, Add or Remove Feature
\n12 – Windows Update, Add or Remove Feature
\n13 – Configuration Manager, Windows Update, Add or Remove Feature
\n14 – File Rename, Windows Update, Add or Remove Feature
\n15 – Configuration Manager, File Rename, Windows Update, Add or Remove Feature<\/p>\n
I can now work on my collection and SQL queries.<\/p>\n
This is collection query is for all systems pending reboot.<\/p>\n
And this SQL query will return all systems pending reboot and the reason<\/p>\n