Marinertek
asked on
Exchange 2010 to 2013 public folder migration
I am having issues in a large organization with public folder migration. The issue is that they fail to migrate because of spaces in the "mailnickname" attribute. There are over 5000 folders total so manually removing all the spaces in the names is out of the question. I attempted to use a script to enumerate all of the issues to replace the invalid characters and it fails because of the output is too large. Anyone have some other method to manage the "mailnickname"?
[PS] C:\PFmigration>$pfs= Get-publicfolder "\" -recurse | where {$_.MailEnabled -eq "True"} | Get-MailPublicFolder | whe
re {$_.alias -like `* *' -or $_.alias -like `*,*'}
Sending data to a remote command failed with the following error message: The WinRM client sent a request to the remote
WS-Management service and got a response saying the request was too large. For more information, see the about_Remote_
Troubleshooting Help topic.
+ CategoryInfo : OperationStopped: (System.Manageme...pressio nSyncJob:P SInvokeExp ressionSyn cJob) [], PSRe
motingTransportException
+ FullyQualifiedErrorId : JobFailure
Invoke-Command : Cannot write input as there are no more running pipelines
At C:\Users\exch13\AppData\Ro aming\Micr osoft\Exch ange\Remot ePowerShel l\mail.xxx xxxxx.loca l\mail.xxx xxxxx.loca l.ps
m1:15587 char:29
+ $scriptCmd = { & <<<< $script:InvokeCommand `
+ CategoryInfo : InvalidOperation: (:) [Invoke-Command], PSInvalidOperationExceptio n
+ FullyQualifiedErrorId : NoMoreInputWrite,Microsoft .PowerShel l.Commands .InvokeCom mandComman d
[PS] C:\PFmigration>$pfs= Get-publicfolder "\" -recurse | where {$_.MailEnabled -eq "True"} | Get-MailPublicFolder | whe
re {$_.alias -like `* *' -or $_.alias -like `*,*'}
Sending data to a remote command failed with the following error message: The WinRM client sent a request to the remote
WS-Management service and got a response saying the request was too large. For more information, see the about_Remote_
Troubleshooting Help topic.
+ CategoryInfo : OperationStopped: (System.Manageme...pressio
motingTransportException
+ FullyQualifiedErrorId : JobFailure
Invoke-Command : Cannot write input as there are no more running pipelines
At C:\Users\exch13\AppData\Ro
m1:15587 char:29
+ $scriptCmd = { & <<<< $script:InvokeCommand `
+ CategoryInfo : InvalidOperation: (:) [Invoke-Command], PSInvalidOperationExceptio
+ FullyQualifiedErrorId : NoMoreInputWrite,Microsoft
Public Folders Migration from Exchange 2007/2010 to Exchange 2013:
http://msexchangeguru.com/2013/04/18/exchange2013-public-folders/
Step-by-Step Guide to Move Public Folders to Exchange 2013:
You may get help from this earlier thread.
http://msexchangeguru.com/2013/04/18/exchange2013-public-folders/
Step-by-Step Guide to Move Public Folders to Exchange 2013:
You may get help from this earlier thread.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
http://exchangeserverpro.com/exchange-server-2010-2013-migration-moving-public-folders/