Are you following the procedures in the below article?

https://technet.microsoft.com/en-us/library/jj150486%28v=exchg.150%29.aspx?f=255&MSPPError=-2147217396

Step4: create public folder mailbox using the below command

New-Mailbox -PublicFolder <Name> -HoldForMigration:$true

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!

can you share the exact error, also I would highly recommend you install the latest updates on both Exchange 2013 and Exchange 2010.

On the 2013 box I get this when running Get-PublicFolderMigrationRequest

[PS] C:\Windows\system32>Get-PublicFolderMigrationRequest
[PS] C:\Windows\system32>

On the 2010 box I get this

[PS] C:\Windows\system32>Get-OrganizationConfig | fl PublicFoldersLockedforMigration, PublicFolderMigrationComplete

PublicFoldersLockedForMigration : False
PublicFolderMigrationComplete   : False

On the 2013 Box if i try to just use the EAC to create a new Public Folder Mailbox I get this:

An existing Public Folder deployment has been detected. To migrate existing Public Folder data, create new Public Folder mailbox using -HoldForMigration switch.

I have to step out for a few hours but i will check back this afternoon. Thanks for the quick reply.

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:

1. Open the Exchange Management Shell.
2. 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

1. 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)    
2. 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,

Hi Zulea,

Any update?

Best regards,

Niko,

Thanks for reminding me about this. I did finally get the public folders to migrate. I followed Mohammad's article he linked to. At the end of that I ran into the mailbox lock error so it wouldn't finish. I found some website that I can't remember that said just restart the server and wait. i did that a couple of times and it did finally work. I am not sure why but it did. 

Thanks for the help.