
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
a month ago
I recently activated the option "Scan computers that are disabled in on-premises Active Directory," which resulted in the identification of numerous inactive assets. I am now looking to remove these assets from our system.
To address this, I selected the option "Remove computers disabled in on-premises Active Directory from the LANSWEEPER database" and ensured that no other settings that could potentially cause conflicts were enabled. Despite multiple scans, these inactive assets remain in the system and have not been deleted.
I am puzzled as to what might be preventing their removal. Additionally, when I navigate to the reports tab and select "Active Directory: Enabled/Disabled Computers," no entries appear.
Could you provide any guidance or suggestions on how to resolve this issue?
Thanks
- Labels:
-
Scanning
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
4 weeks ago
Hi,
Clean up options happen every 24 hours when the service restarts. Do note, most views and reports automatically filter out non-active assets. You can hover over the assets tab and select asset states to see non active assets.
On the asset summary page you will see by the name "Disabled in AD" and also in the active directory section of the summary page. If these show on the asset.
Verify the setting is enabled because you can not have the "Scan computers that are disabled in on-premises Active Directory" and "Remove computers disabled in on-premises Active Directory from the LANSWEEPER database" enabled at the same time. If you enable one it will automictically disabled the conflicting setting.
If all the settings look to be correct you can create a support ticket in our portal that way we can take a deeper dive.
Our tech support team should be able to assist you with this. Please open a ticket in our support portal.
Make sure to add screenshots and the GatherLogs output file so our SME's can start investigating the issue straight away.
