we have successfully installed Exchange 2013, and able to connect to ECP. The Exchange 2007 servers are at sp3 rollup8. Issue: We are unable to create public folders in 2013, as it shows "error An existing public folder deployment has been detected.. To migrate existing public folder data, create new public folder mailbox using -HoldForMigration switch. can you please advise on the instructions on how to migrate all Public folders from 2007 to 2013? Thanks 

In order to migrate public folders you need to create the public folder in Exchange 2013 using 'HoldForMigration' switch. The process to migrate from Exchange 2007 hasn't been officially documented yet, but it'll be similar to Exchange 2010 as described in the below article: http://technet.microsoft.com/en-us/library/jj150486.aspx I would suggest testing this first in a test environment before preforming the steps in production setup. Hope this helps.

Thanks when running .\Export-PublicFolderStatistics.ps1 <FQDNofSourceServer> <FolderToSizeMapPath> on the Exchange 2007 server we only get the following results FolderName,"FolderSize" \IPM_SUBTREE,"0" \NON_IPM_SUBTREE,"0" \NON_IPM_SUBTREE\EFORMS REGISTRY,"0" Can you please advise.

Thanks when running .\Export-PublicFolderStatistics.ps1 <FQDNofSourceServer> <FolderToSizeMapPath> on the Exchange 2007 server we only get the following results FolderName,"FolderSize" \IPM_SUBTREE,"0" \NON_IPM_SUBTREE,"0" \NON_IPM_SUBTREE\EFORMS REGISTRY,"0" Can you please advise.

Hi There are some Prerequisite steps on both server, so, did you follow those steps. Also, I noticed, there is a warning "After resetting the above properties, you will need to wait for Exchange to detect the new settings. This may take several minutes. To expidite the process, you can restart the Microsoft Exchange Information Store by running the following command: Restart-Service MSExchangeIS," Hope it helps Cheers TechNet Subscriber Support in forum If you have any feedback on our support, please contact tnmff@microsoft.com Zi Feng TechNet Community Support

Hi There are some Prerequisite steps on both server, so, did you follow those steps. Also, I noticed, there is a warning "After resetting the above properties, you will need to wait for Exchange to detect the new settings. This may take several minutes. To expidite the process, you can restart the Microsoft Exchange Information Store by running the following command: Restart-Service MSExchangeIS," Hope it helps Cheers TechNet Subscriber Support in forum If you have any feedback on our support, please contact tnmff@microsoft.com Zi Feng TechNet Community Support

I've heard the script is broken in RTM build. This should be fixed by the time Microsoft support coexistence.

I've heard the script is broken in RTM build. This should be fixed by the time Microsoft support coexistence.

Zi Hi; Can you try this in a lab and let me know if you get it to work, and the steps done? Thanks

Any idea when documentation for a 2007 to 2013 migration will be available? I am in need of this too, as well as the public folder migration piece.

Hi wits1 I found the same as what you got in my lab. I will do another test soon. CheersZi Feng TechNet Community Support

Hi wits1 Thank you for your question. I am trying to involve someone familiar with this topic to further look at this issue. Cheers TechNet Subscriber Support in forum If you have any feedback on our support, please contacttnmff@microsoft.comZi Feng TechNet Community Support

Coexistence between Exchange 2013 and earlier versions is currently not supported. I expect more documentation will be available when coexistence will be supported, this will be in the first half of 2013.Did my post help? Please use "Vote As Helpful", "Mark as answer" or "Propose as answer". Thank you!

You state there are some pre-req's on both servers ----> What are the pre-req's on Server 2003 with exchange 2007 to get the PS1 script to work correctlyl. Do we also have to modify the script as well to work on Windows 2003 server w/ Exchange 2007 Or is my only true option is to play Leap-frog and install a Exchange 2010 server / Server 2008R2. then move all public folder to EX2010 then to my EX2013 install. I should not have to install all Roles for 2010 - Should just need mailbox role (should not need, Edge, UM, Hub, Client access) is this correct ??

Coexistence between Exchange 2013 and earlier versions is currently not supported. I expect more documentation will be available when coexistence will be supported, this will be in the first half of 2013. Did my post help? Please use "Vote As Helpful", "Mark as answer" or "Propose as answer". Thank you! Seems ludicrous that M$ would release a product like exchange where "coexistances is not supported at this time". They are making this product useless for 99% of the audience. Why bother releasing Exchange 2013 now? No one can use it. Who is rolling out brand new, fresh domains with virgin Exchange 2013? No one, I can tell you that with almost 1000% certainty. Unless there are some unfortunate souls still on Groupwise or Lotus Notes. This looks like a project manager rushed it out the door so he could be sure he got his bonus for doing so, even if the product was not ready.

Seems to be a "Catch 22" here. As mentioned above, the script fails to see and generate the proper mailbox map file. So, if you decide not to use a migration procedure and simplying instead try to manually create the necessary public folders, the system detects the "existing Public Folder deployment" and prevents you from doing it manually. Either way you lose. Come on Microsoft, step up and deal with your support responsibilties for Exchange 2013! The Exchange 2013 web site says that conversion from Exchange 2007 is supported. Most people would consider being able to move their Public Folders as part of conversion and NOT coexistence. Cut the crap! You can't complete the conversion without moving ALL your data so that you can then WITHDRAW the older server from the Exchange Organization. I am totally aggravated at the previous responses I have seen in this thread. How about some alternatives? Export from Outlook to .pst files from old public folders, build new Public Folder structure manually, import .pst files into new structure ??? Any way to make this work? Alternatives? Solutions?

Hi All, As Jetze Mellema said, coexistence between Exchange 2013 and earlier versions is currently not supported. Although we can install Exchange 2013 into an Exchange 2007 SP3 ru8 environment, it is still not supported for coexistence until Exchange 2013 CU1 which should be released early next year. So, now, please hold on to migrate to Exchange 2013 from Exchange 2007. If you have done so, please move the mailboxes back to Exchange 2007 and wait for CU1. Thanks, Da Xu

Hi All, As Jetze Mellema said, coexistence between Exchange 2013 and earlier versions is currently not supported. Although we can install Exchange 2013 into an Exchange 2007 SP3 ru8 environment, it is still not supported for coexistence until Exchange 2013 CU1 which should be released early next year. So, now, please hold on to migrate to Exchange 2013 from Exchange 2007. If you have done so, please move the mailboxes back to Exchange 2007 and wait for CU1. Thanks, Da Xu

There's a not so subtle point that keeps being missed, perhaps deliberately. Coexistence implies an ongoing, working partnership between different versions on Exchange. Conversion / migration implies getting information off the older server, onto the newer one, and then retiring the old one. Who cares about the terminology? Microsoft has "released" Exchange 2013. That strongly suggests to me that the burden of support is upon Microsoft NOW, not at some later project phase when they feel like it. I don't care about your schedule, I care about mine. Don't give me lame excuses for answers. Oh wait my mistake, how silly of me ... our user mailboxes can be successfully moved ... we really don't need our Public Folder content ... yeah, it's all fully functional ... Public Folders were just a bad idea and we were silly to have ever used them! Do you folks get paid by the number of email or forum posts you reply to? These answers are simply useless and aggravating. Go DO some work and find a solution because your clients NEED one, don't tell me about YOUR schedule! Just "Get 'er done!"