Active Directory scanning not working

[nickrowse]

Now that I have upgraded to 3.5 I am trying to use Active Directory Scanning for the first time. I have read the previous posts about this and have added <add key="Activescanning" value="1" /> to Lansweeperservice.exe.config and have restarted the service, however the errorlog.txt does not say anything about Active Scanning enabled, just Database connection successful, starting service (no errors logged). Here is the config (changed servername and password):

<?xml version="1.0" encoding="utf-8"?>
<configuration>
<appSettings>
<add key="ConnectionString" value="Persist Security Info=False;Data Source=server;Initial Catalog=Lansweeper;User ID=lssqluser;Password=password" />
<add key="ConcurrentThreads" value="10" />
<add key="ListenPort" value="9524" />
<add key="Activescanning" value="1" />
</appSettings>
</configuration>

It looks right to me, but what am I missing?

I noted on previous premium downloads there was a different executable for the service to enable active scanning, now there is not so am I right to assume it is the same Lansweeperservice.exe as the free version?

Can I also get some clarification on where I enter to domain name and also the filter for OU?

[Hemoco]

You can remove <add key="Activescanning" value="1" /> if you wish but the key is ignored anyway.

[opekta]

I should've read your (Lansweeper) reply more closely.

"The config files editing was in the old version."

So, can I remove the following entry from my Lansweeperservice.exe.config file? If so, should I restart the Lansweeper Service?

<add key="Activescanning" value="1" />

NOTE: I'm running version 3.5 (Premium).

Thanks,

Terry

[Ista]

I'm kinda in the same boat.


Except with me, if I put in just a domain name, it starts scanning, but if I restrict it to a OU, I get nothing.

[nickrowse]

Further to this I found the entries for adding domain and OU filter and filled those in, still when starting service there is nothing in log about active scanning enabled, however it did start scanning but did not restrict itself to the OU I specified, so I guess the real issue now is how to make the OU restriction work?

[Hemoco]

nickrowse wrote:
Further to this I found the entries for adding domain and OU filter and filled those in, still when starting service there is nothing in log about active scanning enabled, however it did start scanning but did not restrict itself to the OU I specified, so I guess the real issue now is how to make the OU restriction work?

The config files editing was in the old version.
Please download the documentation from our download page, it explains how to fill in the domain/ou config.

To help solve the problem, please post screenshots of the filled in screens and your active directory topology.