cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

bug reappears

vargaboti
Engaged Sweeper II
Hi All
After updating to v.4.0.0.36 , a previous bug reappears.
Computers existing in AD but not existing any longer physically are reappeared in the “Computers in domain” page.
This bug was solved by (test version provided by you)LansweeperService v.4.0.0.25 now with 4.0.0.36 is back again. Could you help?
Many thanks in advance.
1 ACCEPTED SOLUTION

Lansweeper
Lansweeper Former Employee
Lansweeper Former Employee
The adsi path scanning will scan all computers in the path that are not disabled, this will probably reïntroduce your old machines.

View solution in original post

5 REPLIES 5

vargaboti
Engaged Sweeper II
Then prior applying the update to 4.0.0.36 this was not an issue. Why is now?

Lansweeper
Lansweeper Former Employee
Lansweeper Former Employee
vargaboti wrote:
Then prior applying the update to 4.0.0.36 this was not an issue. Why is now?

The computers were probably scanned when the service restarted and the adsi schedule was triggered.

I suggest disabling the computer accounts in active directory. (or removing them)

Lansweeper
Lansweeper Former Employee
Lansweeper Former Employee
The adsi path scanning will scan all computers in the path that are not disabled, this will probably reïntroduce your old machines.

vargaboti
Engaged Sweeper II
Since installed Active scanning is enabled,ADSI path set to domains, IP scanning on scheduled intervals.
Should we wait the mentioned 24 houre?

Lansweeper
Lansweeper Former Employee
Lansweeper Former Employee
I remember that this was one of the cleanup options that runs every 24 hours.
This code is still the same.

Do you use adsi scheduled scanning or active scanning?