Lansweeper wrote:
Active Scanning only picks up machines that have reported to your domain controllers and that have not been scanned in the last 20 hours.
fjca wrote:
I deleted one today and two hours after it was still listed as active... Unfortunately work caught up with me and I could only check later in the day, and 8 and a half hours after, it was already listed as non-active...
Could you clarify how you tried to delete the machine. The machine being set to non-active was probably caused by one of the cleanup options listed in the Lansweeper configuration console under Scanning Servers\(name of your server)\Options\Scanning & Cleanup Options.
Hello, regarding the first question, what is happening in my enviroment is :
- Machine A is decomissioned and taken for storage. It is not powered on,
not connected to the network, it just sits there waiting to be wiped
and sent to charity.
- Machine A is deleted in Lansweeper, but not on the AD.
- After a few hours, two days maximum, machine A reapperas in Lansweeper.
- Machine A gets deleted again in Lansweeper, but not on the AD
- After a few more hours, two days maximum, it reappears again.
This happens without LS service restarts, and we confirmed on the AD
that the last logon time for the machine was when it was turned off.
Regarding the second question, I deleted the machine on the AD, and them
checked to see when it would get flaged as non-active on Lansweeper.
It took between 2 and 8.5 hours in this case.
Our clean-up options are to place all machines not scanned after 180 days
with a non-active status. We do not delete machines automatically.
Has I said, this is not a major issue for us since our standard procedure
is to delete all machines that are decomissioned, but of course there
are always a few exceptions, and that's a behavior we had not seen on
older versions.