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.
and this was pretty helpful as well.
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.
g = @(Get-PublicFolderDatabase
) $BadItemLimitCount = 5 + ($PublicFolderDatabasesInO
equest -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
g = @<Get-PublicFolderDatabase
> $BadItemLimitCount =5
Unexpected Token '$BadItemLimitCount' in expression or statement.
Categrory Info : ParserError: <:> , ParentContainsErrorRecordE
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.