locked
Public Folder Migration from multiple Exchange 2007 to exchange 2013 RRS feed

  • Question

  • Dear All,

    We were having 2 exchange 2007 (named exch.domain.com and branch.domain.com) in domain.com (2 server setup in SCC in HO and 1 single server with all roles in branch) and 2 exchange 2007 (named exch01.child.domian.com) server in child.domain.com. All 3 are having puplic folders. Now we have deployed Exchange 2013 SP1 following co-existence and migrated all mailbox from exch.domian.com to new ex2013.domain.com without any issue. Users are still able to brows their public folder on old exch2007 server. Now we want to migrate public folders from Exchange 2007 (exch.domian.com and branch.domain.com) to new exchange 2013 Sp1. Currently the public folders are setup like below:

    1. Public folder in exch.domian.com have exch01.child.domain.com in "Public Folder Referral"

    2. Public folder in branch.domain.com have exch.domain.com in "Public Folder Referral"

    3. Public folder in exch01.child.domain.com have exch.domain.com in "Public Folder Referral"

    We want to have below setup

    1. We want to continue with exchange 2007 in exch01.child.domian.com as of now

    2. We want to migrate all public folders from exch.domain.com and branch.domain.com to migrate to new Exchange 2013 Sp1 mailbox with DAG

    Please advise how to do the same without affecting any operational setup. We want to take expert opinion before actual migration to avoid any issue. Also want to share 1 strange issue. If we dismount the public folder on branch.domain.com all the users in domain.com not able to see their public folder. If we mount it again then all become normal. However more public folders are there in exch.domain.com. I am not able to understand why it happens that way. What is the purpose these referrals serve? Do we have to remove referral before migration. I try searching but most article talk about 1 public folder server to exchange 2013 migration where as we have multiple..!!

    Thanks in advance for your time and help!!

    Best Regards,

     

    Thursday, June 12, 2014 10:19 AM

Answers

  • That MS "expert" you talked to couldn't be more wrong.
    Like I mentioned before, moving to modern public folders is a cutover process so its really all or nothing.

    Martina Miskovic

    • Proposed as answer by SarveshGoel Thursday, July 3, 2014 8:01 AM
    • Marked as answer by AjayHunt Friday, July 4, 2014 9:40 AM
    Thursday, July 3, 2014 7:56 AM

