Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 496
  • Last Modified:

Public Folder migration to Office365

We're migrating 8400+ folders and 300GB of public folder data to Office365

We've encountered 1482 failed and skipped elements - yes, we configured a bad item limit or Unlimited. Looks like large items - that is items larger than 49MB fails - not documented anywhere.
But still - the error we struggle with is the 1482 skipped elements - Skipped ITEM Folder ACL - reason CorruptFolderACL

O365 support says we - most likely - can look away from those errors. But hey - what if I'd need to reset permissions on 1482 folders - not likely.
And - going through PublicFolder permissions on EX2007 server I see that my migration user have all administrative permissions, and author for Client Permissions. Any unresolved SIDs (deleted users) are removed from ACL aswell ---

i say "what the heck"
O365 support says - "strange"
me again "what the heck"

Browsing the web I see some cases with this error - but never what the impact or solutions are.

and O365 said "perhaps you can try PST import on your 8402 public folders" - I haven't stopped laughing yet ...
0
Jakob Digranes
Asked:
Jakob Digranes
  • 3
1 Solution
 
Todd NelsonSystems EngineerCommented:
How are you currently migrating the public folders?  Sounds like you are attempting it using the native tools.

Have you looked into any of the third party migration tools like MigrationWiz, Binary Tree, etc?  https://oddytee.wordpress.com/2015/03/05/exchange-public-folder-migrations-with-migrationwiz/

Adding permissions is not a problem if you need to for each PF.

If you need to remove orphaned permissions for all PFs before the migration, run this command...

Get-PublicFolder -Identity "\" -Recurse -ResultSize Unlimited | Get-PublicFolderClientPermission | Where-Object { $_.User -like "NT User:S-1-*" } | ForEach { Remove-PublicFolderClientPermission -Identity $_.Identity -User $_.User -Access $_.AccessRights -Confirm:$false }

Open in new window

0
 
Jakob DigranesSenior ConsultantAuthor Commented:
thanks for getting back to

We'd prefer not to go for 3rd party tools, the native option should work OK. When doing a migration to EX2013 on-prem - we had no errors, but opted for going straight to the cloud.
I've exported all permissions, will be able to re-apply after migration

I've removed all orhpaned permissions
0
 
Ajit SinghCommented:
Please have a look at this similar thread i.e. Public Folder migration corrupt folder ACL, having suggested solutions might helps you.

Hope this helps!
0
 
Jakob DigranesSenior ConsultantAuthor Commented:
okay ---- ran through the migration. The CorruptFolderACL must have been just a scare. No problems after migrations ....
But migrating to O365 took forever !

thanks all-

btw, the other question in another forum is my question ;-)
0
 
Jakob DigranesSenior ConsultantAuthor Commented:
solved myself
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now