Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-22-2016 06:12 PM
I have checked the: "Set computers to non-active if disabled in Active Directory" option, but the computers aren't updating in Lansweeper.
I have the correct DNS and NetBIOS name entered, and have enabled Active Scanning.
Did I miss something? Is there a way to force Lansweeper to scan AD?
I have the correct DNS and NetBIOS name entered, and have enabled Active Scanning.
Did I miss something? Is there a way to force Lansweeper to scan AD?
Solved! Go to Solution.
Labels:
- Labels:
-
General Discussion
1 ACCEPTED SOLUTION
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-28-2016 04:37 PM
The "Set computers to non-active if disabled in Active Directory" item is part of our database cleanup options. Cleanup options are *not* triggered when rescanning your computers. They only get triggered once every 24 hours or when manually restarting the Lansweeper service. During an upgrade - you went from 5.3.0.24 to 5.3.0.30 in your case - Lansweeper forces its scanning service to restart. This explains why your computers were suddenly set to non-active.
To have your computers set to non-active if disabled in AD please do either of the following:
To have your computers set to non-active if disabled in AD please do either of the following:
- Wait for the cleanup options to kick in. This happens every 24 hours. If the cleanup options were triggered four hours ago, you will have to wait another twenty hours for them to kick in again.
- Stop and restart the Lansweeper Service as available in Windows Services and wait for the cleanup options to start. Doing this will prevent you from waiting and is most probably the most recommended solution to your problem.
4 REPLIES 4
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-29-2016 03:36 AM
Thanks for the explicit explanation! I "tested" and confirmed it worked. It took about 6 minutes to mark my "test computer" as non-active.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-28-2016 04:37 PM
The "Set computers to non-active if disabled in Active Directory" item is part of our database cleanup options. Cleanup options are *not* triggered when rescanning your computers. They only get triggered once every 24 hours or when manually restarting the Lansweeper service. During an upgrade - you went from 5.3.0.24 to 5.3.0.30 in your case - Lansweeper forces its scanning service to restart. This explains why your computers were suddenly set to non-active.
To have your computers set to non-active if disabled in AD please do either of the following:
To have your computers set to non-active if disabled in AD please do either of the following:
- Wait for the cleanup options to kick in. This happens every 24 hours. If the cleanup options were triggered four hours ago, you will have to wait another twenty hours for them to kick in again.
- Stop and restart the Lansweeper Service as available in Windows Services and wait for the cleanup options to start. Doing this will prevent you from waiting and is most probably the most recommended solution to your problem.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-25-2016 06:34 AM
I can't replicate my "solution". I have rescanned the OU with the disabled computers, and it doesn't update as "Non-Active" in Lansweeper.
...so frustrating!
...so frustrating!
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-24-2016 10:27 PM
I upgraded to from 5.3.0.24 to 5.3.0.30. I forced an AD update, and it marked the "AD-Disabled" computers as "Lansweeper-non-active".