All replies

  • Also do I need to remove all spaces on public folders before migrating to new Exchange 2013?

    Thanks!!

    Thursday, June 12, 2014 10:31 AM
  • We want to have below setup

    1. We want to continue with exchange 2007 in exch01.child.domian.com as of now

    2. We want to migrate all public folders from exch.domain.com and branch.domain.com to migrate to new Exchange 2013 Sp1 mailbox with DAG


    It is not technically possible to achieve both of your goals.

    You can't have both legacy and modern public folders in your ORG and there is no coexistence between the two versions/technics. The recommendation is to migrate to modern public folders after all mailboxes has been moved to Exchange 2013 since legacy mailboxes can't access modern public folders but EX13 Mailboxes can access legacy public folders.

    Public Folders
    http://technet.microsoft.com/en-us/library/jj150538(v=exchg.150).aspx




    Martina Miskovic

    Thursday, June 12, 2014 12:07 PM
  • Best approach is to migrate all users to Exchange 2013 or all users who needs access to Public Folders to Exchange 2013 and then migrate Public folders.

    You may continue to use Exchange 2007, but you would not be able co-exist public folders in Exchange 2007 and Exchange 2013 due to architecture changes. You may use Exchange 2007 for legacy stuff till you migrate them to Exchange 2013.

    Use Mailbox database properties to see which Public folder replica it is pointing to. If there is incorrect configuration then your dismounted database will result in unavailability of Public folder contents.


    - Sarvesh Goel - Enterprise Messaging Administrator

    Thursday, June 12, 2014 4:25 PM
  • Dear All,

    Thanks a lot for your time and efforts to reply!!

    I want to make 1 thing clear here, what we want in terms of:

    1. Continue with exchange 2007 in child domain with server exch01.child.domain.com (Ex2007). We want to have the existing users of exchange 2007 server able to access the public folders only on exch01.child.domian.com (Ex2007). So its ok if these users cant access the migrated public folder from servers exch.domain.com and branch.domain.com to new Exchange 2013 Sp1. So is it possible this way or not?

    2. All mail users in parent domain exchange servers (exch.domain.com and branch.domain.com) is already migrated to new exchange 2013 Sp1. Now only task remaining is to migrate the public folder from these server to new Exchange 2013 Sp1. And here also we are ok if these users can only able to access the new migrated public folders on Ex2013 Sp1.

    So now please advise its doable or not. If yes what are the things we need to do so that we can able to reach where we want without any major hiccup..

    Thanks again!!

    Friday, June 13, 2014 6:42 AM
  • So now please advise its doable or not. If yes what are the things we need to do so that we can able to reach where we want without any major hiccup..

    Thanks again!!


    No, it is not doable.
    You can't move/migrate parts of your public folders to Exchange 2013 - Moving to modern public folders is a cutover process so its really all or nothing.

    Martina Miskovic

    Friday, June 13, 2014 7:18 AM
  • Dear Martina,

    thanks for your time and reply. So what are our options going forward?

    Dear All,

    Do we all agree with Martina on same.

    Thanks again for the help..

    Sunday, June 15, 2014 2:02 PM
  • Dear All,

    I finally able to speak with MS expert on same and as per him,

    1. We can migrate exchange 2007 public folders partially provided they don't have replica's (like in our case exchange server in parent domain can be migrated if each have its own public folder)

    2. So the above leads to the question- if we remove replica and have all FPs only on respective servers, can we then migrate partially (migrate parent exchange server to new 2013 and leave child to as it is)?

    Please advise!!

    Thanks all for your kind support!!

    Tuesday, June 17, 2014 7:40 AM
  • That MS "expert" you talked to couldn't be more wrong.
    Like I mentioned before, moving to modern public folders is a cutover process so its really all or nothing.

    Martina Miskovic

    • Proposed as answer by SarveshGoel Thursday, July 3, 2014 8:01 AM
    • Marked as answer by AjayHunt Friday, July 4, 2014 9:40 AM
    Thursday, July 3, 2014 7:56 AM
  • Starting with Exchange 2013, you can't have co-existence of Public Folder. Like I have (and Martina as well), please migrate all users to Exchange 2013 first and then plan the public folder migrations.

    Exchange 2013 users can access public folders that are on Exchange 2007 but Exchange 2007 users (mailboxes) can't access Modern Public Folders.


    - Sarvesh Goel - Enterprise Messaging Administrator

    Thursday, July 3, 2014 8:04 AM
  • Dear Martina/ Sarvesh,

    Thanks for your time and efforts. We have postponed the same till all users got migrated to Ex2013. Now we want to decommission public folder server in parent domain and want to keep PF only in child domain (Ex2007) which should be accessible by all users. We are facing a strange issue. As told earlier, in parent domain for ex2007 we have 2 Server in single copy cluster + 1 branch. Both have 1 FP each. We want to remove standalone 1st. We ran "MoveAllReplica.ps1" script on branch to move all replica to single copy cluster. Now it shows system folder with all 0 contents as shown below:

    --------

    [PS] C:\Windows\system32>Get-PublicFolderStatistics -Server branch

    Name                                     ItemCount               LastAccessTime
    ----                                     ---------               --------------
    Default                                  0                 7/4/2014 10:58:36 AM
    exchangeV1                               0                 7/4/2014 10:58:36 AM
    microsoft                                0                 7/4/2014 10:58:36 AM
    schema-root                              0                 7/4/2014 10:58:36 AM
    StoreEvents{90712A34-233D-4E65-B2FF-23DE 0                 7/4/2014 10:58:36 AM
    3C1F6820}
    Nntp Control Folder                      0                 10/8/2010 3:22:12 AM

    ---------------------------------------------------

    Now the issue is, if we dismount the FP store on branch server, all users are not able to access their FP. they get error saying exchange is down for maintenance. If we see connection status then we saw that its trying to connect branch FP server. In all client setting we have removed branch server PF folder. What are we mission. Now our users who migrated to Ex2013 don't have any FP client setting also to look into. We tried reading lots of stuff but nothing seems to fix. Any advise is highly appreciated.

    Thanks in advance!!

    Friday, July 4, 2014 8:21 AM
  • AjayHunt, I think it would be better if you create a new thread. Your original question in this one has been answered.

    Martina Miskovic

    Friday, July 4, 2014 8:24 AM
  • ok.

    Thanks all for the help..

    Friday, July 4, 2014 9:41 AM