troubleshooting Question

Migrating public folders to exchange 2013

Avatar of micromark1
micromark1 asked on
ExchangeSBSWindows Server 2012
9 Comments1 Solution3598 ViewsLast Modified:
A little history first.  Last year we upgraded, (Migrated) from SBS 2003 to sbs 2011. All has went OK, but now we have outgrown our user limit and we are going to full fledged Exchange 2013, and a 2012 Domain controller.    I have a virtual environment setup now and I have got exchange 2013 installed and successfully moved some mailboxes over.  (not all of them).  Now I am practicing the Public Folder Migration.  Extremely important with this company as they get a lot of emails that go to public folders and they work out of them.  (Yes I know SharePoint would be better etc., but right now we cannot afford any downtime or different work flows.  It has to pretty much work the same for now).   Everything has went pretty well until now.  The mailboxes went fine and  I have gotten my information from 3 different sources so far.

http://technet.microsoft.com/en-us/library/jj150486(v=exchg.150).aspx
http://msexchangeguru.com/2013/04/18/exchange2013-public-folders/
and this was pretty helpful as well.

http://www.youtube.com/watch?v=ueODkbylNzY


My Problem is:  on step 5 of the first article.  It mentions that in exchange 2007 there are system public folders such as owa scratch pad etc that will make the migration fail, and to perform this.  
$PublicFolderDatabasesInOrg = @(Get-PublicFolderDatabase) $BadItemLimitCount = 5 + ($PublicFolderDatabasesInOrg.Count -1)

New-PublicFolderMigrationRequest -SourceDatabase (Get-PublicFolderDatabase -Server <Source server name>) -CSVData (Get-Content <Folder to mailbox map path> -Encoding Byte) -BadItemLimit $BadItemLimitCount

They have  a slightly different procedure if you are on exchange 2010 (which we are) but we also do have those legacy folders from the 2003 SBS migration.    
when I do the first command I get:

At line:1  char:59
+ $PublicFolderDatabasesInOrg  = @<Get-PublicFolderDatabase> $BadItemLimitCount =5
Unexpected Token '$BadItemLimitCount' in expression or statement.
Categrory Info     : ParserError:  <:> [], ParentContainsErrorRecordException
FullyQualifiedErrorId : UnexpectedToken


Not sure where to do from here and can't find anything on google etc.  Should I manually remove those legacy folders and then start over?  Not exactly sure that is why it is failing.
Join the community to see this answer!
Join our exclusive community to see this answer & millions of others.
Unlock 1 Answer and 9 Comments.
Join the Community
Learn from the best

Network and collaborate with thousands of CTOs, CISOs, and IT Pros rooting for you and your success.

Andrew Hancock - VMware vExpert
See if this solution works for you by signing up for a 7 day free trial.
Unlock 1 Answer and 9 Comments.
Try for 7 days

”The time we save is the biggest benefit of E-E to our team. What could take multiple guys 2 hours or more each to find is accessed in around 15 minutes on Experts Exchange.

-Mike Kapnisakis, Warner Bros