Migrate OAB/Public Folders from 2007 to 2013

Hello!

We are migrating our 2007 Exchange servers to 2013. We installed 2013 with no issues and have migrated all mailboxes. Users are able to connect to the new server with OutlookAnywhere and ActiveSync and retrieve their mail. However, when connected to Exchange through Outlook 2013 (External) they are getting the time out on OAB sync. When using "Test E-Mail AutoConfiguration", we can see that the client is getting the old server URL as the OAB path. I've checked all the virtual directories on the 2013 server and they are pointing to the new server, so I'm not sure where Outlook is getting this old URL. Also, if we fix the URL is that all that needs to be done or do the OAB's still need to be migrated? When trying to move them we get an error (Catastrophic Failure). From what I read, the OAB's are not compatible from 2007 to 2013. So, do we need to create them or are they automatically generated during install and it's just a matter of getting the correct OAB URL to Outlook?

The other topic is Public Folders. There doesn't seem to be a nice clean way of moving them from 2007 to 2013. I found an article that is pretty extensive the shows how to migrate that requires exporting to an xml. If this is the only way, so be it but I was hoping that there was an easier way built into the ECP or a a shell command that I'm missing somewhere....

Any help is appreciated.

February 20th, 2015 4:48pm

for the OAB you need to configure the Ex2013 as the OAB Generation Server as you must be doing in Exchange 2007.

For public Folder I'd suggest you to open a new topic because it is a vast topic. And yes it is not as easy as Add and Remove Replica. Exchange 2013 Public Folder a Modern Public Folder and 2013 use mailbox for Public Folder and each has limit.

Hope that helps

Free Windows Admin Tool Kit Click here and download it now
February 21st, 2015 8:36pm

What OAB are the users set to use? New OAB ?

What happens if you repair the Outlook profile>?

February 21st, 2015 9:19pm

I would suggest you to follow this well explained technet resource that covers all the parts while doing public folder migration between exchange 2007 and 2013 : http://blogs.technet.com/b/meamcs/archive/2013/07/25/part-4-step-by-step-exchange-2007-to-2013-migration.aspx

In case if the issue still persist, you can have a look on this automated solution (http://www.exchangemailboxmigration.com/) that could be a good approach to move all the public folder database to exchange 2013 without any problem.

Free Windows Admin Tool Kit Click here and download it now
February 23rd, 2015 5:22am

Thank you for you reply.

For the OAB I did try the following command.

Get-MailboxDatabase | Set-MailboxDatabase -OfflineAddressBook "\Default Offline Address Book (Ex2012)"

It didn't seem to make a difference. Outlook clients still continue to go to the old URL for OAB. Is there another way to configure 2013 as the OAB Generation Server?

February 23rd, 2015 2:57pm

Hi,

You can try:

  1. Create the new OAB on Exchange 2013 Server.
  2. Set all the user to use the new OAB.
  3. Remove the old OAB object.

Thanks,

Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com

 

Free Windows Admin Tool Kit Click here and download it now
February 27th, 2015 4:53am

Hi,

You can try:

  1. Create the new OAB on Exchange 2013 Server.
  2. Set all the user to use the new OAB.
  3. Remove the old OAB object.

Thanks,

Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com

 

February 27th, 2015 9:46am

Just wanted to bump this. We are still unable to find why Exchange continues to point Outlook clients to the old OAB path. When trying to create new OAB, it says it already exists. So, I think they are there but the Auto-Configuration test shows the old OAB URL. I have confirmed multiple times that the new OAB URL's are in the configuration. I even went to the old Exchange server and put the new OAB URL's there too. Outlook still asks for the old one?
Free Windows Admin Tool Kit Click here and download it now
March 19th, 2015 12:21pm

Some things to check:

Where is the OAB for Exchange 2013? Is it in a MB that is mounted?

Get-Mailbox -Arbitration | where {$_.PersistedCapabilities -like "*oab*"} | ft name,database

What is the OAB defined on the Exchange 2013 Databases?

Get-MailboxDatabase | select name, OfflineAddressBook

If it's the 2007 OAB, then you can run Set-MailboxDatabase to set the Offline Address book.

http://blogs.technet.com/b/exchange/archive/2013/01/14/managing-oab-in-exchange-server-2013.aspx

March 19th, 2015 1:03pm

Results from both commands below. It appears as if the default OAB is working fine. I tried creating a new account that is not located in the seller/customer OU. If it's just in Users it seems to work fine. It's the accounts that were created in a separate OU by Hosting Controller that are having the problem. The Exchange 2007 server was setup with multiple customers with their own GAL and OAB. These are the ones having the trouble. The mailboxes work fine, but some are unable to see their GAL and none of them are able to download the OAB.

I just did a test after changing the internal and external URL's on the old Exchange server to the new URL paths. This did fix the problem with Auto-Configuration showing the old URL, but Outlook still times out when trying to download the OAB using "Download Address Book..." Is it possible these accounts that have their own GAL and OAB lost something when they were moved between servers? Policies?

Free Windows Admin Tool Kit Click here and download it now
March 19th, 2015 2:52pm

Hmmm... Sounds like you might have been using Address book policies... check out the link below:

https://technet.microsoft.com/en-us/library/jj657455%28v=exchg.150%29.aspx?f=255&MSPPError=-2147217396

March 20th, 2015 9:52am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics