Migrating Exchange 2013 public mailboxes to a new server

We have a client that is leaving their current Hosting company and wants to move to our hosting facility. We have recreated their DC,an Exchange Hub, and Exchange Store. We have exported and imported all of their recipient mailboxes and flipped the switch
and all mail flow is now going through our hosting facility. The problem lies in that I can not figure out how to move the public mailboxes out of the old exchange server and import it into the new server. Both are Exchange 2013 and running on windows server
2012. Any help would be greatly appreciated.

You're looking at a third-party product. MigrationWiz does public folders. There are other cloud-based migration solutions, but I don't know whether they support public folder migrations.
Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Similar Messages

Migrating from Exchange 2007 to Exchange 2013 Public Folders coexistence

Hi all, I'm migrating from Exchange 2007 SP3 to Exchange 2013 SP1.
I have an Exchange 2007 server (Client Access, Hub Transport and Mailbox Server) in Site A, mailboxes and Publics Folders
In another Site in Site B, I have already installed (Client Access and Mailbox Server) Exchange 2013 server.
I am migrating test users, the fact is that users who migrated to Exchange Server 2013 Public folders do not see.
How I can make the migrated users from viewing the Exchange 2007 Public Folders duration coexistence?
Is there a "how to" to migrate Public Folders from Exchange 2007 to Exchange 2013?
thank you very much
Microsoft Certified IT Professional Server Administrator

Hi,
In Exchange 2013, the Public Folder is changed to Public Folder mailbox instead of Public Folder in Exchange 2007 database.
Due to the changes in how public folders are stored, legacy Exchange mailboxes are unable to access the public folder hierarchy on Exchange 2013 servers. However, user mailboxes on Exchange 2013 servers or Exchange Online can connect to legacy
public folders. Exchange 2013 public folders and legacy public folders can’t exist in your Exchange organization simultaneously. This effectively means that
there’s no coexistence between versions.
For this reason, it’s recommended that prior to migrating your public folders, you should
first migrate your all legacy mailboxes to Exchange 2013. For more information about migrating public folder from previous versions, please refer to:
http://technet.microsoft.com/en-us/library/jj150486(v=exchg.150).aspx
(Please note the What do you need to know before you begin part in this link)
Regards,
Winnie Liang
TechNet Community Support

Outlook 2007 - single profile connecting to Exchange 2013 / 2007 mailboxes

Hi,
I am in the early part of a migration from Exchange 2007 to Exchange 2013. So far I have 2013 installed and running in a DAG and just moved my own mailbox to the new server.
I set up a new profile in Outlook 2007 which connects to my mailbox on Exchange 2013. The problem is that I need to add additional mailboxes to my profile which are still hosted on Exchange 2007, however this is not working.
I thought at one stage I tested this and was able to get it work with a test mailbox also hosted on Exchange 2013.. but maybe I never did.
Does anyone know if this is possible at all (single Outlook profile, primary mailbox hosted on Exchange 2013 and other mailboxes on Exchange 2007). Most of our users have an additional mailbox mapped in their profile so I hope there is some way around this.
Thank you!

Hi,
It is possible to open a shared mailboxes on a legacy server.
Your problem could be caused by:
Not having one of the later CU installed (read CU4 or CU5)
Incorrect authentication methods configured (see link below)
Outlook is not at the latest patch level
Users of Exchange Server 2013 can't open public folders or shared mailboxes on an Exchange 2010 or Exchange 2007 server
http://support.microsoft.com/kb/2834139
Martina Miskovic

Unable to Manage custom forms in Exchange 2013 Public Folders or Organizational Forms Library

