Migrating Public Folders from Exchange 2010 to Exchange 2013

Hi,

I am just finishing migrating from SBS2011 with Exchange 2010 to Server 2012 Standard with Exchange 2013.

The problem I am having is when I run the New-MigrationBatch script on the 2012 server to begin migration of public folders from the SBS2011 Server.

I have followed this https://technet.microsoft.com/en-GB/library/jj150486(v=exchg.150).aspx 

I run this cmdlet New-MigrationBatch -Name PFMigration -SourcePublicFolderDatabase (Get-PublicFolderDatabase -Server sbserver) -CSVData (Get-Content C:\PFMigration\folder-to-mailbox.csv -Encoding Byte) -NotificationEmails

I then get this error 

A parameter cannot be found that matches parameter name 'SourcePublicFolderDatabase'.
    + CategoryInfo          : InvalidArgument: (:) [New-MigrationBatch], ParameterBindingException
    + FullyQualifiedErrorId : NamedParameterNotFound,New-MigrationBatch
    + PSComputerName        : server2.domain.local

I have tried changing this to direct public folder database name but I still get errors.

Can anybody shed any light as to what I am doing wrong here?

Thanks in advance

May 11th, 2015 4:05am

Hi,

You are following the right guide to migrate public folders to Exchange 2013 from your old Exchange Server. This error may occurs because at one time Exchange allows only single migration process to log into the public folder database.

You may also follow one of another guideline to do your task of Public Folder migration https://supertekboy.com/2014/10/13/2013-public-folder-migration-made-easy/.

Moreover that i would also suggest you use trusted tool to do PFs migration as it is one of the most complectedtask in whole migration process. Follow the link as suggested "Exchange Public Folder Migration". OR you can also go for Exchange Migration Services.

Hope my suggestions will work for you.

Free Windows Admin Tool Kit Click here and download it now
May 11th, 2015 5:23am

Hi,

I am just finishing migrating from SBS2011 with Exchange 2010 to Server 2012 Standard with Exchange 2013.

The problem I am having is when I run the New-MigrationBatch script on the 2012 server to begin migration of public folders from the SBS2011 Server.

I have followed this https://technet.microsoft.com/en-GB/library/jj150486(v=exchg.150).aspx 

I run this cmdlet New-MigrationBatch -Name PFMigration -SourcePublicFolderDatabase (Get-PublicFolderDatabase -Server sbserver) -CSVData (Get-Content C:\PFMigration\folder-to-mailbox.csv -Encoding Byte) -NotificationEmails

I then get this error 

A parameter cannot be found that matches parameter name 'SourcePublicFolderDatabase'.
    + CategoryInfo          : InvalidArgument: (:) [New-MigrationBatch], ParameterBindingException
    + FullyQualifiedErrorId : NamedParameterNotFound,New-MigrationBatch
    + PSComputerName        : server2.domain.local

I have tried changing this to direct public folder database name but I still get errors.

Can anybody shed any light as to what I am doing wrong here?

Thanks in advance

Looks like your command is wrong.  According to the link you posted it should be:

New-PublicFolderMigrationRequest -SourceDatabase (Get-PublicFolderDatabase -Server <Source server name>) -CSVData (Get-Content <Folder to mailbox map path> -Encoding Byte) -BadItemLimit $BadItemLimitCount

May 11th, 2015 9:41am

Hi dancarter,

Thank you for your question.

Run the following command to check if we could see the public folder:

Get-PublicFolderDatabase Server sbservername

If we could get public folder name, make sure AD replication without any problem then check if the issue persist.

If there are any questions regarding this issue, please be free to let me know. 

Best Regard,

Jim

Free Windows Admin Tool Kit Click here and download it now
May 12th, 2015 9:09am

Hi,

I am just finishing migrating from SBS2011 with Exchange 2010 to Server 2012 Standard with Exchange 2013.

The problem I am having is when I run the New-MigrationBatch script on the 2012 server to begin migration of public folders from the SBS2011 Server.

I have followed this https://technet.microsoft.com/en-GB/library/jj150486(v=exchg.150).aspx 

I run this cmdlet New-MigrationBatch -Name PFMigration -SourcePublicFolderDatabase (Get-PublicFolderDatabase -Server sbserver) -CSVData (Get-Content C:\PFMigration\folder-to-mailbox.csv -Encoding Byte) -NotificationEmails

I then get this error 

A parameter cannot be found that matches parameter name 'SourcePublicFolderDatabase'.
    + CategoryInfo          : InvalidArgument: (:) [New-MigrationBatch], ParameterBindingException
    + FullyQualifiedErrorId : NamedParameterNotFound,New-MigrationBatch
    + PSComputerName        : server2.domain.local

I have tried changing this to direct public folder database name but I still get errors.

Can anybody shed any light as to what I am doing wrong here?

Thanks in advance

Looks like your command is wrong.  According to the link you posted it should be:

New-PublicFolderMigrationRequest -SourceDatabase (Get-PublicFolderDatabase -Server <Source server name>) -CSVData (Get-Content <Folder to mailbox map path> -Encoding Byte) -BadItemLimit $BadItemLimitCount
May 13th, 2015 4:34pm

I ran the above

Get-PublicFolderDatabase Server sbservername

I can see the public folder database.

Thanks

Free Windows Admin Tool Kit Click here and download it now
May 13th, 2015 4:35pm

Hi dancarter,

Did the issue solve?

Best Regard,

Jim

May 14th, 2015 5:21am

eh if it's just one database then toss the database name in the command manually and try running it again.
Free Windows Admin Tool Kit Click here and download it now
May 14th, 2015 8:36am

