If any of the conditions above are seen the diagnostic will wait 90 seconds and then gather a second sample of the Netlogon performance counters. The second sample will be compared to help determine whether a new MaxConcurrentApi setting should be recommended for that computer.
If no MaxConcurrentApi setting is suggested by the diagnostic then the performance data did not suggest an altered setting. If that occurs run the diagnostic when the issue is underway to see if a different suggested MaxConcurrentApi value is suggested.
NOTE: If Average Semaphore Hold Time is zero then the MaxConcurrentApi value should not be changed. Though the problem detection will not reveal the Netlogon performance counters which it used the same performance data is obtained in the SDP %computername%_MaxConcurrentApi.txt file.
More information can be found in the Knowledge Base articles below.
How to do performance tuning for NTLM authentication by using the MaxConcurrentApi setting
You are intermittently prompted for credentials or experience time-outs when you connect to Authenticated Services
[SDP 3][52a5f43b-2db9-40b7-88ae-fd9842cca85f] MaxConcurrentApi NTLM Diagnostic