What is the best MaxConcurrentConfigRequest value and how to change it?
search cancel

What is the best MaxConcurrentConfigRequest value and how to change it?

book

Article ID: 243739

calendar_today

Updated On:

Products

IT Management Suite Client Management Suite

Issue/Introduction

What is the best MaxConcurrentConfigRequest value and how to change it?

Environment

Release: 8.x

Resolution

In the old ITMS version (NS 6.0 SP2), the default MaxConcurrentConfigRequests value was 50 and that proved to be too high for most large enterprise environments. Testing internally within Altiris and in conjunction with several customers showed that NS performs much better when MaxConcurrentConfigRequests was set to a value lower than 30. The default value has since been changed to 10.

Some customers tried to increase the default value for "MaxConcurrentConfigRequests"  from 10 to something higher. This usually causes a bottleneck when there are now more client machines trying to get a new configuration.

If your SMP server has enough resources for more connections, then you can try increasing this value in increments of 10 but never to exceed a new value of 50.

To change this value, under SMP Console go to Settings>Notification Server>Core Settings>Active Settings and search for MaxConcurrentConfigRequest as seen here:

 

Attachments