Aliases & Case insensitivity for service accounts found via Windows autodiscovery

Paula Kingsley

• April 18, 2015 00:07

Depending on how the service was configured to run in Windows, it may show up as USERNAME, DOMAIN\Username, DOMAIN\userName, username@domain.local, USERNAME@domain.local, UserName@domain.local. Several of the above generate dupe end users in D42.  

It would be great if the discovery would ignore case differences

AND

If the End User properties in D42 would allow us to add aliases so that username@domain.local, username@anotherUPNhere.domain.local, USERNAME, can all be the same object. 

0

• 

  Joe Schmitt

  • April 22, 2015 15:56

  This will be addressed in the next release.

  Three changes where made to accomplish this

  1. domain and username are properly parsed in the windows discovery client as separate items
  2. End users (user and domain) look-ups are now done case-insensitive
  3.  Merge user functionality has been added to the end users screen to so you can bulk correct existing end users

  0

Please sign in to leave a comment.