Options
- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
05-17-2022
01:55 PM
LsAgent scans don't generate scanning errors as the agent has the required admin rights to locally scan the machine.
If you are scanning your devices with LsAgent and see scanning issues like RPC unavailable, firewall issues, access denied, etc., these are most likely the result of agentless scans that are still targeting the concerning devices.
To resolve this, ensure that your agentless scanning targets under Scanning > Scanning Targets no longer target the machines you're scanning with LsAgent. This can be done by either removing or disabling the concerning scanning targets or adjusting their scope.
Please note that setting up a scanning exclusion for the concerned devices will prevent the LsAgent scans from being imported, and no record is created in the database.
If you are scanning your devices with LsAgent and see scanning issues like RPC unavailable, firewall issues, access denied, etc., these are most likely the result of agentless scans that are still targeting the concerning devices.
To resolve this, ensure that your agentless scanning targets under Scanning > Scanning Targets no longer target the machines you're scanning with LsAgent. This can be done by either removing or disabling the concerning scanning targets or adjusting their scope.
Please note that setting up a scanning exclusion for the concerned devices will prevent the LsAgent scans from being imported, and no record is created in the database.
Was this post helpful? Leave a Kudo!
Did you have a similar issue and a
different solution? Share your work in the comments below and help your fellow IT Hero's!
More questions?
Browse
our
Quick Tech Solutions
or
Community Forum.
If you can't find what you're looking for, create a post in our Community Forum.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
