Solved

Exchange 2003 to 2007 migration Mapi Public Folder Hierarchy Move

Posted on 2008-10-22
4
1,614 Views
Last Modified: 2012-06-21
I'm in the process of migrating from Exchange 2003 to 2007 SP1 and only have one Exchange 2003 server left.

In the "How to Remove the Last Legacy Exchange Server from an Organization" Tech Net Article (http://technet.microsoft.com/en-us/library/bb288905(EXCHG.80).aspx) they mention moving the mapi public folder hierarchy.

That article and MS Q252105 article seems to treat the mapi hiearchy move as rather minor step where nothing can go wrong.

However, I have seen references mentioning that there can only be one mapi hiearchy in an exchange organization and I see at least issue on this site where someone had a "There are multiple MAPI public trees found." problem.

http://www.experts-exchange.com/Software/Server_Software/Email_Servers/Exchange/Q_23236540.html

My preference is to move the mapi hiearchy and make sure things are working, then a few days later finish the retirement of the Exchange 2003 server.

My questions are:

1.  Am I ending up with one mapi hiearchy after I drag the public folders from the Exchange 2003 administrative group over to the new 2007 administrative group or am going to have two and need to retire the last Exchange 2003 server right away?

2. If the mapi hiearchy move fails, is it merely a Authortative Active Directory restore situation to roll back or am I looking at Exchange restore situation also?
0
Comment
Question by:curesearch
  • 2
  • 2
4 Comments
 
LVL 33

Accepted Solution

by:
Exchange_Geek earned 500 total points
ID: 22784194
1.  Am I ending up with one mapi hiearchy after I drag the public folders from the Exchange 2003 administrative group over to the new 2007 administrative group or am going to have two and need to retire the last Exchange 2003 server right away?

No you would not have multiple MAPI Trees - i have personally done loads of migration and this is not a BUG.


2. If the mapi hierarchy move fails, is it merely a Authoritative Active Directory restore situation to roll back or am I looking at Exchange restore situation also?

There are ways and means to recreate it rather than have to perform a restore. Of course having a system state backup is always handy.

So, do not worry about MAPI trees !!!!
0
 

Author Comment

by:curesearch
ID: 22817918
Regarding Exchange Geeks answers:
So it won't cause a conflict or error to have multiple mapi trees?

When you say there are means to recreate the hierarchy, is that thru the deleting and re-creating in the exchange system manager?

Would the deleting/re-recreating the mapi hiearchy require the restore of the public folder content?
0
 
LVL 33

Expert Comment

by:Exchange_Geek
ID: 22819525
First of all you can never end up with multiple MAPI Trees - Exchange organization has to have only one MAPI Trees, under circumstance of having more than one MAPI Tree - MSFT recommends to remove multiple ones and maintain only one MAPI Tree.

Reason is simple exchange mail stores needs to be related to one public store (by default it is the local one) and the pf store needs to be associated with the only-one mapi tree. Under circumstance, if there are multiple mapi trees (created by xyz reasons - we won't delve in how to create those multiple trees), it is best to decide how to get rid of those unwanted.

When i state recreating hierarchy - i mean removing it from AD configuration partition using ADSIEDIT and not from Exchange System Manager.

Deleting / recreating hierarchy IS NEVER taken a chance for troubleshooting PF issues, however as i earlier stated - there are ways and means to get over any PF hierarchy / tree issue, so there is no need to get so much in-depth (else i may end up explaining for hours and hours about PF)

:)
0
 

Author Closing Comment

by:curesearch
ID: 31509039
Thanks for your feedback Exchange Geek.  I moved the hierarchy over the weekend, it went quickly and so far haven't had any issues.
0

Featured Post

Are your AD admin tools letting you down?

Managing Active Directory can get complicated.  Often, the native tools for managing AD are just not up to the task.  The largest Active Directory installations in the world have relied on one tool to manage their day-to-day administration tasks: Hyena. Start your trial today.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

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.
Read this checklist to learn more about the 15 things you should never include in an email signature.
In this Micro Video tutorial you will learn the basics about Database Availability Groups and How to configure one using a live Exchange Server Environment. The video tutorial explains the basics of the Exchange server Database Availability grou…
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…

730 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