To see which assets are currently being scanned by your Lansweeper installation and which are queued for scanning, access the following section of the web console: Scanning\Scanning Queue. If you have multiple scanning servers, there will be multiple tabs within this menu, one queue for each server.
- There is a queue showing scanned IP addresses and one showing scanned Windows computers. If a Windows computer is scanned based on IP address, it will first show up in the IP queue and then move to the Windows queue once it's been identified as a Windows computer.
- The following types of scans are not visible in your scanning queue but processed silently in the background: Active Directory User/Group Path, AirWatch, AWS, Azure, Chrome OS, Intune, Office 365, SCCM, event log and warranty scans.
- Scans are performed in batches. Scans with a spinning wheel icon are currently in progress. The remaining scans are queued for processing. The number of concurrent scans is determined by the Computer Threads and IP Threads values configured in the Service Options section of the following page: Configuration\Server OptionsComputer thread or IP thread changes won't take effect until you restart the Lansweeper Server service on your Lansweeper server.
- In general, new scan requests are added at the end of the queue and are processed when all previously initiated scans have finished. However, event log scans and scan requests initiated with Batch Scanning or the Rescan buttons are moved to the top of the scanning queue, if the specified assets are not already in the queue. These scans receive priority, though event log scans are not actually visible in the queue.
- There is a Clear queue button per scanning server that allows you to remove any queued scan requests from the scanning queue of that server. Scans already in progress will still be completed.