We've been doing custom forms development for many years and many versions of Exchange. This Exchange 2013 presented me with this new problem. We use Exchange 2013 with Cumulative Update 5, and Outlook 2007, 2010 and 2013. This problem
happens on all versions of the latest patched Outlooks.
1) I have successfully created a Public Folder and an Organizational Forms Library
2) I have granted myself "Owner" privilege to the entire public folder in both the IPM_Subtree and the Non_IPM_Subtree
3) I can publish forms into a Public Folder and the Organizational Forms Library
But, after the form is published, I can't manage it. The COPY, UPDATE, DELETE, PROPERTIES, and SAVE AS buttons are greyed out.
This does not happen for anything in my Personal Forms, my Mailbox or anything in Favorites that are locally cached.
Since the Organizational Forms Library cannot be "Cached" by putting it in Favorites, there seems to be NO way to even delete a form that is published to there.
The closest link that describes a similar (maybe same) problem is
http://www.michev.info/Blog/Post/14/Unable-to-manage-Forms-in-Outlook
A) Anybody else have the same problem?
B) Since it seems I only have control over forms in my Mailbox, and since Public Folders are suppose to be an mailbox, does anyone know how to setup a Public Folder so that you can login to it and attach it as a mailbox?
C) Does anyone know how to make the Organizational Forms Library cached locally so it can be managed?
J Awe TechBldrs Inc. www.TechBldrs.com

Easy steps to reproduce the problem.
1) create a public folder subfolder (do not create a Favorite)
2) make yourself and OWNER
3) publish a form to the subfolder (Open a any form and save it with any name)
4) use the Form Manager select the public folder subfolder that you are an OWNER of
5) select a form and see if the buttons are GRAYED out.
PLEASE TRY THIS ON YOUR OWN SYSTEMS TO VERIFY THE PROBLEM.
J Awe TechBldrs Inc. www.TechBldrs.com

Exchange 2013: This mailbox database is associated with one or more active mailboximport / Cannot uninstall exchange

We have a corrupted installation of Exchange 2013 due to installating CU6
New Exchange server is already installed and mailboxes are migrated over, I am now in the process to uninstall the old exchange 2013 so we can decomission it but I get this error when I try to run uninstall
"This mailbox database is associated with one or more active mailbox import,To get a list of all Mailboximport request associated with this database, run Get MailboxImportRequest | ?{ $_.RequestQueue -eq "<Database ID>"}....
But when i run this command I get an error of" The Get-MailboxImportRequest is not recognized as a cmdlet...
Any advise is appreciated
Thanks.

