Released: September 2021 Quarterly Exchange Updates

Published Sep 28 2021 08:01 AM 40.9K Views

Today we are announcing the availability of quarterly Cumulative Updates (CUs) for Exchange Server 2016 and Exchange Server 2019. These CUs include fixes for customer reported issues, all previously released security updates, and a new security feature.

A full list of fixes is contained in the KB article for each CU, but we wanted to highlight a few changes.

Microsoft Exchange Emergency Mitigation Service

As mentioned in our recent blog post, September 2021 CUs (and later) include the new Microsoft Exchange Emergency Mitigation service. Please familiarize yourself with the new service as it is a new security feature that will be installed on all Exchange Servers (except Edge servers).

Cumulative Update Setup Changes

We wanted to call out two setup changes starting with September 2021 CUs (more information in the Emergency Mitigation Service blog post):

  • We changed the unattended setup switch. The previous /IAcceptExchangeServerLicenseTerms switch will not work starting with the September 2021 CUs. You now must use either /IAcceptExchangeServerLicenseTerms_DiagnosticDataON or /IAcceptExchangeServerLicenseTerms_DiagnosticDataOFF for unattended and scripted installs.
  • The IIS URL Rewrite module is now a prerequisite for Exchange Server installation. This must be installed separately and is not installed as part of Exchange Setup (you need the x64 MSI version).

Release Details

The KB articles that describe the fixes in each release and product downloads are as follows:

Known issues with this release

Due to several changes released in security updates since the last CU release, we wanted you to be aware of the following issues that might impact customers who did not already install recent security updates:

  • Before the update, you should check your Exchange Server authorization certificate. Please see this KB article for more information.
  • If your organization uses Load Balancing, please see this KB article for more information on how to update.

Additional Information

Microsoft recommends all customers test the deployment of any update in their lab environment to determine the proper installation process for your production environment.

These updates do not contain schema changes. If coming from older updates, you can find more information on preparing Active Directory here. Schema changes can be tracked here. For best practices for successful installation, please see this document.

If updating from an older version of the CU, please see the Exchange Update Wizard for detailed steps to follow.

Also, to prevent installation issues you should ensure that the Windows PowerShell Script Execution Policy is set to Unrestricted on the server being upgraded or installed. To verify the policy settings, run the Get-ExecutionPolicy cmdlet from PowerShell on the machine being upgraded. If the policies are NOT set to Unrestricted you should use these resolution steps to adjust the settings.

If you plan to install the update with the unattended install option using either PowerShell or a command prompt, make sure you specify either the full path to the setup.exe file or use a “.” in front of the command if you are running it directly from the folder containing the update. If you do not, Exchange Setup may indicate that it completed successfully when it did not. Read more here.

Note: Customers in Exchange hybrid deployments and those using Exchange Online Archiving with an on-premises Exchange deployment are required to deploy a supported CU for the product version in use.

For the latest information on the Exchange Server and product announcements please see What's New in Exchange Server and Exchange Server Release Notes.

Note: Documentation may not be fully available at the time this post is published.

The Exchange Server team

65 Comments
New Contributor

Hi Exchange team,

I guess, for the IIS URL Rewrite module, we just need the regular 'x64' msi installer, not the  Web Platform Installer (WebPI) Regards Stephen

Microsoft

@sjhudson Correct, x64 MSI version. I added that to the bullet. Thanks!

Senior Member

4. "IMPORTANT: You must install the CU from an elevated command prompt. If the CU installation is being started from PowerShell, ensure the full path to setup.exe is provided"

I normally Run As Admin the setup.exe in the mounted ISO(after a fresh reboot).     this sentence makes me think I should NOT do this?  I like using the GUI, it's worked in the past just fine.   I know I'll need the URL rewrite msi and I think I'll have a schema update coming from CU19, but the gui walks me through that.   and since I don't have a DAG I think I don't need to enter maintenance mode.   thanks!

Microsoft

@jordanl17 You are good and you can continue doing what works for you; CU setup is more advanced than the SU (security update) setup so either will work. The truth is that due to the fact that the SU setup is something that actually requires elevated CMD line, we have just gone to suggest to do the same thing (elevated) all the time. But CU setup will check for permissions and prompt for elevation if required.

Regular Visitor

We are running CU20 with Jul21SU... - does this mean, we must install CU21 first to get CU22 - or is it possible to go directly from CU20/Jul21SU to CU22?

Microsoft

@Duncan1528 You are go directly from CU20+(any SU) to CU22, yes. You will need to install IIS URL rewrite before you do that, though.

EDIT: you can always check https://aka.ms/exchangeupdatewizard for all of the steps!

Occasional Visitor

KB2999226 is listed as a prerequisite for EM and therefore this CU. That KB only applies to Server 2012 R2 and lower. Is there a modern KB available for Server 2016/2019 available that we should be installing?

Microsoft

@NHawk257 That's... well, that is a little awkward. This update is quite old and I do not expect it to be an issue on say an Exchange 2019 server (which does not even run on 2012 R2). Bottom line is - if WU says your server is up to date, you are OK. I would hope that even on Exchange 2016 servers, this KB would be installed everywhere by now... but thinking about this as a reference in the KB; especially for E2019 CU, it does not make much sense, does it...

The KB articles in the Known issues point to the same URL. Can you verify the one for Load balancing? thanks

Microsoft

@Ricardo Costa da Silva That is correct; both issues are covered in the same KB; there is Cause 1 and Cause 2, with their own resolutions.

Occasional Visitor

The Deployment instructions for Exchange 2016 CU in the Exchange Update Wizard when going from CU21 to CU22 says to "Install the latest applicable security update (SU) as listed in Exchange Server build numbers and release dates." I notice that "Exchange Server 2016 CU21 Jul21SU" is listed under CU22 on the build page. If I have already installed that SU while at CU21, do I need to install it again after installing CU22?

Senior Member

We are running Exchange 2016 CU21 in Windows 2012 server and I am planning to apply CU22 to our server. Please advice whether I have to install following pre request before apply CU22. Thanks

 

Microsoft

@RadHaz75 No; the reason why it says this is because it cannot know when you would be installing the CU; immediately after release or say... 2 months down the road (when there might be SUs for that CU). All of the SUs are CU specific. There are no SUs for latest set of CUs (released yesterday). That might change in the future but right now - there is nothing newer than the CU. We talk about this stuff here.

@vigna840 IIS Rewrite Module is a hard requirement, yes. You will be blocked from installation if you do not install that first. On the C Runtime - if your server is up to date on it's WU updates, then you should be good with this.

Occasional Visitor

@Nino Bilic Thanks. That's what I thought. Can you explain why the Jul21SU is listed under CU22 the same way it is listed under CU21 here https://docs.microsoft.com/en-us/Exchange/new-features/build-numbers-and-release-dates?view=exchserv... Is this just a mistake?

Microsoft

@RadHaz75 The article does not show Jul21SU "under" CU11... if you look at all of the updates on the page, they are actually listed chronologically from oldest to newest. So there is a 2019 CU9, then all the SUs on top of that going "upward". Then 2019 CU10 and it's SU (released on Jul 13). Then there is CU11. The SU for CU11 (when released) will come on the top of the list and will be indented a bit to show that it is an SU vs. the CU which start at the start of each row.

I do agree this can be misinterpreted unless you realize the context of the list. Hmm. Thinking of how this could be presented clearer perhaps...

Frequent Visitor

For 2019 CU10 without the SU installed...do we need to apply that first prior to going to CU11?  Also no schema changes right so need to run the commands for that correct?  What about being in a hybrid mode?  Do we need to include the command line switches when installing?  Thanks!

Occasional Visitor

@Nino Bilic I think I see what you're saying. The fact that the SU is indented under CU21 implies to me it's like a subpart of that, like required after, hence my confusion there.

Microsoft

@Russo1485 No you do not need to install any SUs before going to next CU. No schema changes if you are on CU10 (there was a schema change in CU10). You can use the CMD line switches or use the UI; the CU setup is smart enough to prompt for admin elevation if needed.

Frequent Visitor

@Nino Bilic thanks for the clarification.  If in hybrid I'm assuming you still have to run the setup command with your XML file...can you confirm?  Thanks!

Microsoft

@Russo1485 Sorry what does this mean? What do you mean Setup with the XML file?

The bottom line is I guess - as you ran it before; no difference with this CU compared to older ones; I'm guessing you might have some custom settings or something...

Frequent Visitor

Setup.exe /IAcceptExchangeServerLicenseTerms /PrepareAD /TenantOrganizationConfig C:\Source\MyTenantOrganizationConfig.xml

 

I've had to use that command when installing CUs because we're in a hybrid setup.  I'm assuming we have to, but of course the new "Wizard" doesn't cover that aspect and neither does the documentation.

 

Thanks

New Contributor

Dumb question: Does config related to the IIS Rewrite Module need to be done? Or just install the msi and move on?

Occasional Visitor

The IIS Rewrite Module should be installed in a maintenance window, possibly right before installing the CU. I had to reboot our server after installing it, else Outlook wouldn't connect and OWA/ECP etc showed an HTTP 500 Internal Server Error on our Exchange 2016 Server (running on Windows Server 2012R2).

Microsoft

@Karen Brown Just install, do not need to config stuff.

Microsoft

@Russo1485 Sorry, I had a brain burp there - no, you are doing the right thing, just keep doing it! Prepare Active Directory and domains for Exchange Server, Active Directory Exchange Server, Exchange... 

Senior Member

Also, to prevent installation issues you should ensure that the Windows PowerShell Script Execution Policy is set to Unrestricted on the server being upgraded or installed

Hi, my current execution policy is RemoteSigned. I've changed it to Unrestricted before installing the latest CU. Can I revert back to RemoteSigned after installation? I've got to repeat the installation on the other servers in my DAG. Will RemoteSigned not work during installation?

Microsoft

@aleach Yes you can return it back later, sure.

Senior Member

Is this the last expected CU for Exchange 2016? If so, which 2016 CUs are supported?

Visitor

Hi Exchange Team,

I'm trying to upgrade my test environment from Exch2016 CU21 + SU1 to Exch2016 CU22. My normal approach is to run it from an elevated cmd prompt but every single time I've tried to run the installer on the first server it's thrown the "there's a reboot pending" exception.

 

C:\Windows\system32>f:\setup.exe /m:Upgrade /IAcceptExchangeServerLicenseTerms_DiagnosticDataON

Microsoft Exchange Server 2016 Cumulative Update 22 Unattended Setup

Copying Files...
File copy complete. Setup will now collect additional information needed for installation.

Languages
Management tools
Mailbox role: Transport service
Mailbox role: Client Access service
Mailbox role: Unified Messaging service
Mailbox role: Mailbox service
Mailbox role: Front End Transport service
Mailbox role: Client Access Front End service

Performing Microsoft Exchange Server Prerequisite Check

    Configuring Prerequisites                                                                         COMPLETED
    Prerequisite Analysis                                                                             FAILED

There is a pending reboot from a previous installation of a Windows Server role or feature. Please restart the computer
and then run Setup again.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.PendingRebootWindowsComponents.aspx


The Exchange Server setup operation didn't complete. More details can be found in ExchangeSetup.log located in the
<SystemDrive>:\ExchangeSetupLogs folder.

 

