Public Folder
4 TopicsHow to repair a corrupted Public Folder (on-prem)
Hello guys, Hope all is well. In our Exchange 2019 environment we use Public Folders extensively. Everything seems ok except one of folders that looks corrupted. I can execute commands Get-PublicFolder / Set-PublicFolder against it, I can get its items statistics (Get-PublicFolderItemStatistics) and have access to items through Outlook. But commands Get-PublicFolderStatistics, Get-PublicFolderClientPermission return the same error: The security principal specified is already on the permission set. + CategoryInfo : NotSpecified: (:) [Get-PublicFolderStatistics], CorruptDataException + FullyQualifiedErrorId : [Server=E7,RequestId=b2f89187-878f-4cab-b05f-fcdaa7d82c0d,TimeStamp=2/17/2025 3:19:42 PM] [FailureCategory=Cmdlet-CorruptDataException] B960021F,Microsoft.Exchange.Manag ement.MapiTasks.GetPublicFolderStatistics I tried to repair the corresponding public folder mailbox (New-MailboxRepairRequest) but none of my requests found errors. I moved the public folder content to a different public folder mailbox, no success. Any ideas how to fix the issue? My guess is that ACL list of the public folder is corrupted. Regards, Dmitry Horushin14Views0likes0CommentsPublic Folder Migration Failed
We have a problem migrating public folders from an Exchange 2019 OnPremise to an Exchange Online. We followed the Microsoft guide: Batch migrate Exchange Server public folders to Microsoft 365 or Office 365 | Microsoft Learn We get to step 7. When completing the PublicFolderMigration job, the status changes to “Completing” and then to “Failed”. The error message in the EXO Shell is: Status: Failed Message: Error calling “net.tcp://be1p281mb2001.deup281.prod.outlook.com:9821/Microsoft.Exchange.MailboxReplicationService BE1P281MB2001.DEUP281.PROD.OUTLOOK.COM (15.20.8207.17 ServerCaps:FFFFFFFF, ProxyCaps:1FFFFFFFFFFFFFFFC7DD2DFDBF5FFFFFCB07EFFF, MailboxCaps:, legacyCaps:FFFFFFFF)”. Error details: The communication object System.ServiceModel.Channels.ServiceChannel cannot be used for communication because it is in a Faulted state. --> The communication object System.ServiceModel.Channels.ServiceChannel cannot be used for communication because it is in a Faulted state. Does anyone have an idea what this error means? We have already removed and restarted the entire migration, but the same error occurs again.121Views0likes2CommentsUnable to export all public folder permissions to .CSV
Hello, I've been trying to export a list of every single public folder user's permission to a csv file. Its successful when I use : get-publicfolder -recurse | get-publicfolderclientpermissions | export-csv XXX , however it does only return about 10000 entries. If I add resultsize -unlimited to the above script it returns nothing - the csv file is completely blank. Any ideas? I also need to get a list of permissions to all public folders for a single user ( we've about 1000 of them in our env and user would like to know to which folders he has an access to). In addition it does return the below error now:1.4KViews0likes3CommentsRedirect mail to a shared mailbox subfolder
Hi, I want to ask if it is possible to automatically move new mails for a shared mailbox to a subfolder within that same mailbox, e.g. shared mailbox abc@dot.com gets a mail from def@sff.com than this mail is placed in the inbox subfolder "def" and another mail from ght@egd.com is placed in the inbox subfolder "ght"? I'm planning to hybrid migrate an exchange 2010 public folder environment to exchange online shared mailboxes but customer wants to have only a few shared mailboxes compared to the count of public folders. Besides is it even possible to migrate public folders to shared mailboxes with a hybrid deployment and native tools? Sry for the double question. Kind RegardsSolved8.8KViews1like6Comments