→ The Lansweeper Customer Excellence Awards 2024 - Submit Your Project Now! Learn More & Enter Here
04-26-2024 11:46 AM - edited 04-26-2024 11:47 AM
LS 11.2:
Changed: LAN-16076 Improved the AD data cleanup functionality and added the option to throttle the volume of requests.
Could you explain about these options? I can't find.
Solved! Go to Solution.
04-26-2024 12:01 PM
Hello there!
Sure! In previous versions, our AD cleanup was querying the domain controllers a bit too enthusiastically. Think multiple thousands of times per minute. Our developers have optimized most of the code that cleans up the active directory records. The newer code should greatly reduce the amount of connections being created/dropped.
04-26-2024 01:28 PM
Hello there!
There is not, but if you still experience a high load, you can use a new app setting:
AdCleanupThrottleTimeMs
Here you can put the amount of milliseconds the system should wait between every AD call (so 1000 for 1 second). If needed, this should limit the load on your domain controller. You can add this in the <appsettings> section in the Lansweeperservice.exe.config file of the service.
I have not tested this setting myself yet, and for further questions I will need to check with the developers. 😉
04-26-2024 12:01 PM
Hello there!
Sure! In previous versions, our AD cleanup was querying the domain controllers a bit too enthusiastically. Think multiple thousands of times per minute. Our developers have optimized most of the code that cleans up the active directory records. The newer code should greatly reduce the amount of connections being created/dropped.
04-26-2024 12:23 PM
Is there user interface to tune throttle?
04-26-2024 01:28 PM
Hello there!
There is not, but if you still experience a high load, you can use a new app setting:
AdCleanupThrottleTimeMs
Here you can put the amount of milliseconds the system should wait between every AD call (so 1000 for 1 second). If needed, this should limit the load on your domain controller. You can add this in the <appsettings> section in the Lansweeperservice.exe.config file of the service.
I have not tested this setting myself yet, and for further questions I will need to check with the developers. 😉
Experience Lansweeper with your own data. Sign up now for a 14-day free trial.
Try Now