
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-21-2016 01:11 AM
Hello,
I'm new to Lansweeper and need some help scanning my assets successfully.
I am running Lansweeper agentless and performing an IP range scan, AD domain scan, and AD User Path scan but after all the scans finish I receive scanning errors of "Never scanned OS(50), Offline or firewall errors(16), and Other scanning errors(60).
All endpoints are running a cloud based Nortan Endpoint Protection and local windows firewalls are disabled. Is there any pre-configuration that needs to happen on our host server or on any of our assets that I am not aware of? How do I have all my assets successful tagged for future reports?
Thanks,
I'm new to Lansweeper and need some help scanning my assets successfully.
I am running Lansweeper agentless and performing an IP range scan, AD domain scan, and AD User Path scan but after all the scans finish I receive scanning errors of "Never scanned OS(50), Offline or firewall errors(16), and Other scanning errors(60).
All endpoints are running a cloud based Nortan Endpoint Protection and local windows firewalls are disabled. Is there any pre-configuration that needs to happen on our host server or on any of our assets that I am not aware of? How do I have all my assets successful tagged for future reports?
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
‎04-26-2016 12:31 AM
I recommend reviewing the Windows domain scanning requirements in this knowledge base article and the troubleshooting guide for scanning errors found here. The most common causes of Windows scanning errors are credentials lacking administrative privileges on the client machines and firewalls or anti-virus software blocking WMI (Windows Management Instrumentation) traffic to the client machines. WMI data is by default sent over random ports.
A sure way to resolve any Windows scanning errors is to scan locally with our LsPush scanning agent.
A sure way to resolve any Windows scanning errors is to scan locally with our LsPush scanning agent.
1 REPLY 1
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-26-2016 12:31 AM
I recommend reviewing the Windows domain scanning requirements in this knowledge base article and the troubleshooting guide for scanning errors found here. The most common causes of Windows scanning errors are credentials lacking administrative privileges on the client machines and firewalls or anti-virus software blocking WMI (Windows Management Instrumentation) traffic to the client machines. WMI data is by default sent over random ports.
A sure way to resolve any Windows scanning errors is to scan locally with our LsPush scanning agent.
A sure way to resolve any Windows scanning errors is to scan locally with our LsPush scanning agent.
