Active Directory Optimization

[sukaitsu]

Hi,

It has been brought to my attention that the form in which Lansweeper queries active directory waste computational resources and adds too much of an overhead on our domain controllers. We worked with Microsoft directly to pinpoint Lansweeper as the root of the problem. Even though OU filtering is turned on and configured in Lansweeper; the queries performed against the domain controller are against the forest name. The results are then filtered later through Lansweeper, but waste a large amount of resources on the domain controller. Please look into adding the filter for OU in the initial query to Active Directory compared to filtering the results of a unfiltered search at the forest.

Thank you,

Jeffrey

[sukaitsu]

Thank you Susan. We look forward to the Beta release of 6.0.

[Susan_A · Accepted solution]

Development informs us that this will be fixed in Lansweeper 6.0. We are currently in the final stages of internal alpha testing for 6.0 and cannot give an exact release date for the public beta. You are on our list of beta testers however, so you'll be notified via email as soon as the beta becomes available.

[Susan_A]

We've created a ticket about this for development. They should be taking a look at this and posting a response within the next few days.