Exchange 2003 User Name Resolution Appearance in OUTLOOK 2003

Posted on 2005-04-07
Medium Priority
Last Modified: 2012-05-05
Hello --- I have noticed a wierd behavior in OUTLOOK 2003 with regards to name resolution of Exchange users in my organization and am wondering if anyone could tell me why this occurs.  

I have an Exchange 2003 server (sp1) that runs on a W2k3 server to which I recently migrated my exchange environment from Exchange 5.5 on Win NT 4.0 (which has been taken out of the Exchange site).  My users are all using OFFICE 2k3 which means they now use OUTLOOK 2003 for email.

When a user types in the name of an individual from the Global Address List who is a member of the organization, their Display Name appears along with a bracketed alphanumeric code, i.e., <B758237B> , while others show their display name along with their alias, i.e., John Doe <jdoe> .  

I know that OUTLOOK caches names of correspondents used repeatedly in a hidden local file (whose name escapes me).  Does anyone recognize what it's doing in this instance?  Is it OUTLOOK, or is EXCHANGE doing this?  Please advise; thanks.
Question by:nmorris510
  • 2

Accepted Solution

MontyV earned 750 total points
ID: 13745174
Delete the .nk2 file in the local directory of the computer.  Usually it is in this directory and will be recreated automatically when you restart Outlook.  Close Outlook first when you do this.

C:\Documents and Settings\<username>\Application Data\Microsoft\Outlook

Here is the link that will describe what each file does and where it is.


Author Comment

ID: 13785074
Thanks very much for the suggestion, MontyV; however, this does not resolve the issue for me.  The same strange name resolution behavior soon occurs even with a brand new .nk2 file.

Mind you, this does NOT mean the names don't resolve at all, they DO.  It's just that for some of the names, as I describe above, you get the alias appearing in brackets after the display name, and for others the display name appears with an alphanumeric code in brackets.  I'm trying to figure out where this comes from but I can't find the information I need on Microsoft's web site.

The only other pattern I *thought* I had discerned that may be relevant is that some of the names which resolved with the alphanumeric code are ones whose user accounts were migrated into Active Directory 2003 from a Windows NT 4.0 domain prior to putting up Exchange 2003.  User accounts created after the AD 2k3 domain assumed control did not appear initially to behave in this fashion; however, I have since determined that the same can be said of a number of other user accounts that were migrated over from the NT 4.0 domain, so that can't be it necessarilly.  I also checked the possiblity that the information was being read from the "pre-Windows 2000 login name" field in AD; however, this field appears as it should for ALL the users concerned.

If anyone has any ideas what might be generating this "bracketed alphanumeric code", I'd appreciate the information.  Thanks.


Author Comment

ID: 14322176
Sorry for not getting back to close this out sooner.

FYI:  AD is the source of this issue; I did some poking around in my AD environment using ADSIEDIT and found that the following AD setting was the source of the alphanumeric code:  


Doing a partial modification of the data in this field to replace the alphanumeric code with the user's correct alias resolved the issue, with 2 caveats:

1.  The user has to re-create his/her OUTLOOK 2003 desktop profile, as this modification "breaks" their existing one.

2.  The information other users have in their nickname or. nk2 files for the user with the changed alpha code will find their emails to said person using the existing entry will BOUNCE.  The altered user's reference in the nickname file has to be changed to the reference to the newly-altered user in the GAL.

Thanks to MontyV for the suggestion.



Featured Post

Easily manage email signatures in Office 365

Managing email signatures in Office 365 can be a challenging task if you don't have the right tool. CodeTwo Email Signatures for Office 365 will help you implement a unified email signature look, no matter what email client is used by users. Test it for free!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This article will help to fix the below errors for MS Exchange Server 2016 I. Certificate error "name on the security certificate is invalid or does not match the name of the site" II. Out of Office not working III. Make Internal URLs and Externa…
Today as you open your Outlook, you witness an error message: “Outlook is using an old copy of your Outlook Data File…”. Probably, Outlook is accessing an old OST file.
Many of my clients call in with monstrous Gmail overloading issues with Outlook. A quick tip is to turn off the All Mail and Important folders from synching. Here is a quick video I made to show you how to turn off these and other folders in Gmail s…
This is my first video review of Microsoft Bookings, I will be doing a part two with a bit more information, but wanted to get this out to you folks.
Suggested Courses

588 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question