Ask a question


How can we help you today?

Ask Question
Manage notifications
Subscribe to this question
User

Public Folder Migration Failed

Hi Mariëtte,

It's me again, your problem child. :-) 

Today I followed the instructions to migrate public folders. At first everything went as expected; the only thing I was not sure about was how to verify whether the number of public folders was correct. (The script found 58 public folders, and the number of public folders users can see in Outlook is definitely fewer than that.) I assumed that the public folder count must have included some system, hidden public folders. Since every other step in your guide ran as expected, I proceeded.

I started the migration batch and waited for the result. Eventually I got the result: synced with errors, and failed. I've attached two screenshots and the downloaded report for that user. 

It seems that some things may have synced successfully, so I'm not sure what state things are in now and how to recover properly from this.

Thanks,

Bryan

 

Attached Files
asked12/23/2019 17:25
51 views
Add Comment
Last Activity 12/24/2019 12:42

1 Answer(s)

  • Mariette Knap

    Bryan,

    You need to roll back. This means that you do the steps backwards so that you can use Exchange manager on the old SBS to rename the offending PF's. Let me know if you need assistance with this?

    answered 12/23/2019 17:36
    Add Comment
    User

    Hi Mariëtte,

    Well, I didn't see your reply until now. I believe I've moved past the problem.

    I had 3 mail-enabled public folders with inconsistencies/invalid data. Some had invalid aliases, while others had a Guid issue. I found solutions and fixed the problems until the command: 

    C:\Windows\system32>Get-MailPublicfolder -ResultSize Unlimited | Measure-Object

    ...came back clean with no errors. 

    Then I refreshed (or resumed or restarted - I can't remember the word they used now) the migration batch, and quite quickly it reached the state of "Synced".

    So I believe I'm okay to proceed now. Would you agree? 

    Also, I'm concerned that if I have to restart the Microsoft Exchange Information Store to complete the job, it will disconnect my users, so I should wait until a maintenance window to do this. I think if I proceed by running the command:

    Set-OrganizationConfig -PublicFoldersLockedForMigration:$true

    that will lock users out of being able to access the Public Folders, and IF I then get the error that requires me to restart the MS Exchange Information Store, I will have to wait until after hours to fix the problem, and public folders will be unavailable to all users until then.

    Do I understand that correctly?

    Bryan

    Reply
    replied 12/23/2019 18:20
Add an Answer