The LANDesk
Unmanaged device discovery (UDD) tool is accessed from the main
LANDesk console
(Tools > Configuration > Unmanaged Device Discovery).
This tool provides a way for you to find devices on your network
that haven't submitted an inventory scan to the LANDesk core database. UDD has
multiple ways of finding unmanaged devices. This tool also provides
Extended device discovery (XDD), which relies on a device agent
that listens for network ARP and WAP broadcasts. The extended
device discovery agent on a device then checks discovered devices
for the LANDesk agent.
If the LANDesk agent
doesn't respond, extended device discovery displays the device in
the Computers list. Extended device discovery is ideal in
situations involving firewalls that prevent devices from responding
to the normal ping-based UDD discovery methods.
The Unmanaged device discovery chapter
introduces this tool. In that chapter you'll find overview
information, as well as step-by-step instructions on how to use all
of the tool's features.
This chapter contains the following online help sections that
describe the Unmanaged device discovery tool's dialog boxes. From
the console interface, these help sections are accessed by clicking
the Help button on their respective dialogs boxes.
About the Scanner
Configuration dialog box
Use this dialog box to customize and launch unmanaged device
scans. To access this dialog box, at the Unmanaged device
discovery tool windows, click the Scan network toolbar
button.
Saved configurations: Shows the saved scanner
configurations. Save a configuration by changing the settings you
want, then clicking New, name the configuration, and with
your new configuration selected, click Save.
More >>: Expands the dialog box to show
discovery options.
Network scan: Discovers devices using an ICMP
ping sweep. This is the most thorough and recommended discovery
method.
IP OS fingerprinting: An additional level of
discovery that uses packet responses to try and determine the
installed OS on a discovered device.
Use SNMP: An additional level of discovery
that uses SNMP for device detection.
Discover devices with LANDesk CBA installed:
Discovers devices with the CBA agent running. If your devices have
CBA, this is the fastest discovery method.
Discover devices with LANDesk PDS2 installed:
Discovers devices using the older LANDesk PDS2 agent. You can only
select this option if you select CBA discovery first.
Discover devices using NT domain: Discovers
devices in a Windows NT domain. This option uses the NT domain
account information and doesn't require an IP address range, though
you can specify one. Select this option and click Configure
to show the NT domain configuration
dialog box where you can customize the NT domain discovery
settings.
Filter by IP range (for both NT domain and
LDAP): Filters NT domain and LDAP discovery by the IP ranges
specified in Starting IP and Ending IP.
Discover devices using LDAP: Discovers devices
in an LDAP directory. Select this option and click Configure
to show the LDAP configuration
dialog box where you can customize the LDAP discovery
settings.
Discover IPMI-enabled devices: Looks for
servers enabled with Intelligent Platform Management Interface,
which allows you to access many features regardless of whether the
server is turned on or not, or what state the OS may be in.
Discover Intel vPro AMT devices: Looks for
Intel Active Management Technology-enabled devices. Intel vPro
devices appear in the Intel vPro folder.
Discover virtual hosts: Looks for servers
running the VMware ESX Server.
Starting IP: Enter the starting IP address
for the range of addresses you want to scan.
Ending IP: Enter the ending IP address for
the range of addresses you want to scan. UDD automatically updates
this field as you type the Starting IP, but you can change
the ending IP address manually. Ending IP is calculated
using the value of Subnet mask + what is typed in
Starting IP.
Subnet mask: Enter the subnet mask for the IP
address range you're scanning.
Add and Remove: Adds or removes your
IP address ranges from the work queue at the bottom of the dialog
box.
Schedule task: Schedules the scan based on
your settings. You can customize the start time in the Scheduled
tasks window. Scheduled scans originate from the core
server.
Scan now: Starts the scan immediately based
on your settings. Scans started here originate from the console
you're at. Once you start the scan, a Scan status
dialog box appears showing the total number of devices found, how
many existing devices were updated, and how many new unmanaged
devices were added.
About the NT domain
configuration dialog box
Use this dialog box to configure how you connect to the domain
you want to scan.
Domain: Enter the domain you want to
scan.
Log in as current user: Select this if you're
logged in as a user with access to the domain you're scanning.
Log in as: Select this if you aren't logged in
as a user with access to the domain you're scanning. Also enter a
User name and a Password.
Use domain info: Uses information from the
domain about the detected device OS.
Add and Remove: Add each domain you
configure and want to scan to the work queue by clicking
Add. Click Remove to delete the selected domain from
the work queue.
About the LDAP
configuration dialog box
Use this dialog box to configure how you connect to the LDAP
directory you want to scan.
LDAP://: Enter the LDAP directory you want to
scan.
Log in as current user: Select this if you're
logged in as a user with access to the directory you're
scanning.
Log in as: Select this if you aren't logged on
as a user with access to the directory you're scanning. Also enter
a User name and a Password.
Select individual OUs: Select the OUs that you
want to scan. Click Add to add them to the work queue. Click
Remove to delete the selected OU from the queue.
Active directory path: Shows the active
directory path, if applicable.
Configuring SNMP
scans
Network scan discoveries can use SNMP. Depending on your
network's SNMP configuration, you may need to enter additional SNMP
information in UDD. Click Configure next to the SNMP
option to show the SNMP configuration
dialog box, which has these options:
Retries: How many times UDD retries the SNMP
connection.
Wait for response in seconds: How long UDD
should wait for an SNMP response.
Port: What port UDD should send SNMP queries
to.
Community name: The SNMP community name UDD
should use.
Configure SNMP V3: UDD also supports SNMP V3.
Click this button to configure SNMP V3 options in the SNMP V3
configuration
dialog box.
The SNMP V3 configuration
dialog box has these options:
User name: The username UDD should use to
authenticate with the remote SNMP service.
Password: The password for the remote SNMP
service.
Authentication type: The authentication type
SNMP is using. Can be MD5, SHA, or None.
Privacy Type: The encryption method the SNMP
service is using. Can be DES, AES128, or
None.
Privacy Password: The password to use with the
specified privacy type. Not available if you selected a privacy
type of None.
About the ARP (or WAP)
Discovery Settings list dialog box
Use this dialog box to manage your ARP and WAP settings that are
used for extended device discovery. Once configured, you can apply
XDD settings to scan tasks.
This dialog box contains the following options:
New: Opens the settings dialog box where you
can configure the discovery method options.
Edit: Opens the settings dialog box where you
can modify the selected setting.
Copy: Opens a copy of the selected setting as
a template, which you can then modify and rename. This is useful if
you want to make minor adjustments to settings and save them for a
specific purpose.
Delete: Removes the selected setting from the
database.
Note that the selected setting may currently be associated with one
or more tasks or managed devices. If you choose to delete the
setting, devices with that setting still have it and continue to
use it until a new agent configuration task is deployed; scheduled
tasks with that setting still run on target devices, as do local
scheduler tasks with that setting, until a new configuration is
deployed.
Close: Closes the dialog box, without applying
a setting to the task.
About the Configure ARP
Discovery Settings dialog box
Use this dialog box (Configure extended device discovery
toolbar button > Configure ARP discovery settings) to
customize ARP-based extended device discovery scan settings.
Configuration name: Identifies the setting
with a unique name. This name appears in the settings drop-down
list on the settings list dialog box.
Duration ARP entry stats cached (in seconds):
How long devices with the extended device discovery agent keep an
address in the ARP table. Devices in the ARP cache won't be pinged
after the initial discovery ping. The default is 24 hours (86,400
seconds). The minimum value is 900 seconds.
Maximum delay before pinging an unknown device for
the LANDesk agent (in
seconds): When a new ARP is recognized by a device with the
extended device discovery agent, the device waits two minutes for
the detected device to boot and then waits a random amount of time
within the value you specify here. The agent with the shortest
random wait will ping first and then UDP broadcast to the subnet
that it took care of the ping for that device. If you have multiple
extended device discovery agents installed, this prevents devices
from generating excess traffic by all pinging at the same time. If
you set this too high, unmanaged devices may leave the network
before they can be pinged. If you set this too low, multiple agents
may ping and report the same device. The default is one hour (3,600
seconds).
Frequency the cached ARP table is refreshed (in
seconds): How often the device writes the ARP cache to disk so
the data isn't lost in case the device shuts off, crashes, or
reboots. The default value is five minutes (300 seconds).
Logging level: The local extended device
discovery logging level for errors (1), warnings (2), or everything
(3). The default level is 1- errors only. Logs are stored locally
in C:\Program Files\LANDesk\LDClient\xddclient.log.
Force logging level: Overrides the log level
setting from the core server. If you clear this option, you can set
the log level manually on a particular device. This can be useful
for troubleshooting a particular device without having to change
the log level on all devices. This is enabled by default.
About the Configure WAP Discovery Settings dialog box
Use this dialog box (Configure extended device discovery
toolbar button > Configure WAP discovery settings) to
configure WAP-based extended device discovery scan settings.
This dialog box contains the following options:
Configuration name: Identifies the setting
with a unique name. This name appears in the settings drop-down
list on the settings list dialog box.
Frequency of WAP scan (in seconds): Specifies
how often the extended device discovery agent scans for WAP
points.
Logging level: The local extended device
discovery logging level for errors (1), warnings (2), or everything
(3). The default level is 1- errors only. Logs are stored locally
in C:\Program Files\LANDesk\LDClient\xddclient.log.
Force logging level: Overrides the log level
setting from the core server. If you clear this option, you can set
the log level manually on a particular device. This can be useful
for troubleshooting a particular device without having to change
the log level on all devices. This is enabled by default.
About the ARP discovery
history dialog box
Use this dialog box (Configure ARP discovery history
toolbar button) to configure how the core server maintains the ARP
discovery history. This history data is used for generating
extended device discovery reports. The options in this dialog box
don't affect the discovered devices you see in the main unmanaged
device discovery window. This history only applies to devices that
were discovered through ARP discovery and that don't have
LANDesk agents on
them.
Maintain history for this period of days:
Clicking this option allows you to specify how many days of ARP
discovery history data you want to save in the database. ARP
discovery history data older than the number of days you specify
will be deleted from the database during maintenance.
Clear entries manually: This is the default.
The ARP discovery history won't be deleted during maintenance.
Clear all entries now: Click this button to
immediately delete the ARP discovery history from the
database.