Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1623
  • Last Modified:

Exchange 2003 to 2007 migration Mapi Public Folder Hierarchy Move

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
curesearch
Asked:
curesearch
  • 2
  • 2
1 Solution
 
Exchange_GeekCommented:
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
 
curesearchAuthor Commented:
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
 
Exchange_GeekCommented:
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
 
curesearchAuthor Commented:
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

Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now