Hello,
Some months ago, I set up an AD import on a test installation of SDP. This was back on version 9 or 10. I had no real trouble and the import worked well.
I have tried to set up the same AD import on our live system today, running version 11, but I have a problem. The import is only partially successful.
It depends on the status of the "Login name" field from the User. All existing users have been created automatically by e-mail ticket import, or manually by technicians. In most cases it is blank therefore. The effect on the AD import is:
- If the Login Name is populated, the user details are imported from AD and overwritten in the database.
- If the Login Name is blank, the user is not imported from AD.
It seems this was not the same behaviour with version 9 or 10, as I did not have this issue in the past.
The repeating error from serverout0.txt which appears to relate to the import is as follows:
- [com.manageengine.mdh.MDHUsers]|[SEVERE]|[59]: Exception while getting user credentials in getUserId. Assuming Non-Login view.|
At the moment, I am using local authentication only, however I have tried to enable AD authentication and it does work.
Is there a way I can make the AD import use the e-mail address for matching the existing User records with the new data imported from AD? If not, I shall have to manually set the Login Name for the 100+ users we have.
On a related note, both the old test system and the live system will not suggest any users for deletion when the checkbox is enabled for deleting users (manually). I am only importing users from one specific OU of our large corporate tree. 'Deleted' users are moved to another part of the tree which SDP is not importing from. Should this be enough for SDP to consider the user 'deleted'? I would have thought so.
Many thanks,
Martyn