I've set this up before for an import from AD by doing the following-
- Configure the user import to bring in the LDAP distinguished name attribute and the Manager attribute
- Map the Manager attribute to the LDAP Distinguished Name field under the Manager related object (so expand Manager and map Manager from AD to LDAP Dist Name in LANDesk)
- Set this as the Target Key Attribute
- Run the import
If you're mapping from somwhere other than AD the Manager info simply needs to contain info that can be mapped to a unique field in LANDesk, i.e. Email Address, Login ID, LDAP Dist Name etc, and ocne you've mapped it to the appropriate field under the Manager related object it should populate this drop down field.
I'm pulling directly from the manager attribute in AD which is LDAP.
So map it to the existing LDAP Dist Name that I set up for comuputer association or do I need a new one for LDAP Manager Name?
I'm getting the same
"Could not find related object User.LDAP Dist Name = (it gives the fully qualified here).
That is odd, if you display the LDAP field on your user window does it show that it is populated with any data?
Or can you search specifically on the LDAP Dist Name returned by the error in LANDesk and find any record?
Oh I have the LDAP Dist Name for the user and the LDAP Manager Name populated on the User Record.
If you grab that LDAP Dist Name from one of the errors in the import log and query the User object in LANDesk can you find their Manager's LANDesk account by searching with that LDAP Dist Name?
Quick question... and maybe I am missing something. Should managers be imported into "Account Managers"?
Yes I can. I can query the LDAP name in the error against the End User and it'll show me that record.