cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Camille
Engaged Sweeper

When using "rescan", the items excluded in "scanned item interval" are not ignored.

I set items "CERTIFICATES" and "EVENTLOG" LsAgent Only, all items are still scanned, it takes more than 5 minutes per asset.

Lansweeper version is 10.3.1.0

3 REPLIES 3
Obi_1_Cinobi
Lansweeper Tech Support
Lansweeper Tech Support

Hello there!

Unfortunately, this is indeed a known bug in the current Lansweeper version (version 10.3). This bug was logged under bug ID: LAN-14483. We cannot provide you with an ETA for a fix at this time.

treespanner
Engaged Sweeper II

Same here.  I updated to 10.3.1 and multiple issues have arisen.  

1. Scan durations have increased dramatically.  Previously Windows assets took 45 seconds or so.  Currently scans take 5+ minutes per device.

2. Disabling scanned item interval doesn't exclude from scanning server scans or from History even when unchecked.  

3. Domain credentials would not detect credentials so after digging through forum posts someone said to remove any preferred domain controllers and add them back later.  That fixed it so thank you whomever you are.

I will say the UX and feel of the web gui is the best I've version I've used, not much lag and moving from link>link is fast and smooth.  My only gripe since I use LS all day is I wish I didn't have to type my orgs pc location/device prefix info just to get the last 3/4 characters.  You can do exactly this when at the deployment page>deploy now>selection instead of typing AB123-PCINFO999 you can type 999 and get any asset with 999, extremely useful and time saving.  

Obi_1_Cinobi
Lansweeper Tech Support
Lansweeper Tech Support

Hello there!

For issue 1, we would recommend reaching out to tech support: https://www.lansweeper.com/contact-support/

For issue 2, this is indeed a known bug in the current Lansweeper version (version 10.3). This bug was logged under bug ID: LAN-14483. We cannot provide you with an ETA for a fix at this time.

With regard to issue number 3, this was resolved in our latest release (Lansweeper 10.3.2.0). You can update to the latest Lansweeper version by following the steps in this guide: https://www.lansweeper.com/knowledgebase/updating-your-installation/

If needed, you can always check our changelog to see all the additions, changes, and fixes that have been implemented in the Lansweeper software: https://www.lansweeper.com/changelog.aspx