none
Migrating Public Folders from Exchange 2007 to Exchange 2010

    Question

  • I am trying to do a (simple?) migration of Public Folders, in the same site from Exchange 2007 to 2010, which should be easy, no? Not!
    I created a PF database on the Exchange 2010, ran this command:
    AddReplicaToPFRecursive.ps1 -TopPublicFolder \NON_IPM_SUBTREE -ServerToAdd Ex_2010_server

    Which supposedly did all replication, which it did not, but did allow me to do each public folder below Default Public Folders. I gave the servers 8 hours to replicate and then rehomed the PFs to the Exchange 2010 server, which broke everything - PF weren't visible from Outlook or OWA, etc. for users still on the Exchange 2007 server. So, I rehomed every database back to the original Exchange 2007 server, but everything is NOT back to normal. I am the owner on the PFs and I can't see them from my Outlook anymore, nor can I see them from OWA.

    I looked in Technet for any hints - found none. Bing only returned 2003 to 2007 migration, been there done that already. How I wish that Bing could be scoped for a given product when searching Technet!!!

    So what is the *proper* way to migrate the folders in lieu of any documentation on how to do it?

     


    SnoBoy
    Tuesday, November 23, 2010 8:49 PM

Answers

  • Ok, finally figured out why Public Folder replication never occurred. I went from Exchange 2003 à2007 à2010. And therein is the problem. An obscure problem prevents Public Folders from replicating, even if you do everything “right.” It requires ADSIedit to fix the problem.

    First, start ADSIedit. Then, right-click the ADSI Edit at the top of the left-hand column and choose Connect to. Then in the drop down in Select a well known Naming Context, choose Configuration. Then choose

    CN-Services,CN=Microsoft Exchange,CN=site_name,CN=Administrative Groups,CN=First Administrative Group and then delete the empty CN=Servers, after 15 minutes the replication started running and get-publicfolder –recurse on the 2010 server started showing Public Folders instead of returning nothing as it had been all along. It also fixed the broken mail-enabled public folders and allowed them to receive email instead of bouncing as they did every time I had tried to start replication in the past.

     

     

     


    SnoBoy
    • Marked as answer by SnoBoy Friday, December 17, 2010 2:10 PM
    Friday, December 17, 2010 2:10 PM

