I have an issue of trying to migrate public folder from the old 2007 exchange to the current 2013 exchange and it fails. When trying to start the migration request I get the error "Couldn't connect to the source mailbox".
This is the main documentation guideline that I followed.
http://blogs.technet.com/b/meamcs/archive/2013/07/25/part-1-step-by-step-exchange-2007-to-2013-migration.aspx
I have done a lot of research online and especially TechNet and found a few people with the exact same issue. I have tried each of the options that suggest a fix. I have tried creating a new user on the old Exchange 2007, adding a new mailbox, and I have tried
restarting exchange services. I have made certain that both the exchange services use NTLM, and I have tried both of the PFMigration processes (batch and serial).
Serial migration
https://technet.microsoft.com/en-us/library/jj150486(v=exchg.150).aspx
Batch migration
https://technet.microsoft.com/en-us/library/Dn912663(v=EXCHG.150).aspx
[PS] C:\PFMigration>Get-OutlookAnywhere | fl Identity,*auth*
Identity
: EX2013\Rpc (Default Web Site)
ExternalClientAuthenticationMethod : Ntlm
InternalClientAuthenticationMethod : Ntlm
IISAuthenticationMethods : {Basic, Ntlm, Negotiate}
Identity
: EX2007\Rpc (Default Web Site)
ExternalClientAuthenticationMethod : Ntlm
InternalClientAuthenticationMethod : Ntlm
IISAuthenticationMethods : {Ntlm}
[PS] C:\PFMigration>New-PublicFolderMigrationRequest -SourceDatabase (Get-PublicFolderDatabase -Server EX2007.EXDOM.int) -CSVData (Get-Content C:\PFMigration\FolderToMailbox.csv -Encoding Byte) -BadItemLimit $BadItemLimitCount
WARNING: When an item can't be read from the source database or it can't be written to the destination database, it will be considered corrupted. By specifying a non-zero BadItemLimit, you are requesting Exchange not copy such items to the destination
mailbox. At move completion, these corrupted items will not be available at the destination mailbox.
Couldn't connect to the source mailbox.
+ CategoryInfo
: NotSpecified: (:) [New-PublicFolderMigrationRequest], RemoteTransientException
+ FullyQualifiedErrorId : [Server=EX2013,RequestId=df177ab0-e9c7-40bc-9c61-cd0e19f56a0b,TimeStamp=8/5/2015 1:25:34AM] [FailureCategory=Cmdlet-RemoteTransientException] 19495301,Microsoft.Exchange.Management.RecipientTasks.NewPublicFolderMigrationRequest
+ PSComputerName
: EX2013.EXDOM.int
[PS] C:\PFMigration>Get-PublicFolderDatabase -Server EX2007
Name
Server
----
------
Public Folder Database EX2007
Running the Batch PF Migration I get a different error:
[PS] C:\PFMigration>New-MigrationBatch -Name PFMigration -SourcePublicFolderDatabase (Get-PublicFolderDatabase -Server EX2007.EXDOM.int) -CSVData (Get-Content C:\PFMigration\FolderToMailbox.csv -Encoding Byte) -BadItemLimit $BadItemLimitCountA parameter cannot be found that matches parameter name 'SourcePublicFolderDatabase'.
+ CategoryInfo : InvalidArgument: (:) [New-MigrationBatch], ParameterBindingException
+ FullyQualifiedErrorId : NamedParameterNotFound,New-MigrationBatch
+ PSComputerName : EX2013.EXDOM.int
Other recent topics
