#REMOVE EXCHANGE PUBLIC FOLDER ADSIEDIT WINDOWS#
Distributed File Server Replication on Windows Ser.Windows Server 2012 R2 Print Managmenet Console."Failed to submit the request because public folder migration has already been successfully completed previously" I got a couple of warnings (source MSExchange ADAccess, Event ID 2937) after removing a Exchange 2007 server at the end of a Exchange 2007 > 2013 migration. Without the final step, the following error is experienced: This final step has caught out many Exchange Admins and is not documented at all online. Remove the Exchange 2013 public folder move request using Get-PublicFolderMigrationRequest | Remove-PublicFolderMoveRequestĪt this point you would think you should be ready to migrate the public folders to Exchange 2013 again however there is a final step which needs to be performed.Clearing the MsExchDefaultPublicFolderMailbox attribute on the Exchange organisation with ADSIEdit as per Exchange MVP Satheshwaran Manoharan's article.
![remove exchange public folder adsiedit remove exchange public folder adsiedit](https://i0.wp.com/ares.gobien.be/wp-content/uploads/2013/05/error2.png)
Removing the default public folder hierarchy mailbox with Get-Mailbox –PublicFolder | Remove-Mailbox -PublicFolder.Removing all public folders from the newly created public folder mailbox with Get- PublicFolder –Recurse | Remove-PublicFolder (make sure you run this on Exchange 2013 Management Shell so you don't delete the public folders on your 2007/2010 environment).
![remove exchange public folder adsiedit remove exchange public folder adsiedit](https://content.spiceworksstatic.com/service.community/p/how_to_step_attachments/0000106722/55fb1778/attached_file/614a3a48190fb4654a4e7288370688a2794909fd23eb5f43b52b7a0dd1afe8f2_Browse_to_the_exchange_servers.jpg)
To repeat the migration progress you need to perform the following steps: When migrating to Exchange 2013 modern public folders, you may want to repeat the migration especially if you need to tweak the Public Folder-to-Mailbox Mapping File and perform the migration again.