Hi everybody,
it is hard to categorize which part of the forum is the correct one because the problem stretches to multiple problems.
Since I migrated from Exchange 2010 SP3 to Exchange 2013 SP1 I have problem with the name resolution as I believe it should work. (BTW: we are using AD 2012 R2)
When I am trying to search for an user in the addressbook in outlook (2013 and 2016) with the samaccountname I can't find the user (using GAL so no offline address book). I actually can only find the user while using his last name (surname does not work
either)
When I am writing an E-Mail via ActiveSync or OWA-Client and I try using the samaccountname in from,cc,bcc it does not work either. I am not sure about the GAL but I am very certain (as are my co-workers) this was possible before the migration.
(However it works with e-mail/name -> using "Mark" in OWA or ActiveSync I will get every user who has that in his name/email (Mark, Markus, Marketing, etc.)
When I am writing an E-Mail with Outlook and I am using samaccountname in from,cc,bcc it wont recognize the user while searching for it for the very first time. If I type in every samaccountname I want (seperated with an ; of course) and I use the "check
name"-button it works.
But with an exception that I dont think is right. For example: if I have an samaccountname "mark" and I am using that in outlook with the name resolution -> I have to choose between every single user that has "mark" somewhere in his
name (e.g. everybody called Mark or Markus)
However: if I type in =Mark he will find the exact user after using the "name resolution"-button
So I started googling where this problem could come from and I stumbled upon
ambiguous name resolution (ANR).
I found an old article (2004 - hell):
https://blogs.technet.microsoft.com/exchange/2004/08/23/why-we-named-a-bit-in-the-directory-after-billg/
After reading that I checked via ADSI-Editor if the mentioned dSHeuristics-Attribut inCN=Directory Service,CN=Windows NT,CN=Services,CN=Configurationwas set with the value 1 or 1000.
But the value is not set and according to this article this should turn off ANR.
Besides that I really dont understand the mentioned 4th character - maybe here are some changes since server 2003. I can only set dSHeuristics in the properties of the CN=directory-service (maybe I am missing something)
My problem is now that I do not know if this could essentially be the problem or if this feature was somehow replaced or is configured somewhere else in the AD (since between 2004 and 2016 (2012 R2 AD) could change a lot)
And if this is the right place -> is it really deactivated, could this be my problem and is the number 1000 still the right one or did this change?
I would really appreciate any help to solve this since my colleagues really wanna use the samaccountname to search via activesync on their smartphone instead of typing the IP-Address - same for OWA and Outlook.
Ask away if anything is unclear.