Exchange 2013 cached email addresses in address list, how to remove on specific domains

Hi all,

After an major error on our Exchange 2010 we were forced to move to an Exchange 2013 solution. This was planned and executed on 2.5 days !! and it workd !! just to have it said :)

What we experience now is that some of the mailboxes needed to be created again. I had to disconnect from the old db on exchange 2010 and recreate on exchange 2013 db. This worked and users were able to send and receive mails again.

The error I am looking to solve is that all cached email addresses is now pointing to the old folder. This gives an error as the receiver is not found. (since the user and db is not there anymore)

Is there any suggestions to how to solve this issue ? I have pussed the address list after som smaller adjustments to see if that updated the cache but no go.


This server hosts several domains as accepted domains (about 25)
This relates to about 80 users on 10 domains.
It is, off course, only affecting users on this server.

Is there any scrpts (PS) that can force an cache update ?
Or even remove old cached email addresses ?
Any other solutions I have not thought of ?  :) (I have been thinking alot on this issue)

Looking forward for suggestions :)

Mr WooberAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

We had something similar when we moved from a third party email system for some of our users to Exchange. If you just started to type the email address in to the TO: field it would always select the account that wasn't working anymore. The only fix we found for it, and it did work, was to select the names from the GAL. As people did that the new address was the one selected and the old one went away. I'd assume it would work the same with an Exchange to an Exchange move.
There are several outlook command line switches....
If you start outlook with /cleanautocompletecache, the local Outlook cache is cleaned up and Outlook doesn't remember any old name....

More Outlook switches here:
FOXActive Directory/Exchange EngineerCommented:
I agree with jhyiesla.  To start off fresh they should open up their Outlook (2010)File>options>Mail>Send Messages  click EMPTY AUTO-COMPLETE LIST.
The 7 Worst Nightmares of a Sysadmin

Fear not! To defend your business’ IT systems we’re going to shine a light on the seven most sinister terrors that haunt sysadmins. That way you can be sure there’s nothing in your stack waiting to go bump in the night.

And yes, as jhyiesla talks about the GAL....
You should make sure that the GAL is generated and the Address-Books are up to date as well.
On the client site, in the Outlook profile you may check, if the profile settings are pointing to the new Addressbook. If Clients use a OAB (cache mode), they need some time until they get the changes from the GAL / OAB. You can force on the Server to update the GAL and on the client do download the OAB (cache mode).

The Check Names button should work, even the cache shows something different. If the Check Names doesn't work, the connection from the client to the GAL or OAB is broken and has to be corrected on the client.  

CTRL - right click on the Oulook tray icon, select Test E-Mail Autoconfiguration and see in the results, where Outlook is pointing to .

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Mr WooberAuthor Commented:
Hmm, Ok.

Seems the solution here is to let the users delete the local cache and make sure the GAL and OAB is up2date.

There is no scripts to delete caches stored locally based on domains ?
You can create a batch to start outlook with the command line for some days and put it into a group policy...
If this solves the problem I mean...
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.