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...pressionSyncJob:PSInvokeExpressionSyncJob) [], PSRe
   motingTransportException
    + FullyQualifiedErrorId : JobFailure

Invoke-Command : Cannot write input as there are no more running pipelines
At C:\Users\exch13\AppData\Roaming\Microsoft\Exchange\RemotePowerShell\mail.xxxxxxxx.local\mail.xxxxxxxx.local.ps
m1:15587 char:29
+             $scriptCmd = { & <<<<  $script:InvokeCommand `
    + CategoryInfo          : InvalidOperation: (:) [Invoke-Command], PSInvalidOperationException
    + FullyQualifiedErrorId : NoMoreInputWrite,Microsoft.PowerShell.Commands.InvokeCommandCommand
LVL 5
MarinertekAsked:
Who is Participating?
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.

MASEE Solution Guide - Technical Dept HeadCommented:
E ATech LeadCommented:
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.
Jakob DigranesSenior advisorCommented:
ah .... beauty of Public Folders ...

you could do the easy way - i guess -
get-mailpublicfolder - then you get an overview how many fails for you. Had a customer with 300GB and and 10s of 1000s of public folders.

however, they had "only" 50 - 60 PFs with failed alias. Enter ADSI - fix

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
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
Exchange

From novice to tech pro — start learning today.