Managing OAB in Exchange Server 2013

re: Managing OAB in Exchange Server 2013

Ahsan Kabir — Mon, 21 Jan 2013 16:42:55 GMT

Excellent post. Thanks!

re: Managing OAB in Exchange Server 2013

Bhalchandra Atre-MSFT — Thu, 17 Jan 2013 21:43:56 GMT

ASHigginbotham # If you go for more than one org mailbox per site, each OAB mailbox will have it's own setup of OAB files, with different names, generation time etc. The Outlook client, if CAS proxies them to different org mailboxes, will download the Full OAB as they see new file names/generation times etc. It may some time even result in corruption of OAB files.

re: Managing OAB in Exchange Server 2013

ASHigginbotham — Wed, 16 Jan 2013 06:18:58 GMT

"It can proxy the request in round robin fashion if it finds more than one organization mailbox active in same AD site. This might result in frequent full OAB download."

Can you please expand on this scenario & explain how having multiple OAB-Arbitration mailboxes in the same AD site could result in more full OAB downloads than normal? Thanks.

re: Managing OAB in Exchange Server 2013

Satheshwaran Manoharan — Tue, 15 Jan 2013 08:29:59 GMT

Nice Article bhalchandra. Thanks for sharing about logging and stuffs.

re: Managing OAB in Exchange Server 2013

Andrei Kondrashov — Tue, 15 Jan 2013 07:29:48 GMT

Ok... by "till" you probably meant - before 2010 and including 2010 :) I think you should rephrase the sentence though :)

re: Managing OAB in Exchange Server 2013

Andrei Kondrashov — Tue, 15 Jan 2013 07:24:46 GMT

You are writing "The OAB Generation till Exchange Server 2010 was based on a “Schedule”. It means in 2010 it does not start on schedule too. Is that right?

re: Managing OAB in Exchange Server 2013

Charles Derber — Tue, 15 Jan 2013 03:52:10 GMT

Thanks Bhalchandra.

Nicely mentioned the log results and scenario, It is useful and informative :)

re: Managing OAB in Exchange Server 2013

Bhalchandra Atre — Tue, 15 Jan 2013 03:15:59 GMT

Andrei # Thanks for catching the First one, it is indeed for multi-domain environment. About second point, OAB generation in Exchange 2013 does not start at a fixed schedule.

re: Managing OAB in Exchange Server 2013

Andrei Kondrashov — Tue, 15 Jan 2013 02:00:26 GMT

Here "Note: If you are in multi-forest Active Directory domain environment..." you probably meant "in multi-domain AD forest environment'.

And here "The OAB Generation till Exchange Server 2010 was based on a “Schedule”..." you probably meant "till Exchange 2013".

re: Managing OAB in Exchange Server 2013

Rodger — Mon, 14 Jan 2013 23:50:48 GMT

So, it's all command-line PowerShell based? Nah, I'll wait for the GUI.