Novell ZENWORKS 10 CONFIGURATION MANAGEMENT SP3 - SYSTEM PLANNING-DEPLOYMENT-BEST PRACTICES GUIDE 10.3 30-03-2010 System Planning Manual page 61

Use the ZENworks Migration Wizard to migrate your devices from eDirectory and target them
for deployment to avoid discovery of the initial assets that are already part of an existing
ZENworks system.
Use pilot groups.
These tips help you discover assets and roll out the ZENworks Adaptive Agent in a very manageable
way, which avoids failures for deployment and installation.
Table 4-1 lists the duration and CPU usage for a discovery task performed by using the MAC
Address technology. This information helps you configure the discovery settings in an efficient way.
Duration and CPU Usage for a Discovery Task
Table 4-1
IP Address Range
Single IP address
164.99.94.0–164.99.94.255
(254 devices)
164.99.0.0–164.99.255.255
(65,534 devices)
164.0.0.0–164.255.255.255
(16,277,214 devices)
There are several things you can do to increase the speed of IP Discovery tasks.
Increase the Maximum Concurrent Discoveries from 5 to 20. This allows more addresses to be
scanned simultaneously.
Select only the discovery technologies that are required. We recommend enabling only the
discovery technologies that are configured within the environment. If SSH, NMAP, or SNMP is
not available or is not configured in the environment do not enable it. Every discovery
technology that is scanned for an IP address adds time to the discovery task. As a rule of thumb,
start with only WinAPI and the ZENworks discovery technologies enabled for the Management
Zone. You can override discovery technologies in the Discovery task, which means that
specific discovery technologies can be directed at certain subnets.
Duration of the
CPU Usage
Discovery Task
Less than 1 minute Less than 5%
10 minutes 5%
30 hours 36%
Always in a Pending 100%
state
Additional Details
The discovery task starts
immediately when it is launched.
The discovery task starts
immediately when it is launched.
The discovery task starts
immediately when it is launched.
The discovery task is not
started. The status of the task
remains as Pending.
CPU usage is normal 10
minutes after the time the
discovery task is launched.
If any other discovery or loader
task is running simultaneously,
it might take a considerable
time to complete.
Performing Design Activities 61