‎04-27-2020 04:26 PM
‎05-22-2020 09:55 AM
‎07-09-2020 11:09 AM
MDahitule wrote:
To provide you with some context, both the active domain scanning target and user scanning target will query the LastLogon attribute, and try to connect to all domain controllers to get the highest value for this attribute.
It is "expected" behaviour that Lansweeper will not be able to access all DCs, and as such the error messages in the server log do not really serve a purpose, as there is no real issue. We have already escalated the issue to our development so that they can look into optimizing this page.
If required, you can disable the scanning of LastLogon for users in the Active Directory Scanning Options section under Configuration\Server Options.
‎04-28-2020 10:24 AM
Experience Lansweeper with your own data. Sign up now for a 14-day free trial.
Try Now