I've restarted the server 5 times and it's thrown the same thing every time, I checked the setup log and it doesn't seem like this is actually the case:

 

[09/30/2021 10:58:27.0938] [1] Started [Rule:PendingRebootWindowsComponents] [Parent:RootAnalysisMember] [RuleType:Error]
[09/30/2021 10:58:27.0998] [1] Evaluated [Rule:PendingRebootWindowsComponents] [HasException:False] [Value:"True"] [ParentValue:"<NULL>"] [Thread:17] [Duration:00:00:00.0570024]
[09/30/2021 10:58:28.0000] [1] Finished [Rule:PendingRebootWindowsComponents] [Duration:00:00:00.0610040]

 

Just on the off chance that it was something related to the unattended installer I've tried launching the upgrade through the GUI setup and it is now successfully performing the upgrade. Underlying OS is fully-patched WinSvr2016.

 

Senior Member

Thank for your Update Nino

 

New Contributor

A bit of encouraging news. We normally wait longer than the day a CU is released to install it....hoping to let others discover if there is fallout first.

 

This time, we went for it and it was smooth sailing.

Now to read about the EM piece.

2019 CU10 to CU11.

Microsoft

@ScottKnights As of now, we do not have anything to announce if there will be more E2016 CUs. We made those announcements before. Then things changed. We will see! Always, the last two CUs are what is "supported".

@joeykins82 Thanks for providing details; we just tried to reproduce this using the same builds you mentioned, and could not, hmm. Will keep looking!

Senior Member

@Nino Bilic 

Hi Nino, I just wanted to clarify which CUs are supported as the support policy for Exchange server stipulates:
Critical product updates are packages that address a Microsoft-released security bulletin or that contain a change in time zone definitions. When in Mainstream Support, critical product updates are released as needed on a monthly basis for the most recently released CU and for the immediately previous CU. When in Extended Support, critical product updates are released as needed on a monthly basis for only the most recently released CU.

 

This was also stated again in this blog post about the end of Mainstream Support for Exchange 2016:
https://techcommunity.microsoft.com/t5/exchange-team-blog/exchange-server-2016-and-the-end-of-mainst...

Microsoft encourages Exchange Server 2016 customers to adopt CU20 as soon as possible to ensure uninterrupted delivery of any future security related fixes. After March 16, 2021, only CU20 or its successors will receive updates. During the Extended Support phase, only the latest CU is eligible to receive updates once the standard 3 month transition period of the prior CU has lapsed.  

 

That is on this blog so is official information! Exchange 2016 has been in Extended Support since last October. Can you please ensure that when any future 2016 CUs are released (assuming any are) that you explicitly clarify which will receive critical updates.

Occasional Visitor

Why does my Exchange shows two different things

 

Exchange: Exchange 2016 CU18
Build Number: 15.1.2308.8

 

Build 15.1.2308.8 should be CU21

 

At this point I don't know If I should treat this as upgrade CU18 -> 22 or CU21 -> CU22

 

Senior Member

Hi @Nino Bilic & Team,

 

At present we are on Exchange 2019 CU9, can we install or go directly to CU11...?

 

Regards,

Sree

Microsoft

@Sreejith yes, you can install CU11. Please note that PrepareSchema is required if CU9 is your current version.

New Contributor

Hello Microsoft,

 

I note that these CUs include the fix for "Exchange Server 2019 and 2016 certificates created during setup use SHA-1 hash (KB5006983)"

 

For those SHA-1 certificates that were previously created by Microsoft Exchange, what is the procedure to convert them to SHA-256 ? 

Microsoft

@Sam_T you must recreate/renew them. There is no way to convert the existing certificates to SHA256. 

Microsoft

@Sreejith In addition to what Lukas mentioned - please see https://aka.ms/exchangeupdatewizard - we always update this to make sure that all the steps are listed when updating CUs.

New Contributor

@Lukas Sassl 

Thanks for your response Lukas. So what is the Microsoft recommended procedure to recreate or renew the SHA-1 certificates that were previously created by Microsoft Exchange, so that they are SHA-256 ? 

Microsoft

@Sam_T the steps to renew an Exchange certificate are described here: Renew an Exchange Server certificate | Microsoft Docs . The issue which is fixed with the latest CU has only affected the certificates created during the initial Exchange installation. 

