What is the best "MaxConcurrentConfigRequest" value and how can it be changed?
Article ID: 243739
Updated On:
Products
Issue/Introduction
What is the default value of the "MaxConcurrentConfigRequest" and what is the best way to change it?
Environment
ITMS 8.x
Resolution
In the past versions of ITMS 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 much 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 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:
Additional Information
The following KB articles provide more information on the MaxConcurrentConfigRequest setting:
236852 Some client machines will display "Failed to update configuration" when trying to request new configuration
152447 Connection to database failed. Error: Timeout expired. The timeout period elapsed prior to obtaining a connection from the pool.
Feedback
