IT Management Suite

 View Only

  • 1.  Last Boot Up Time field no longer updated?

    Posted Dec 06, 2016 12:06 AM

    Hi all,

    We've recently taken our ITMS from 7.6 HF7 to 8.0 HF4 and, since the upgrade, the Last Boot Up Time field of the Inv_OS_Operating_System table seems not to be updating.

    After noticing this on our production server, I rebuilt our sandbox NS and installed a clean 8.0 HF4 to compare. This is also not updating the Last Boot Up Time field.

    Was this feature removed sometime between 7.6 HF7 and 8.0 HF4? I realise it's a basic WMI query (which I'm about to duplicate as a custom inventory), but not having it is quite a hassle, since it's a cornerstone of our status reports which are dispatched to teams daily.

    Keen to know if others are having a similar experience.



  • 2.  RE: Last Boot Up Time field no longer updated?

    Broadcom Employee
    Posted Dec 08, 2016 07:33 AM

    How you've determined that "Last Boot Up Time" field doesn't get updated in "Inv_OS_Operating_System" table?

    I don't see any problem in 8.0 HF4 released build, and see that "Last Boot Up Time" field updates after each "Collect Delta Hardware Inventory" or "Collect Full Inventory" scan where it has at '

    1. Any useful information in "Altiris Log Viewer" on Notification Server about NSE processing?
    2. No License problems for "Inventory Solution" for expired state or exceeding of seat count?
    3. "C:\ProgramData\Symantec\SMP\EventQueue" isn't full on Notification Server machine?
    4. "Inventory Scan" task or policy shows that scan successfully completed on targeted managed clients or? Double click on execution state in Inventory task or switch view to "Task Runs" in "Collect Inventory" policy and check when last inventory scan has been executed on targeted PC.


  • 3.  RE: Last Boot Up Time field no longer updated?

    Posted Dec 08, 2016 11:54 PM

    Hi Igor,

    Thanks for that. I ended up having to recreate the inventory policy entirely because the targets were, and you'll forgive the non-technical term, a bit screwy. Everything appears to be updating properly now.

    I did go back through your checklist to confirm none of the other potential causes were in play; point 4 was the nearest to my actual issue.

    Cheers

    DMcG