Problem Migrating Public Folder Database from Exchange 2007 to 2013

I am just finishing migrating from Exchange 2007 on  Server 2003 to Exchange 2013 on Server 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 Exchange 2007 I get an error.

I have followed this

I run this cmdlet
New-MigrationBatch -Name PFMigration -SourcePublicFolderDatabase "Public Folder Database" -CSVData (Get-Content \\2003Server\pfmigration\csvs\maps.cvs -Encoding Byte) -NotificationEmails -BadItemLimit $BadItemLimitCount-

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        :

I've searched the net for answers without success.

Any help is appreciate.
Thanks in advance
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Simon Butler (Sembee)ConsultantCommented:
Why aren't you using the example command that they have provided on that page?

New-MigrationBatch -Name PFMigration -SourcePublicFolderDatabase (Get-PublicFolderDatabase -Server <Source server name>) -CSVData (Get-Content <Folder to mailbox map path> -Encoding Byte) NotificationEmails <email addresses for migration notifications> -BadItemLimit $BadItemLimitCount

Simply change the source server name to the name of the Exchange 2007 server and then the other changes that you have already made in your example above?

That will deal with the problem effectively going forwards.

From memory, I think the name of the public folder database has to be what you see here:

Get-PublicFolderDatabase | select identity

But the example that Microsoft have provided avoids the problem of doing the lookup on the database name by querying the server and populating the information for you.

EICTAuthor Commented:
Thanks for your prompt reply Simon,
I tried using the Get-PublicFolderDatabase command below first but someone suggested manually entering the name.

New-MigrationBatch -Name PFMigration -SourcePublicFolderDatabase (Get-PublicFolderDatabase -Server 2003Server) -CSVData (Get-Content \\2003Server\pfmigration\csvs\maps.cvs -Encoding Byte) -NotificationEmails -BadItemLimit $BadItemLimitCount

When I run the Get-PublicFolderDatabase cmdlet I get the following returned
Name                                      Server
----                                             ------
Public Folder Database         2003Sever

Regards Matt
Simon Butler (Sembee)ConsultantCommented:
When you use the command from Microsoft as I have posted, what happens? The same error?

The 7 Worst Nightmares of a Sysadmin

Fear not! To defend your business’ IT systems we’re going to shine a light on the seven most sinister terrors that haunt sysadmins. That way you can be sure there’s nothing in your stack waiting to go bump in the night.

EICTAuthor Commented:
Hi Simon,
Yes I get the same error.  The only difference between my original code and the microsoft code, as far as I can see the -NotificationEmails as there is a type in the Microsoft one i.e. no '-'

Thanks for your help
Simon Butler (Sembee)ConsultantCommented:
How much content is in Public Folders?

I will have to admit that I haven't migrated Exchange 2007 on Windows 2003 to Exchange 2013 - I haven't seen Exchange 2007 on Windows 2003 for four or five years. That shouldn't matter, but for whatever reason the Exchange 2013 server cannot see the public folder database.

If you have limited amount of content then I would be looking to get rid of public folders on Exchange 2007 completely. Create a shared mailbox to hold the content, drop public folders on Exchange 2007 and then build a new hierarchy on Exchange 2013. It makes things a lot more reliable in my experience.


Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
EICTAuthor Commented:
In the end I managed to access the public folders from a client connected to Exchange 2007. I exported the content to PST, dropped the entire 2007 pubic folder infrastructure. I was then able to recreate afresh in Exchange 2013 and import from PST.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.