My first guess would be to open the Job (edit it), go into the Recovery tab, and make your changes there.  I would think deselecting the checkbox for "Run on startup if last run missed", but play with the other settings.

My second guess, or option really, would be to change the process so adTempus looks for new file(s) in a directory, executes the Job when it 'sees' an new file(s), then when done it deletes the file(s), leaving a blank directory.

My question would be, why so many server reboots?  That doesn't sound right in the first place.

Are you using File Triggers or File Conditions?

adTempus doesn't "remember" anything about the files it's monitoring when the service is shut down. Once it starts up, it starts watching those files again, and triggers if any of them are created/modified/deleted, based on your settings. So it shouldn't be starting the jobs when it's rebooted unless the files are getting modified.

Please submit a support request for further assistance with this issue.

The server reboots are necessary for MS Security patches and such.

I'm using file triggers for when files are changed/created.  I'll send a support request as I believe that now we are looking at something that may be a little too intense for a forum.  I suspect it may have something to do with the environment it is running on as I have two licenses and one box works as you would expect, but the other kicks off EVERY job that is set to a file trigger leaving only the few jobs I have that run on a scheduled execution to act normal.

Thanks for the help, fellas.

Regards,

Mark