Hi ,
From the error message i came to know few things i have mentioned mentioned below .
If you want to remove the problematic exchange server , you need to remove the existing mailbox import requests.
For that you should need to have the required permission for the user account from which you are trying to execute the command
Just check your user account is having the Mailbox Import Export role permissions .
If you have the required permissions then go ahead and execute the commands
Get-MailboxImportRequest | ft -au ( this is to see how many no of the mailbox import request are available
Remove-MailboxImportRequest
( this command is to remove the entire mailbox import move request)
Once you have done with that , then you start proceeding uninstalling the exchange server .
Regards
S.Nithyanandham
Thanks S.Nithyanandham

Migrate Exchange 2003 Public folders and OAB to Office365?

Hi guys,
I am trying to migrate exchange 2003 public folders to office 365. I have read various documentation however they were either out of date or half-solutions.
The company stored OAB's in each public folder as well, how do I go about migrating these lists into office 365? Will it just "work" if I migrate the public folders across?
Thanks,
Alex

Hi,
If you are migrating from inhouse 2003 to office 365, then the best options for you are-
1. Either you can go for the manaul process. You can create PST files and can upload them to mailboxes through office 365 account.
Kindly refer the below mentioned link for the same
http://blogs.technet.com/b/canitpro/archive/2013/05/31/step-by-step-migration-of-exchange-2003-server-to-office-365.aspx
2. Or you can go for any 3rd party tool using the same you can migrate your public folders to office 365. This is required when you need to avoid the risks associated and need to keep your environment up and running even while migration process. Respond
back for third party tool suggestions.

Migration Exchange 2013 to Exchange 2013

Hello,
I have 1 Exchange server 2013 (Mbx+Cas) and for some resons I need to install one more Exchange server 2013 (Mbx+Cas) and I changed all of the virtualdirectory's link, I changed Autodiscover internal URL. When I check Client Outlook Test E-mail
Auto configuration I see autodiscover links shows old server's name. Thats why I can't turn off the old server. in Outlook Test E-mail Auto Configuration how can I change Autodiscover to https:\\...... link? thanks in advance

Hi
Have you moved the mailboxes to the new server? You can install a new server and gradually move the mailboxes. you will need to setup your urls, autodiscover record in DNS etc.

Exchange 2013 Health Mailbox filling up security logs

I'm doing security audits and having the Exchange 2013 Health Mailbox fill up my security logs. I've read that if I delete the mailboxes and re-create them and restart the service the errors will go away. My question is how do I delete them?
I found the full mailbox name with this command.
get-mailbox -monitoring | select-object -expandproperty name
Do I use this method?
Remove-Mailbox -Identity contoso\johnor this one?Remove-Mailbox -Identity contoso\john -Permanent $trueOr something else?
Thanks!
Fernando

I did help on the setup in Exchange server folder. Looks like prepares Active Directory forest for Exchange Install. /PrepareAD, /p So this is what I'm supposed to run?
C:\Program Files\Microsoft\Exchange Server\V15\Bin>setup /?
Welcome to Microsoft Exchange Server 2013 Cumulative Update 3 Unattended Setup
For detailed help, type one of the following options:
Setup /help:Install - Install Exchange server roles.
Setup /help:Upgrade - Upgrade an existing Exchange server.
Setup /help:Uninstall - Uninstall Exchange server roles.
Setup /help:RecoverServer - Recover an existing Exchange server.
Setup /help:PrepareTopology - Prepare your topology for Exchange.
Setup /help:Delegation - Delegate server installations.
Setup /help:UmLanguagePacks - Add or remove Unified Messaging
language packs.
C:\Program Files\Microsoft\Exchange Server\V15\Bin>Setup /help:PrepareTopology
Welcome to Microsoft Exchange Server 2013 Cumulative Update 3 Unattended Setup
Microsoft Exchange Server 2013 Setup Parameter Help
Prepare Topology Usage:
Setup /PrepareAD [<OptionalParameters>]
/IAcceptExchangeServerLicenseTerms
Setup /PrepareSchema [<OptionalParameters>]
/IAcceptExchangeServerLicenseTerms
Setup /PrepareDomain [<OptionalParameters>]
/IAcceptExchangeServerLicenseTerms
Setup /PrepareDomain:<domainA, domainB> [<OptionalParameters>]
/IAcceptExchangeServerLicenseTerms
Setup /PrepareAllDomains [<OptionalParameters>]
/IAcceptExchangeServerLicenseTerms
--Prepare Topology Required Parameters--
/PrepareAD, /p
Prepares the Active Directory forest for the Exchange
installation.
Fernando

Exchange 2013 Shared Mailbox Get-MailboxSentItemsConfiguration SP1 Help

Hello
My Setup
Server1: Server 2012 Standard + Exchange 2013 CU2 Standard (MBX+CAS)
Server2: Server 2012 Standard + Exchange 2013 CU2 Standard (MBX+CAS)
DAG Enable
I am having problems with Shared mailboxes, when sending E-mail from the Shared mailbox the sent E-mail will show up in the recipients Sent Items insted of the Shared mailbox sent Items.
I know that in Exchange 2010 Later SP and RU there where a PowerShell command that could send a copy to the Shared mailbox Sent Items (Get-MailboxSentItemsConfiguration)
but it doesn't seem to be there anymore, does anyone know if the cmdlet is back in CU3 or SP1? will it come back?
there is a workaround (Registry) but it doesn't help us, not for our environment.
Can I set this up by Outlook rules or maybe some kind of forwarding?
If you have any experience with this, feel free to give some advice.
Thank You very much!

Hi,
*.MailboxSentItemsConfiguration has not been brought back in CU3 or CU4/SP1 and I don't know if it ever will be.
If DelegateSentItemsStyle configured in the registry is not an option for you, then using multiple Exchange accounts in the same Outlook Profile might be. The support for that was added in Outlook 2010 and personally, I like that option a lot.
Martina Miskovic

Exchange 2013 "451 4.7.0 Temporary server error. Please try again later. PRX5" Error

I know this error message is discussed on other topics on several different forums including TechNet but I ended up opening this as the suggestions that solved the problems with the previous threads dos not work on mine.
We have a ticketing software that runs on client computers which sends mails to local Exchange server for notifications using port 25.
Approximately 1 out of 5 mails end up getting the "451 4.7.0 Temporary server error. Please try again later. PRX5" error. I have confirmed this by running Wireshark on the clients, saw the exact error message. This has been replicated with
several client machines running Win7 & 8.
I have tried several solutions to this, one of them being this:
http://www.techieshelp.com/exchange-2013-451-4-7-0-temporary-server-error-please-try-again-later-prx5/
I still get the same error from time to time after doing this, so it is not the issue. All the records in local hosts file, receive connector is listening to port 25 on all IPv4 addresses.
The server has a single NIC and the DNS lookups are done through that single NIC, not through "All available adapters" as set by default on ECP.
Almost everyone seems to be convinced that this is related to DNS but looking at how fast I get the error message, it doesn't look like it's waiting for a timeout (maybe unrelated, just an observation). Do you think it is possible that the DNS servers themselves
are causing this issue?
Also, I see Event 5504 on the primary dns server almost all of them coming from the mail server, saying that the DNS query was invalid. It may be related.
Additional Notes:
- CU6 is applied but did not fix the issue.
- None of these have solved it for me: http://www.servolutions.com/support/articles/Temporaryservererror2013.htm
- Receive Connectors do listen to separate ports 25 & 2525 -> There is a single instance of both Transport Service and Edge Transport service respectively. Anonymous users are accepted in both Receive connectors.

Thank you for your post.
This is a quick note to let you know that we are performing research on this issue.
Niko Cheng
TechNet Community Support
Thank you Niko. I'm looking forward to your answer as I've gone through every post regarding this and none of them worked. I will let everyone know if I can find a solution to this.

Exchange 2013 Public Folders - Adding another PF mailbox

Hi,
I'm sure this is obvious, but I've looked and can't find anything.
We're in the process of completing a cross forest migration from Exchange 2010 to Exchange 2013 on premise. We've migrated PF content (using a third party app) and we're currently at around 90% of the quota for the first PF mailbox (PFMAILBOX1). My question
is, how do we start using the second mailbox (PFMAILBOX2 in this case)? Does it just roll over when it breaches the PF quota?
PFMAILBOX1 has the primary hierarchy and PFMAILBOX2 has secondary - not sure if this makes any difference?
As usual, any help appreciated.
Regards
Steve

Hello,
You can use New-PublicFolderMoveRequest to move Public Folders to new mailbox (single folder, folder tree etc). For further informations look at:
http://technet.microsoft.com/en-us/library/jj878081%28v=exchg.150%29.aspx.
Hope it helps,
Adam
CodeTwo: Software solutions for Exchange and Office 365
If this post helps resolve your issue, please click the "Mark as Answer" or "Helpful" button at the top of this message. By marking a post as Answered, or Helpful you help others find the answer faster.

Exchange 2013 Public Folder Migration Not Listed

I started a public folder migration from my 2010 SP3 Exchange server to my new 2013 SP1 Exchange server. Somewhere during the process I failed. Not sure where but I am now at the point where if I try to create a new public folder on teh 2013 box i get a
warning like this.
An existing Public Folder deployment has been detected. To migrate existing Public Folder data, create new Public Folder mailbox using -HoldForMigration switch.
So I then run Get-PublicFoldermIgrationRequest to see what is still waiting... I get no migration listed in Exchange Management Shell.
I would like to find the place in AD or in the Server that thinks there is still an active request out there and remove it so I can start again with a clean slate. How do I do that?
Thanks!

Hi Zulea,
This is a known issue, I recommend you refer to the following article to resolve the issue:
http://support.microsoft.com/kb/3004062/en-us
Cause:
This problem occurs when the Exchange organization coexists with an earlier version of Exchange Server, and one or more public folder databases from the earlier version of Exchange still exist.
Resolution:
To resolve this issue, use one of the following methods.
Method 1: Create the mailbox by using the -HoldForMigration switch:
This option lets an administrator create a public folder mailbox in order to begin a migration from the existing public folders:
Open the Exchange Management Shell.
Run the following cmdlet to create the public folder mailbox:
New-Mailbox "Public Folder Mailbox" -PublicFolder -HoldForMigration
Method 2: Remove all public folder databases from earlier versions of Exchange Server
To remove existing public folder databases, see the following TechNet websites, as appropriate for the version of Exchange that an existing public folder resides on.
Exchange 2010:
http://technet.microsoft.com/en-us/library/dd876883(v=exchg.141).aspx
(http://technet.microsoft.com/en-us/library/dd876883(v=exchg.141).aspx)
Exchange 2007:
http://technet.microsoft.com/en-us/library/aa998329(v=EXCHG.80).aspx
(http://technet.microsoft.com/en-us/library/aa998329(v=EXCHG.80).aspx)
Create the public folder mailbox by using either the Exchange Admin Center (EAC) or the Exchange Management Shell (EMS). To do this, see the following TechNet website:
http://technet.microsoft.com/en-us/library/jj552410(v=exchg.150).aspx
Best regards,
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Niko Cheng
TechNet Community Support

Exchange 2013 Public Folder Migration Problem

Hi All,
Wonder if any of you can assist with a public folder issue I am having with Exchange 2013. We have migrated from Exchange 2010 to 2013.
I have followed the guide for public folder migration here
http://technet.microsoft.com/en-us/library/jj150486(v=exchg.150).aspx
Everything went fine and as per the document - except I had to use the "largeitemlimit" parameter to get the public folder migration to complete.
We tested the public folder migration by adding content to public folders and creating public folders and it all appeared to be OK, we completed the migration and removed our old public folder databases from Exchange 2010.
However we noticed later that users cannot CREATE folders in SOME public folders. It appears from some testing that any folder that does not lie in the first public folder mailbox, end users cannot create public folders. Administrators can create them
fine from the ECP - just not from outlook.
It also appears some users cannot see some folders that they have permissions to.
Can anyone assist with some ideas to resolve ?
Thanks.

Question?
Are you able to create the Folder in OWA?
Cheers,
Gulab Prasad,
Technology Consultant
Blog:
www.exchangeranger.com
Twitter:
   LinkedIn:
Check out CodeTwo’s tools for Exchange admins
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.
it is not functionally possible to create Public Folders in OWA user interface in Exchange 2013!.... From admin ECP it works fine!
My Bad, that's what I was trying to say.
Testing the same thing in the LAB, should have some update tomorrow morning.
Cheers,
Gulab Prasad,
Technology Consultant
Blog:
www.exchangeranger.com
Twitter:
LinkedIn:
Check out CodeTwo’s tools for Exchange admins
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

Exchange 2013 - Public Folder Mailbox and Single Item Recovery

Hello,
I recently had a request to recover some messages that an ex-employee deleted from the "recover deleted items" folder in their public folder. Since this resides on a public folder mailbox and it does have the option for
"Single Item Recovery" to be enabled on the box (which I enabled not knowing if this really works or not), is there a way I can still recovery these items or do I have to go to a backup to obtain those messages. Since ExFolders does not work that
is not an option. I've seen commands to restore a public folder that was deleted but not items that were deleted directly from a public folder. I checked using MFCMAPI and I do see the dumper root and the public folder dumpster for each folder but it
looks to be only the "deletions" folder and don't see anything similar to a "purges" type folder. Any ideas or am I stuck recovering from backup? Thanks in advance!

So I think you are stuck and will need to restore the EDB to a Recovery Database to restore the items because when the end user purged the items from the "Recover Deleted Items" it removes them from the Recoverable Items/Deletions folder.
Check out this article
http://blogs.technet.com/b/exchange/archive/2013/08/23/recovering-public-folder-information-in-exchange-2013.aspx
I have not played with the recoverable items settings on the 2013 public folder enabled mailbox EDB but you might try checking out Litigation or In Place Hold to use as a safety mechanism moving forward. That said this will also increase the
DB size so consider all the options before implementing
Search, Recover, & Extract Mailboxes, Folders, & Email Items from Offline Exchange Mailbox and Public Folder EDB's and Live Exchange Servers or Import/Migrate direct from Offline EDB to Any Production Exchange Server, even cross version i.e. 2003 -->
2007 --> 2010 --> 2013 with Lucid8's
DigiScope

EXCHANGE 2013 Public Folder Migration across Domain Forest

Hi
I am planning to migration public folder across the forest but unable find any documentation. can you guys share the step by step guide to move/migrate public folder. we have exchange 2013 in source and target forest.
Please help!

Hi,
Currently, there is no official document about Exchange 2013 cross-forest public folder migration. Maybe some third party software can help you to do cross forest public folder migration.
Best regards,
Belinda Ma
TechNet Community Support

Migrating Exchange 2013 public mailboxes to a new server

Similar Messages

Maybe you are looking for