How to clear OWA 2007n autocomplete entries

Posted on 2009-07-02
Medium Priority
Last Modified: 2015-01-05
I need tor remove a number of OWA autocomplete entries for all users on the network, without going to each user's mailbox and manually deleting the entry. Is there a way of automating this process?
Question by:itmtsn
  • 3
  • 2

Assisted Solution

aslamsurve earned 300 total points
ID: 24763875
As a user, you have two ways:
1. Delete an entry from the list using OWA
2. Delete the entire list using OWA

1. Delete an entry from the list using OWA:
To remove one entry of the list, highlight the name in the list (arrow up and arrow
down allow you to highlight the name you want to remove, and press the Delete
button on your keyboard.

2. Delete the entire list using OWA
To remove all entries in the list, you can log on to your mailbox using Outlook Web
Access Light
Go to Options - Messaging - Under Email Name Resolution - Click Clear Most Recent
Recipients List

Author Comment

ID: 24764046

But say I know I have a rogue entry Fred Bloggs and want to remove that from all two thousand mailboxes OWA receipient lists. Is there a way to do this without reproducing your step one 2000 times?
LVL 65

Accepted Solution

Mestha earned 1200 total points
ID: 24765825
As far as I am aware, the autocomplete list is a per mailbox setting, it cannot be controlled centrally. Therefore I am not aware of a way to remove the entry globally.

Is the rouge entry internal? If so then you could look to do something to redirect that entry across. Otherwise it has to be done individually.

Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.


Author Comment

ID: 24770622
We used to have two networks here. Each with seperate domains and email.

We will be merging the smaller network into our domain.

There used to be an SMTP contact in our AD so that Exchange users could easily email members of our Accounts team (the sperate network).

Before creating en exchange mailbox for that user I deleted the SMTP contact for them and this is where the problem seems to be.

If you email them at their new address (domain1) it works fine as does emailing them to their old address (domain2) which we have set Outlook to deliver to their Exchange mailbox. The problem comes within our Exchange organisation using OWA.

A user who has previously emailed that user Fred Bloggs (FBloggs@domain2) will just type in Fred select the Fred Bloggs entry from their autocomplete list and hit send. The email goes off. It then bounces back a few seconds later with an undeliverable error.

I thought this was strange because as I said their old Pop3 email still works fine and is delivered to their Exchange address.

When investigatin the error it seems it is trying to deliver the message to FredBloggs@domain1. Somehow concatenating the name and appending our exchange domain onto it as it doesnt fine it as an SMTP contact within AD and doesn't seem to use the FQemail address associated with the autocomplete entry.

Kinda weird!.

The only way around this I can think of either re-creating the SMTP contact at their old address or creating an alias of FredBloggs@domain1 for each user we move over.
LVL 65

Assisted Solution

Mestha earned 1200 total points
ID: 24780291
If you look at the Contacts you will find they actually have two addresses - an SMTP address and an X.400 address. Exchange uses that X.400 address for its internal routing.
Therefore what you should have done (I know - easy to say after the event) was lift both he X.400 address and the SMTP address and apply them to the new User Account.

This article from the Microsoft SBS team covers what would need to have been done in more detail - it doesn't just apply to Mailboxes, but contacts as well.

As for what can be done about it now, you might be able to recreate the address if you are careful, and place it on to the live user's account. That should ensure the previously used names work.

POP3 etc works because they are using straight SMTP address. Exchange doesn't use the SMTP address for routing email internally, it does its own thing.


Author Closing Comment

ID: 31599181

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.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

What is the biggest problem in managing an exchange environment today? It is the lack of backups, disaster recovery (DR) plan, testing of the DR plan or believing that it won’t happen to us.
A method of moving multiple mailboxes (in bulk) to another database in an Exchange 2010/2013/2016 environment...
This video demonstrates how to sync Microsoft Exchange Public Folders with smartphones using CodeTwo Exchange Sync and Exchange ActiveSync. To learn more about CodeTwo Exchange Sync and download the free trial, go to: http://www.codetwo.com/excha…
There are cases when e.g. an IT administrator wants to have full access and view into selected mailboxes on Exchange server, directly from his own email account in Outlook or Outlook Web Access. This proves useful when for example administrator want…

622 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