The New-ExchangeCertificate cmdlet automatically generates certificates using SHA-256. You can also use the Exchange HealthChecker (https://aka.ms/ExchangeHealthChecker) to check the hash algorithm.

 

EDIT:

If you create a new auth certificate, make sure to configure it as next certificate via Set-AuthConfig (Set-AuthConfig (ExchangePowerShell) | Microsoft Docs) or follow these steps if it has already expired: https://aka.ms/HC-OAuthExpired 

Senior Member

I'm seeing my Microsoft Exchange Server Auth Certificate (and other cert) as SHA1.     reading above makes me think I need to create new a new Auth cert as SHA256 before applying CU22 ??

Microsoft

@jordanl17 No, it's no requirement to re-create the Auth certificate if it's valid and using SHA1 hash algorithm before applying CU22.

Frequent Visitor

Hello,

we run two Edge Servers in a hybrid environment with two Exchange servers and since the upgrade to CU22 I see these Eventlog Errors. Does anyone else have such errors? Nothing changed in certificates since upgrade to CU21. E-mail flow seems not to be affected. The requested certificate is the hostname for the Edge Server.

Peter_2021_0-1633434389599.png

 

Senior Member

Has anyone with Exchange servers residing behind a NLB applied this CU yet? Curious to know if this months CU break OWA and ECP like July's did. 

 

All of our certificates were vailid and the session persistance workaround did not work for us in July. 

Senior Member

Hi @Lukas Sassl 

 

Do I need to run PrepareSchema if I am on Exchange 2019 CU10....?

 

New Contributor

@Sreejith There is no need to 'PrepareSchema' going from Exchange 2019 CU10 to CU11.

The document states "These updates do not contain schema changes". I did exactly this update yesterday.

Microsoft

@Sreejith as listed here: https://docs.microsoft.com/en-us/exchange/plan-and-deploy/active-directory/ad-schema-changes?view=ex... , no Schema Update is required if your current version is CU10. 

The Exchange Update Wizard show all required steps: https://aka.ms/exchangeupdatewizard 

Microsoft

@PatchesOhoulihan14 If the organization is coming from pre July 2021 SU then I would expect the behavior of going to September 2021 CUs to be the same as going to July SUs. Once the organization is on July+ SUs, they should not be seeing problems related to LB.

Senior Member

@Nino Bilic Thank you, Nino. The organization is going from Exchange 2019 CU10 to CU11, so based on your reply, the issues relating to the LB should not be experienced during this upgrade?

%3CLINGO-SUB%20id%3D%22lingo-sub-2792081%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20September%202021%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2792081%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Exchange%20team%2C%3C%2FP%3E%3CP%3EI%20guess%2C%20for%20the%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fwww.iis.net%2Fdownloads%2Fmicrosoft%2Furl-rewrite%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noreferrer%22%3EIIS%20URL%20Rewrite%3C%2FA%3E%3CSPAN%3E%26nbsp%3Bmodule%2C%20we%20just%20need%20the%20regular%20'x64'%20msi%20installer%2C%20not%20the%26nbsp%3B%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fwww.microsoft.com%2Fweb%2Fhandlers%2Fwebpi.ashx%3Fcommand%3Dgetinstallerredirect%26amp%3Bappid%3Durlrewrite2%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3EWeb%20Platform%20Installer%20(WebPI)%3C%2FA%3E%26nbsp%3B%3C%2FSPAN%3ERegards%20Stephen%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2779883%22%20slang%3D%22en-US%22%3EReleased%3A%20September%202021%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2779883%22%20slang%3D%22en-US%22%3E%3CP%3EToday%20we%20are%20announcing%20the%20availability%20of%20quarterly%20Cumulative%20Updates%20(CUs)%20for%20Exchange%20Server%202016%20and%20Exchange%20Server%202019.%20These%20CUs%20include%20fixes%20for%20customer%20reported%20issues%2C%20all%20previously%20released%20security%20updates%2C%20and%20a%20new%20security%20feature.%3C%2FP%3E%0A%3CP%3EA%20full%20list%20of%20fixes%20is%20contained%20in%20the%20KB%20article%20for%20each%20CU%2C%20but%20we%20wanted%20to%20highlight%20a%20few%20changes.%3C%2FP%3E%0A%3CP%3E%3CFONT%20size%3D%226%22%3EMicrosoft%20Exchange%20Emergency%20Mitigation%20Service%3C%2FFONT%3E%3C%2FP%3E%0A%3CP%3EAs%20mentioned%20in%20our%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fexchange-team-blog%2Fnew-security-feature-in-september-2021-cumulative-update-for%2Fba-p%2F2783155%22%20target%3D%22_blank%22%3Erecent%20blog%20post%3C%2FA%3E%2C%20September%202021%20CUs%20(and%20later)%20include%20the%20new%20Microsoft%20Exchange%20Emergency%20Mitigation%20service.%20Please%20familiarize%20yourself%20with%20the%20new%20service%20as%20it%20is%20a%20new%20security%20feature%20that%20will%20be%20installed%20on%20all%20Exchange%20Servers%20(except%20Edge%20servers).%3C%2FP%3E%0A%3CP%3E%3CFONT%20size%3D%226%22%3ECumulative%20Update%20Setup%20Changes%3C%2FFONT%3E%3C%2FP%3E%0A%3CP%20data-unlink%3D%22true%22%3EWe%20wanted%20to%20call%20out%20two%20setup%20changes%20starting%20with%20September%202021%20CUs%20(more%20information%20in%20the%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fexchange-team-blog%2Fnew-security-feature-in-september-2021-cumulative-update-for%2Fba-p%2F2783155%22%20target%3D%22_self%22%3EEmergency%20Mitigation%20Service%20blog%20post%3C%2FA%3E%3A(%3C%2Fimg%3E%26nbsp%3B%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3EWe%20changed%20the%20unattended%20setup%20switch.%20The%20previous%20%3CSTRONG%3E%2FIAcceptExchangeServerLicenseTerms%3C%2FSTRONG%3E%20switch%20will%20%3CEM%3Enot%3C%2FEM%3E%20work%20starting%20with%20the%20September%202021%20CUs.%20You%20now%20must%20use%20either%20%3CSTRONG%3E%2FIAcceptExchangeServerLicenseTerms_DiagnosticDataON%3C%2FSTRONG%3E%20or%20%3CSTRONG%3E%2FIAcceptExchangeServerLicenseTerms_DiagnosticDataOFF%3C%2FSTRONG%3E%20for%20unattended%20and%20scripted%20installs.%3C%2FLI%3E%0A%3CLI%3EThe%20%3CA%20href%3D%22https%3A%2F%2Fwww.iis.net%2Fdownloads%2Fmicrosoft%2Furl-rewrite%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noreferrer%22%3EIIS%20URL%20Rewrite%3C%2FA%3E%20module%20is%20now%20a%20prerequisite%20for%20Exchange%20Server%20installation.%20This%20must%20be%20installed%20separately%20and%20is%20not%20installed%20as%20part%20of%20Exchange%20Setup%20(you%20need%20the%20x64%20MSI%20version).%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%3CFONT%20size%3D%226%22%3ERelease%20Details%3C%2FFONT%3E%3C%2FP%3E%0A%3CP%3EThe%20KB%20articles%20that%20describe%20the%20fixes%20in%20each%20release%20and%20product%20downloads%20are%20as%20follows%3A%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3EExchange%20Server%202019%20Cumulative%20Update%2011%20(%3CA%20href%3D%22https%3A%2F%2Fsupport.microsoft.com%2Fhelp%2F5005334%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3EKB5005334%3C%2FA%3E)%2C%20%3CA%20href%3D%22https%3A%2F%2Fwww.microsoft.com%2FLicensing%2Fservicecenter%2Fdefault.aspx%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3EVLSC%20Download%3C%2FA%3E%2C%20%3CA%20href%3D%22https%3A%2F%2Fwww.microsoft.com%2Fen-us%2Fdownload%2Fdetails.aspx%3FfamilyID%3D40be4769-0188-4b1a-a023-1a3ecb919870%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3EDownload%3C%2FA%3E%3C%2FLI%3E%0A%3CLI%3EExchange%20Server%202016%20Cumulative%20Update%2022%20(%3CA%20href%3D%22https%3A%2F%2Fsupport.microsoft.com%2Fhelp%2F5005333%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3EKB5005333%3C%2FA%3E)%2C%20%3CA%20href%3D%22https%3A%2F%2Fwww.microsoft.com%2Fen-us%2Fdownload%2Fdetails.aspx%3FfamilyID%3Da7d608a2-d81b-46af-8753-8c3c2ea1f783%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3EDownload%3C%2FA%3E%2C%20%3CA%20href%3D%22https%3A%2F%2Fwww.microsoft.com%2Fen-us%2Fdownload%2Fdetails.aspx%3FfamilyID%3D20b4c3e6-bb8c-440d-ba4e-f2b4e6cdcd05%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3EUM%20Lang%20Packs%3C%2FA%3E%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%3CFONT%20size%3D%226%22%3EKnown%20issues%20with%20this%20release%3C%2FFONT%3E%3C%2FP%3E%0A%3CP%3EDue%20to%20several%20changes%20released%20in%20security%20updates%20since%20the%20last%20CU%20release%2C%20we%20wanted%20you%20to%20be%20aware%20of%20the%20following%20issues%20that%20might%20impact%20customers%20who%20did%20%3CEM%3Enot%3C%2FEM%3E%20already%20install%20recent%20security%20updates%3A%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3EBefore%20the%20update%2C%20you%20should%20check%20your%20Exchange%20Server%20authorization%20certificate.%20Please%20see%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Fhelp%2F5005341%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ethis%20KB%20article%3C%2FA%3E%26nbsp%3Bfor%20more%20information.%3C%2FLI%3E%0A%3CLI%3EIf%20your%20organization%20uses%20Load%20Balancing%2C%20please%20see%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Fhelp%2F5005341%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ethis%20KB%20article%3C%2FA%3E%26nbsp%3Bfor%20more%20information%20on%20how%20to%20update.%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%3CFONT%20size%3D%225%22%3EAdditional%20Information%3C%2FFONT%3E%3C%2FP%3E%0A%3CP%3EMicrosoft%20recommends%20all%20customers%20test%20the%20deployment%20of%20any%20update%20in%20their%20lab%20environment%20to%20determine%20the%20proper%20installation%20process%20for%20your%20production%20environment.%3C%2FP%3E%0A%3CP%3EThese%20updates%20do%20not%20contain%20schema%20changes.%20If%20coming%20from%20older%20updates%2C%20you%20can%20find%20more%20information%20on%20preparing%20Active%20Directory%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fexchange%2Fplan-and-deploy%2Fprepare-ad-and-domains%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehere%3C%2FA%3E.%20Schema%20changes%20can%20be%20tracked%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2FExchange%2Fplan-and-deploy%2Factive-directory%2Fad-schema-changes%3Fview%3Dexchserver-2019%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehere%3C%2FA%3E.%20For%20best%20practices%20for%20successful%20installation%2C%20please%20see%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2FExchange%2Fplan-and-deploy%2Finstall-cumulative-updates%3Fview%3Dexchserver-2019%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ethis%20document%3C%2FA%3E.%3C%2FP%3E%0A%3CP%3EIf%20updating%20from%20an%20older%20version%20of%20the%20CU%2C%20please%20see%20the%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Faka.ms%2Fexchangeupdatewizard%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3EExchange%20Update%20Wizard%3C%2FA%3E%26nbsp%3Bfor%20detailed%20steps%20to%20follow.%3C%2FP%3E%0A%3CP%3EAlso%2C%20to%20prevent%20installation%20issues%20you%20should%20ensure%20that%20the%20Windows%20PowerShell%20Script%20Execution%20Policy%20is%20set%20to%26nbsp%3B%3CSTRONG%3EUnrestricted%3C%2FSTRONG%3E%26nbsp%3Bon%20the%20server%20being%20upgraded%20or%20installed.%20To%20verify%20the%20policy%20settings%2C%20run%20the%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fpowershell%2Fmodule%2Fmicrosoft.powershell.security%2Fget-executionpolicy%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3EGet-ExecutionPolicy%3C%2FA%3E%26nbsp%3Bcmdlet%20from%20PowerShell%20on%20the%20machine%20being%20upgraded.%20If%20the%20policies%20are%20NOT%20set%20to%20Unrestricted%20you%20should%20use%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fexchange%2Fplan-and-deploy%2Fdeployment-ref%2Fms-exch-setupreadiness-powershellexecutionpolicycheckset%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ethese%20resolution%20steps%3C%2FA%3E%26nbsp%3Bto%20adjust%20the%20settings.%3C%2FP%3E%0A%3CP%3EIf%20you%20plan%20to%20install%20the%20update%20with%20the%20unattended%20install%20option%20using%20either%20PowerShell%20or%20a%20command%20prompt%2C%20make%20sure%20you%20specify%20either%20the%20full%20path%20to%20the%20setup.exe%20file%20or%20use%20a%20%E2%80%9C.%E2%80%9D%20in%20front%20of%20the%20command%20if%20you%20are%20running%20it%20directly%20from%20the%20folder%20containing%20the%20update.%20If%20you%20do%20not%2C%20Exchange%20Setup%20may%20indicate%20that%20it%20completed%20successfully%20when%20it%20did%20not.%20Read%20more%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fexchange%2Ftroubleshoot%2Fsetup%2Fex2019-setup-does-not-run-correctly-started-powershell%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehere%3C%2FA%3E.%3C%2FP%3E%0A%3CP%20style%3D%22background%3A%20%23F0F0F0%3B%20padding%3A%20.5em%3B%20margin%3A%201em%200%201em%200%3B%22%3E%3CSTRONG%3ENote%3A%3C%2FSTRONG%3E%20Customers%20in%20Exchange%20hybrid%20deployments%20and%20those%20using%20Exchange%20Online%20Archiving%20with%20an%20on-premises%20Exchange%20deployment%20are%20required%20to%20deploy%20a%20supported%20CU%20for%20the%20product%20version%20in%20use.%3C%2FP%3E%0A%3CP%3EFor%20the%20latest%20information%20on%20the%20Exchange%20Server%20and%20product%20announcements%20please%20see%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2FExchange%2Fnew-features%2Fnew-features%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3EWhat's%20New%20in%20Exchange%20Server%3C%2FA%3E%26nbsp%3Band%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2FExchange%2Frelease-notes%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3EExchange%20Server%20Release%20Notes%3C%2FA%3E.%3C%2FP%3E%0A%3CP%20style%3D%22background%3A%20%23F0F0F0%3B%20padding%3A%20.5em%3B%20margin%3A%201em%200%201em%200%3B%22%3E%3CSTRONG%3ENote%3A%3C%2FSTRONG%3E%20Documentation%20may%20not%20be%20fully%20available%20at%20the%20time%20this%20post%20is%20published.%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22author%22%3EThe%20Exchange%20Server%20team%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-2779883%22%20slang%3D%22en-US%22%3E%3CP%3EToday%20we%20are%20announcing%20the%20availability%20of%20quarterly%20Cumulative%20Updates%20(CUs)%20for%20Exchange%20Server%202016%20and%20Exchange%20Server%202019.%3C%2FP%3E%3C%2FLINGO-TEASER%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2779883%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAnnouncements%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EExchange%202016%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EExchange%202019%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOn%20premises%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2792192%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20September%202021%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2792192%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F566935%22%20target%3D%22_blank%22%3E%40sjhudson%3C%2FA%3E%26nbsp%3BCorrect%2C%26nbsp%3Bx64%20MSI%20version.%20I%20added%20that%20to%20the%20bullet.%20Thanks!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2792546%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20September%202021%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2792546%22%20slang%3D%22en-US%22%3E%3CP%3E4.%20%22%3CSPAN%3EIMPORTANT%3A%26nbsp%3B%3C%2FSPAN%3E%3CSPAN%3EYou%20must%20install%20the%20CU%20from%20an%20elevated%20command%20prompt.%20If%20the%20CU%20installation%20is%20being%20started%20from%20PowerShell%2C%20ensure%20the%20full%20path%20to%20setup.exe%20is%20provided%22%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3EI%20normally%20Run%20As%20Admin%20the%20setup.exe%20in%20the%20mounted%20ISO(after%20a%20fresh%20reboot).%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3Bthis%20sentence%20makes%20me%20think%20I%20should%20NOT%20do%20this%3F%26nbsp%3B%20I%20like%20using%20the%20GUI%2C%20it's%20worked%20in%20the%20past%20just%20fine.%26nbsp%3B%20%26nbsp%3BI%20know%20I'll%20need%20the%20URL%20rewrite%20msi%20and%20I%20think%20I'll%20have%20a%20schema%20update%20coming%20from%20CU19%2C%20but%20the%20gui%20walks%20me%20through%20that.%26nbsp%3B%20%26nbsp%3Band%20since%20I%20don't%20have%20a%20DAG%20I%20think%20I%20don't%20need%20to%20enter%20maintenance%26nbsp%3Bmode.%26nbsp%3B%20%26nbsp%3Bthanks!%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2792614%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20September%202021%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2792614%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F420225%22%20target%3D%22_blank%22%3E%40jordanl17%3C%2FA%3E%26nbsp%3BYou%20are%20good%20and%20you%20can%20continue%20doing%20what%20works%20for%20you%3B%20CU%20setup%20is%20more%20advanced%20than%20the%20SU%20(security%20update)%20setup%20so%20either%20will%20work.%20The%20truth%20is%20that%20due%20to%20the%20fact%20that%20the%20SU%20setup%20is%20something%20that%20actually%20%3CEM%3Erequires%3C%2FEM%3E%20elevated%20CMD%20line%2C%20we%20have%20just%20gone%20to%20suggest%20to%20do%20the%20same%20thing%20(elevated)%20all%20the%20time.%20But%20CU%20setup%20will%20check%20for%20permissions%20and%20prompt%20for%20elevation%20if%20required.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2792742%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20September%202021%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2792742%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20are%20running%20CU20%20with%20Jul21SU...%20-%20does%20this%20mean%2C%20we%20must%20install%20CU21%20first%20to%20get%20CU22%20-%20or%20is%20it%20possible%20to%20go%20directly%20from%20CU20%2FJul21SU%20to%20CU22%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2793147%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20September%202021%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2793147%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1106110%22%20target%3D%22_blank%22%3E%40Duncan1528%3C%2FA%3E%26nbsp%3BYou%20are%20go%20directly%20from%20CU20%2B(any%20SU)%20to%20CU22%2C%20yes.%20You%20will%20need%20to%20install%20IIS%20URL%20rewrite%20before%20you%20do%20that%2C%20though.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2793183%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20September%202021%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2793183%22%20slang%3D%22en-US%22%3E%3CP%3EKB2999226%20is%20listed%20as%20a%26nbsp%3Bprerequisite%20for%20EM%20and%20therefore%20this%20CU.%20That%20KB%20only%20applies%20to%20Server%202012%20R2%20and%20lower.%20Is%20there%20a%20modern%20KB%20available%20for%20Server%202016%2F2019%20available%20that%20we%20should%20be%20installing%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2794596%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20September%202021%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2794596%22%20slang%3D%22en-US%22%3E%3CP%3EThe%20KB%20articles%20in%20the%20Known%20issues%20point%20to%20the%20same%20URL.%20Can%20you%20verify%20the%20one%20for%20Load%20balancing%3F%20thanks%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2795065%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20September%202021%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2795065%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F225823%22%20target%3D%22_blank%22%3E%40Ricardo%20Costa%20da%20Silva%3C%2FA%3E%26nbsp%3BThat%20is%20correct%3B%20both%20issues%20are%20covered%20in%20the%20same%20KB%3B%20there%20is%20Cause%201%20and%20Cause%202%2C%20with%20their%20own%20resolutions.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2793210%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20September%202021%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2793210%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1169340%22%20target%3D%22_blank%22%3E%40NHawk257%3C%2FA%3E%26nbsp%3BThat's...%20well%2C%20that%20is%20a%20little%20awkward.%20This%20update%20is%20quite%20old%20and%20I%20do%20not%20expect%20it%20to%20be%20an%20issue%20on%20say%20an%20Exchange%202019%20server%20(which%20does%20not%20even%20run%20on%202012%20R2).%20Bottom%20line%20is%20-%20if%20WU%20says%20your%20server%20is%20up%20to%20date%2C%20you%20are%20OK.%20I%20would%20hope%20that%20even%20on%20Exchange%202016%20servers%2C%20this%20KB%20would%20be%20installed%20everywhere%20by%20now...%20but%20thinking%20about%20this%20as%20a%20reference%20in%20the%20KB%3B%20especially%20for%20E2019%20CU%2C%20it%20does%20not%20make%20much%20sense%2C%20does%20it...%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2795502%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20September%202021%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2795502%22%20slang%3D%22en-US%22%3E%3CP%3EThe%26nbsp%3BDeployment%20instructions%20for%20Exchange%202016%20CU%20in%20the%20Exchange%20Update%20Wizard%20when%20going%20from%20CU21%20to%20CU22%20says%20to%20%22Install%20the%20latest%20applicable%20security%20update%20(SU)%20as%20listed%20in%20Exchange%20Server%20build%20numbers%20and%20release%20dates.%22%20I%20notice%20that%20%22Exchange%20Server%202016%20CU21%20Jul21SU%22%20is%20listed%20under%20CU22%20on%20the%20build%20page.%20If%20I%20have%20already%20installed%20that%20SU%20while%20at%20CU21%2C%20do%20I%20need%20to%20install%20it%20again%20after%20installing%20CU22%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2795525%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20September%202021%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2795525%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20are%20running%20Exchange%202016%20CU21%20in%20Windows%202012%20server%20and%20I%20am%20planning%20to%20apply%20CU22%20to%20our%20server.%20Please%20advice%20whether%20I%20have%20to%20install%20following%20pre%20request%20before%20apply%20CU22.%20Thanks%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CUL%20class%3D%22%22%3E%3CLI%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fnam06.safelinks.protection.outlook.com%2F%3Furl%3Dhttps%253A%252F%252Fwww.iis.net%252Fdownloads%252Fmicrosoft%252Furl-rewrite%26amp%3Bdata%3D04%257C01%257Cv-jesits%2540microsoft.com%257C7a2101c9287640d517df08d97e9ec2ed%257C72f988bf86f141af91ab2d7cd011db47%257C1%257C0%257C637680042637944856%257CUnknown%257CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%253D%257C1000%26amp%3Bsdata%3DS**bleep**dgSg0CmS1iOXr%252B3eFrU9Y9CjWpbv%252Ff7mRESOjA%253D%26amp%3Breserved%3D0%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noreferrer%22%3EIIS%20URL%20Rewrite%20Module%3C%2FA%3E%3CBR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Fnam06.safelinks.protection.outlook.com%2F%3Furl%3Dhttps%253A%252F%252Fsupport.microsoft.com%252Fen-us%252Ftopic%252Fupdate-for-universal-c-runtime-in-windows-c0514201-7fe6-95a3-b0a5-287930f3560c%26amp%3Bdata%3D04%257C01%257Cv-jesits%2540microsoft.com%257C7a2101c9287640d517df08d97e9ec2ed%257C72f988bf86f141af91ab2d7cd011db47%257C1%257C0%257C637680042637954847%257CUnknown%257CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%253D%257C1000%26amp%3Bsdata%3DBnavMXIcJjRIPpUXU8LdycyGs9iPMpJ50k9%252FSco0878%253D%26amp%3Breserved%3D0%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noreferrer%22%3EUniversal%20C%20Runtime%20in%20Windows%20(KB%202999226)%3C%2FA%3E%3C%2FP%3E%3C%2FLI%3E%3C%2FUL%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2795764%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20September%202021%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2795764%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1170172%22%20target%3D%22_blank%22%3E%40RadHaz75%3C%2FA%3E%26nbsp%3BNo%3B%20the%20reason%20why%20it%20says%20this%20is%20because%20it%20cannot%20know%20when%20you%20would%20be%20installing%20the%20CU%3B%20immediately%20after%20release%20or%20say...%202%20months%20down%20the%20road%20(when%20there%20might%20be%20SUs%20for%20that%20CU).%20All%20of%20the%20SUs%20are%20CU%20specific.%20There%20are%20no%20SUs%20for%20latest%20set%20of%20CUs%20(released%20yesterday).%20That%20might%20change%20in%20the%20future%20but%20right%20now%20-%20there%20is%20nothing%20newer%20than%20the%20CU.%20We%20talk%20about%20this%20stuff%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fexchange-team-blog%2Fwhy-exchange-server-updates-matter%2Fba-p%2F2280770%22%20target%3D%22_self%22%3Ehere%3C%2FA%3E.%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1007004%22%20target%3D%22_blank%22%3E%40vigna840%3C%2FA%3E%26nbsp%3BIIS%20Rewrite%20Module%20is%20a%20hard%20requirement%2C%20yes.%20You%20will%20be%20blocked%20from%20installation%20if%20you%20do%20not%20install%20that%20first.%20On%20the%20C%20Runtime%20-%20if%20your%20server%20is%20up%20to%20date%20on%20it's%20WU%20updates%2C%20then%20you%20should%20be%20good%20with%20this.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2795783%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20September%202021%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2795783%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F5374%22%20target%3D%22_blank%22%3E%40Nino%20Bilic%3C%2FA%3E%26nbsp%3BThanks.%20That's%20what%20I%20thought.%20Can%20you%20explain%20why%20the%26nbsp%3BJul21SU%20is%20listed%20under%20CU22%20the%20same%20way%20it%20is%20listed%20under%20CU21%20here%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2FExchange%2Fnew-features%2Fbuild-numbers-and-release-dates%3Fview%3Dexchserver-2019%23exchange-server-2016%3F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2FExchange%2Fnew-features%2Fbuild-numbers-and-release-dates%3Fview%3Dexchserver-2019%23exchange-server-2016%3F%3C%2FA%3E%26nbsp%3BIs%20this%20just%20a%20mistake%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2795797%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20September%202021%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2795797%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1170172%22%20target%3D%22_blank%22%3E%40RadHaz75%3C%2FA%3E%26nbsp%3BThe%20article%20does%20not%20show%20Jul21SU%20%22under%22%20CU11...%20if%20you%20look%20at%20all%20of%20the%20updates%20on%20the%20page%2C%20they%20are%20actually%20listed%20chronologically%20from%20oldest%20to%20newest.%20So%20there%20is%20a%202019%20CU9%2C%20then%20all%20the%20SUs%20on%20top%20of%20that%20going%20%22upward%22.%20Then%202019%20CU10%20and%20it's%20SU%20(released%20on%20Jul%2013).%20Then%20there%20is%20CU11.%20The%20SU%20for%20CU11%20(when%20released)%20will%20come%20on%20the%20top%20of%20the%20list%20and%20will%20be%20indented%20a%20bit%20to%20show%20that%20it%20is%20an%20SU%20vs.%20the%20CU%20which%20start%20at%20the%20start%20of%20each%20row.%3C%2FP%3E%0A%3CP%3EI%20do%20agree%20this%20can%20be%20misinterpreted%20unless%20you%20realize%20the%20context%20of%20the%20list.%20Hmm.%20Thinking%20of%20how%20this%20could%20be%20presented%20clearer%20perhaps...%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2795822%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20September%202021%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2795822%22%20slang%3D%22en-US%22%3E%3CP%3EFor%202019%20CU10%20without%20the%20SU%20installed...do%20we%20need%20to%20apply%20that%20first%20prior%20to%20going%20to%20CU11%3F%26nbsp%3B%20Also%20no%20schema%20changes%20right%20so%20need%20to%20run%20the%20commands%20for%20that%20correct%3F%26nbsp%3B%20What%20about%20being%20in%20a%20hybrid%20mode%3F%26nbsp%3B%20Do%20we%20need%20to%20include%20the%20command%20line%20switches%20when%20installing%3F%26nbsp%3B%20Thanks!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2795837%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20September%202021%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2795837%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F5374%22%20target%3D%22_blank%22%3E%40Nino%20Bilic%3C%2FA%3E%26nbsp%3BI%20think%20I%20see%20what%20you're%20saying.%20The%20fact%20that%20the%20SU%20is%20indented%20under%20CU21%20implies%20to%20me%20it's%20like%20a%20subpart%20of%20that%2C%20like%20required%20after%2C%20hence%20my%20confusion%20there.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2795972%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20September%202021%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2795972%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1170290%22%20target%3D%22_blank%22%3E%40Russo1485%3C%2FA%3E%26nbsp%3BNo%20you%20do%20not%20need%20to%20install%20any%20SUs%20before%20going%20to%20next%20CU.%20No%20schema%20changes%20if%20you%20are%20on%20CU10%20(%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2FExchange%2Fplan-and-deploy%2Factive-directory%2Fad-schema-changes%3Fview%3Dexchserver-2019%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%22%3Ethere%20was%3C%2FA%3E%20a%20schema%20change%20in%20CU10).%20You%20can%20use%20the%20CMD%20line%20switches%20or%20use%20the%20UI%3B%20the%20CU%20setup%20is%20smart%20enough%20to%20prompt%20for%20admin%20elevation%20if%20needed.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2796018%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20September%202021%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2796018%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F5374%22%20target%3D%22_blank%22%3E%40Nino%20Bilic%3C%2FA%3E%26nbsp%3Bthanks%20for%20the%20clarification.%26nbsp%3B%20If%20in%20hybrid%20I'm%20assuming%20you%20still%20have%20to%20run%20the%20setup%20command%20with%20your%20XML%20file...can%20you%20confirm%3F%26nbsp%3B%20Thanks!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2796026%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20September%202021%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2796026%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1170290%22%20target%3D%22_blank%22%3E%40Russo1485%3C%2FA%3E%26nbsp%3BSorry%20what%20does%20this%20mean%3F%20What%20do%20you%20mean%20Setup%20with%20the%20XML%20file%3F%3C%2FP%3E%0A%3CP%3EThe%20bottom%20line%20is%20I%20guess%20-%20as%20you%20ran%20it%20before%3B%20no%20difference%20with%20this%20CU%20compared%20to%20older%20ones%3B%20I'm%20guessing%20you%20might%20have%20some%20custom%20settings%20or%20something...%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2796042%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20September%202021%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2796042%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSPAN%3ESetup.exe%20%2FIAcceptExchangeServerLicenseTerms%20%2FPrepareAD%20%2FTenantOrganizationConfig%20C%3A%5CSource%5CMyTenantOrganizationConfig.xml%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EI've%20had%20to%20use%20that%20command%20when%20installing%20CUs%20because%20we're%20in%20a%20hybrid%20setup.%26nbsp%3B%20I'm%20assuming%20we%20have%20to%2C%20but%20of%20course%20the%20new%20%22Wizard%22%20doesn't%20cover%20that%20aspect%20and%20neither%20does%20the%20documentation.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EThanks%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2796183%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20September%202021%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2796183%22%20slang%3D%22en-US%22%3E%3CP%3EDumb%20question%3A%20Does%20config%20related%20to%20the%20IIS%20Rewrite%20Module%20need%20to%20be%20done%3F%20Or%20just%20install%20the%20msi%20and%20move%20on%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2796237%22%20slang%3D%22de-DE%22%3ESubject%3A%20Released%3A%20September%202021%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2796237%22%20slang%3D%22de-DE%22%3E%3CP%3EThe%20IIS%20Rewrite%20Module%20should%20be%20installed%20in%20a%20maintenance%20window%2C%20possibly%20right%20before%20installing%20the%20CU.%20I%20had%20to%20reboot%20our%20server%20after%20installing%20it%2C%20else%20Outlook%20wouldn't%20connect%20and%20OWA%2FECP%20etc%20showed%20an%20HTTP%20500%20Internal%20Server%20Error%20on%20our%20Exchange%202016%20Server%20(running%20on%20Windows%20Server%202012R2).%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2796267%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20September%202021%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2796267%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F56010%22%20target%3D%22_blank%22%3E%40Karen%20Brown%3C%2FA%3E%26nbsp%3BJust%20install%2C%20do%20not%20need%20to%20config%20stuff.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2796351%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20September%202021%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2796351%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1170290%22%20target%3D%22_blank%22%3E%40Russo1485%3C%2FA%3E%26nbsp%3BSorry%2C%20I%20had%20a%20brain%20burp%20there%20-%20no%2C%20you%20are%20doing%20the%20right%20thing%2C%20just%20keep%20doing%20it!%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2FExchange%2Fplan-and-deploy%2Fprepare-ad-and-domains%3Fview%3Dexchserver-2019%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3EPrepare%20Active%20Directory%20and%20domains%20for%20Exchange%20Server%2C%20Active%20Directory%20Exchange%20Server%2C%20Exchange%20Server%20Active%20Directory%2C%20Exchange%202019%20Active%20Directory%20%7C%20Microsoft%20Docs%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2796545%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20September%202021%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2796545%22%20slang%3D%22en-US%22%3E%3CBLOCKQUOTE%3E%3CP%3E%3CSPAN%3EAlso%2C%20to%20prevent%20installation%20issues%20you%20should%20ensure%20that%20the%20Windows%20PowerShell%20Script%20Execution%20Policy%20is%20set%20to%26nbsp%3B%3C%2FSPAN%3E%3CSTRONG%3EUnrestricted%3C%2FSTRONG%3E%3CSPAN%3E%26nbsp%3Bon%20the%20server%20being%20upgraded%20or%20installed%3C%2FSPAN%3E%3C%2FP%3E%3C%2FBLOCKQUOTE%3E%3CP%3E%3CSPAN%3EHi%2C%20my%20current%20execution%20policy%20is%20RemoteSigned.%20I've%20changed%20it%20to%20Unrestricted%20before%20installing%20the%20latest%20CU.%20Can%20I%20revert%20back%20to%20RemoteSigned%20after%20installation%3F%20I've%20got%20to%20repeat%20the%20installation%20on%20the%20other%20servers%20in%20my%20DAG.%20Will%20RemoteSigned%20not%20work%20during%20installation%3F%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2796555%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20September%202021%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2796555%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F903579%22%20target%3D%22_blank%22%3E%40aleach%3C%2FA%3E%26nbsp%3BYes%20you%20can%20return%20it%20back%20later%2C%20sure.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2797545%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20September%202021%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2797545%22%20slang%3D%22en-US%22%3E%3CP%3EIs%20this%20the%20last%20expected%20CU%20for%20Exchange%202016%3F%20If%20so%2C%20which%202016%20CUs%20are%20supported%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2799407%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20September%202021%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2799407%22%20slang%3D%22en-US%22%3E%3CP%3EThank%20for%20your%20Update%20Nino%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2798785%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20September%202021%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2798785%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Exchange%20Team%2C%3C%2FP%3E%3CP%3EI'm%20trying%20to%20upgrade%20my%20test%20environment%20from%20Exch2016%20CU21%20%2B%20SU1%20to%20Exch2016%20CU22.%20My%20normal%20approach%20is%20to%20run%20it%20from%20an%20elevated%20cmd%20prompt%20but%20every%20single%20time%20I've%20tried%20to%20run%20the%20installer%20on%20the%20first%20server%20it's%20thrown%20the%20%22there's%20a%20reboot%20pending%22%20exception.%3C%2FP%3E%3CPRE%20class%3D%22lia-code-sample%20language-markdown%22%3E%3CCODE%3EC%3A%5CWindows%5Csystem32%26gt%3Bf%3A%5Csetup.exe%20%2Fm%3AUpgrade%20%2FIAcceptExchangeServerLicenseTerms_DiagnosticDataON%0A%0AMicrosoft%20Exchange%20Server%202016%20Cumulative%20Update%2022%20Unattended%20Setup%0A%0ACopying%20Files...%0AFile%20copy%20complete.%20Setup%20will%20now%20collect%20additional%20information%20needed%20for%20installation.%0A%0ALanguages%0AManagement%20tools%0AMailbox%20role%3A%20Transport%20service%0AMailbox%20role%3A%20Client%20Access%20service%0AMailbox%20role%3A%20Unified%20Messaging%20service%0AMailbox%20role%3A%20Mailbox%20service%0AMailbox%20role%3A%20Front%20End%20Transport%20service%0AMailbox%20role%3A%20Client%20Access%20Front%20End%20service%0A%0APerforming%20Microsoft%20Exchange%20Server%20Prerequisite%20Check%0A%0A%20%20%20%20Configuring%20Prerequisites%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20COMPLETED%0A%20%20%20%20Prerequisite%20Analysis%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20FAILED%0A%0AThere%20is%20a%20pending%20reboot%20from%20a%20previous%20installation%20of%20a%20Windows%20Server%20role%20or%20feature.%20Please%20restart%20the%20computer%0Aand%20then%20run%20Setup%20again.%0AFor%20more%20information%2C%20visit%3A%20http%3A%2F%2Ftechnet.microsoft.com%2Flibrary(EXCHG.150)%2Fms.exch.setupreadiness.PendingRebootWindowsComponents.aspx%0A%0A%0AThe%20Exchange%20Server%20setup%20operation%20didn't%20complete.%20More%20details%20can%20be%20found%20in%20ExchangeSetup.log%20located%20in%20the%0A%3CSYSTEMDRIVE%3E%3A%5CExchangeSetupLogs%20folder.%3C%2FSYSTEMDRIVE%3E%3C%2FCODE%3E%3C%2FPRE%3E%3CP%3EI've%20restarted%20the%20server%205%20times%20and%20it's%20thrown%20the%20same%20thing%20every%20time%2C%20I%20checked%20the%20setup%20log%20and%20it%20doesn't%20seem%20like%20this%20is%20actually%20the%20case%3A%3C%2FP%3E%3CPRE%20class%3D%22lia-code-sample%20language-markdown%22%3E%3CCODE%3E%5B09%2F30%2F2021%2010%3A58%3A27.0938%5D%20%5B1%5D%20Started%20%5BRule%3APendingRebootWindowsComponents%5D%20%5BParent%3ARootAnalysisMember%5D%20%5BRuleType%3AError%5D%0A%5B09%2F30%2F2021%2010%3A58%3A27.0998%5D%20%5B1%5D%20Evaluated%20%5BRule%3APendingRebootWindowsComponents%5D%20%5BHasException%3AFalse%5D%20%5BValue%3A%22True%22%5D%20%5BParentValue%3A%22%3CNULL%3E%22%5D%20%5BThread%3A17%5D%20%5BDuration%3A00%3A00%3A00.0570024%5D%0A%5B09%2F30%2F2021%2010%3A58%3A28.0000%5D%20%5B1%5D%20Finished%20%5BRule%3APendingRebootWindowsComponents%5D%20%5BDuration%3A00%3A00%3A00.0610040%5D%3C%2FNULL%3E%3C%2FCODE%3E%3C%2FPRE%3E%3CP%3EJust%20on%20the%20off%20chance%20that%20it%20was%20something%20related%20to%20the%20unattended%20installer%20I've%20tried%20launching%20the%20upgrade%20through%20the%20GUI%20setup%20and%20it%20is%20now%20successfully%20performing%20the%20upgrade.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2800246%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20September%202021%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2800246%22%20slang%3D%22en-US%22%3E%3CP%3EA%20bit%20of%20encouraging%20news.%20We%20normally%20wait%20longer%20than%20the%20day%20a%20CU%20is%20released%20to%20install%20it....hoping%20to%20let%20others%20discover%20if%20there%20is%20fallout%20first.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThis%20time%2C%20we%20went%20for%20it%20and%20it%20was%20smooth%20sailing.%3C%2FP%3E%3CP%3ENow%20to%20read%20about%20the%20EM%20piece.%3C%2FP%3E%3CP%3E2019%20CU10%20to%20CU11.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2800347%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20September%202021%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2800347%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1025421%22%20target%3D%22_blank%22%3E%40ScottKnights%3C%2FA%3E%26nbsp%3BAs%20of%20now%2C%20we%20do%20not%20have%20anything%20to%20announce%20if%20there%20will%20be%20more%20E2016%20CUs.%20We%20made%20those%20announcements%20before.%20Then%20things%20changed.%20We%20will%20see!%20Always%2C%20the%20last%20two%20CUs%20are%20what%20is%20%22supported%22.%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F655075%22%20target%3D%22_blank%22%3E%40joeykins82%3C%2FA%3E%26nbsp%3BThanks%20for%20providing%20details%3B%20we%20just%20tried%20to%20reproduce%20this%20using%20the%20same%20builds%20you%20mentioned%2C%20and%20could%20not%2C%20hmm.%20Will%20keep%20looking!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2801257%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20September%202021%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2801257%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F5374%22%20target%3D%22_blank%22%3E%40Nino%20Bilic%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHi%20Nino%2C%20I%20just%20wanted%20to%20clarify%20which%20CUs%20are%20supported%20as%20the%20support%20policy%20for%20Exchange%20server%20stipulates%3A%3CBR%20%2F%3E%3CEM%3ECritical%20product%20updates%20are%20packages%20that%20address%20a%20Microsoft-released%20security%20bulletin%20or%20that%20contain%20a%20change%20in%20time%20zone%20definitions.%20When%20in%20Mainstream%20Support%2C%20critical%20product%20updates%20are%20released%20as%20needed%20on%20a%20monthly%20basis%20for%20the%20most%20recently%20released%20CU%20and%20for%20the%20immediately%20previous%20CU.%20%3CSTRONG%3EWhen%20in%20Extended%20Support%2C%20critical%20product%20updates%20are%20released%20as%20needed%20on%20a%20monthly%20basis%20for%20only%20the%20most%20recently%20released%20CU%3C%2FSTRONG%3E.%3C%2FEM%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThis%20was%20also%20stated%20again%20in%20this%20blog%20post%20about%20the%20end%20of%20Mainstream%20Support%20for%20Exchange%202016%3A%3CBR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fexchange-team-blog%2Fexchange-server-2016-and-the-end-of-mainstream-support%2Fba-p%2F1574110%22%20target%3D%22_blank%22%3Ehttps%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fexchange-team-blog%2Fexchange-server-2016-and-the-end-of-mainstream-support%2Fba-p%2F1574110%3C%2FA%3E%3C%2FP%3E%3CP%3E%3CEM%3E%3CSPAN%3EMicrosoft%20encourages%20Exchange%20Server%202016%20customers%20to%20adopt%20CU20%20as%20soon%20as%20possible%20to%20ensure%20uninterrupted%20delivery%20of%20any%20future%20security%20related%20fixes.%20After%20March%2016%2C%202021%2C%20only%20CU20%20or%20its%20successors%20will%20receive%20updates.%20During%20the%20Extended%20Support%20phase%2C%20only%20the%20latest%20CU%20is%20eligible%20to%20receive%20updates%20once%20the%26nbsp%3B%3C%2FSPAN%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fexchange-team-blog%2Fservicing-exchange-2013%2Fba-p%2F596398%22%20target%3D%22_blank%22%3Estandard%203%20month%20transition%3C%2FA%3E%3CSPAN%3E%26nbsp%3Bperiod%20of%20the%20prior%20CU%20has%20lapsed.%20%26nbsp%3B%3C%2FSPAN%3E%3C%2FEM%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThat%20is%20on%20this%20blog%20so%20is%20official%20information!%20Exchange%202016%20has%20been%20in%20Extended%20Support%20since%20last%20October.%20Can%20you%20please%20ensure%20that%20when%20any%20future%202016%20CUs%20are%20released%20(assuming%20any%20are)%20that%20you%20explicitly%20clarify%20which%20will%20receive%20critical%20updates.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2803765%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20September%202021%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2803765%22%20slang%3D%22en-US%22%3E%3CP%3EWhy%20does%20my%20Exchange%20shows%20two%20different%20things%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EExchange%3A%20Exchange%202016%20CU18%3C%2FSPAN%3E%3CBR%20%2F%3E%3CSPAN%3EBuild%20Number%3A%2015.1.2308.8%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EBuild%26nbsp%3B15.1.2308.8%20should%20be%20CU21%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EAt%20this%20point%20I%26nbsp%3Bdon't%20know%20If%20I%20should%20treat%20this%20as%20upgrade%20CU18%20-%26gt%3B%2022%20or%20CU21%20-%26gt%3B%20CU22%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2806621%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20September%202021%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2806621%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Team%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAt%20present%20we%20are%20on%20Exchange%202019%20CU9%2C%20can%20we%20install%20or%20go%20directly%20to%20CU11...%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ERegards%2C%3C%2FP%3E%3CP%3ESree%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2806663%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20September%202021%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2806663%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1102839%22%20target%3D%22_blank%22%3E%40Sreejith%3C%2FA%3E%26nbsp%3Byes%2C%20you%20can%20install%20CU11.%20Please%20note%20that%20PrepareSchema%20is%20required%20if%20CU9%20is%20your%20current%20version.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2807504%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20September%202021%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2807504%22%20slang%3D%22en-US%22%3E%3CP%3EHello%20Microsoft%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20note%20that%20these%20CUs%20include%20the%20fix%20for%20%3CEM%3E%22Exchange%20Server%202019%20and%202016%20certificates%20created%20during%20setup%20use%20SHA-1%20hash%20(KB5006983)%22%3C%2FEM%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EFor%20those%20SHA-1%20certificates%20that%20were%20previously%20created%20by%20Microsoft%20Exchange%2C%20what%20is%20the%20procedure%20to%20convert%20them%20to%20SHA-256%20%3F%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2807850%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20September%202021%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2807850%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F286871%22%20target%3D%22_blank%22%3E%40Sam_T%3C%2FA%3E%26nbsp%3Byou%20must%20recreate%2Frenew%20them.%20There%20is%20no%20way%20to%20convert%20the%20existing%20certificates%20to%20SHA256.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2808987%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20September%202021%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2808987%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1102839%22%20target%3D%22_blank%22%3E%40Sreejith%3C%2FA%3E%26nbsp%3BIn%20addition%20to%20what%20Lukas%20mentioned%20-%20please%20see%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Faka.ms%2Fexchangeupdatewizard%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Faka.ms%2Fexchangeupdatewizard%3C%2FA%3E%26nbsp%3B-%20we%20always%20update%20this%20to%20make%20sure%20that%20all%20the%20steps%20are%20listed%20when%20updating%20CUs.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2809101%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20September%202021%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2809101%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F164282%22%20target%3D%22_blank%22%3E%40Lukas%20Sassl%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%20for%20your%20response%20Lukas.%20So%20what%20is%20the%20Microsoft%20recommended%20procedure%20to%20recreate%20or%20renew%20the%26nbsp%3B%3CSPAN%3ESHA-1%20certificates%20that%20were%20previously%3CEM%3E%20created%20by%20Microsoft%20Exchange%3C%2FEM%3E%2C%20so%20that%20they%20are%20SHA-256%20%3F%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2809258%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20September%202021%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2809258%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F286871%22%20target%3D%22_blank%22%3E%40Sam_T%3C%2FA%3E%26nbsp%3Bthe%20steps%20to%20renew%20an%20Exchange%20certificate%20are%20described%20here%3A%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fexchange%2Farchitecture%2Fclient-access%2Frenew-certificates%3Fview%3Dexchserver-2019%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3ERenew%20an%20Exchange%20Server%20certificate%20%7C%20Microsoft%20Docs%3C%2FA%3E%26nbsp%3B.%20The%20issue%20which%20is%20fixed%20with%20the%20latest%20CU%20has%20only%20affected%20the%20certificates%20created%20during%20the%20initial%20Exchange%20installation.%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThe%20New-ExchangeCertificate%20cmdlet%20automatically%20generates%20certificates%20using%20SHA-256.%20You%20can%20also%20use%20the%20Exchange%20HealthChecker%20(%3CA%20href%3D%22https%3A%2F%2Faka.ms%2FExchangeHealthChecker%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Faka.ms%2FExchangeHealthChecker%3C%2FA%3E)%20to%20check%20the%20hash%20algorithm.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EEDIT%3A%3C%2FP%3E%0A%3CP%3EIf%20you%20create%20a%20new%20auth%20certificate%2C%20make%20sure%20to%20configure%20it%20as%20next%20certificate%20via%20Set-AuthConfig%20(%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fpowershell%2Fmodule%2Fexchange%2Fset-authconfig%3Fview%3Dexchange-ps%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3ESet-AuthConfig%20(ExchangePowerShell)%20%7C%20Microsoft%20Docs%3C%2FA%3E)%20or%20follow%20these%20steps%20if%20it%20has%20already%20expired%3A%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Faka.ms%2FHC-OAuthExpired%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Faka.ms%2FHC-OAuthExpired%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2811116%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20September%202021%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2811116%22%20slang%3D%22en-US%22%3E%3CP%3EI'm%20seeing%20my%26nbsp%3BMicrosoft%20Exchange%20Server%20Auth%20Certificate%20(and%20other%20cert)%20as%20SHA1.%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3Breading%20above%20makes%20me%20think%20I%20need%20to%20create%20new%20a%20new%20Auth%20cert%20as%20SHA256%20before%20applying%20CU22%20%3F%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2811695%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20September%202021%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2811695%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F420225%22%20target%3D%22_blank%22%3E%40jordanl17%3C%2FA%3E%26nbsp%3BNo%2C%20it's%20%3CSTRONG%3Eno%20requirement%3C%2FSTRONG%3E%20to%20re-create%20the%20Auth%20certificate%20if%20it's%20valid%20and%20using%20SHA1%20hash%20algorithm%20before%20applying%20CU22.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2812622%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20September%202021%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2812622%22%20slang%3D%22en-US%22%3E%3CP%3EHello%2C%3C%2FP%3E%3CP%3Ewe%20run%20two%20Edge%20Servers%20in%20a%20hybrid%20environment%20with%20two%20Exchange%20servers%20and%20since%20the%20upgrade%20to%20CU22%20I%20see%20these%20Eventlog%20Errors.%20Does%20anyone%20else%20have%20such%20errors%3F%20Nothing%20changed%20in%20certificates%20since%20upgrade%20to%20CU21.%20E-mail%20flow%20seems%20not%20to%20be%20affected.%20The%20requested%20certificate%20is%20the%20hostname%20for%20the%20Edge%20Server.%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22Peter_2021_0-1633434389599.png%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F315256iD533FD4361A65050%2Fimage-size%2Flarge%3Fv%3Dv2%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%22Peter_2021_0-1633434389599.png%22%20alt%3D%22Peter_2021_0-1633434389599.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2812956%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20September%202021%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2812956%22%20slang%3D%22en-US%22%3E%3CP%3EHas%20anyone%20with%20Exchange%20servers%20residing%20behind%20a%20NLB%20applied%20this%20CU%20yet%3F%20Curious%20to%20know%20if%20this%20months%20CU%20break%20OWA%20and%20ECP%20like%20July's%20did.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAll%20of%20our%20certificates%20were%20vailid%20and%20the%20session%20persistance%20workaround%20did%20not%20work%20for%20us%20in%20July.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2813346%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20September%202021%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2813346%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F164282%22%20target%3D%22_blank%22%3E%40Lukas%20Sassl%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EDo%20I%20need%20to%20run%20PrepareSchema%20if%20I%20am%20on%20Exchange%202019%20CU10....%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2813473%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20September%202021%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2813473%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1102839%22%20target%3D%22_blank%22%3E%40Sreejith%3C%2FA%3E%26nbsp%3BThere%20is%20no%20need%20to%20'%3CSPAN%3EPrepareSchema'%20going%20from%20Exchange%202019%20CU%3CSTRONG%3E10%3C%2FSTRONG%3E%20to%20CU%3CSTRONG%3E11%3C%2FSTRONG%3E.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3EThe%20document%20states%20%22These%20updates%20do%20not%20contain%20schema%20changes%22.%20I%20did%20exactly%20this%20update%20yesterday.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2813489%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20September%202021%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2813489%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1102839%22%20target%3D%22_blank%22%3E%40Sreejith%3C%2FA%3E%26nbsp%3Bas%20listed%20here%3A%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fexchange%2Fplan-and-deploy%2Factive-directory%2Fad-schema-changes%3Fview%3Dexchserver-2019%23exchange-2019-cu11-active-directory-schema-changes%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fexchange%2Fplan-and-deploy%2Factive-directory%2Fad-schema-changes%3Fview%3Dexchserver-2019%23exchange-2019-cu11-active-directory-schema-changes%3C%2FA%3E%26nbsp%3B%2C%20no%20Schema%20Update%20is%20required%20if%20your%20current%20version%20is%20CU10.%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThe%20Exchange%20Update%20Wizard%20show%20all%20required%20steps%3A%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Faka.ms%2Fexchangeupdatewizard%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Faka.ms%2Fexchangeupdatewizard%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2814681%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20September%202021%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2814681%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F5374%22%20target%3D%22_blank%22%3E%40Nino%20Bilic%3C%2FA%3E%26nbsp%3BThank%20you%2C%20Nino.%20The%20organization%20is%20going%20from%20Exchange%202019%20CU10%20to%20CU11%2C%20so%20based%20on%20your%20reply%2C%20the%20issues%20relating%20to%20the%20LB%20should%20not%20be%20experienced%20during%20this%20upgrade%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2814708%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20September%202021%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2814708%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F683542%22%20target%3D%22_blank%22%3E%40PatchesOhoulihan14%3C%2FA%3E%26nbsp%3BI'm%20sorry%2C%20that%20was%20incorrect!%20(I%20have%20now%20edited%20my%20reply%20to%20you%20above%20so%20it%20does%20not%20confuse%20someone%20else)%3A%3C%2FP%3E%0A%3CP%3EThe%20change%20that%20caused%20the%20LB%20behavior%20was%20introduced%20in%20July%20Security%20Update%20(SU).%20So%20if%20the%20organization%20is%20coming%20from%20(any%20CU%20that%20supported%20July%20SU)%20%2B%20July%20SU%20-%20then%20there%20should%20be%20no%20LB%20problem.%20But%20if%20you%20are%20coming%20from%20straight%20up%20June%20CU%20(without%20any%20later%20SUs)%20then%20you%20are%20likely%20going%20to%20see%20the%20LB%20problem%20because%20the%20new%20CUs%20are%20the%20first%20CUs%20now%20to%20have%20this%20security%20change%20%22baked%20in%22.%3C%2FP%3E%0A%3CP%3EHope%20this%20makes%20sense%3F!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2814828%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20September%202021%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2814828%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F5374%22%20target%3D%22_blank%22%3E%40Nino%20Bilic%3C%2FA%3E%26nbsp%3BYes%2C%20thank%20you.%20We%20are%20coming%20straight%20from%20CU10%20with%20the%20latest%20SU's%20installed.%20So%2C%20we%20should%20not%20experience%20the%20LB%20issue%20again.%20Appreicate%20your%20quick%20response!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2814611%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20September%202021%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2814611%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F683542%22%20target%3D%22_blank%22%3E%40PatchesOhoulihan14%3C%2FA%3E%26nbsp%3BIf%20the%20organization%20is%20coming%20from%20pre%20July%202021%20SU%20then%20I%20would%20expect%20the%20behavior%20of%20going%20to%20September%202021%20CUs%20to%20be%20the%20same%20as%20going%20to%20July%20SUs.%20Once%20the%20organization%20is%20on%20July%2B%20SUs%2C%20they%20should%20not%20be%20seeing%20problems%20related%20to%20LB.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2825732%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20September%202021%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2825732%22%20slang%3D%22en-US%22%3E%3CP%3EHi.%20Just%20one%20quick%20question.%3C%2FP%3E%3CP%3EI%20read%20that%20t%3CSPAN%3Ehere%20is%20no%20need%20to%20'%3C%2FSPAN%3E%3CSPAN%3EPrepareSchema'%20going%20from%20Exchange%202016%20CU21%20to%20CU22.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3EDoes%20that%20mean%20that%20all%20that%20is%20needed%20is%20to%20install%20the%20IIS%20URL%20Rewrite%20msi%2C%20reboot%20and%20then%20run%20the%20CU22%20installer.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3EThere%20is%20noe%20need%20to%20run%20any%20%2FprepareAD%20or%20other%20commands%20before%20starting%20the%20installation.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3EPlease%20advise%20as%20even%20after%20reading%20comments%20several%20times%20and%20the%20release%20notes%20even%20more%20I%20don't%20really%20get%20it.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EI%20am%20running%20Hypbrid%20setup%20just%20as%20a%20sidenote.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EThanks%20in%20advance.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2825836%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20September%202021%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2825836%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F387929%22%20target%3D%22_blank%22%3E%40elindem%3C%2FA%3E%26nbsp%3Byou're%20right%20-%20there%20is%20no%20schema%20change%20when%20you%20update%20from%20Exchange%202016%20CU21%20(see%3A%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fexchange%2Fplan-and-deploy%2Factive-directory%2Fad-schema-changes%3Fview%3Dexchserver-2016%23exchange-2016-cu22-active-directory-schema-changes%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fexchange%2Fplan-and-deploy%2Factive-directory%2Fad-schema-changes%3Fview%3Dexchserver-2016%23exchange-2016-cu22-active-directory-schema-changes%3C%2FA%3E).%20However%2C%20there%20are%20changes%20in%20the%20directory%20(see%3A%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fexchange%2Fplan-and-deploy%2Fprepare-ad-and-domains%3Fview%3Dexchserver-2016%23exchange-2016-active-directory-versions%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fexchange%2Fplan-and-deploy%2Fprepare-ad-and-domains%3Fview%3Dexchserver-2016%23exchange-2016-active-directory-versions%3C%2FA%3E)%20which%20means%20that%20you%20must%20run%20%2FPrepareAD.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIf%20you're%20running%20Exchange%20on%20Server%202012%2C%20the%26nbsp%3B%3CEM%3EUpdate%20for%20Universal%20C%20Runtime%20in%20Windows%20(KB2999226)%26nbsp%3B%3C%2FEM%3Eis%20also%20a%20prerequisite%20(see%3A%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fexchange%2Fplan-and-deploy%2Fprerequisites%3Fview%3Dexchserver-2016%23exchange-2016-mailbox-servers-on-windows-server-2012-or-windows-server-2012-r2%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fexchange%2Fplan-and-deploy%2Fprerequisites%3Fview%3Dexchserver-2016%23exchange-2016-mailbox-servers-on-windows-server-2012-or-windows-server-2012-r2%3C%2FA%3E).%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Faka.ms%2Fexchangeupdatewizard%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Faka.ms%2Fexchangeupdatewizard%3C%2FA%3E%26nbsp%3Bcan%20help%20you%20to%20determine%20the%20requirements.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2825971%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20September%202021%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2825971%22%20slang%3D%22en-US%22%3E%3CP%3EThank%20you%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F164282%22%20target%3D%22_blank%22%3E%40Lukas%20Sassl%3C%2FA%3E%26nbsp%3B%20for%20your%20quick%20reply.%3C%2FP%3E%3CP%3EI%20am%20running%20on%20Windows%20server%202016%20by%20the%20way.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ECan%20you%20just%20confirm%20one%20more%20thing%20for%20me%20please%20as%20I%20think%20the%20guides%20and%20exchangeupdatewizard%20does%20not%20take%20in%20to%20consideration%20Hybrid%20setup%20and%20I%20find%20that%20very%20strange.%20There%20must%20be%20a%20bundle%20of%20people%20out%20there%20running%20Hybrid%20mode.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20%22thing%22%20then%2C%20I%20usually%20run%20these%20two%20commands%20when%20upgrading%20a%20CU%3A%3C%2FP%3E%3CP%3E%3CSPAN%3Esetup.exe%20%2FPrepareAD%20%2FTenantOrganizationconfig%3AC%3A%5Cscripts%5C0365oconfig.xml%20%2FIAcceptExchangeServerLicenseTerms%3C%2FSPAN%3E%3CBR%20%2F%3E%3CSPAN%3Esetup.exe%20%2FPrepareAD%20%2FIAcceptExchangeServerLicenseTerms%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3EAnd%20then%20I%20do%20a%20Azure%20AD%26nbsp%3BRefresh%20from%20Azure%20AD%20connect%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ECan%20you%20confirm%20that%20all%20these%20steps%20are%20still%20required%20going%20from%20CU21%20to%20CU22%20or%20can%20any%20of%20them%20be%20skipped.%3C%2FP%3E%3CP%3EReally%20appreciate%20your%20help.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2826222%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20September%202021%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2826222%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F387929%22%20target%3D%22_blank%22%3E%40elindem%3C%2FA%3E%26nbsp%3BIt's%20not%20required%20to%20run%20the%20PrepareAD%20command%20twice.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EE%3A%5CSetup.exe%20%2F%3CSTRONG%3EIAcceptExchangeServerLicenseTerms_DiagnosticDataON%3C%2FSTRONG%3E%20%2FPrepareAD%20%2FTenantOrganizationConfig%20C%3A%5CSource%5CMyTenantOrganizationConfig.xml%3CBR%20%2F%3E%3CSTRONG%3Eor%3C%2FSTRONG%3E%3CBR%20%2F%3EE%3A%5CSetup.exe%20%2F%3CSTRONG%3EIAcceptExchangeServerLicenseTerms_DiagnosticDataOFF%3C%2FSTRONG%3E%20%2FPrepareAD%20%2FTenantOrganizationConfig%20C%3A%5CSource%5CMyTenantOrganizationConfig.xml%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EShould%20do%20the%20job%20to%20prepare%20the%20AD.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2826747%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20September%202021%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2826747%22%20slang%3D%22en-US%22%3E%3CP%3EHello%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F164282%22%20target%3D%22_blank%22%3E%40Lukas%20Sassl%3C%2FA%3E%26nbsp%3B%26amp%3B%20Team%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EJust%20wanted%20a%20clarity%20here%20on%20the%20below%20point%2C%20does%20this%20mean%20we%20have%20to%20use%20%3CSTRONG%3E_DiagnosticDataON%20or%20OFF%26nbsp%3B%3C%2FSTRONG%3Ewith%20all%20the%20below%20switches.....%3F%3C%2FP%3E%3CP%3Esetup.exe%20%2FPrepareSchema%20%2FIAcceptExchangeServerLicenseTerms%3CBR%20%2F%3Esetup.exe%20%2FPrepareAD%20%2FIAcceptExchangeServerLicenseTerms%3CBR%20%2F%3Esetup.exe%20%2FPrepareDomain%20%2FIAcceptExchangeServerLicenseTerms%3CBR%20%2F%3Esetup.exe%20%2FPrepareAllDomains%20%2FIAcceptExchangeServerLicenseTermsswitches%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20thought%20it%20was%20only%20needed%20for%20the%20upgrade%20switch%20%22%3CSTRONG%3ED%3A%5Csetup.exe%20%2Fm%3Aupgrade%20%2FIAcceptExchangeServerLicenseTerms_DiagnosticDataON%20or%20OFF%22%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CUL%3E%3CLI%3EWe%20changed%20the%20unattended%20setup%20switch.%20The%20previous%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3CSTRONG%3E%2FIAcceptExchangeServerLicenseTerms%3C%2FSTRONG%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3Eswitch%20will%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3CEM%3Enot%3C%2FEM%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3Ework%20starting%20with%20the%20September%202021%20CUs.%20You%20now%20must%20use%20either%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3CSTRONG%3E%2FIAcceptExchangeServerLicenseTerms_DiagnosticDataON%3C%2FSTRONG%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3Eor%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3CSTRONG%3E%2FIAcceptExchangeServerLicenseTerms_DiagnosticDataOFF%3C%2FSTRONG%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3Efor%20unattended%20and%20scripted%20installs.%3C%2FLI%3E%3C%2FUL%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2827882%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20September%202021%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2827882%22%20slang%3D%22en-US%22%3E%3CP%3EHello%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F164282%22%20target%3D%22_blank%22%3E%40Lukas%20Sassl%3C%2FA%3E%26nbsp%3B-%20Do%20we%20have%20to%20run%20this%20command%26nbsp%3B%3CSPAN%3EE%3A%5CSetup.exe%20%2F%3C%2FSPAN%3E%3CSTRONG%3EIAcceptExchangeServerLicenseTerms_DiagnosticDataOFF%3C%2FSTRONG%3E%3CSPAN%3E%26nbsp%3B%2FPrepareAD%20%2FTenantOrganizationConfig%20C%3A%5CSource%5CMyTenantOrganizationConfig.xml%20for%20Exchange%20Hybrid%20CU%20update%20(First%20time%20updating%20since%20I%20configured%20Hybrid)%20or%20can%20we%20just%20run%20this%20from%20GUI%20without%20the%20parameters%3F%20If%20I%20did%2C%20do%20I%20also%20have%20to%20do%20the%20%2FPrepareSchema%20as%20well%3F%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EAlso%2C%20I%20am%20going%20from%20CU20%20to%20CU22.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2827879%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20September%202021%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2827879%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1102839%22%20target%3D%22_blank%22%3E%40Sreejith%3C%2FA%3E%26nbsp%3B%20The%20old%20switch%20(%3CSTRONG%3EIAcceptExchangeServerLicenseTerms)%20%3C%2FSTRONG%3Ewill%20no%20longer%20work%20with%20the%20latest%20CU.%26nbsp%3B%3CBR%20%2F%3EYou%20now%20must%20use%20either%26nbsp%3B%2FIAcceptExchangeServerLicenseTerms_DiagnosticDataON%26nbsp%3Bor%26nbsp%3B%2FIAcceptExchangeServerLicenseTerms_DiagnosticDataOFF%20(also%20for%20the%20commands%20you%20mentioned)%3CSTRONG%3E%3CBR%20%2F%3E%3C%2FSTRONG%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2833155%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20September%202021%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2833155%22%20slang%3D%22en-US%22%3E%3CP%3Efixed%20it%20out%20on%20my%20own%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2834320%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20September%202021%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2834320%22%20slang%3D%22en-US%22%3E%3CP%3EHi%3C%2FP%3E%3CP%3EI%20have%20read%20the%20release%20notes%20and%20all%20the%20posts%20here.%20But%20unfortunately%20not%20sure%20about%20the%20process.%3C%2FP%3E%3CP%3EWe%20are%20now%20in%20mixed%20environment%20Exchange%202013%20latest%20CU%2BSU%20in%20hybrid%20mode%20and%20Exchange%202019%20CU10%20%2B%20latest%20SU.%20And%20planning%20migration%20of%20mailboxes.%20And%20I%20have%20two%20main%20questions%2Ftopics%3C%2FP%3E%3COL%3E%3CLI%3EDo%20we%20need%20to%20use%20again%20%2FTenantOrganizationConfig%20parameter%20when%20going%20to%20Ex2019%20CU11%20(it%20was%20obviously%20done%20in%20the%20past%20with%20previous%20CU%20installation)%3F%3CBR%20%2F%3EMy%20understanding%20is%2C%20that%20it%20is%20not%20necessary%2C%20because%20we%20are%20not%20upgrading%20schema%2C%20right%3F%20There's%20no%20schema%20upgrade%20from%20CU10%20to%20CU11.%3C%2FLI%3E%3CLI%3EWe%20(Exchange%20admins)%20do%20not%20have%20any%20special%20AD%20rights.%20Will%20the%20old%20approach%20work%20-%20asking%20AD%20team%20to%20execute%20%2FPrepareAD%20and%20then%20we%20will%20run%20only%20the%20CU%20update%3F%20Or%20we%20need%20to%20be%20granted%20special%20AD%20permissions%20for%20the%20CU11%20installation%3F%20I%20guess%20the%20old%20approach%20will%20not%20work%2C%20based%20on%20the%20official%20release%20notes%20statement%3A%3CBR%20%2F%3E%3CEM%3EBecause%26nbsp%3B%3CSTRONG%3E%2FPrepareAD%3C%2FSTRONG%3E%20is%20triggered%20in%20Setup%2C%20if%20the%20user%20who%20initiates%20Setup%20isn't%20a%20member%20of%20Schema%20Admins%20and%20Enterprise%20Admins%2C%20the%20readiness%20check%20will%20fail%20and%20you%20receive%20the%20following%20error%20messages.%3C%2FEM%3E%3C%2FLI%3E%3C%2FOL%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2835487%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20September%202021%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2835487%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F324116%22%20target%3D%22_blank%22%3E%40The_Exchange_Team%3C%2FA%3E%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F164282%22%20target%3D%22_blank%22%3E%40Lukas%20Sassl%3C%2FA%3E%26nbsp%3B%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAfter%20upgrading%20from%20EX%202019%20CU9%20to%20CU11%20I%20saw%20a%20weird%20thing.%20The%203rd%20party%20Certificate%20I%20had%20assigned%20only%20to%20SMTP%20%26amp%3B%20IIS.%20But%20after%20completion%20of%20CU11%20upgrade%20the%20Certificate%20got%20assigned%20to%20all%204%20services%20IIS%2CPOP3%2CIMAP%20%26amp%3B%20SMTP%20automatically.%20I%20did%20not%20understand%20why%20did%20that%20happen.....%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%2C%3C%2FP%3E%3CP%3ESree%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2839123%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20September%202021%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2839123%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F324116%22%20target%3D%22_blank%22%3E%40The_Exchange_Team%3C%2FA%3E%26nbsp%3BDoes%20IIS%20URL%20Rewrite%20need%20to%20be%20installed%20on%20Edge%20Transport%20Servers%20or%20just%20Mailbox%20servers%20for%20Exchange%202016%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2853829%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20September%202021%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2853829%22%20slang%3D%22en-US%22%3E%3CP%3Eheres%20the%20error%20i%20get.%26nbsp%3B%20afterwards%20exch%20transport%2C%20notifications%20broker%2C%20health%20manager%2C%20or%20health%20manager%20recovery%20services%20won't%20start.%26nbsp%3B%20HELP!%26nbsp%3B%20It%20won't%20stop%20the%20services%20so%20CU22%20can%20install.%3C%2FP%3E%3CP%3EError%3A%3CBR%20%2F%3EThe%20following%20error%20was%20generated%20when%20%22%24error.Clear()%3B%3CBR%20%2F%3E%26amp%3B%20%24RoleBinPath%5CServiceControl.ps1%20-Operation%3ADisableServices%20-Roles%3A(%24RoleRoles.Replace('Role'%2C'').Split('%2C'))%20-SetupScriptsDirectory%3A%24RoleBinPath%3B%3CBR%20%2F%3E%26amp%3B%20%24RoleBinPath%5CServiceControl.ps1%20-Operation%3AStop%20-Roles%3A(%24RoleRoles.Replace('Role'%2C'').Split('%2C'))%20-IsDatacenter%3A(%5Bbool%5D%24RoleIsDatacenter)%3CBR%20%2F%3E%22%20was%20run%3A%20%22Microsoft.Exchange.Configuration.Tasks.ServiceStopFailureException%3A%20Service%20'MSExchangeDelivery'%20failed%20to%20stop%20due%20to%20error%3A'Cannot%20stop%20MSExchangeDelivery%20service%20on%20computer%20'.'.'.%20---%26gt%3B%20System.InvalidOperationException%3A%20Cannot%20stop%20MSExchangeDelivery%20service%20on%20computer%20'.'.%20---%26gt%3B%20System.ComponentModel.Win32Exception%3A%20The%20service%20cannot%20accept%20control%20messages%20at%20this%20time%3CBR%20%2F%3E---%20End%20of%20inner%20exception%20stack%20trace%20---%3CBR%20%2F%3Eat%20System.ServiceProcess.ServiceController.Stop()%3CBR%20%2F%3Eat%20Microsoft.Exchange.Management.Tasks.ManageSetupService.StopService(ServiceController%20serviceController%2C%20Boolean%20ignoreServiceStopTimeout%2C%20Boolean%20failIfServiceNotInstalled%2C%20Unlimited%601%20maximumWaitTime)%3CBR%20%2F%3E---%20End%20of%20inner%20exception%20stack%20trace%20---%3CBR%20%2F%3Eat%20Microsoft.Exchange.Configuration.Tasks.Task.ThrowError(Exception%20exception%2C%20ErrorCategory%20errorCategory%2C%20Object%20target%2C%20String%20helpUrl)%3CBR%20%2F%3Eat%20Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception%20exception%2C%20ErrorCategory%20category%2C%20Object%20target)%3CBR%20%2F%3Eat%20Microsoft.Exchange.Management.Tasks.ManageSetupService.StopService(ServiceController%20serviceController%2C%20Boolean%20ignoreServiceStopTimeout%2C%20Boolean%20failIfServiceNotInstalled%2C%20Unlimited%601%20maximumWaitTime)%3CBR%20%2F%3Eat%20Microsoft.Exchange.Management.Tasks.ManageSetupService.StopService(String%20serviceName%2C%20Boolean%20ignoreServiceStopTimeout%2C%20Boolean%20failIfServiceNotInstalled%2C%20Unlimited%601%20maximumWaitTime)%3CBR%20%2F%3Eat%20Microsoft.Exchange.Management.Tasks.StopSetupService.InternalProcessRecord()%3CBR%20%2F%3Eat%20Microsoft.Exchange.Configuration.Tasks.Task.%3CPROCESSRECORD%3Eb__91_1()%3CBR%20%2F%3Eat%20Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String%20funcName%2C%20Action%20func%2C%20Boolean%20terminatePipelineIfFailed)%22.%3C%2FPROCESSRECORD%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2856543%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20September%202021%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2856543%22%20slang%3D%22en-US%22%3E%3CP%3EI%20got%20the%20above%20services%20to%20start%2C%20got%20exchange%20out%20of%20maintenance%20mode%20and%20back%20online.%26nbsp%3B%20Still%20doesn't%20make%20sense%20CU22%20install%20won't%20stop%20MSExchangeDelivery%20service.%26nbsp%3B%26nbsp%3B%20This%20is%20Exchange%202016%20at%20CU21%20on%202012R2.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Co-Authors
Version history
Last update:
‎Sep 28 2021 08:48 AM
Updated by: