Data Analytics powered by Landesk
LDAP export wizard
You can use an LDAP export rule to export inventory database attributes to an LDAP data source, such as Active Directory. This wizard includes an LDAP browser to help you easily find the proper LDAP container to export the attributes to.
Open the wizard by right-clicking LDAP Export in the DTS tree and selecting New rule. Enter a unique name and description for this rule, then select the database where the rule will store the data it gathers. On the continuing pages, enter the following information:
Use this page to set up a connection to your LDAP data source.
LDAP://: The path for the LDAP server, usually just a server name or IP address.
Use anonymous access: An option to connect to the LDAP server anonymously; use only if you're required to.
- User name: The user name to connect to the LDAP server. For Active Directory, use the format <domain>\<user>.
- Password: The password for the LDAP user.
Use this page to select the LDAP container that the rule will map to when exporting the database attributes.
- LDAP container: The LDAP container you want the rule to map to and search. Click the ellipsis (...) button to open an LDAP browser for searching LDAP objects in the current tree that you have rights to see. This LDAP browser is similar to the Active Directory Users and Computers browser.
Browse to an LDAP object, right-click it in the right pane, and select View Properties to view all possible LDAP properties for this object type.
- Search subcontainers: Subcontainers of the specified LDAP container that the rule will search. To search the entire tree, select this check box and leave the container field blank.
It's necessary to map an attribute to the property of an LDAP object type. You can select one of the two default mappings that are configured (User or Computer), or select Other to configure your own mappings.
- User: Maps the Computer.Login Name attribute to the SAMaccountName property for user objects.
- Computer: Maps the Computer.Device Name attribute to the cn property for computer objects.
- Other: Opens a dialog where you can customize the mapping between the database and an LDAP object. For example, you may want to use Computer.Primary Owner instead of Computer.Login Name for the Ivanti attribute. In this dialog, the Object type is the LDAP object to search for, the Ivanti attribute is the database attribute to use as a source for searching, and the LDAP property is a property that must match the attribute value.
This page lists the database attributes you want to export and the LDAP properties they'll be stored in. You can export as many attributes as you want. Click the Add button to include attributes in this list.
Once you've added all the attributes you want to export, click the Finish button. Your new rule will appear in the LDAP Export > All Rules folder.
From this page, you can select the attributes you want to export and the LDAP properties they'll be stored in.
LDAP property: The property to store the attribute data in.
Instead of property use static value: You may want to add a particular fixed value when exporting, such as where the data should go or the location, regardless of what is in LDAP.
Value: The static value to use.
Database attribute: The attribute to map to.
VBScript textbox: You can use VBScript to modify the returned value (optional). Click the Test button to verify that the VBScript works.
Was this article useful?
The topic was:
Not what I expected
Copyright © 2017, Ivanti. All rights reserved.