cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
mlein
Engaged Sweeper
We are wanting lansweeper to not do any automatic scanning. We have deployed the lspush.exe file and when the systems that we want to monitor login, they run the lspush.exe agent and report in to the server.

So far in the scanning options - scanning targets i've added an exclusion for the IP address of our domain controller, changed the AD Domain scanning options check interval to 240 minutes, the Min time between scan to 999 days and the Max time between scan to 999 days and 1 hour. I've also added a bogus AD preferred DC

In the event viewer log for the DC, I see that there were failed logins from the server with Lansweeper installed on it using the .\lansweeperuser account at 4:37pm and 4:52pm last night and then again at 7:57am this morning.

We're using version 6.0.100.29. Any suggestions?

Thanks,

Mark
1 ACCEPTED SOLUTION
Bruce_B
Lansweeper Alumni
If you have no scanning targets set up under Scanning\Scanning targets, your Lansweeper server will only scan itself automatically, as far as computer scanning goes. When importing LsPush files of domain computers though, your Lansweeper server will try to retrieve AD information regarding these computers, as LsPush is not able to retrieve this due to the nature of the agent.

Do note that when you exclude a computer in Lansweeper you'll also not be able to scan it via LsPush either.

It's kind of an indirect solution, but if you want to prevent your Lansweeper server from contacting DCs for AD information regarding your computers, you could theoretically block outbound traffic on port 389 on your Lansweeper server.

View solution in original post

2 REPLIES 2
mlein
Engaged Sweeper
Thanks for that Bruce.
Bruce_B
Lansweeper Alumni
If you have no scanning targets set up under Scanning\Scanning targets, your Lansweeper server will only scan itself automatically, as far as computer scanning goes. When importing LsPush files of domain computers though, your Lansweeper server will try to retrieve AD information regarding these computers, as LsPush is not able to retrieve this due to the nature of the agent.

Do note that when you exclude a computer in Lansweeper you'll also not be able to scan it via LsPush either.

It's kind of an indirect solution, but if you want to prevent your Lansweeper server from contacting DCs for AD information regarding your computers, you could theoretically block outbound traffic on port 389 on your Lansweeper server.