
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-06-2016 09:42 PM
Can anyone describe the behavior of AD integration. If I have it set to scan my entire domain. I also had it scan quite an IP range. Here's the thing -- we have some AD objects that did not show up.
I was running a test to see what factors determined whether or not something showed up as an asset. I have AD objects (computers) that were not on when I scanned the network, but were nevertheless in AD. These systems never showed up as assets. Is this standard behavior?
Thanks.
I was running a test to see what factors determined whether or not something showed up as an asset. I have AD objects (computers) that were not on when I scanned the network, but were nevertheless in AD. These systems never showed up as assets. Is this standard behavior?
Thanks.
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
‎05-19-2016 01:11 PM
Active Scanning (Active Directory Domain target in 6.0) only scans computers as they report to a domain controller. To scan all (enabled) computer objects directly from Active Directory, use Scheduled Computer Scanning instead. In Lansweeper 6.0, this is the Active Directory Computer Path target under Scanning\Scanning Targets.
5 REPLIES 5

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-07-2016 08:28 PM
By "this", I am referring to scanning Linux servers joined to the domain using Active Scanning. "this" does not appear to be working.
Thanks,
Jim Lovejoy
__________________________________________________________________________________________________
James W. Lovejoy | IBM - Cloud Managed Services Delivery | Infrastructure Architect (Windows Server ...
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-15-2016 04:01 PM
AdmJLovejoy wrote:
By "this", I am referring to scanning Linux servers joined to the domain using Active Scanning. "this" does not appear to be working.
If the issue persists in the latest 5.3 or 6.0 release of Lansweeper, could you contact support@lansweeper.com so we can troubleshoot via email.

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-19-2016 08:09 PM
Hi Susan, this does not appear to be true for Linux computers joined to the Domain. Please confirm.
Thanks,
Jim Lovejoy
__________________________________________________________________________________________________
James W. Lovejoy | IBM - Cloud Managed Services Delivery | Infrastructure Architect (Windows Server ...
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-07-2016 07:57 PM
AdmJLovejoy wrote:
Hi Susan, this does not appear to be true for Linux computers joined to the Domain. Please confirm.
Not sure what you are specifically referring to with "this", but both Active Scanning and Scheduled Computer Scanning should scan non-Windows machines as well. Active Scanning will only scan ones that report to domain controllers, while Scheduled Computer Scanning will pull enabled computer objects directly from AD. (Specifically, these non-Windows machines are scanned as if they were submitted for IP Address Range Scanning.)
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-19-2016 01:11 PM
Active Scanning (Active Directory Domain target in 6.0) only scans computers as they report to a domain controller. To scan all (enabled) computer objects directly from Active Directory, use Scheduled Computer Scanning instead. In Lansweeper 6.0, this is the Active Directory Computer Path target under Scanning\Scanning Targets.