Hi Jim

No please see my above replies as to the next error I got when I changed the cmdlet script.

Thanks in advance

Dan

May 16th, 2015 2:39am

eh if it's just one database then toss the database name in the command manually and try running
Free Windows Admin Tool Kit Click here and download it now
May 16th, 2015 2:44am

I ran the above

Get-PublicFolderDatabase Server sbservername

I can see the public folder database.

Thanks

Hi dancarter,

Did you get error when you run the following command:

Get-PublicFolderDatabase Server sbservername

Then run the following command:

Get-PublicFolderDatabase server contoso\<sbsname>

If there are any questions regarding this issue, please be free to let me know.

Best Regard,

Jim


May 19th, 2015 4:06am

I ran the above

Get-PublicFolderDatabase Server sbservername

I can see the public folder database.

Thanks

Hi dancarter,

Did you get error when you run the following command:

Get-PublicFolderDatabase Server sbservername

Then run the following command:

Get-PublicFolderDatabase server contoso\<sbsname>

If there are any questions regarding this issue, please be free to let me know.

Best Regard,

Jim

Free Windows Admin Tool Kit Click here and download it now
May 19th, 2015 4:36pm

Hi dan,

Did the parameter of sbsname replace into server2.leven.local?

Are there any errors in application log when we run command with errors?

We could use the following command to retrieve the name of public folder:

Get-PublicFolderDatabase -Server sbserver | FL

Then run:

New-MigrationBatch -Name PFMigration -SourcePublicFolderDatabase Public folder Database 1065 -CSVData (Get-Content C:\PFMigration\folder-to-mailbox.csv -Encoding B) -NotificationEmails

If there are any questions regarding this issue, please be free to let me know.

Best Regard,

Jim

May 19th, 2015 11:21pm

Hi Jim,

So I ran the above in this format New-MigrationBatch -Name PFMigration -SourcePublicFolderDatabase 'Public Folder Database 1065320222' -CSVData (Get-Content C:\PFMigration\folder-to-mailbox.csv -Encoding Byte) -NotificationEmails myemail address

I got this error

[PS] C:\Windows\system32>New-MigrationBatch -Name PFMigration -SourcePublicFolderDatabase 'Public Folder Database 106532
0222' -CSVData (Get-Content C:\PFMigration\folder-to-mailbox.csv -Encoding Byte) -NotificationEmails myemail.com
A parameter cannot be found that matches parameter name 'SourcePublicFolderDatabase'.
    + CategoryInfo          : InvalidArgument: (:) [New-MigrationBatch], ParameterBindingException
    + FullyQualifiedErrorId : NamedParameterNotFound,New-MigrationBatch
    + PSComputerName        : server2.domain.local

Once again thanks very much for your help

Free Windows Admin Tool Kit Click here and download it now
May 21st, 2015 5:00pm

Why are you running the new-migrationbatch again? That's not going work for this process.  Try running this:

New-PublicFolderMigrationRequest -SourceDatabase "Your Public Folder Database Name in quotes" -CSVData (Get-Content <Folder to mailbox map path> -Encoding Byte) -BadItemLimit $BadItemLimitCount

May 21st, 2015 7:33pm

Why are you running the new-migrationbatch again? That's not going work for this process.  Try running this:

New-PublicFolderMigrationRequest -SourceDatabase "Your Public Folder Database Name in quotes" -CSVData (Get-Content <Folder to mailbox map path> -Encoding Byte) -BadItemLimit $BadItemLimitCount
Free Windows Admin Tool Kit Click here and download it now
May 22nd, 2015 9:00am

Looks like you didn't create the PFMailbox (or you did and it is a different name).  

Run Get-Mailbox -PublicFolder

If this returns something, use whatever value it returns for the public folder mailbox.  If it doesn't you need to do Step 4 (https://technet.microsoft.com/en-us/library/jj150486%28v=exchg.150%29.aspx?f=255&MSPPError=-2147217396)

May 22nd, 2015 9:06am

Was this ever resolved? I'm having the same issue.
Free Windows Admin Tool Kit Click here and download it now
June 4th, 2015 12:12pm

Here is what I found out working with support. The SourcePublicFolderDatabase parameter of New-MigrationBatch doesn't work in some installs. The workaround is to run powershell and add the exchange snapin. "Add-PSSnapin Microsoft.exchange.*" After doing this I could create the batch for public folder migration.

June 8th, 2015 12:47pm

Hi,

had the same error. Solved by installing Exchange 2013 CU8

I had Exchange 2013 SP1 and the -SourcePublicFolderDatabase parameter in the New-MigrationBatch cmdlet was missing. Probably SP1 supports only serial migration.

Best Regards,
Marco

Free Windows Admin Tool Kit Click here and download it now
July 7th, 2015 11:52am

That may work for some but in certain instances when going to CU8 and you still have the issue. If so then use the workaround I posted.
July 7th, 2015 12:21pm

Here is what I found out working with support. The SourcePublicFolderDatabase parameter of New-MigrationBatch doesn't work in some installs. The workaround is to run powershell and add the exchange snapin. "Add-PSSnapin Microsoft.exchange.*" After doing this I could create the batch for public folder migr

Free Windows Admin Tool Kit Click here and download it now
August 3rd, 2015 11:37am

This is still not working for me.  I have tried running the command within the EMS, an elevated EMS, regular Powershell and elevated Powershell and I get the same darn error EVERY TIME.

"New-MigrationBatch : A parameter cannot be found that matches parameter name 'SourcePublicFolderDatabase'"

What the heck is going on and how do I fix it??!?!?

August 18th, 2015 2:32pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics