Hi All.

We are doing a mass managed install of Office 2013.  I'm worried about flooding our network when the machines check in and start to download the OCT configuration file I created.  How do I (or can I) limit how many machines it tires and pushes out to?

0 Comments   [ - ] Hide Comments


Please log in to comment

Community Chosen Answer


Task throughput limits the flooding of the network.  This is adjusted under general settings in the system area.  You can also create replication shares and groups will then go to the shares vs the server for the files.

Search google for:
kace agent task throughput
Answered 02/05/2015 by: SMal.tmcc
Red Belt

  • Hi SMal.tmcc,
    From the description of the Task Throughput, I'm not sure that will help. We won't be doing any patching or scripting at the time, just the managed install. Am I wrong on that assumption?
    • The replication shares are your best bet to divide the MI workload if you did not want to stage it thru labels.
      One other choice is to use a KScript and that will be throttled by the throughput for the initial wave of machines. Once you finish the initial wave, go back to an MI for new machines.
Please log in to comment
Answer this question or Comment on this question for clarity


Your best bet would be to use smart labels to group machines together by some common aspect and then target those labels one at a time or two at a time. Once they are all done, change the managed install to target another group of labels. 

Ex. Use smart label to group locations together by IP address or by departments. 
Kace only pushes out using the three options - All Devices, Labels or Individual Devices
Answered 02/05/2015 by: nshah
Red Belt

  • Thank you nshah. That's what I was afraid of. I appreciate your response.
Please log in to comment