Kris gave some very good tips in his post, the most important one being that you should narrow down your IP ranges as much as possible, under Configuration\Scanning Methods. This would force Lansweeper to start a full active scan every time the service started though and may cause more harm than good. Also increasing the Check Interval from 15 minutes to 30/60 minute or even 4 hours may also help.Īn unsupported way to do it would create a scheduled task to start and stop the Lansweeper service so that it is not running during the day. I do not believe there is a way to stop active scanning during the day (well, supported at least), but you can increase the Minimum Time Between Scans to more than 20 hours so that devices aren't scanned every day. I believe you can increase it higher, but you may not want to. Default is 12, 20 should be fine (depending your scanning server). Tip 5: Under 'Server Options' increase the number of simultaneous IP address scans. You can't tell it to stop at a certain time, but you should be able to set them up well enough that all ranges are done by the time the work day starts. This will skip trying to do any WMI queries which in turns doesn't have to wait for a fail response. Tip 3: Check No Windows for any subnet you know does not have a windows device (printers, wyse terminals, etc). Tip 2: Change the timeout to 1 instead of 4, this will fail unused IP's faster. Tip 1: The more narrow the range the faster it will scan since it does not have to scan IP's that have nothing on them.
But take note of any performance issues that may come from the following changes as they may not work the best, or be practical, in all environments. For each of the IP scan ranges use the following tips. Under Configuration go to Scanning Methods (which I'm sure you've already been here). There are ways to make this faster, but would require a lot of configuration if you have 1000 subnets.
0 kommentar(er)
