How do I make a script actually run at a specific time?
I am working on a script to deploy a new piece of software and I have having issues with the reliability of setting a time for the script to be run. I need to deploy an upgrade to some software we are using between 5am and 7am.
The script requires network credentials so the software can be installed off the network and it is currently setup in a .bat file being as it needs to uninstall numerous thing before installing the new version.
Yesterday I scheduled a test task to run on the ~35 workstations at 5:00 am and when I checked this morning, it ran on a total of 2 workstations at 6:24 am and then the other ~33 workstations at 7:52 am - 2 hrs and 52 min late.
I tried just clicking "run now", and planned on doing that for deployment, but sometimes it would run in 30 seconds, and sometimes it would take 4 hours.
After setting a schedule, does the device need to check in before it will run?
Is there a better way to do this?
Is there any way to give a script priority over other tasks the appliance might be running?
How long does it normally take for your scripts to kick off? (We have been having discussions with Kace to try and speed things up a bit, they are better now, but scripting still seems slow. )
You do not need to do more (well, except you need to run the script in 2 min on all 500000 endpoints)
As soon as you have the script enabled and have a schedule all nessesary is done.
The endpoints download the script Informations regulary using a preconfigured script
When the schedule kicks in, the script downloads any changes (and the first time this means all stuff) since the last download and runs the script afterwards.
the example with the 2min and 500000 endpoints would do the same, but due to the huge amoint of downloads (the stufdf is likely not yet replicated to the repl shares) could lead to a timeout so not all systems are reached and prepared for the run.