Solved

duplicate OAB Public folders in Exchange 2003/2010 mixed migration environment

Posted on 2015-01-26
1
114 Views
Last Modified: 2015-01-28
I am migrating from Exchange 2003 to 2010. One forest, One domain. All of the end users are on Exchange 2003 still. There are no Outlook clients older than Outlook 2003 SP2. I have moved the OAB to Exchange 2010.

Any new mailboxes added to Exchange 2003 are not appearing in the GAL of the 2003 mailboxes.

I investigated and found I had replicated the OAB System Public Folders from 2010 to 2003 and visa versa. As a result, both my 2010 PF server and my 2003 PF server have duplicate OAB Version 4, 3a and 2 folders. So there are two 4s, two 3as and two 2s. By examining the folder properties in PFDAVAdmin and ExFolders, I can see that the 2003 PF server is posting to one of each version duplicate and 2010 to the other. It appears that the 2003 server mailboxes are dependent upon the 2003 "Version 4 OAB" (for example) but the 2010 server is generating the OAB and posting to the other "OAB Version 4" from the 2010 servers.

Exchange 2003 Server                  Exchange 2010 Server
Version 2 OAB (from 2003)          Version 2 OAB (from 2003)
Version 2 OAB (from 2010)          Version 2 OAB (from 2010)
Version 3a OAB (from 2003)        Version 3a OAB (from 2003)
Version 3a OAB (from 2010)        Version 3a OAB (from 2010)
Version 4 OAB (from 2003)          Version 4 OAB (from 2003)
Version 4 OAB (from 2010)          Version 4 OAB (from 2010)

So how do I fix this?

If I remove the replica of the Version 4 OAB (from 2003) from the 2003 PF server, will the Exchange 2003 mailboxes then start using Version 4 OAB (from 2010)?

Is there another solution?
0
Comment
Question by:pminer1844
1 Comment
 

Accepted Solution

by:
pminer1844 earned 0 total points
Comment Utility
Issue resolved. I was just different replicas is system folders from a 2003 server and a 2010 server.
0

Featured Post

How your wiki can always stay up-to-date

Quip doubles as a “living” wiki and a project management tool that evolves with your organization. As you finish projects in Quip, the work remains, easily accessible to all team members, new and old.
- Increase transparency
- Onboard new hires faster
- Access from mobile/offline

Join & Write a Comment

Granting full access permission allows users to access mailboxes present in their database. By giving full access permission one can open and read the content of any mailbox but cannot send emails from that mailbox.
Follow this checklist to learn more about the 15 things you should never include in an email signature from personal quotes, animated gifs and out-of-date marketing content.
Familiarize people with the process of retrieving data from SQL Server using an Access pass-thru query. Microsoft Access is a very powerful client/server development tool. One of the ways that you can retrieve data from a SQL Server is by using a pa…
To add imagery to an HTML email signature, you have two options available to you. You can either add a logo/image by embedding it directly into the signature or hosting it externally and linking to it. The vast majority of email clients display l…

771 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

Need Help in Real-Time?

Connect with top rated Experts

7 Experts available now in Live!

Get 1:1 Help Now