Staggering script deployment?
Sorry for all the posts this week - but I figured I'd make a different one instead of adding it to an existing, so if people have similar questions they could find it easily.
Is there a way to stagger a script deployment over certain periods of time? We have labels for each of our schools (about 100-500 in each school). Is there a way to set a label of a school of 200 machines to a script and have the machines do a "run now" but almost stagger them to be 1 at a time?
We've tried using deployment, but pushing out 300mb installs kills our network since they all tend to check in at once (they all arrive around the same time and turn on their machines on the same time, etc). So is there a way to do a run now script almost, and say do 1 at a time until all PCs on the label are done?
Any suggestions? It's not needed for a constant update - just a one time push, but I don't want to have to create 20 labels of 10 machines each to push it out. Would almost be nice to set it to do 1 or 2 at a time and upon success/failure of completion, go to the next.
Is there a way to stagger a script deployment over certain periods of time? We have labels for each of our schools (about 100-500 in each school). Is there a way to set a label of a school of 200 machines to a script and have the machines do a "run now" but almost stagger them to be 1 at a time?
We've tried using deployment, but pushing out 300mb installs kills our network since they all tend to check in at once (they all arrive around the same time and turn on their machines on the same time, etc). So is there a way to do a run now script almost, and say do 1 at a time until all PCs on the label are done?
Any suggestions? It's not needed for a constant update - just a one time push, but I don't want to have to create 20 labels of 10 machines each to push it out. Would almost be nice to set it to do 1 or 2 at a time and upon success/failure of completion, go to the next.
0 Comments
[ + ] Show comments
Answers (1)
Please log in to answer
Posted by:
ms01ak
12 years ago
Here's a couple of options:
1) Set the schedule time to overnight during non business hours (create groups, monday, tuesday, wednesday group to try and push out the script to on those days)
2) Put a wait command in the script with a variable so it executes at different times. See here for the wait function http://ss64.com/nt/waitfor.html
3) You could change the communication window of the kace agent so it doesn't check in during certain hours.
cheers,
Mike
1) Set the schedule time to overnight during non business hours (create groups, monday, tuesday, wednesday group to try and push out the script to on those days)
2) Put a wait command in the script with a variable so it executes at different times. See here for the wait function http://ss64.com/nt/waitfor.html
3) You could change the communication window of the kace agent so it doesn't check in during certain hours.
cheers,
Mike
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.
