Address Book Issues
We are running a single E2K10 SP1 Roll up 6 and all clients are running Outlook 2010. We have cached mode forced for all clients.
We are seeing random issues throughout the organization when trying to send as another address.
Lets say that I am trying to send a message as Bob Smith to John Doe. I will receive a NDR stating that I do not have rights to send on behalf of John Doe. If I force a full download of the OAB, the restart Outlook the problem is resolved.
A few days later the same issue will popup until the OAB is downloaded again.
We have a single OAB which is only enabled for version 4 and is set as the default. All mailbox databases have this OAB selected. We have not seen any event log data indicating issues downloading the OAB.
Any suggestions?-Drew
December 28th, 2011 2:13pm
Hello,
It may be cache issue. Please try to take the client out of cached mode, and check if the problem still exists.
If the problem persists, please force the oab to generate.
get-offlineaddressbook | update-offlineaddressbook.
Also, please check what distribution method has been set for the OAB in EMC.
And when you remove the OAB files from the local machines, do you see the updated OAB?
Best Regards,
Lisa
Free Windows Admin Tool Kit Click here and download it now
December 28th, 2011 11:53pm
It is definitely an OAB issue. If we force downloading the new address book or remove the computer from cached mode the issue is resolved. We have tried running an update on the OAB with the suggested PS command. Currently distribution
is only allowed via web, and is limited to version 4 (all clients are Outlook 2010).
We have not see the issue this week, I am wondering if it just took some time to iron out. The following changes had been made in the environment in the last 30 days:
-All clients to cached mode
-Registry key to move items sent from other mailbox to other mailboxes sent items
-New OAB, v4 web distribution, set as default on all databases
Thank you for the reply, I will report back if we see this issue crop up again. Oddly enough, this started happening more than a week after any of the above changes.-Drew
January 6th, 2012 11:55am