I'm assuming you are using a 7.4.x version of BL. There is actually no information provided by the third party vendor on Microsoft patches need for reboot so it cannot be available through a property such as REBOOT_TYPE on a patch-by-patch basis. For Windows patching at some point in the patch cycle a reboot will need to be performed to ensure the installed patches are reported as correctly installed in a post-install patch analysis job.
There's an NSH script in the KB that checks the Windows registry to see if an option has been set to indicate that the box needs a reboot. search the KB for "NEEDS_REBOOT". The script checks the registry location and then sets a server property. This may help.
Also, in the deploy job of the patches, you should see a green check mark w/ a shadow - that indicates the box needs a reboot.
I believe you can also set an option on the job to reboot at the end of the deployment if required.
I opened Ticket 24368 earlier this year after we upgraded to 742 because Shavlik DOES publish this information.
And which is the ticket status?
That script is here:
While this script checks two areas of the registry, I've seen additional areas where Windows will set if a server needs reboot or not. If you do find these additional areas, please post a comment on the script download page and I can update the script.
But for the most part this script seems to work really well to determine which servers in your environment need reboot. It's good practice to run this prior to any patching to see if any servers need reboot before you apply more patches.
Unfortunately it has gone nowhere and is stuck in "review"
Might help if you open your own for the same issue to let them know others care about it as well.