1 of 1 people found this helpful
My recommendation would be to open a case with LANDesk support.
There's "more" to getting a task working in 8.7 than just the Scheduler Service - namely the Global Scheduler. It's probable that this is where your problem is - and depending on how technical you are, you might be able to figure it out from the Global Scheduler logs
However, I'd recommend opening a case with LANDesk support for this, as this is not usually the sort of problem that's easily sorted out through a forum and requires some trawling through logs, potentially looking at your DB and other things.
It has nothing to do with your clients - if the task isn't starting, this is purely on the Core.
Also - what are those other "routine jobs". Bear in mind that there are different parts to get a "job" to run. I.e. - if you're running scripts on a client, that doesn't use the Scheduler per se, but uses CUSTJOB - a different animal entirely. So the devil is in the detail :).
LANDesk EMEA Technical Lead.
Thanks for the speedy answer. I called the other jobs routine because they run often and on a weekly timescale. They were all software distribution jobs. One that ran after was an swd package like the problem job, the others were mostly exes.
I will log with LANDesk and take at look at the logs.