I`m in a process of migrating PF from Exchange 2003 to Exchange 2010. I have add replica Exchange 2010 server. I have move OAB generator to Exchange 2010 server. But when I look old Exchange 2003 serrve, under system Public folder, under offline address list, I can se that OAB Version 2/3a/4 under Status is showing Last update received on date when OAB generator was changed.

Ignore that information. It cannot be relied upon. Dates, times, status etc mean nothing. The only thing that counts is item count. Simon.Simon Butler, Exchange MVP Blog | Exchange Resources | In the UK? Hire Me.

Hello, Since Exchange 2007 and Outlook 2007, Outlook no longer downloads OAB via public folder. It uses the OAB web service and download the OAB files from CAS server c:\Program Files\Microsoft\Exchange Server\V14\ClientAccess\OAB Thanks, Simon

Hello, Since Exchange 2007 and Outlook 2007, Outlook no longer downloads OAB via public folder. It uses the OAB web service and download the OAB files from CAS server c:\Program Files\Microsoft\Exchange Server\V14\ClientAccess\OAB Thanks, Simon Not strictly true. It would only do web services only if the platform was native Exchange 2007 (ie no co-existence period) or if it had been changed to use public folders. In this scenario public folder download will be used because a migration from Exchange 2003 is under way. You shouldn't change to web services download until you are native Exchange 2007/Outlook 2007. Simon.Simon Butler, Exchange MVP Blog | Exchange Resources | In the UK? Hire Me.

Good update by Simon, but i have a question on one statement, kindly answer if you don't mind. You shouldn't change to web services download until you are native Exchange 2007/Outlook 2007. Do you mean to say that until of unless Migration is complete do not change the OAB to Web Based Distribution?Gulab | MCITP: Exchange 2010-2007 | Skype: Gulab.Mallah | Blog: www.ExchangeRanger.Blogspot.com

That is correct. If you have mailbox that has any version of Outlook client on Exchange 2003, you may not decommission public folder on Exchange 2007/2010, because client will use Exchange 2003 PF for OAB download. Only and only when you remove last exchange 2003 server, and you do not have Outlook 2003 client, you may switch to web distribution and remove PF from Exchange 2007 or 2010. That is my field experience. Info. When you move mail enabled PF to Exchange 2010 SP1, be aware, that anonymous contribute permission does not apply, when authenticated user send mail to mail enabled PF. User has to be granted permission to post to PF before he can send mail to it.

Hello Malistane, You can select both Web-based distibution & Public folder distribution even during exchange 2003 coexistence thereby allowing outlook 2003 clients to download OAB from public folder & outlook 2007+ clients from web-based CAS distribution.

Hello, Thank you Sembee for the supplement. Yes, we need to enable the public folder distribution due to the following conditions: 1. Any user uses Outlook 2003 clients. 2. Any user is still on the Exchange 2003 mailbox. MaliStane, if you are going to move all the users to Exchange 2010 and no user uses Outlook client, you can consider disabling the public folder distribution and only use the web distribution. Thanks, Simon

Yes, that is correct. If client are not Outlook 2003, than you can delete PF database. Exchange 2003 will forward unresolved recipient to Exchange 2010 organization, if you configured to do so. Problem is why you will keep Exchange 2003 organization? I think only x400. If you disable Public folders in Exchange 2010 organization, you "might" have problem, if mail come to Exchange 2003 server. And get stuck there with NDR. Than you should leave RGC connector between organization, or forward all email to exchange organization. But I do not think, that someone will leave Exchange 2003 organization, because, you cannot rise "forest and" domain level to Windows server 2008 R2.

The domain and forest level has nothing to do with Exchange, so I don't see why that was even mentioned. A lot of this comes down to the client version involved AND the server generating the OAB. If the server generating the OAB is Exchange 2003, you are fine. If it is Exchange 2007 and you are co-existing, then I have seen problems where web only distribution is used. Enabling both public folder and web distribution allows the OAB to be generated on the Exchange 2007 server and that information then replicated to the Exchange 2003 server correctly. Simon.Simon Butler, Exchange MVP Blog | Exchange Resources | In the UK? Hire Me.