How long would it take the KACE konductor to work through a script that was set to online and pushed to 12,000 machines?
I have inherited a k1000 system that we use to manage about 12,000 machines currently.
My predecessor had a Kace script that he would manually push out to small labels because he seemingly had issues when pushing to larger groups. After looking at the script i found that it was set to be an online script. The script itself wouldn't initiate any communications back to Kbox (logs etc) so there was no reason for it to be set that way. It just launches a vbs to kick off the download for specific windows updates. (We are using an embedded system so we cant use the catalog).
Is there a way to figure out how many agents that the konductor would start the script on at once? I belive that the script would take at least 5-10 minutes to run on each machine.
My predecessor had a Kace script that he would manually push out to small labels because he seemingly had issues when pushing to larger groups. After looking at the script i found that it was set to be an online script. The script itself wouldn't initiate any communications back to Kbox (logs etc) so there was no reason for it to be set that way. It just launches a vbs to kick off the download for specific windows updates. (We are using an embedded system so we cant use the catalog).
Is there a way to figure out how many agents that the konductor would start the script on at once? I belive that the script would take at least 5-10 minutes to run on each machine.
0 Comments
[ + ] Show comments
Answers (0)
Please log in to answer
Be the first to answer this question