We have just over 460 machines checking in to Kace. If you're in a similar scenario I was curious as to what you use as your settings for the following:

-Agent "Run Interval"

-Agent "Inventory Interval" (if different than above)

-Scripting Update Interval

Please feel free to add any feedback to how your settings work for you. Thanks!

Answer Summary:
System resources and your individual tasks for clients will change what your settings should be. Judge this using the load average on the agent settings page. The load average is on a scale from 1 to 10. Support has noted in the past that the UI will start to behave sluggishly as your load average increases past five.
Cancel
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Answers

2

We have the "Run Interval" and the "Scripting Update Interval' set to run every hour, with the Inventory Interval set to 0, which runs it at every Run Interval. We have a little over 350 machines, and we haven't had any issues.

Answered 05/01/2012 by: WGM_Jeff
Fourth Degree Black Belt

Please log in to comment
2

We have "Run Interval set to 1hr, Inventory Interval set to 0 and the scripting update interval set to 12hr. We have 456 systems connecting. Have not had any system issues with these settings.

Answered 05/01/2012 by: ckubaska
Fourth Degree Brown Belt

Please log in to comment
1

Run Interval: 1 hour

Inventory Interval: 2 hours

Scripting: 1 hour

Connected systems: 800+

Because all of us have different scripts, deployments, and patching running, the important part on this page is the load average.

The load average is a scale from 1 to 10.  I've been told in the past by support that you will start to see the KACE UI get sluggish around 5.  Once you get toward ten, you will note that the UI has trouble loading in your browser and you will get a lot of timeouts or page unreachable notices.  I've often seen this happen if someone misconfigures a report, or if there is a lot of data activity, such as deleting all agent logs.

Answered 05/10/2012 by: philologist
Red Belt

Please log in to comment
0

We have Run Interval set to 4hr, Inventory Interval set to 0 and the scripting update interval set to 4hr. We have 2500 systems connecting. Have not had any system issues with these settings.

Answered 05/02/2012 by: merrymax
Senior Purple Belt

Please log in to comment
0

Run Interval: 8 hours

Inventory Interval: 0

Scripting: 4 hours

520 systems connected.  No issues at all.

Answered 05/02/2012 by: dpyett
Third Degree Blue Belt

Please log in to comment
0

Run Interval: 2 hours

Inventory Interval: 0

Scripting: 8 hours

250 systems connected.

I've found if you just pay attention to the Load average, as long as it doesn't get too high, we don't have any problems (never have). We've considered lowering the Run Interval, but it's not necessary.

 

Answered 05/02/2012 by: chadbaldwin
Senior White Belt

Please log in to comment
0
Run/Inventory Interval: 3 Hours
Scripting Update: 1 Hour
1586 system connected. 
Load Average is usually between 1-2. 
Answered 04/20/2016 by: MAXintosh
Senior Purple Belt

Please log in to comment
Answer this question or Comment on this question for clarity