Analysis of a job that has already run?

(imported topic written by toweegar91)

Hi.

I have a job that I ran to over 700 machines and it appears that machines that were locked (as opposed to logged off) did not get the job to run until the user logged back in in the morning.

Is there any way in B/F to run an analysis of a job/action in order to let me see how many jobs were run at the assigned time of midnight and how many ran when the user logged on again in the morning?

ie. Is there a way for me to get some output on when the machine ACTUALLY rebooted?

Thanks in advance.

TERRY

(imported comment written by BenKus)

Hi Terry,

The uptime property is usually the easiest way to see the last restart… Additionally, you can double-click on a computer’s action status to see when it ran…

Not sure why some computers waited until the morning… did you use a message box?

Ben

(imported comment written by toweegar91)

Thnx Ben.

No, we didn’t use a msg box, but it appears that computers that were locked (as opposed to logged off) did not get the job to run until the users logged on in the morning… Maybe B/F didn’t like the fact that someone was logged on? We ran it without user intervention or anything, but?..

I was just hoping there was a quick/easy way to see what computers the job ran on and what ones waited till morning. I’ll try the “Uptime” idea and see if I can get a common listing that way.

Thanks.