E-Mail Account Rename
Hi! We renamed a Exchange 2007 E-Mail Account and make a new one with the same name that was renamed but e-mails for the new account are going to the renamed one. Is there any solution for this or we have to ask every user to select the e-mail addresses from GAL and not from cache? Secondly, how many internal recepients a outlook user can send e-mail to in exchange 2007? Thanks!
August 23rd, 2010 2:13pm

Total number of recipients is defined can be defined at several places: http://technet.microsoft.com/en-us/library/bb310760.aspx http://technet.microsoft.com/en-us/library/bb310760(EXCHG.80).aspx Restrict the Number of Recipients per Message As for the rename, are all messages going to the old mailbox? Or just replies? Are the outlook clients in cache mode or online? If cache mode, has the new OAB been generated on the server yet and have the clients dowloaded the updated OAB? how about OWA? Does the problem exist there?
Free Windows Admin Tool Kit Click here and download it now
August 23rd, 2010 2:30pm

OAB was regenerated after we renamed the account. It is happening both with OWA and Outlook. Outlook is in cached mode. Thanks!
August 23rd, 2010 5:51pm

Chances are what is happening is users have the original users GUID cached in Outlook (the type ahead "feature" in outlook) and so the users start typing and what they think is the new account, is actually the old accounts addressing. The solution would be to have the user start typing the account's display name and if it populates, delete that entry, then pull it from the GAL which will re-populate the users cache. This is assuming the two accounts don't have conflicting SMTP addresses ;) Good luck!
Free Windows Admin Tool Kit Click here and download it now
August 23rd, 2010 7:16pm

This is happening OWA as well? What if they pick the address explicitly from the GAL?
August 23rd, 2010 7:34pm

I never found the specifics on it, but OWA also stores such addresses. Keeping in mind the Display name you see isn't what these clients are using, but the GUID is what is stored, then resolved locally. Once this entry is cleared pulling the user from the GAL will update (and re-add) the cached information. If they are using an updated version of the GAL and your still having this issue, it may be worth testing out of cached mode, and consider deleting client cache files. I have also run into problems where even though I have generated an updated OAB it never actually gets updated. When in a CCR cluster I found that the primary mailbox server (where the OAB is generated) will fail to have permissions if currently on the passive node. You will need to increase logging to see the errors about this, but it's clear when this happens.
Free Windows Admin Tool Kit Click here and download it now
August 23rd, 2010 7:47pm

How addresses are cached depends on the version of Outlook. Outlook 2010 does not use a nickname file unlike pervious versions of Outlook. ( Instead it uses suggested contacts) The cached addresses in OWA are in the mailbox. Bottom Line, pick the address excplicitly from the GAL and see if the message delivery is successful. If it is, then you know you probably have a cache issue.
August 23rd, 2010 7:57pm

By the way, you never answered the first part there about whether this happens for all messags or only replies. Cached entries are typically a reply only problem. I would also say that if the problem continues, re-think the renaming thing. That's always asking for trouble. You may to change the names of those accounts in such a way so there is not conflicts.
Free Windows Admin Tool Kit Click here and download it now
August 23rd, 2010 8:03pm

On Mon, 23 Aug 2010 17:03:21 +0000, AndyD_ wrote: > > >By the way, you never answered the first part there about whether this happens for all messags or only replies. Cached entries are typically a reply only problem. .. . . unless someone's added an AD user to their mailbox's Contacts folder. It happens. :-( --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP
August 24th, 2010 5:36am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics