→ 🚀What's New? Join Us for the Fall Product Launch! Register Now !

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
fjca
Champion Sweeper II
Hello, I would like to have the option to force Lansweeper to use a list of Domain Controllers for getting AD information, instead of doing a domain wide search and them trying them all.

We are migrating our local/national domains to the Enterprise World Wide AD, but we only have access to our local tree, so Lansweeper tries to reach 130+ domain controllers, when it only was permissions for two (for now, of course).

So I've got my logs full of failed logon attempts, it takes about 90 minutes to start scanning after the service is started, etc.

I do have one of the domain controllers as a preferred DC, but that doesn't seem to make any diference in my case...
2 REPLIES 2
bcalluy
Engaged Sweeper II
+1
jshride
Engaged Sweeper II
I think this would also be very useful. In larger org's its not a very good idea to have some systems randomly utilizing other UNSPECIFIED systems. Could we make this a select-able option? for example, use ONLY specified server OR use all available servers.