All replies

  • after running the

    AddReplicaToPFRecursive.ps1 -TopPublicFolder \NON_IPM_SUBTREE -ServerToAdd Ex_2010_server

    IT takes time for replication to complete. depends on how many public folders you have and contents within them

    when you rehomed everything to 2010. you missed to specify 2007 mailboxes to use 2010 pf as default pf that is where you missed.

    and you have misunderstanding that things didn't work as they should where they did.

    AT this point. do you see the folders in exchagne management console or using get-publicfolder cmdlet in exchagne 2007 ?

     


    Dhruv
    Tuesday, November 23, 2010 9:29 PM
  • I did give it plenty of time, I actually looked at the databases to be sure that the size was approximately the same (and it had overnight to replicate about 8 GB of data, which ought to go pretty quickly over a 1 gig ethernet connection), I did rehome on both servers and each and every database. Today, I found out that any email going to the mail-enabled PFs went into a loop between the Exchange 2007 and 2010 servers.

    I had to fix it, so I removed every replica that pointed to the Exchange 2010 server. I again went through each and every database to be sure they were pointing to the 2007 server and then I removed the Public Folder Database from the Exchange 2010 server so that a loop was impossible.

    Now back to my *original* question. Where is it documented exactly how to *safely* migrate the Public Folders to the Exchange 2010 server without totally screwing everything up?

    P.S. It would sure be nice if SharePoint had all the features that Public Folders do - Id turn that over to our SharePoint admins in a heartbeat if it did.


    SnoBoy
    Wednesday, November 24, 2010 9:23 PM
  • Hi SnoBoy,

    Per my known, there are not detailed information about how to move the publicfolder from exchange 2007 to exchange 2010.
    However, there are some information(through EMC) in the below link:
    http://technet.microsoft.com/en-us/exdeploy2010/default(EXCHG.140).aspx
    We could do some test in the test lab firstly, some useful information for you:
    http://technet.microsoft.com/en-us/library/bb397221(EXCHG.140).aspx
    http://technet.microsoft.com/en-us/library/bb629523.aspx?t=exchgf1
    Sure, you also could use SCRIPT to do the move operation.
    General prcodures1.
    1. create publicdatabase on exchange 2010 server
    2. add the replicas on the exchange 2010
    3. wait for the replication
    4. confirm the replication successfully
    5. change the default public folder database for the users
    6. let the exchange 2007 down, confirm everything work well
    7. remove the exchange 2007
       There are some information about how to remove the exchange 2007 server from the coexistence scenario, you could refer to it.
    I would suggest that you could test it firstly, if there are some issue, then you could post here and we could help you.

    Regards!
    Gavin 

    • Proposed as answer by Gavin-Zhang Monday, November 29, 2010 3:17 AM
    Friday, November 26, 2010 9:46 AM
  • The Deployment Wizard (that I couldn't find with Bing or with any other search methodology I have used, BTW) is very helpful. Because of the problems with Public Folders, I am going to do them last in the migration. Every move of mail-enabled folders has always broken their ability to receive email. I am 1/3 of the way through migrating mailboxes to the Exchange 2010 server and because Outlook 2007 chokes on about 1 out of 10 moves, I have been doing the moves during the day so that one of our tech folks can go and force Outlook to the new server via the Mail commandlet. We have some huge mailboxes, because of management decisions above my pay grade, we have no quotas in place and we have a bunch of email packrats. :-)

    At any rate PFs will move last and I fully expect problems, but I will give it a shot with this information. Thanks!


    SnoBoy
    • Edited by SnoBoy Friday, November 26, 2010 2:56 PM Spelling
    Friday, November 26, 2010 2:54 PM
  • I am about to scream! So I carefully followed the guide, setup a Public Folder database on the Exchange 2010 server, then set up replication - that is all. And users on the 2007 server coulpdn't see the Public Folders any more!!

    I have had to deal with so many stupid esoteric problems on Exchange 2007 and 2010. This is getting crazy. When is Microsoft going back to making software that just works instead of adding features out the wazoo and leaving the core functions broken!

    From Exchange 5.3 all the way up to Exchange 2003, I never had the need to call MS support for anything. I could always fix it for myself. Since 2007, I have had to spend lots of cach and time calling support to get it to work. I fore one am sick and tired of chasing down little issues that screw up the whole system.

    So, no this issue is still unanswered. I will leave all the stuff I can't fix for last then blow a bunch of cash to fix the rest so I can shut down the old 2007 server.


    SnoBoy
    • Marked as answer by SnoBoy Friday, December 17, 2010 2:10 PM
    • Unmarked as answer by SnoBoy Friday, December 17, 2010 2:10 PM
    Tuesday, November 30, 2010 9:10 PM
  • Ok, finally figured out why Public Folder replication never occurred. I went from Exchange 2003 à2007 à2010. And therein is the problem. An obscure problem prevents Public Folders from replicating, even if you do everything “right.” It requires ADSIedit to fix the problem.

    First, start ADSIedit. Then, right-click the ADSI Edit at the top of the left-hand column and choose Connect to. Then in the drop down in Select a well known Naming Context, choose Configuration. Then choose

    CN-Services,CN=Microsoft Exchange,CN=site_name,CN=Administrative Groups,CN=First Administrative Group and then delete the empty CN=Servers, after 15 minutes the replication started running and get-publicfolder –recurse on the 2010 server started showing Public Folders instead of returning nothing as it had been all along. It also fixed the broken mail-enabled public folders and allowed them to receive email instead of bouncing as they did every time I had tried to start replication in the past.

     

     

     


    SnoBoy
    • Marked as answer by SnoBoy Friday, December 17, 2010 2:10 PM
    Friday, December 17, 2010 2:10 PM