Scanning large IP ranges for deploy
G'Afternoon
How long does it take KACE to scan an IP range? or, 34k IP addresses?
I'm currently rolling out through our organisation and have approx 1/3rd complete. Once the rollout has finished and the 98% of clients are setup, I would like to setup a single job to scan all our WAN ranges in one job (currently I have about 40/50 jobs) , I dont envision that it would be setting up that many new clients once the estate has been done.
The scan is just to catch new sites (6/7 devices generally) or sites where tills and office PC have been rebuilt (generally 1 or 2, rarely, 6/7 etc)
We use 6 class Bs, each site is it's own class C within those class Bs, and I will be scanning between .2 and .64 on each class C, approx 102K IP addresses. How an insane idea is this?
Generally how long would it take to scan that many IP addresses (assuming that each scan only results in approx 10 or so clients being installed, if that).
How long does it take KACE to scan an IP range? or, 34k IP addresses?
I'm currently rolling out through our organisation and have approx 1/3rd complete. Once the rollout has finished and the 98% of clients are setup, I would like to setup a single job to scan all our WAN ranges in one job (currently I have about 40/50 jobs) , I dont envision that it would be setting up that many new clients once the estate has been done.
The scan is just to catch new sites (6/7 devices generally) or sites where tills and office PC have been rebuilt (generally 1 or 2, rarely, 6/7 etc)
We use 6 class Bs, each site is it's own class C within those class Bs, and I will be scanning between .2 and .64 on each class C, approx 102K IP addresses. How an insane idea is this?
Generally how long would it take to scan that many IP addresses (assuming that each scan only results in approx 10 or so clients being installed, if that).
0 Comments
[ + ] Show comments
Answers (3)
Please log in to answer
Posted by:
ms01ak
13 years ago
Here's my experience,
I've scanned about 58,764 and it took a really, really, really long time. That being said, it was a provisioning scan for Mac computers. The impact on the core and the users were not noticeable (no screamed at me) but it was slow.
My strategy has been to split the the task into several smaller jobs.
Cheers,
M
I've scanned about 58,764 and it took a really, really, really long time. That being said, it was a provisioning scan for Mac computers. The impact on the core and the users were not noticeable (no screamed at me) but it was slow.
My strategy has been to split the the task into several smaller jobs.
Cheers,
M
Posted by:
nbs
13 years ago
Thanks M
I think I'm going to be far more selective about the scans and only run wider scans once or twice a month.
I think I'm going to be far more selective about the scans and only run wider scans once or twice a month.
Posted by:
cblake
13 years ago
I always recommend smaller jobs. You can streamline large jobs by bypassing port checks, but that tool is there for good reasons obviously. Alternatively suppliment the provisioning with a GPO or login script for long term solution. Ultimately working it into your images/OS installations.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.