/build/static/layout/Breadcrumb_cap_w.png

User Import from Active Directory

So we are getting ready to implement our Help Desk from Kace but I want to import the users first so I can assign them to their device assets as well. The problem i am running into is that it is not pulling the email address in from Active Directory. My AD admin wants to know what field KACE is looking in for this but i don't know. Does anyone here? Thanks

0 Comments   [ + ] Show comments

Answers (4)

Answer Summary:
Used the mail option from the drop down.
Posted by: airwolf 12 years ago
Red Belt
0
You specify the field you want to map when you setup the import...
Posted by: andibogard 12 years ago
Blue Belt
0
samaccountname

I believe is what he's asking for.
Posted by: airwolf 12 years ago
Red Belt
0
The OP is looking for the email address, which is typically denoted in AD by the "mail" attribute.

"Samaccountname" is not the email address - it's typically used to denote logon name.
Posted by: andibogard 12 years ago
Blue Belt
0
Correct... I misread. Question to the OP though. What is the naming convention for the email addresses in your company?

For example we use

username: jdoe
email address jdoe@company.com

We aren't using the helpdesk, but we are using the Software Library portion of the user portal. The only ldap server we configured has

(samaccountname=KBOX_USER) as the search filter.

Not sure if this is correct, but this works for us. Username Full name and email address are pulled from AD without any issue.
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