Lansweeper on-premises does not support supernetting, nor does it support CIDR notation for setting up IP range scanning targets. IP range scanning targets can only be defined by setting a start and end IP address for the range that you want to scan. The size of the IP range you have entered determines the scan time. When manually entering the IP range in Lansweeper, you will be presented with an estimated scan duration to help you determine the size of your scanning range.
Lansweeper does not have any limitations on the size of the subnet that is being scanned. Depending on how frequently you wish to scan your assets, the scan time must be taken into account. For example, if you wish to scan your assets every hour, then you must ensure that your scanning targets can complete the scanning process within that hour.
We would also recommend spreading the load on your scanning server by ensuring that not all scanning targets start at the same time. A staggered approach is preferred to maximize the use of available scanning threads.
Please note that you can expand your available scanning threads by distributing your scanning targets across multiple scanning servers. You can set up a combined maximum of 99 scanning threads per scanning server under Configuration\Server Options, divided between Computer threads and IP threads (one extra thread is allocated to your scan service):
- IP Threads determine the maximum number of IPs that can be scanned simultaneously.
- Computer Threads determine how many Windows computers can be scanned simultaneously.
We can't really provide detailed instructions on how much you should spread the scanning of your subnets, as this will depend on the type of assets you are scanning, your scan intervals for your Windows scan items, the CPU available for your scanning servers, network speed, to name a few.
Some recommendations though:
