Exchange 2016 CU22 Failed & Broke Exchange

Gary Smith 121 Reputation points
2021-11-18T10:25:51.297+00:00

Hi
I recently tried installing CU22 for Exchange 2016. It failed and subsequently i couldn't get exchange online. I thus restored a backup from previous day. However it looks like the update changed attributes in AD as i'm getting the following error now in EAC:
150651-2021-11-18-10-17-27-chi-ex16-connected-dameware-mi.png

Whats the options going forward?
Thanks

Active Directory
Active Directory
A set of directory-based technologies included in Windows Server.
5,848 questions
Exchange Server Management
Exchange Server Management
Exchange Server: A family of Microsoft client/server messaging and collaboration software.Management: The act or process of organizing, handling, directing or controlling something.
7,346 questions
0 comments

3 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Gary Smith 121 Reputation points
    2021-11-19T10:10:40.5+00:00

    A re-run of the setup with /upgrade has fixed it. I also had to re-create the local certificate for OWA/EAC to work and re-run the HCW. All is well again.

    CU22 isnt very stable.

    1 person found this answer helpful.
  2. Yuki Sun-MSFT 40,856 Reputation points
    2021-11-19T02:01:45.023+00:00

    Hi @Gary Smith ，

    Does the error prompt when clicking the "Compliance Management" tab in the EAC? Is everything else in the EAC working fine?

    From the error message, it seems that it could be related to the Microsoft Exchange Discovery system mailbox "SystemMailbox{e0dc1c29-89c3-4034-b678-e6c29d823ed9}", so I'd recommend trying to recreate it and see if it works. See Re-create the Microsoft Exchange Discovery system mailbox.

    If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    0 comments
  3. Limitless Technology 39,351 Reputation points
    2021-12-16T17:15:06.107+00:00

    For someone stuck with this, I finally figured it out.

    First of all, what made this difficult was the list of accounts when running it on PS

    Get-ADUser -Filter * -Properties * | where {$. legacyExchangeDN -ne $null -and $. homeMDB -eq $null} | ft Name, legacyExchangeDN, homeMDB -AutoSize

    However, if you upload to a file or even remove anything that's hosted externally on the LegacyExchangeDN, you'll only be left with the stuff that's in place.

    Mine turned out to have some HealthMailboxes without homeMDBs, I have no idea how or why, but once Exchange was fixed it installed correctly.

    --If the answer is helpful, please vote positively and accept the answer--

    0 comments