Printable View
We've been running into this problem that some new users and older users that get new computers will open up Outlook and get an error stating "The name could not be matched to a name in the address list.". They then have to type their username in a box and click Check Names before it will let them check their e-mail. Their Outlook is fully updated. Our Exchange server was recently updated, and I think that was when we first started running into this problem. Has anyone else seen this problem?
I believe this is by design...
When you first run Outlook...you have to setup the user profile and exchange server.
If this continues after initial setup...then it could be another issue...such as communication.
What version of Outlook...and are you running in Cached mode?
MLF
We create the user account and e-mail account at the same time via AD w/ Exchange extensions. On the client, we have Outlook pointed to the Exchange server and user is handled by the domain login. Using Outlook 2003 and no using cached mode.
Well...I have always had to add the user even after the domain login...only once during the inital setup....Probably has to do with domain username is a different format then mailbox name
eg domain log on is JBlow
mailbox is Joe Blow
I think that may be the issue???
I also run Outlook 2003 in Cached mode....
MLF
Account naming should not matter. Once the profile has been created and mapped to the mailbox you can do whatever you want with the mailbox display name and it will still open the correct mailbox. Just have to be clear on what you are changing when you say "name."
So I have to ask, how are you creating the outlook profiles? If you are using an automated tool to create the outlook profile for the subscriber I would suspect you are not fully creating the profile. You cannot create a "new" profile that only has the server information populated without giving it the user information. Well, you can do it, but when you select that profile you will get asked what mailbox to connect to. Exchange/outlook will use the AD account for authentication, but you still have to tell the profile what mailbox to open.
If they are trying to use an older profile, and during your exchange upgrade you changed information on their AD account, such as LEDN(legacy exchange distinguished name), they may need to re-check the name to map it to what it believes is the new account.
If they are using an older profile and the users were moved to a different server and the original server is no longer online the automated profile redirection will not happen. To have a profile redirected to the new location of a moved mailbox the old server has to stay online.
We just use the Active Directory Users and Computers tool to create the accounts (with Excahnge extensions, it asks if you want to create a mailbox for them). For brevity, we just make a copy of an existing account. This not only happens to new users, though. it also happens to old users that get a new computer. And not everytime, just a select few.
We've been banging our heads against this one for weeks now. Starting to drive us nuts.
By chance are the users "Hidden" from the Global Address book?
Oh yea and there is this
http://support.microsoft.com/default...b;en-us;309622
dinowuff : no
How are you creating the profile? If it is a new user account, or an existing user gets a new computer the user will get prompted to create a new profile. Part of that process is entering the mailbox name and doing a check name... So far, I've not heard you describe anything to me that sounds unusual. Outlook has to have a configured profile to use an exchange server.Quote:
Originally Posted by delstar
as stated in previous post...this is by design.
Profiles in oulook need to be configured before connecting to an exchange server.
If the profile has to repeatedly be created on the same machine...then you have another issue.
MLF
mohaughn : yes, we go through that. Standard as everybody else that doesn't have this problem.
It's not the profile that's the problem, as far as I know. Everything in the profile creation is pretty standard around here, and only a select few have this problem. In fact, the first time they sign into Outlook, it works fine. It keeps working fine until they logoff and back in again. Then, when they start Outlook, they are given that error. If they put in their account name and click 'Check Names', it finds it and works properly. It continues to work properly until they logoff again.
From what we've seen and the Googling we've done, this isn't a common thing, and in no way by design.
What version of exchange?
What is different about these users...as in group membership???
http://support.microsoft.com/kb/322832
Are these 2000 or xp machines??
MLF
Edit> Have you tried cached mode??
Have you tried the profiles on another machine that does not experience this behavior??
Ok. Your first post made it sound like the problem only happens when existing users are given a new computer.. Which would require that a new profile be created. I did not realize from your description that this was happening to users with an established profile that has worked for some time.
Check out this article. Have you confirmed that RUS is running properly?
http://support.microsoft.com/kb/297801/en-us
Morgan : 2003, nothing in particular that's unique to them, XP, and I was wrong before, we do use cached mode, and thanks for the link
Mohaughn : thanks for the link. There's some things on there we haven't tried. I'll give it a more in-depth read and let you know how it goes.