Summary:  Occasionally, users will have their email sourced to an outside hosting company. When companies do this, best practices call for importing the user email address into their Active Directory listing, but this does not always occur. When the email address is not listed in AD, LDAP importation will fail. Users can still be added, but they are added as they log into the KBOX, rather than being imported all at once.

Solution:

So how do we get around this?

For this guide, we will assume that the Base DN and Search Filters for the authentication server are already set correctly and we will move on to scheduling the import.

Configure Step 1 normally, adding any attributes the customer needs in addition to the listed defaults.

In Step 2, configure LDAP Uid and User Name fields normally. For Email, use “userprinciplename”.

Set your role to whatever you need it to be and then click Next.

Notice that the Email field now shows username@domain.local. These users can now be imported via LDAP.

Cautions:

Notice that the Email field now shows username@domain.local. These users can now be imported via LDAP.

If the domain is configured with .local, the email functionality of the helpdesk will not work for these addresses.

If the domain is configured with a .com or the like, email may work, but only if the externally hosted email uses the same username@domain.com naming convention. If the externally hosted email does not match, email will not work from the helpdesk.