(Edit...I was wrong)

Not really....

We flow up the last time a PC rebooted.

We flow up if a PC is in a state where changes will occur at reboot, such as entries in "PendingFileRenameOperations". (We check quite a few things...)

However, there is no entry in the DB to indicate when those entries were first created on the PC.

The closest you can get is PCs in a Need Reboot State that have not rebooted in X Days.

--

(Edit Update:)

Try this....

select zdeviceex.rebootpendingsince rebootpendingsince , zzenobject.path from zdeviceex join zzenobject on zzenobject.zuid=zdeviceex.zuid order by rebootpendingsince asc;

So where does the dates showing on the General and Patches tabs of a device come from?

we want a report based on those types of numbers.  They are clearly stored somehow somewhere?  Even if performing some derivations is required to get there.

Fresh playing with reports finds a "LastBootTime"  but it comes out empty 

And the dates still come out in a format that doesn't work for my LibreOffice Calc, do we have support yet for the international date standard vs that one local only one?  Little endian and mixed endian dates are such a pain, give me a good big endian like ISO 8601. I grew up between those two local unsortable ones, and so latched on to that standard when it came out as logical and so sortable without having to apply oddball mechanics to do so.

Hmmm maybe it does ...keep that extra data....

Buried somewhere.  Hopefully not with the Ark of the Covenant over in Building 13.  I think we have a quest now.

Yup...I found it....

I updated my original post that I was wrong as well as with a query....

Thanks for forcing me to double check..

Craig Wilson said:

Yup...I found it....

ah ha,  so you doffed your fedora, and whipped that challenge into hand.  Perfect.

so I guess that means dusting off DBeaver for that query, to go hunting for that, certainly doesn't look like anything I can do within ZCC.

The DBeaver route worked once I figured the export (only 2nd time with it) and it appears the date/times are in UTC rather than local, which makes sense.   Just had to manipulate the csv a bit to get it cleaned up just a bit. Perhaps see if I can script that part.

ZRS can do it, but doubt you can easily do in in ZCC.  I could not find the fields exposed in the Inventory Reports.

So shops that can justify setting up the ZRS have it easy,  and this is the sort of thing to help provide some justification.

So notes for others to follow:
- It only shows times for those with reboots pending, rest are blank.
- Times are in UTC, and with DBeaver come in proper date format (ISO8601, but that could be a DBeaver or my system default coming through)
- Devices that have never updated that field (old agents or related, we still have a few 17.4 left that are being retired this summer)

So easy to just have DBeaver open, and rerun the script as we badger users to reboot when on a tare about that. Also for deployment of bundles that need a reboot. (a long weekend here, so pushing on both fronts)