You can search an LDAP directory for devices to add to your ZENworks database. The directory can be one that is already defined as a user source in your Management Zone, or it can be a new directory.
You can recursively search for device in all the directories from the root context. Or, you can limit the search by specifying one or more contexts to search. Device objects that are found are queried for well-known attributes (dnsHostName, OperatingSystem, wmNameDNS, wmNameOS, and so forth) to attempt to determine the OS version and DNS name of the device.
Before performing an LDAP discovery, make sure the following prerequisites are satisfied:
An LDAP search requires the ZENworks Server to provide credentials that give read access to the contexts being searched. When accessing Novell eDirectory, the account also requires read rights to the WM:NAME DNS attributes on the workstation and server objects.
An LDAP search of Active Directory requires the ZENworks Server to use a DNS server to resolve the device’s DNS name (as recorded on the object’s DNS name attribute in Active Directory) to its IP address. Otherwise, the device is not added as a discovered device.
You use the Create New Discovery Task Wizard to create and schedule an LDAP discovery task:
In ZENworks Control Center, click the
tab.In the Discovery Task panel, click
to launch the New Discovery Task Wizard.Complete the wizard by using information from the following table to fill in the fields.
Wizard Page |
Details |
---|---|
Select Discovery Type page |
Select .Specify a name for the task. The name cannot include any of the following invalid characters: / \ * ? : " ' < > | ` % ~ |
Enter LDAP Settings page > field |
The Enter LDAP Settings page lets you identify the LDAP directory and contexts where you want to perform the discovery task. A preconfigured LDAP source is one that has already been defined as a user source in your Management Zone. If you want to select a new source, see Enter LDAP Settings page > Specify an LDAP Source field. To use a preconfigured source:
|
Enter LDAP Settings page > field |
You can create a new connection to a LDAP directory in order to discover devices in the directory. If you want to use an existing connection, see Enter LDAP Settings page > Search pre-configured LDAP source field above. To create a new connection to an LDAP directory:
|
Discovery Settings page |
LDAP discovery retrieves the hostname, operating system type and version, and IP address of a discovered device from the LDAP source. Based on the selected discovery technologies, you can obtain the following additional information on a device:
To obtain additional information on a device:
|
Set the Discovery Schedule page |
Choose whether you want the task to run as soon as it is created (the option) or if you want to schedule the task to run at a future date and time. If you select , choose one of the following schedules:No Schedule: Indicates that no schedule has been set. The task does not run until a schedule is set or it is manually launched. This is useful if you want to create the task and come back to it later to establish the schedule or run it manually. Date Specific: Specifies one or more dates on which to run the task. Recurring: Identifies specific days each week, month, or a fixed interval on which to run the task. For more information about the schedules, click the button. |
Select Primary Server page |
Select the ZENworks Server that you want to perform the deployment task. |
Select Windows Proxy page > field |
Select this option if you want to override the Windows Proxy settings configured at the Management Zone in order to modify the settings of a task. A Windows Proxy is primarily used for Linux Primary Servers that cannot perform Windows-specific discovery tasks. However, you can also use a Windows Proxy for Windows Servers if you want to discover devices in a different subnet than the Primary Server. In order to protect information, such as a discovery credential, that is passed between the ZENworks Server and the Windows Proxy, the connection between the ZENworks Server and the Windows Proxy is secured through SSL. |
Select Windows Proxy page > field |
Select this option if you want to use a Windows Proxy instead of the Windows Primary Server to perform the discovery tasks. Discovery through WMI, WinAPI and SNMP requires certain ports to be reachable on the target devices, so the Primary Server can send Remote Registry, WMI, or SNMP requests to the target devices. Ports are opened by adding them as an exception in the Windows Firewall configuration settings. By default, the scope of the exception applies only to the local subnet. If the target device is in a different subnet than the Primary Server from which the discovery is run, you need to add the IP address of the Primary Server as an exception. However, if you use a Windows Proxy in the same subnet as a target device, you do not need to change the scope of the Windows Firewall exception. Windows Proxy: Select the managed Windows device (server or workstation) on which you want to perform discovery tasks on behalf of Linux Primary Servers or Windows Servers. Windows Proxy Timeout: Specify the number of seconds you want the ZENworks Server to wait for a response from the Windows Proxy. |
When you finish the wizard, the discovery task is added to the list in the Discovery Tasks panel. You can use the panel to monitor the status of the task. As devices are discovered, they are listed in the Deployable Devices panel.