Updating Exchange Server Hybrid for CU13 - CU22

TryingHard 26 Reputation points
2021-11-16T07:08:11.103+00:00

I'm looking to update my Exchange Hybrid servers from CU13 to CU22 with the latest security patches.

First I'll give the environment so the you can better understand the problem. I have two Hybrid Exchange servers in different sites (Site1 and Site2) but the same domain / forest (domain.lcl). These Exchange servers both connect to our O365 Tenant. There are DCs in both sites.

Site 1 - has a Exchange Server and 3 DC's . The schema is in this site. Servers are all 2016 DataCentre.
Site 2 - has a Exchange Server and 1 DC. Servers are all 2016 DataCentre.

I intended to install the prereqs - .Net 4.8 and IIS URL Rewrite.

I'm attempting to update the exchange server at Site 2 first as a test. This is what I have used so far to not avail.

  1. setup.exe /PrepareSchema /IAcceptExchangeServerLicenseTerms_DiagnosticDataON
  2. setup.exe /m:upgrade /IAcceptExchangeServerLicenseTerms_DiagnosticDataON

These fail for a number of reasons.

  • [ERROR] Setup encountered a problem while validating the state of Active Directory: Exchange organization-level objects have not been created, and setup cannot create them because the local computer is not in the same domain and site as the schema master. Run setup with the /prepareAD parameter on a computer in the domain domain.lcl and site Site 1, and wait for replication to complete. See the Exchange setup log for more information on this error.

How can I get the Schema updated in the current environment? Can I update the Schema directly using the files that the setup copies?

Any help would be greatly appreciated.

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,349 questions
Microsoft Exchange Hybrid Management
Microsoft Exchange Hybrid Management
Microsoft Exchange: Microsoft messaging and collaboration software.Hybrid Management: Organizing, handling, directing or controlling hybrid deployments.
1,886 questions

4 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Andy David - MVP 141.6K Reputation points MVP
    2021-11-16T12:36:17.217+00:00

    You need to run
    setup.exe /PrepareSchema /IAcceptExchangeServerLicenseTerms_DiagnosticDataON

    in the site that has the schema with the correct perms - then follow up with the other two steps

    https://learn.microsoft.com/en-us/exchange/plan-and-deploy/prepare-ad-and-domains?view=exchserver-2019 

    Setup.exe /IAcceptExchangeServerLicenseTerms_DiagnosticDataON /PrepareAD   
Setup.exe /IAcceptExchangeServerLicenseTerms_DiagnosticDataON /PrepareAllDomains

    Its not supported to update the schema directly with the files, you must run setup.

    0 comments
  2. TryingHard 26 Reputation points
    2021-11-16T22:03:03.16+00:00

    Can I assume that only new Schema classes are added and no changes made to existing data?

  3. TryingHard 26 Reputation points
    2021-11-17T23:27:11.127+00:00

    Had problem with running PrepareSchema on the DC.

    There was an error while running 'ldifde.exe' to import the schema file 'c:\Windows\Temp\ExchangeStup\Setup\Data\PostExchange2003_schema0.ldf'. The error cod is: 8224.

    I didn't expect that the setup would attempt to import that schema as I am currently running Exchange so would that schema already be in AD. Am I missing something?

    0 comments
  4. TryingHard 26 Reputation points
    2021-11-18T03:23:50.32+00:00

    Thanks AndyDavid.
    I have now successfully run the /PrepareSchema.

    As I am install the Exchange CU22 for my Hybrid environment I don't believe that the /PrepareAD or / PrepareAllDomains need to be run.

    All I should need is...

    • Save any configuration files as these are over-ridden by the install. eg web.config or EdgeTransport.exe.config
    • SETUP.EXEC /IAcceptExchangeServerLicenseTerms_DiagnosticDataON /TenantOrganizationConfig MyTenantOrganizationConfig.XML Does this appear correct to you?