Removing Public Folders in Exchange 2016 Hybrid
We have Public Folders, and Public Folder Mailboxes in Exchange 2016 Hybrid. All users' mailboxes have been migrated to Exchange Online. We want to discontinue, remove / Delete Public Folders in Exchange, don't want to migrate onto Exchange online. What is the best practice to delete Public Folders in Exchange 2016? Any guidelines to check Public Folders usage, backup, removing without business interruption much appreciated. Thanks in advance
Cross forest Distribution Group list expansion
We have two forests in a 2-way trust. On each forest there's an Exchange 2016 Organization installed. On one forest a Distribution group has been created with users from both the forests, in ADUC we see the membership correctly for all the users. On the Exchange Console of that Forest opening the DG we can see only the "local" users and the SID for the remote one. Sending an email to the DG it only delivers to local forest's users. Why Exchange Server doesn't expand the DG membership as the ADUC does and deliver emails to all recipient ? Do we have to replicate remote Forest's Users as local contacts ? thanks
Questions for Exchange 2016 to EXO
Hi, I have a few questions regarding a migration/transition to Exchange Online. I'm new to this environment but we are currently running Exchange 2016 and will deploy Exchange 2019 during the summer and then upgrade to Exchange SE during the fall. I know 2016/2019 will be unsupported in Oct. We recently got the thumbs up for moving to Exchange Online for the majority of mailboxes but we will keep a few on-premises servers to host some mailboxes as well as acting as a mail-relay for a few servers/systems. Im throwing a few questions I have here while I'm trying to search and read the articles online: Questions/comments: We have the sync to Entra ID up and running so that part seems OK We will run the HCW and establish a hybrid between the current Exchange 2016 environment and Exchange Online. MX shall still be pointing towards on-prem. When Exchange 2019/SE is deployed we will run the HCW again to link the new servers. Do I need to run the HCW while on Exchange 2019 and then again after the servers are upgraded to Exchange SE? Or are they concidered the same servers and this is like a CU? In terms of mailboxmigrations and DNS entries like mail.company.com and autodiscover.company.com. How can we plan and manage so its seamless for the users? Shall we keep mail and autodiscover for internal lookups pointed to the current on-premises environment (via hardware load balancer) and add the external ones pointing towards EXO? If internal clients still on Exchange 2016 starts Outlook they will still use internal DNS and connect to the Exchange 2016 environment? If external clients starts Outlook they will connect to Exchange Online and proxied back to its mailbox on-prem? (if they are not yet migrated) If a mailbox is moved, internal outlook clients will be proxied to Exchange Online? If a mailbox is moved, external outlook clients will stop the proxy and connect directly to the mailbox in Exchange Online? After a mailbox migration, will the enduser see the "Please restart Outlook notification?" Are mailboxes still on-prem able to connect to a shared mailbox hosted online? Are mailboxes online able to connect to shared mailboxes hosted on-prem? Thanks for your help and hope the answers bring some clarity so we can start planning for the migration strategy.
Problem with mailbox migration form Exchange online to Exchange On-Prem
During the mailbox migration process between Exchange Online to Exchange On-Prem, the following error occurs: Write-ErrorMessage : || At C:\Users\s***.p***\AppData\Local\Temp\tmpEXO_kahlyk0j.2eq\tmpEXO_kahlyk0j.2eq.psm1:1189 char:13 + Write-ErrorMessage $ErrorObject + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : NotSpecified: (:) [New-MoveRequest], MRSRemotePermanentException + FullyQualifiedErrorId : [Server=VI1P195MB******,RequestId=14ff539b-f726-de45-6d8f-d0380df2d970,TimeStamp=Wed, 04 Jun 2025 08:38:19 GMT],Write-ErrorMessage
Pointing MX and Autodiscover to 365
We recently migrated to Exchange Online via Exchange Hybrid. MX and Autodiscover are still pointed to on-prem environment as we have room booking mailboxes and resource mailboxes located on-prem. Is it ok to Cut-over MX and AutoDiscover to Exchange Online now? What implications would it have on Room booking for cloud users and devices configured to use these mailboxes? Much appreciate your ideas.Exchange Mailbox Migration Errors - Corrupted items
Howdy Folks! I'm getting a lot of errors in one of the last mailboxes we're migrating to 365 from Exchange 2019 Hybrid. Has anyone managed to remediate these type of errors? I've remediated abandoned users from permissions but nothing has worked. The errors still popping up even after creating a new batch. Subject Kind Scoring Classification Folder Name FolderACL CorruptFolderACL FolderACL, SourcePrincipalError Tasks FolderACL CorruptFolderACL FolderACL, SourcePrincipalError Tasks FolderACL CorruptFolderACL FolderACL, SourcePrincipalError Notes FolderACL CorruptFolderACL FolderACL, SourcePrincipalError Notes FolderACL CorruptFolderACL Inbox, FolderACL, SourcePrincipalError Inbox FolderACL CorruptFolderACL Inbox, FolderACL, SourcePrincipalError Inbox FolderACL CorruptFolderACL FolderACL, SourcePrincipalError Investments FolderACL CorruptFolderACL FolderACL, SourcePrincipalError Investments FolderACL CorruptFolderACL FolderACL, SourcePrincipalError Health FolderACL CorruptFolderACL FolderACL, SourcePrincipalError Health FolderACL CorruptFolderACL FolderACL, SourcePrincipalError Eleanor FolderACL CorruptFolderACL FolderACL, SourcePrincipalError Eleanor FolderACL CorruptFolderACL FolderACL, SourcePrincipalError Clover FolderACL CorruptFolderACL FolderACL, SourcePrincipalError Clover FolderACL CorruptFolderACL FolderACL, SourcePrincipalError ACL ASIC FolderACL CorruptFolderACL FolderACL, SourcePrincipalError ACL ASIC FolderACL CorruptFolderACL FolderACL, SourcePrincipalError __Pre 2011 FolderACL CorruptFolderACL FolderACL, SourcePrincipalError __Pre 2011 FolderACL CorruptFolderACL FolderACL, TargetPrincipalError __Pre 2011 FolderACL CorruptFolderACL FolderACL, SourcePrincipalError __2011-2012 FolderACL CorruptFolderACL FolderACL, SourcePrincipalError __2011-2012 FolderACL CorruptFolderACL FolderACL, TargetPrincipalError __2011-2012 FolderACL CorruptFolderACL FolderACL, SourcePrincipalError Contacts FolderACL CorruptFolderACL FolderACL, SourcePrincipalError Contacts FolderACL CorruptFolderACL FolderACL, SourcePrincipalError Recipient Cache FolderACL CorruptFolderACL FolderACL, SourcePrincipalError Recipient Cache FolderACL CorruptFolderACL FolderACL, SourcePrincipalError Recipient Cache FolderACL CorruptFolderACL FolderACL, SourcePrincipalError Recipient Cache FolderACL CorruptFolderACL FolderACL, SourcePrincipalError PeopleCentricConversation Buddies FolderACL CorruptFolderACL FolderACL, SourcePrincipalError PeopleCentricConversation Buddies FolderACL CorruptFolderACL FolderACL, SourcePrincipalError PeopleCentricConversation Buddies FolderACL CorruptFolderACL FolderACL, SourcePrincipalError PeopleCentricConversation Buddies FolderACL CorruptFolderACL FolderACL, SourcePrincipalError Organizational Contacts FolderACL CorruptFolderACL FolderACL, SourcePrincipalError Organizational Contacts FolderACL CorruptFolderACL FolderACL, SourcePrincipalError Organizational Contacts FolderACL CorruptFolderACL FolderACL, SourcePrincipalError Organizational Contacts FolderACL CorruptFolderACL FolderACL, SourcePrincipalError GAL Contacts FolderACL CorruptFolderACL FolderACL, SourcePrincipalError GAL Contacts FolderACL CorruptFolderACL FolderACL, SourcePrincipalError GAL Contacts FolderACL CorruptFolderACL FolderACL, SourcePrincipalError GAL Contacts FolderACL CorruptFolderACL FolderACL, SourcePrincipalError Companies FolderACL CorruptFolderACL FolderACL, SourcePrincipalError Companies FolderACL CorruptFolderACL FolderACL, SourcePrincipalError Companies FolderACL CorruptFolderACL FolderACL, SourcePrincipalError Companies FolderACL CorruptFolderACL FolderACL, SourcePrincipalError {A9E2BC46-B3A0-4243-B315-60D991004455} FolderACL CorruptFolderACL FolderACL, SourcePrincipalError {A9E2BC46-B3A0-4243-B315-60D991004455} FolderACL CorruptFolderACL FolderACL, SourcePrincipalError {06967759-274D-40B2-A3EB-D7F9E73727D7} FolderACL CorruptFolderACL FolderACL, SourcePrincipalError {06967759-274D-40B2-A3EB-D7F9E73727D7} FolderACL CorruptFolderACL FolderACL, SourcePrincipalError Calendar FolderACL CorruptFolderACL FolderACL, SourcePrincipalError Calendar FolderACL CorruptFolderACL FolderACL, SourcePrincipalError Calendar FolderACL CorruptFolderACL FolderACL, SourcePrincipalError Calendar FolderACL CorruptFolderACL FolderACL, SourcePrincipalError Calendar FolderACL CorruptFolderACL FolderACL, SourcePrincipalError Calendar FolderFreeBusyACL CorruptFolderACL FolderACL, SourcePrincipalError Calendar FolderFreeBusyACL CorruptFolderACL FolderACL, SourcePrincipalError Calendar FolderFreeBusyACL CorruptFolderACL FolderACL, SourcePrincipalError Calendar FolderFreeBusyACL CorruptFolderACL FolderACL, SourcePrincipalError Calendar FolderFreeBusyACL CorruptFolderACL FolderACL, SourcePrincipalError Calendar FolderFreeBusyACL CorruptFolderACL FolderACL, SourcePrincipalError Calendar FolderFreeBusyACL CorruptFolderACL FolderACL, SourcePrincipalError Calendar FolderACL CorruptFolderACL FolderACL, SourcePrincipalError Calendar_JFK3F8.ics FolderACL CorruptFolderACL FolderACL, SourcePrincipalError Calendar_JFK3F8.ics FolderACL CorruptFolderACL FolderACL, SourcePrincipalError Calendar_JFK3F8.ics FolderACL CorruptFolderACL FolderACL, SourcePrincipalError Calendar_JFK3F8.ics FolderACL CorruptFolderACL FolderACL, SourcePrincipalError Calendar_JFK3F8.ics FolderACL CorruptFolderACL FolderACL, SourcePrincipalError Calendar_JFK3F8.ics FolderACL CorruptFolderACL FolderACL, SourcePrincipalError Calendar_JFK3F8.ics FolderACL CorruptFolderACL FolderACL, SourcePrincipalError Calendar_JFK3F8.ics FolderACL CorruptFolderACL FolderACL, SourcePrincipalError Calendar_JFK3F8.ics FolderACL CorruptFolderACL FolderACL, TargetPrincipalError Calendar_JFK3F8.ics FolderACL CorruptFolderACL FolderACL, SourcePrincipalError Freebusy Data Model walkthrough with NT CorruptItem Calendar, Item, StartMustExistCalendarCorruption CalendarExchange 2019 Mailbox Migration Error - Folder conflicts with Exchange Online folder
Hi Exchange Experts, I'm migrating a small Exchange 2019 environment to 365. Been pulling my hair out becuase of just one mailbox giving this error Error description --------------------------- Error: AggregateMailboxFolderConflictPermanentException: The folder 'Files' conflicts with Exchange Online folder 'Files', please move the messages to another folder and restart the job. Data migrated: 0 B (0 bytes) Migration rate: -------------------------------------- Migration user report: 5/14/2025 12:32:05 PM [MEUP300MB0105] Request processing continued, stage CreatingFolderHierarchy. 5/14/2025 12:32:05 PM [MEUP300MB0105] Stage: CreatingFolderHierarchy. Percent complete: 10. 5/14/2025 12:32:12 PM [MEUP300MB0105] Stage: CreatingFolderHierarchy. Percent complete: 10. 5/14/2025 12:32:12 PM [MEUP300MB0105] Fatal error AggregateMailboxFolderConflictPermanentException has occurred. ---------------------- It seems to be a system folder and I've tried to remove files from it (although there're no files in it) using MFCMAPI tool with no success. Renamed the folder and tried to re-run the migration with no luck. Has anyone experience this issue? any thoughts or tips are much appreciated ! Thank you.Exchange 2016 CU23 breaks Outlook 2010 connection
Hello, I have an environment with an Exchange 2016 CU22, that connects to a public folders in legacy, which resides on an Exchange 2010. We have many users still using Outlook 2010 and all is working fine. Yesterday we decided, to my great regrets, to install CU23 and a nightmare began, Outlook 2010, on the first start since CU23, connects no issue, but if we close Outlook then reopen it, no more connections, it just shows disconnected and if I look deeper, I see it just keeps retrying but Exchange refuses it to connect. I looked everywhere in the CU23 documentation for changes and nowhere there is mention about Outlook versions and legacy connections being affected by it! Anything I can do to get Outlook 2010 going again? What happened on the first connection, what did Exchange tell Outlook to reconfigure? Newer Outlook works fine. All Outlooks connect with RPC because of the legacy public folders.
