–Public folders are a hidden gem of Exchange Server and provided a way of co-working when today’s solutions were still a thing of the future. Even with on-premises modern public folders, you might encounter situations where you have to perform tasks maintaining and preparing for public folder migration to Exchange Online or for moving public folder mailboxes to Exchange Server 2019.
You are hopefully familiar with the new Exchange Emergency Mitigation Service (EEMS) for Exchange Server 2016 and 2019. That is a new service providing automated emergency configuration of your Exchange servers by Microsoft in the case a security risk has been identified. This post covers specific issues where EEMS does not work as expected.
When you prepare your on-premises public folder hierarchy ACLs for migration to Exchange Online or for moving from Exchange Server 2016 to 2019 you might see the following error:
Multiple objects with legacy DN ADCDisabledMail were found.
When you move mailboxes using migration batches you might encounter a situation that your batch contains migration users that fail during batch execution.
These are the results of the Exchange Server Questionnaire from August 2021.
How to solve issues with MSExchangeApplicationLogic event id 3018.
You might face a situation during an Exchange Server migration where your Exchange Server 2019 mailbox users are not able to open their public folder favorites when using Outlook on the Web (OWA).
The solution is pretty easy.
The Exchange Product Group announced Exchange Server vNEXT for fall 2021. angekündigt. We are all very excited to see what the new version has to offer.
But what is the current situation in on-premises Exchange organizations? I have put a short questionnaire online for gathering information from you.
When you create or update an Exchange hybrid configuration using the Hybrid Configuration Wizard magic things happen. That’s why it is called a Wizard.
One essential step of the Hybrid Configuration Wizard (HCW) is the configuration of the hybrid mail-flow. The hybrid mail-flow is required for both, classic and modern Exchange hybrid.
Recently I had to support the uninstall of Exchange Server 2016 CU10 on a Windows Server 2019 system. That this setup is not supported is a different topic. In this case, a new Exchange Server 2016 system was placed in service, and the old system needed to be removed from the on-premises Exchange organization.
But uninstalling the Exchange Server failed.