asked on

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 https://technet.microsoft.com/en-us/library/dn912663(v=exchg.150).aspx

I run this cmdlet
New-MigrationBatch -Name PFMigration -SourcePublicFolderDatabase "Public Folder Database" -CSVData (Get-Content \\2003Server\pfmigration\csvs\maps.cvs -Encoding Byte) -NotificationEmails support@domain.org -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 : 2012Server.domain.org

I've searched the net for answers without success.

Any help is appreciate.
Thanks in advance

Simon Butler (Sembee)

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.

Simon.

EICT

ASKER

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 support@domain.org -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)

When you use the command from Microsoft as I have posted, what happens? The same error?

Simon.

EICT

ASKER

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

ASKER CERTIFIED SOLUTION

Simon Butler (Sembee)

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

EICT

ASKER

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.