Released: April 2021 Exchange Server Security Updates

Published Apr 13 2021 10:01 AM 359K Views

Microsoft has released security updates for vulnerabilities found in:

  • Exchange Server 2013
  • Exchange Server 2016
  • Exchange Server 2019

These updates are available for the following specific builds of Exchange Server:

IMPORTANT: If manually installing security updates, you must install .msp from elevated command prompt (see Known Issues in update KB article).

  • Exchange Server 2013 CU23
  • Exchange Server 2016 CU19 and CU20
  • Exchange Server 2019 CU8 and CU9

Vulnerabilities addressed in the April 2021 security updates were responsibly reported to Microsoft by a security partner. Although we are not aware of any active exploits in the wild, our recommendation is to install these updates immediately to protect your environment.

These vulnerabilities affect Microsoft Exchange Server. Exchange Online customers are already protected and do not need to take any action.

For additional information, please see the Microsoft Security Response Center (MSRC) blog. More details about specific CVEs can be found in Security Update Guide (filter on Exchange Server under Product Family).

Two update paths are:

ExApril21SU01_1.jpg

Inventory your Exchange Servers

Use the Exchange Server Health Checker script, which can be downloaded from GitHub (use the latest release), to inventory your servers. Running this script will tell you if any of your Exchange Servers are behind on updates (CUs and SUs).

Update to the latest Cumulative Update

Go to https://aka.ms/ExchangeUpdateWizard and choose your currently running CU and your target CU. Then click the “Tell me the steps” button, to get directions for your environment.

ExApril21SU02.jpg

If you encounter errors during or after installation of Exchange Server updates

Make sure to follow the ExchangeUpdateWizard instructions and best practices for installation of updates carefully, including when to install using elevated command prompt. If you encounter errors during or after installation, see Repair failed installations of Exchange Cumulative and Security updates.

FAQs

My organization is in Hybrid mode with Exchange Online. Do I need to do anything?
While Exchange Online customers are already protected, the April 2021 security updates do need to be applied to your on-premises Exchange Server, even if it is used only for management purposes. You do not need to re-run the Hybrid Configuration Wizard (HCW) after applying updates.

Do the April 2021 security updates contain the March 2021 security updates for Exchange Server?
Yes, our security updates are cumulative. Customers who installed the March 2021 security updates for supported CUs can install the April 2021 security updates and be protected against the vulnerabilities that were disclosed during both months. If you are installing an update manually, do not double-click on the .msp file, but instead run the install from an elevated CMD prompt.

Is Microsoft planning to release April 2021 security updates for older (unsupported) versions of Exchange CUs?
No, we have no plans to release the April 2021 security updates for older or unsupported CUs. In March, we took unprecedented steps and released SUs for unsupported CUs because there were active exploits in the wild. You should update your Exchange Servers to supported CUs and then install the SUs. There are 47 unsupported CUs for the affected versions of Exchange Server, and it is not sustainable to release updates for all of them. We strongly recommend that you keep your environments current.

Can we use March 2021 mitigation scripts (like EOMT) as a temporary solution?
The vulnerabilities fixed in the April 2021 updates are different from those we fixed before. Therefore, running March 2021 security tools and scripts will not mitigate the vulnerabilities fixed in April 2021. You should update your servers as soon as possible. Please note that if March EOMT is ran after April updates are installed, it will mistakenly mention that systems are possibly vulnerable (As EOMT is not aware of April updates).

Do I need to install the updates on ‘Exchange Management Tools only’ workstations?
Servers or workstations running only Microsoft Exchange Management Tools (no Exchange services) do not need to apply these updates.

Why are there security updates two months in a row?
Microsoft regularly releases Exchange Server security updates on ‘patch Tuesday’. We are always looking for ways to make Exchange Server more secure. You should expect us to continue releasing updates for Exchange Server in the future. The best way to be prepared for new updates is to keep your environment current.

Is there no update for Exchange Server 2010?
No, Exchange 2010 is not affected by the vulnerabilities fixed in the April 2021 security updates.

Is there a specific order of installation for the April 2021 security updates?
We recommend that you update all on-premises Exchange Servers with the April 2021 security updates using your usual update process.

Known Issues

  1. After application of the Exchange Server April security update CMDlets executed against the Exchange Management Console using an invoked runspace might fail with the following error message: The syntax is not supported by this runspace. This can occur if the runspace is in no-language mode. Please see the following KB article: “The syntax is not supported by this runspace” error after installing April 2021 Exchange security u...
  2. Requesting free/busy information for a user in a different forest in a trusted cross-forest topology might fail with the following Autodiscover error: The remote server returned an error: (400) Bad Request. Please see the following KB article: "(400) Bad Request" error during Autodiscover for per-user free/busy in a trusted cross-forest topol...
  3. Administrator or Service accounts ending in symbol '$' might fail connecting to Exchange Management Shell or ECP. The only workaround at this time is to use accounts without the symbol '$' at the end of the name.

Major updates to this post:

  • 5/4: Edits to Known Issues section
  • 4/16: Added a Known Issues section
  • 4/14: Added info to March EOMT note and behavior after April updates are installed
  • 4/13: Changed download links to the KB article (has additional download information)
  • 4/13: Fixed a typo in the upgrade path graphics (to reflect correct CUs for Exchange Server 2019)

The Exchange Team

229 Comments
Occasional Contributor
@Nino Bilic @The_Exchange_Team Thank you for the nice information. We just wanted to make you aware that we are also having issues with the security update and remote powershell. This is the error that we are getting:

System.Management.Automation.RemoteException: The syntax is not supported by this runspace. This can occur if the runspace is in no-language mode.
It seems we are still waiting for an official response.
Occasional Visitor

We are using PRTG to monitor our Exchange Servers 2013 C23 and it can't do remote powershell with remote exchange management shell with the Exchange server after I installed the April Security update.

 

 

Microsoft

@niels haaijer - Yes, apply to Edge servers too

@Alex Sanin - There is a specifici FAQ about Hybrid in the post; but if you are running hybrid, you are running Exchange on-premises. If you are on CU23 for Exchange 2013, you simply need to either install the April update from Microsoft Update or if you are downloading it, you MUST install the update from the elevated CMD prompt. The KB article tells you what to do (in known issues) and download instructions tell you also. It should be ~30 minutes.

@Vinch_BE - yes, best is to reboot after done!

@FreakyNL - unknown at this time; we do have a repro of this and engineering is looking into it. Sorry, no better answer right now!

@Michael Hincapie @anthonytenherkel @JazDotKiwi650 @nickvp @GregS410 - at this time, I do not have an answer for you; I think based on error samples you have provided (thank you!), we have a good idea where to look; engineering has been engaged on this. 3rd party monitoring is something that we cannot test for in our test passes but still - if we have deliberately changed something here, we need to document it for sure. Consider this under investigation.

Senior Member

@Nino Bilic Do you know if we apply the April update and then update from Exchange CU19 to CU20, do we have to reapply the patch?

@Nino Bilic  @The_Exchange_Team 

I installed correct security patch on my Exchange and it messed ECP.  Not sure why it happened. 

Finally i could recover it using following link.

 

https://docs.microsoft.com/en-us/answers/questions/116565/event-id-1310-aspnet-40-exchange-2016.html

Microsoft

@nick_ap If you update the CU, you will need to install the April SU post CU20.

@Prashant_A-Rookie This can happen if the update was downloaded for manual installation and then .msp was double-clicked on (vs. installed from elevated CMD prompt). We are working on long term solution for this but until then, .msp MUST be installed from elevated CMD prompt!

Frequent Visitor
Senior Member

Is the patch applicable to Exchange Edge Servers as well?

@niels haaijer 

Yes. Tested on W2019 & Ex2019 CU9

Regular Visitor

Hey,

 

Since many of our customers reported the issues here. We wanted to communicate some more information to get this sorted faster.

 

@Nino Bilic 

PRTG is using Remote Powershell and accessing the Exchange Management Shell, which was reported as broken already. 

var credential = new PSCredential(user,pw);
var connectionInfo = new WSManConnectionInfo(false, server, port, "/Powershell", "http://schemas.microsoft.com/powershell/Microsoft.Exchange",                                                      credential)
System.Management.Automation.Runspace.Runspace = RunspaceFactory.CreateRunspace(connectionInfo);
Runspace.Open()

While the errormessage said something about Language Mode, we tried to adapt that. Sadly the System.Management.Automation.Runspaces.RunspaceFactory does not have a overload, which takes the arguments for a System.Management.Automation.Runspaces.InitialSessionState object, where you can adjust the Language Mode and a RunspaceConnectionInfo(specifically WSManConnectionInfo) object.

Once the Runspace is created, the Language Mode cannot be changed anymore.

 

Thanks,

Eugen Wilhelm (Paessler AG)

Established Member

When we had the issues I had removed the powershell virtual directories through powershell on both our servers and recreated them.

They oddly also showed powershell virtual directories on the back-end. Had removed those too.

Make new powershell virtual directories, but on the back-end the 'PowerShell' didn't show up as an application but just a regular folder. Recreated it, and it's application pool, based on working server.

 

PowerShell works now, but only as user w/o $ in account.

Frequent Visitor
Occasional Visitor

Sorry for such a basic question but can someone please verify for me to update procedure?  I am on Exchange 2013 CU23.

 

Step 1 - Do monthly security updates from Windows update. 

Step 2 - Manually download the MSP file and install from an elevated command prompt.

 

The point being there is a manual download and install for Exchange.  Simply running Windows Update is not enough.

 

Thanks!

Frequent Visitor

@FreakyNL , @The_Exchange_Team 

I have both exchange 2016 and 2019 servers.

Edge server is 2016, the edge server's exchange tool box works just fine with $ account. (The user's name and display name does not have $, the server is in DMZ, a separate domain)

Both exchange mailbox server 2016 and 2019's  exchange toolbox does not work when used with $ account (this account's name and display name has $, it still does not work even after I changed name and display name)

Both exchange mailbox server 2016 and 2019's  exchange toolbox works when used an account with $.

I re-installed the patch to one of exchange 2016 and 2019 each, and tested, the behavior is the same.

 

Because our organization does not allow PowerShell to be executed remotely, I can't test the PowerShell remote-ability.

All exchange mailbox server 2016 and 2019's local powershell works even if I used $ account.

 

 

 

 

Frequent Visitor

I don't know why I can't edit my post but the previous one has misinformation/typo, so here we go again.

 

@FreakyNL , @The_Exchange_Team 

I have both exchange 2016 and 2019 servers.

Edge server is 2016, the edge server's exchange tool box works just fine with $ account. (The user's name and display name does not have $, the server is in DMZ, a separate domain)

Both exchange mailbox server 2016 and 2019's  exchange toolbox does not work when used with $ account (this account's name and display name has $, it still does not work even after I changed name and display name)

Both exchange mailbox server 2016 and 2019's  exchange toolbox works when used an account w/o $.

I re-installed the patch to one of exchange 2016 and 2019 each, and tested, the behavior is the same.

 

Because our organization does not allow PowerShell to be executed remotely, I can't test the PowerShell remote-ability.

All exchange mailbox server 2016 and 2019's local powershell works even if I used $ account.

Frequent Visitor

@The_Exchange_Team @FreakyNL 

 

The problem got fixed after simply changing the $ account ID. For example changing johnd$ to john.doe fixed the issue.

 

 

Occasional Visitor

Hello,

 

I tried this update on Exchange Server 2019 with the latest CU and it worked just fine, but unfortunately..

 

I applied the patch for Exchanger Server 2016 with CU19 installed on a Windows Server 2012 R2, but the server broke:

 

- All Exchange sevices seem to be running, but no one can connect to the Exchange server with their Outlook clients

- The ECP/OWA logins are "successful but show only a blank page

- Starting the Exchange Management Shell gives a lot of error messages and can not find any exchange server(s) on any site. Parts of the error messages:

 

VERBOSE: Connecting to bla.blaaa.net.
New-PSSession : [bla.blaaa.net] Connecting to remote server bla.blaaa.net failed with the follo
wing error message : [ClientAccessServer=BLA,BackEndServer=ebla.blaaa.net,RequestId=aff1b744-4ccd
-434c-ba90-29bec457cc17,TimeStamp=2021-04-14 16:25:16] [FailureCategory=Cafe-SendFailure] For more information, see th
e about_Remote_Troubleshooting Help topic.
At line:1 char:1
+ New-PSSession -ConnectionURI "$connectionUri" -ConfigurationName Microsoft.Excha ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin
gTransportException
+ FullyQualifiedErrorId : -2144108477,PSSessionOpenFailed
WARNING: No Exchange servers are available in the Active Directory site my-site. Connecting to an Exchange server in
another Active Directory site.

VERBOSE: Connecting to bla.blaaa.net.
New-PSSession : [bla.blaaa.net] Connecting to remote server bla.blaaa.net failed with the follo
wing error message : [ClientAccessServer=BLA,BackEndServer=bla.blaaa.net,RequestId=33fd0e97-f88e
-4a91-a6d6-e7bcaae62ee5,TimeStamp=2021-04-14 16:25:26] [FailureCategory=Cafe-SendFailure] For more information, see th
e about_Remote_Troubleshooting Help topic.
At line:1 char:1
+ New-PSSession -ConnectionURI "$connectionUri" -ConfigurationName Microsoft.Excha ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin
gTransportException
+ FullyQualifiedErrorId : -2144108477,PSSessionOpenFailed
Failed to connect to an Exchange server in the current site.

 

The installation did not encounter any problems at all and went "fine".

 

Any clues?

Frequent Visitor

@John_Smirnoff 

Did you manually download the MSP file and installed from an elevated command prompt?

 

Occasional Visitor
Regular Visitor

    Anyone actually have a success, without these issues or are they constant? Can anyone note what they may have done differently in this post to install and make the install success without these issues? We are planning on upgrading to CU19 over the next couple of days on our 4 node cluster. Then we will install the security patch pending any workarounds for ALL the issues found in this blog.

 

MICROSOFT: Your assistance would be appreciated here. You have many Exchange admin's frustrated and worried about the install of the patch. 

 

NOTES:
-Related to CU19 vs CU 20, doesn;t seem to matter. These issues occur on each.
-I think we all know now to install via Elevated cmd
-Edge servers need the patch as well
-If on CU19 and you install the patch, and updating to CU20, the CU20 paytch will need to be installed. = Nino Bilic

 

Seems pretty consistent, this patch created problems in the following areas

1. FreakyNL = If $ is in the Username = "Copied my admin account to one without $ in the names - problems be gone"
2. FreakyNL = "Admin account (only have one w/o a mailbox here I'm afraid) on either /owa or /ecp throws 'Cannot serialize context'" Seems to be if the Admin account doesn't have a mailbox. Arbitration mailbox has been mentioned as a potential.
3. FreakyNL = "Start exchange management shell doesn't work" Not sure if this is specificly because the admin account has a mailbox
4. Multiple people with Exchange Toolbox issues as well. .NET assembelies have been mentioned = FreakyNL
5. GregS410 = "something is up with the ability to remotely monitor Exchange 2016" Seems to affect many monitoring products such as PRTG
6. Prashant_A-Rookie = ECP issue may be resolved by https://docs.microsoft.com/en-us/answers/questions/116565/event-id-1310-aspnet-40-exchange-2016.html. Anyone else try this?

Visitor

Is this a patch that can be installed like a regular windows update patch or is it more like a CU where the server will need downtime while the patch installs?

Regular Visitor

@Nino Bilic @The_Exchange_Team Looks like a few different problems at once

 

I see advice to remove and re-add Powershell virtual directory - does this fix the remote powershell/third party monitoring tool issue that affects us, or just the ECP issue which is not what I am seeing.

 

Also, recreating Powershell virtual directory looks more complicated on a single server lab node because its a single server.

 

I had initially installed via Windows Update powershell run from a powershell admin window.   I tried the uninstall and reinstall by downloading the .msp and installing from command prompt admin window.   no difference.

 

Hopefully this will be resolved soon, it looks like a high risk update, but breaking monitoring will cause its own problems.

 

Thanks for everyones help with this

 

Greg

 

 

Frequent Visitor

@John_Smirnoff 

If outlook can't connect, if I were you, I would delete the C: and reinstall the OS, fully patch it, give the same computer name, reconnect exchange data and log disks and assign original drive letters, and install exchange in recovery mode using the latest CU. It can be done in a few hours.

Making sure users can use email is top priority in my mind, other than waiting for M$ to fix the issue as it seems they don't have a QA department anymore.

 

Frequent Visitor

@RWhitmire 

It requires a downtime.

In my case,

Exchange 2016 edge took 10 min.

Exchange 2016 mailbox took 45 min

Exchange 2019 mailbox took 1 hour to apply the patch.

While it is applied yes exchange was down, and once it is done. you have to reboot the server.

 

 

Frequent Visitor

@ewilhelm_paessler 

Hi there, In case this helps you I've been able to make our inhouse Exchange admin tool work with remote powershell.

I did nothing to change the setup of the runspace but changed the way powershell commands are executed and it appears to be working.

Using AddCommand() instead of AddScript()

 

Example code that is not working:

Powershell ps = GetPowerShellInstance();

ps.AddScript("Get-Mailbox -identity 'testuser@contoso.com'");

Collection<PSObject> collection = ps.Invoke();

 

Example code that is working:

Powershell ps = GetPowerShellInstance();

ps.AddCommand("Get-Mailbox");

ps.AddParameter("Identity","testuser@contoso.com");

Collection<PSObject> collection = ps.Invoke();

 

I hope this is helpful for others.

 

 

 

Occasional Visitor

Thank you for the suggestions, but another problem is the hybrid environment which is a H*** to set up. We are considering different options, but we would appreciate a reply/a solution from MS very VERY much.

Senior Member

Thanks @Nino Bilic I installed patches on 3 node cluster Exchange 2013 last night and so far so good.

 

@jeffc1670 go to https://aka.ms/ExchangeUpdateWizard and it will tell you the steps to update Exchange 2013 CU23

 

if you have applied March security patch then you may have installed net framework 4.8 so you can skip that.

 

Don't get download from windows update.  Download the patch, use elevated command prompt to run patch .MSP.

 

Additional step that I did before installing patch is to stop ALL Exchange services manually.  during the patch install, I also keep checking the service to make sure the service doesn't restart automatically.

 

It took me about 1 hour per server.

Occasional Visitor

Another frustrated engineer here.

Microsoft Exchange update KB5001779 broke the PRTG DAG sensor.....

 

The sensor was able to connect to the device using Remote PowerShell but could not retrieve access to Remote Exchange Management Shell. Ensure that remote management is enabled on the Exchange Server and the user has sufficient rights. See https://kb.paessler.com/en/topic/54353 for details. The syntax is not supported by this runspace. This can occur if the runspace is in no-language mode.

Microsoft

@-MeandExchange (for some reason I can't tag you?) - there have been tons of people who applied updates by now. Every time we release any kind of update (Su or CU) there is discussion here in blog comments about issues that come up. Every time.

@GregS410 and @Caspian - I got no updates as of now about 3rd party monitoring solutions that might be broken; we understand that this is important to folks. We have a few support tickets in play on this now, and they are sitting with someone who will be able to debug this problem. We'd call this 'under investigation' then. No workarounds or other ideas as of yet.

Regular Visitor

Thanks @Nino Bilic 

 

I just submitted a PSS case as well - hopefully this will get linked to the others.

Visitor

After installing this update ems stops working for managed service accounts, so we have to switch back to regular users that have no automatic password management, which is bad. You cannot remove $ from managed account username, since install-adserviceaccount cannot find it after such change. This affects exchange 2013|2016|2019. Is there a fix for it?

Occasional Visitor

Do i need to put exchange server into maintenance before installing the SU for CU23? 

any ideas?

Regular Visitor

@Nino Bilic  Probably because the "-" in the name. 

 

Discussion, yes.. But these types of issue among this many Exchange admin's no. I'm concerned to have these same issues even when following the proper procedure. Looking for additional ways to mitigate risk. Your attention is appreciated.  

Senior Member

@Tbrian5  put in maintenance mode will be safer.  putting the Exchange Server into the maintenance mode avoid any disconnectivity issues from the clients perspective and a seamless upgrade/update.

Occasional Visitor

After many hours of troubleshooting and finding tons of errors (maybe because of our setup nad the patch??) we managed to "solve"the problem somehow, so forget about my issues. Time to hit the bed.

Microsoft

@Vgubin - as of now, we do not have workaround for either the accounts with "$" in the name or certain 3rd party monitoring solutions that cannot connect to Exchange PS/ECP after April updates.

Frequent Visitor

@Nino Bilic 

 

This from the FAQ seems conflicting to me:

 

My organization is in Hybrid mode with Exchange Online. Do I need to do anything?
While Exchange Online customers are already protected, the April 2021 security updates do need to be applied to your on-premises Exchange Server, even if it is used only for management purposes.

 

Do I need to install the updates on ‘Exchange Management Tools only’ workstations?
Servers or workstations running only Microsoft Exchange Management Tools (no Exchange services) do not need to apply these updates.

 

As I said before, I have an Exchange lite (Exchange Express) install because it's hybrid, literally it's just got management tools on it (no exchange services)

Occasional Visitor

Bricked Exchange 2016. Rebooted, updates removed, all Exchange services disabled. All were re enabled and

Currently trying to fix the transport service.

Microsoft

@luke_q7 Thing is - there is no such thing as "Exchange express". If your organization is in fact in Hybrid, then you have an Exchange Server on-premises. I take it you use it for management, right? Which means that EAC, or Exchange PowerShell have to connect somewhere on-premises. So Exchange services and IIS virtual directories are running somewhere. Now, you could also have a "Management tools only" machine which only has Exchange Management Tools installed, but in that case, those management tools still need somewhere on-premises to connect to.

I am making an assumption here that you run Exchange Admin Center and/or PowerShell on-premises? If yes - there is Exchange Server somewhere. That is the machine that needs updating if you are in hybrid.

Frequent Visitor

@Nino Bilic

Thanks, I guess when I say Exchange express, I meant there is no mailboxes, no DAGs etc, literally just for management purposes but yes, it is running IIS etc.

When I tried to update the CU in March from 16 to 19 (20 just arrived - I tired that too), it went on and on about no mailboxes (correct)- mailbox server role not installed, that's because everything is O365, and also issues around not being able to talk to AD (doesn't exist or can't be contacted) - probably because AD hadn't been extended.

Regular Visitor

Also issue with management shell and account using $ in the username.  I don't want to rename my account, so I guess we wait for a fix.

Occasional Contributor

@Nino BilicThank you for all the information provided and for being proactive.  Just wanted to clarify that our issue with the following error is not related to the 3rd Party Monitoring Tools but with our custom tool we have. So it seems something change in the process of remote management. hope this helps. Please let us know if you need more information.

System.Management.Automation.RemoteException: The syntax is not supported by this runspace. This can occur if the runspace is in no-language mode.



Contributor

To give positive comments I can say, that I have pathed Exchange Server 2016 CU19 with the latest security update and it was a success. No issues found afterwards. .MSP ran from elevated command prompt.

Established Member

@John_Smirnoff 

Perhaps something went wrong with the web part.

Did you run from evelated prompt like alex kim said? Otherwise run it again from elevated prompt and if it doesn't work then there's a UpdateCAS.ps1 in the bin folder of the exchange installation. Try running that and see if things improve. You can run it from regular (admin) powershell.

 

@-MeandExchange 

Yes, multiple environments without issues, all of them after renaming accounts with $ in them and fixing powershell I broke whilst troubleshooting. The environment with issues I removed and recreated powershell VDs, oddly those servers showed a VD for powershell on both the front-end and the back-end. Removing the back-end one broke some things in IIS I presume (application pool was gone and the 'powershell' on back-end showed up as a folder instead of an application). Threw the same error code in Management Shell as with $ accounts. After recreating the IIS config manually it started working (w/o $ in account then, still doesn't with $). It's not related to the account not having a mailbox.

 

@GregS410 I thought issue might stem from some non-default config on the powershell VDs (mostly them appearing on back-end too - someone might have created them by accident). If it comes from me, I'd let it be, our issues came solely from $ in account.

Regular Visitor

There’s any workaground or mitigation for those cve ? i’m using F5 for load balancer and trendmicro for endpoint (IPS included). I cannot update security right away for reason. Please advice.

Occasional Visitor

Is the exchange 2019 version number supposed to bump up after the patch installation?

Mine is still CU9 version number (I think)

AdminDisplayVersion : Version 15.2 (Build 858.5)
ExchangeVersion : 0.1 (8.0.535.0)

 

Frequent Visitor

@Nino Bilic, we had an issue after installing the patch on our Windows Server 2012r2 box with Exchange 2013 where %ExchangeInstallDir% wasn't expanded to the full path in any of the web.config files, with the result that assemblies wasn't loading.

We fixed this by running a find/replace to manually change to full paths in the config files.

Microsoft

@ngtlam1806 - we have not released any mitigations for those particular CVEs, no.

@boredoutofmyskull - no, the version change will not be different after SU; you can either check add/remove (the update will show there under update to the current CU) or the Health Checker script.

Occasional Visitor

All of my mailboxes are in the cloud, when can we (officially) get rid of this on prem server permanently? Skype/Teams did not require us to KEEP an on prem server to manage AD objects once moved to the cloud in hybrid AD mode, why does exchange?

 

FYI: I am aware that we can technically get rid of it and edit AD objects directly but it is not a supported config.

Regular Visitor

Can you clarify a point on EX 2013 CU23. Your wizard says installs .Net 4.8 yet the Comparability Matrix says both 4.7.2 and 4.8 are support.  

Any issues with installing .Net 4.8 on top of CU 23? , is it REQUIRED for this April patch?  No issues in previous months with .Net 4.7.2 (I know, I know easy upgrade just reviewing options)

 

If it is required, can you update the KB to reflect the system requirement 

Microsoft

@David__G - Yeah, we hear you. No immediate news or announcements but we heard this loud and clear.

@KrisHappe - Unclear what you mean; I mean the ExchangeUpdateWizard will suggest to install the 'latest' if you are going from older version to CU23; it would not really make sense to suggest installation of older version? You are correct that both are supported in this scenario. And no, upgrade of .NET is NOT needed to install the April update. The wizard is really geared to be the "steps to update from older unsupported CU to latest supported CU" because once you are on latest CU, you can simply install the update (via MU or manually, from elevated CMD prompt).

After this update our support tool does not work any more. We run a exchange 2016 server, and the tool does a simple:

 

 

        public void SearchExchangeMailBox()
        {
           
            PSCredential cred = new PSCredential(ADtoolUserName, ADtoolUserPassword);
            WSManConnectionInfo connectionInfo = new WSManConnectionInfo(new Uri("http://exch01/powershell?serializationLevel=Full"), "http://schemas.microsoft.com/powershell/Microsoft.Exchange", cred);
            connectionInfo.AuthenticationMechanism = AuthenticationMechanism.Kerberos;




                using (Runspace runspace = RunspaceFactory.CreateRunspace(connectionInfo))
                {

                        using (PowerShell powershell = PowerShell.Create())
                        {

                            powershell.AddScript("Get-Mailbox " + SelectedUsername + "*");
                            runspace.Open();
                            powershell.Runspace = runspace;

                            Collection<PSObject> results = powershell.Invoke();
                            foreach (ErrorRecord err in powershell.Streams.Error)
                            {
                                MessageBox.Show("Error");
                                MessageBox.Show(err.ToString());
                            }

 

 

But that now throws a error now. Nothing has change on our part. 

System.Management.Automation.RemoteException: The syntax is not supported by this runspace. This can occur if the runspace is in no-language mode.
   ved System.Management.Automation.Runspaces.AsyncResult.EndInvoke()
   ved System.Management.Automation.PowerShell.CoreInvokeRemoteHelper[TInput,TOutput](PSDataCollection`1 input, PSDataCollection`1 output, PSInvocationSettings settings)
   ved System.Management.Automation.PowerShell.CoreInvoke[TInput,TOutput](PSDataCollection`1 input, PSDataCollection`1 output, PSInvocationSettings settings)
   ved System.Management.Automation.PowerShell.Invoke(IEnumerable input, PSInvocationSettings settings)
   ved ADTool.MainForm.SearchExchangeMailBox()
   ved ADTool.MainForm.searchBtn_Click(Object sender, EventArgs e)
   ved System.Windows.Forms.Control.OnClick(EventArgs e)
   ved System.Windows.Forms.Button.OnClick(EventArgs e)
   ved System.Windows.Forms.Button.PerformClick()
   ved ADTool.MainForm.searchBox_KeyUp(Object sender, KeyEventArgs e)
   ved System.Windows.Forms.Control.OnKeyUp(KeyEventArgs e)
   ved System.Windows.Forms.Control.ProcessKeyEventArgs(Message& m)
   ved System.Windows.Forms.Control.WmKeyChar(Message& m)
   ved System.Windows.Forms.Control.WndProc(Message& m)
   ved System.Windows.Forms.TextBox.WndProc(Message& m)
   ved System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
%3CLINGO-SUB%20id%3D%22lingo-sub-2254617%22%20slang%3D%22en-US%22%3EReleased%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2254617%22%20slang%3D%22en-US%22%3E%3CP%3EMicrosoft%20has%20released%20security%20updates%20for%20vulnerabilities%20found%20in%3A%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3EExchange%20Server%202013%3C%2FLI%3E%0A%3CLI%3EExchange%20Server%202016%3C%2FLI%3E%0A%3CLI%3EExchange%20Server%202019%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3EThese%20updates%20are%20available%20for%20the%20following%20specific%20builds%20of%20Exchange%20Server%3A%3C%2FP%3E%0A%3CP%20class%3D%22note%22%3E%3CFONT%20color%3D%22%23FF0000%22%3E%3CSTRONG%3EIMPORTANT%3A%3C%2FSTRONG%3E%3C%2FFONT%3E%20If%20manually%20installing%20security%20updates%2C%20you%20%3CEM%3Emust%3C%2FEM%3E%20install%20.msp%20from%20elevated%20command%20prompt%20(see%20Known%20Issues%20in%20update%20KB%20article).%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3EExchange%20Server%202013%20%3CA%20href%3D%22https%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Ftopic%2Fdescription-of-the-security-update-for-microsoft-exchange-server-2019-2016-and-2013-april-13-2021-kb5001779-8e08f3b3-fc7b-466c-bbb7-5d5aa16ef064%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%22%3ECU23%3C%2FA%3E%3C%2FLI%3E%0A%3CLI%3EExchange%20Server%202016%20%3CA%20href%3D%22https%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Ftopic%2Fdescription-of-the-security-update-for-microsoft-exchange-server-2019-2016-and-2013-april-13-2021-kb5001779-8e08f3b3-fc7b-466c-bbb7-5d5aa16ef064%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%22%3ECU19%3C%2FA%3E%20and%20%3CA%20href%3D%22https%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Ftopic%2Fdescription-of-the-security-update-for-microsoft-exchange-server-2019-2016-and-2013-april-13-2021-kb5001779-8e08f3b3-fc7b-466c-bbb7-5d5aa16ef064%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%22%3ECU20%3C%2FA%3E%3C%2FLI%3E%0A%3CLI%3EExchange%20Server%202019%20%3CA%20href%3D%22https%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Ftopic%2Fdescription-of-the-security-update-for-microsoft-exchange-server-2019-2016-and-2013-april-13-2021-kb5001779-8e08f3b3-fc7b-466c-bbb7-5d5aa16ef064%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%22%3ECU8%3C%2FA%3E%20and%20%3CA%20href%3D%22https%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Ftopic%2Fdescription-of-the-security-update-for-microsoft-exchange-server-2019-2016-and-2013-april-13-2021-kb5001779-8e08f3b3-fc7b-466c-bbb7-5d5aa16ef064%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%22%3ECU9%3C%2FA%3E%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3EVulnerabilities%20addressed%20in%20the%20April%202021%20security%20updates%20were%20responsibly%20reported%20to%20Microsoft%20by%20a%20security%20partner.%20Although%20we%20are%20not%20aware%20of%20any%20active%20exploits%20in%20the%20wild%2C%20our%20recommendation%20is%20to%20install%20these%20updates%20immediately%20to%20protect%20your%20environment.%3C%2FP%3E%0A%3CP%3EThese%20vulnerabilities%20affect%20Microsoft%20Exchange%20Server.%20Exchange%20Online%20customers%20are%20already%20protected%20and%20do%20not%20need%20to%20take%20any%20action.%3C%2FP%3E%0A%3CP%3EFor%20additional%20information%2C%20please%20see%20the%20%3CA%20href%3D%22https%3A%2F%2Faka.ms%2FApril2021SecUpdate%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3EMicrosoft%20Security%20Response%20Center%20(MSRC)%20blog%3C%2FA%3E.%20More%20details%20about%20specific%20CVEs%20can%20be%20found%20in%20%3CA%20href%3D%22https%3A%2F%2Fmsrc.microsoft.com%2Fupdate-guide%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3ESecurity%20Update%20Guide%3C%2FA%3E%20(filter%20on%20Exchange%20Server%20under%20Product%20Family).%3C%2FP%3E%0A%3CP%3ETwo%20update%20paths%20are%3A%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-center%22%20image-alt%3D%22ExApril21SU01_1.jpg%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F272570i4E57FDA8EAA31649%2Fimage-size%2Flarge%3Fv%3Dv2%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%22ExApril21SU01_1.jpg%22%20alt%3D%22ExApril21SU01_1.jpg%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CH2%20id%3D%22toc-hId--493863912%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493863042%22%20id%3D%22toc-hId--493776548%22%3EInventory%20your%20Exchange%20Servers%3C%2FH2%3E%0A%3CP%3EUse%20the%20%3CA%20href%3D%22https%3A%2F%2Faka.ms%2FExchangeHealthChecker%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3EExchange%20Server%20Health%20Checker%20script%3C%2FA%3E%2C%20which%20can%20be%20downloaded%20from%20GitHub%20(use%20the%20latest%20release)%2C%20to%20inventory%20your%20servers.%20Running%20this%20script%20will%20tell%20you%20if%20any%20of%20your%20Exchange%20Servers%20are%20behind%20on%20updates%20(CUs%20and%20SUs).%3C%2FP%3E%0A%3CH2%20id%3D%22toc-hId-1993648921%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993649791%22%20id%3D%22toc-hId-1993736285%22%3EUpdate%20to%20the%20latest%20Cumulative%20Update%3C%2FH2%3E%0A%3CP%3EGo%20to%20%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%20and%20choose%20your%20currently%20running%20CU%20and%20your%20target%20CU.%20Then%20click%20the%20%E2%80%9CTell%20me%20the%20steps%E2%80%9D%20button%2C%20to%20get%20directions%20for%20your%20environment.%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-center%22%20image-alt%3D%22ExApril21SU02.jpg%22%20style%3D%22width%3A%20263px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F272473i034A30E80BAF99D7%2Fimage-size%2Flarge%3Fv%3Dv2%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%22ExApril21SU02.jpg%22%20alt%3D%22ExApril21SU02.jpg%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CH2%20id%3D%22toc-hId-186194458%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186195328%22%20id%3D%22toc-hId-186281822%22%3EIf%20you%20encounter%20errors%20during%20or%20after%20installation%20of%20Exchange%20Server%20updates%3C%2FH2%3E%0A%3CP%3EMake%20sure%20to%20follow%20the%20%3CA%20href%3D%22https%3A%2F%2Faka.ms%2FExchangeUpdateWizard%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3EExchangeUpdateWizard%3C%2FA%3E%20instructions%20and%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2FExchange%2Fplan-and-deploy%2Finstall-cumulative-updates%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ebest%20practices%20for%20installation%20of%20updates%3C%2FA%3E%20carefully%2C%20including%20when%20to%20install%20using%20elevated%20command%20prompt.%20If%20you%20encounter%20errors%20during%20or%20after%20installation%2C%20see%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fexchange%2Ftroubleshoot%2Fclient-connectivity%2Fexchange-security-update-issues%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3ERepair%20failed%20installations%20of%20Exchange%20Cumulative%20and%20Security%20updates%3C%2FA%3E.%3C%2FP%3E%0A%3CH1%20id%3D%22toc-hId-175691354%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175692224%22%20id%3D%22toc-hId-175778718%22%3EFAQs%3C%2FH1%3E%0A%3CP%3E%3CSTRONG%3E%3CEM%3EMy%20organization%20is%20in%20Hybrid%20mode%20with%20Exchange%20Online.%20Do%20I%20need%20to%20do%20anything%3F%3C%2FEM%3E%3C%2FSTRONG%3E%3CBR%20%2F%3EWhile%20Exchange%20Online%20customers%20are%20already%20protected%2C%20the%20April%202021%20security%20updates%20do%20need%20to%20be%20applied%20to%20your%20on-premises%20Exchange%20Server%2C%20even%20if%20it%20is%20used%20only%20for%20management%20purposes.%20You%20do%20%3CEM%3Enot%3C%2FEM%3E%20need%20to%20re-run%20the%20Hybrid%20Configuration%20Wizard%20(HCW)%20after%20applying%20updates.%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3E%3CEM%3EDo%20the%20April%202021%20security%20updates%20contain%20the%20March%202021%20security%20updates%20for%20Exchange%20Server%3F%3C%2FEM%3E%3C%2FSTRONG%3E%3CBR%20%2F%3EYes%2C%20our%20security%20updates%20are%20cumulative.%20Customers%20who%20installed%20the%20March%202021%20security%20updates%20for%20supported%20CUs%20can%20install%20the%20April%202021%20security%20updates%20and%20be%20protected%20against%20the%20vulnerabilities%20that%20were%20disclosed%20during%20both%20months.%20If%20you%20are%20installing%20an%20update%20manually%2C%20do%20not%20double-click%20on%20the%20.msp%20file%2C%20but%20instead%20run%20the%20install%20from%20an%20elevated%20CMD%20prompt.%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3E%3CEM%3EIs%20Microsoft%20planning%20to%20release%20April%202021%20security%20updates%20for%20older%20(unsupported)%20versions%20of%20Exchange%20CUs%3F%3C%2FEM%3E%3C%2FSTRONG%3E%3CBR%20%2F%3ENo%2C%20we%20have%20no%20plans%20to%20release%20the%20April%202021%20security%20updates%20for%20older%20or%20unsupported%20CUs.%20In%20March%2C%20we%20took%20unprecedented%20steps%20and%20released%20SUs%20for%20unsupported%20CUs%20because%20there%20were%20active%20exploits%20in%20the%20wild.%20You%20should%20update%20your%20Exchange%20Servers%20to%20supported%20CUs%20and%20then%20install%20the%20SUs.%20There%20are%2047%20unsupported%20CUs%20for%20the%20affected%20versions%20of%20Exchange%20Server%2C%20and%20it%20is%20not%20sustainable%20to%20release%20updates%20for%20all%20of%20them.%20We%20strongly%20recommend%20that%20you%20keep%20your%20environments%20current.%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3E%3CEM%3ECan%20we%20use%20March%202021%20mitigation%20scripts%20(like%20EOMT)%20as%20a%20temporary%20solution%3F%3C%2FEM%3E%3C%2FSTRONG%3E%3CBR%20%2F%3EThe%20vulnerabilities%20fixed%20in%20the%20April%202021%20updates%20are%20different%20from%20those%20we%20fixed%20before.%20Therefore%2C%20running%20March%202021%20security%20tools%20and%20scripts%20will%20%3CEM%3Enot%3C%2FEM%3E%20mitigate%20the%20vulnerabilities%20fixed%20in%20April%202021.%20You%20should%20update%20your%20servers%20as%20soon%20as%20possible.%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3E%3CEM%3EDo%20I%20need%20to%20install%20the%20updates%20on%20%E2%80%98Exchange%20Management%20Tools%20only%E2%80%99%20workstations%3F%3CBR%20%2F%3E%3C%2FEM%3E%3C%2FSTRONG%3EServers%20or%20workstations%20running%20only%20Microsoft%20Exchange%20Management%20Tools%20(no%20Exchange%20services)%20do%20not%20need%20to%20apply%20these%20updates.%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3E%3CEM%3EWhy%20are%20there%20security%20updates%20two%20months%20in%20a%20row%3F%3C%2FEM%3E%3C%2FSTRONG%3E%3CBR%20%2F%3EMicrosoft%20regularly%20releases%20Exchange%20Server%20security%20updates%20on%20%E2%80%98patch%20Tuesday%E2%80%99.%20We%20are%20always%20looking%20for%20ways%20to%20make%20Exchange%20Server%20more%20secure.%20You%20should%20expect%20us%20to%20continue%20releasing%20updates%20for%20Exchange%20Server%20in%20the%20future.%20The%20best%20way%20to%20be%20prepared%20for%20new%20updates%20is%20to%20keep%20your%20environment%20current.%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3E%3CEM%3EIs%20there%20no%20update%20for%20Exchange%20Server%202010%3F%3CBR%20%2F%3E%3C%2FEM%3E%3C%2FSTRONG%3ENo%2C%20Exchange%202010%20is%20not%20affected%20by%20the%20vulnerabilities%20fixed%20in%20the%20April%202021%20security%20updates.%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3E%3CEM%3EIs%20there%20a%20specific%20order%20of%20installation%20for%3C%2FEM%3E%3C%2FSTRONG%3E%3CSTRONG%3E%3CEM%3E%20the%20April%202021%20security%20updates%3F%3C%2FEM%3E%3C%2FSTRONG%3E%3CBR%20%2F%3EWe%20recommend%20that%20you%20update%20all%20on-premises%20Exchange%20Servers%20with%20the%20April%202021%20security%20updates%20using%20your%20usual%20update%20process.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3EMajor%20updates%20to%20this%20post%3A%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3E4%2F13%3A%20Changed%20download%20links%20to%20the%20KB%20article%20(has%20additional%20download%20information)%3C%2FLI%3E%0A%3CLI%3E4%2F13%3A%20Fixed%20a%20typo%20in%20the%20upgrade%20path%20graphics%20(to%20reflect%20correct%20CUs%20for%20Exchange%20Server%202019)%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%3CSPAN%20class%3D%22author%22%3EThe%20Exchange%20Team%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-2254617%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20are%20releasing%20a%20set%20of%20security%20updates%20for%20Exchange%20Server%202013%2C%202016%20and%202019.%3C%2FP%3E%3C%2FLINGO-TEASER%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2254617%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAnnouncements%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EExchange%202013%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EExchange%202016%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EExchange%202019%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EExchange%20Online%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESecurity%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2271051%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2271051%22%20slang%3D%22en-US%22%3E%3CP%3E!!!The%20upgrade%20patch%20cannot%20be%20installed%20by%20Windows%20Installer%20service%20because%20the%20program%20to%20be%20upgraded%20may%20be%20missing%2C%20or%20the%20upgrade%20patch%20may%20update%20q%20different%20version%20of%20the%20program.%20!!!%3CBR%20%2F%3E%3CBR%20%2F%3EWhat%20are%20prerequisites%20for%20thew%20patch%3F%3C%2FP%3E%3CP%3EWin%20Srv%202019%2C%20Exchange%202019%20CU9%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2271064%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2271064%22%20slang%3D%22en-US%22%3E%3CP%3EThank%20you%20for%20keeping%20up%20the%20update%20history%20for%20the%20OP.%3C%2FP%3E%3CP%3EAlso%20Kudos%20for%20the%20very%20comprehensive%20guidance%20and%20references%20how%20to%20check%20and%20apply%20patches%20correctly.%3C%2FP%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%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2271068%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2271068%22%20slang%3D%22en-US%22%3E%3CP%3ELast%20patch%20messed%20up%20the%20environment.%20Now%20this%20one%20does%20too.%3C%2FP%3E%3CP%3EIf%20I%20log%20on%20with%20a%20regular%20user%20account%20to%20%2Fowa%20it%20seems%20to%20work%20fine.%3C%2FP%3E%3CP%3EAdmin%20account%20(only%20have%20one%20w%2Fo%20a%20mailbox%20here%20I'm%20afraid)%20on%20either%20%2Fowa%20or%20%2Fecp%20throws%20'%3CSPAN%3ECannot%20serialize%20context'%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3EPowershell%20seems%20to%20have%20moved%20the%20DAG%20to%20the%20other%20server%20however.%20Now%20that%20the%20second%20one%20is%20patching%20I%20can't%20use%20the%20webinterface%20anymore%20though.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2271085%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2271085%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F790194%22%20target%3D%22_blank%22%3E%40vmilanov%3C%2FA%3E%26nbsp%3B-%20are%20you%20100%25%20sure%20that%20you%20got%20the%20update%20for%20the%20right%20CU%3F%20See%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fexchange%2Ftroubleshoot%2Fclient-connectivity%2Fexchange-security-update-issues%23upgrade-patch-cant-be-installed%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3ERepair%20failed%20installations%20of%20Exchange%20Cumulative%20and%20Security%20updates%20-%20Exchange%20%7C%20Microsoft%20Docs%3C%2FA%3E%26nbsp%3B(this%20links%20directly%20to%20that%20specific%20error).%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F977615%22%20target%3D%22_blank%22%3E%40FreakyNL%3C%2FA%3E%26nbsp%3B-%20can%20you%20elaborate%3F%20Do%20you%20mean%20access%20%2Fecp%20is%20permanently%20broken%20for%20admin%20account%20without%20a%20mailbox%20only%2C%20after%20the%20installation%20of%20March%20and%20April%20SUs%3F%20Or%20did%20this%20start%20happening%20after%20specific%20CU%3F%20What%20version%20of%20Exchange%3F%20I%20would%20not%20expect%20%2Fowa%20to%20work%2C%20BTW%20(because%20the%20account%20does%20not%20have%20a%20mailbox)...%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2271086%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2271086%22%20slang%3D%22en-US%22%3E%3CP%3EThank%20you%20for%20the%20great%20information.%20Here%20we%20go%20again!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2271095%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2271095%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3C%2FP%3E%3CP%3Edon't%20know.%20Don't%20have%20an%20admin%20account%20with%20a%20mailbox.%20Second%20server%20is%20running%20CU20%20update%20and%20KB%20after%20it.%20Will%20take%20a%20while.%3C%2FP%3E%3CP%3EStart%20exchange%20management%20shell%20doesn't%20work%2C%20throws%20errors.%20Will%20connect%20to%202010%20after%20attempting%20both%202016's.%3C%2FP%3E%3CP%3E%3CSPAN%3EAdd-PSSnapin%20Microsoft.Exchange.Management.PowerShell.SnapIn%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3Eseems%20to%20work%20though.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2271205%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2271205%22%20slang%3D%22en-US%22%3E%3CP%3EAfter%20Exchange%202016%20CU20%20on%20the%20other%20server%20%2Fecp%20and%20Exchange%20Management%20Shell%20still%20worked%20on%20the%20second%20server.%3C%2FP%3E%3CP%3EAfter%20installing%20the%20patch%20it%20broke%20on%20that%20server%20too.%3C%2FP%3E%3CP%3E%2Fowa%20and%20%2Fecp%20state%20'Cannot%20serialize%20context'%20whilst%20PowerShell%20throws%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CPRE%3ENew-PSSession%20%3A%20%5BSERVER2.domain.local%5D%20Connecting%20to%20remote%20server%20SERVER2%20failed%20with%20the%20following%20error%0Amessage%20%3A%20For%20more%20information%2C%20see%20the%20about_Remote_Troubleshooting%20Help%20topic.%0AAt%20line%3A1%20char%3A1%0A%2B%20New-PSSession%20-ConnectionURI%20%22%24connectionUri%22%20-ConfigurationName%20Micr%20...%0A%2B%20~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~%0A%2B%20CategoryInfo%20%3A%20OpenError%3A%20(System.Manageme....RemoteRunspace%3ARemoteRunspace)%20%5BNew-PSSession%5D%2C%20PSRemotin%0AgTransportException%0A%2B%20FullyQualifiedErrorId%20%3A%20-2144108477%2CPSSessionOpenFailed%3C%2FPRE%3E%3CP%3EFor%20both%20the%202016%20servers.%20It%20connects%20to%20the%20Exchange%202010%20that's%20still%20alive%20after%20that.%3C%2FP%3E%3CP%3EBack-end%20certificates%20look%20fine%20on%20both%20servers.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2271212%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2271212%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%3Bthe%20link%20to%26nbsp%3Bkb5001779%20appears%20to%20be%20dead.%20Can%20you%20please%20provide%20and%20updated%20link%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2271213%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2271213%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F977615%22%20target%3D%22_blank%22%3E%40FreakyNL%3C%2FA%3E%26nbsp%3BCan%20you%20check%20the%20bindings%20on%20default%20web%20site%20and%20Exchange%20Back%20End%3F%20This%20will%20take%20you%20to%20this%20specific%20section%20of%20the%20troubleshooting%20doc%3A%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fexchange%2Ftroubleshoot%2Fclient-connectivity%2Fexchange-security-update-issues%23blank-page-in-eac-or-owa%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3ERepair%20failed%20installations%20of%20Exchange%20Cumulative%20and%20Security%20updates%20-%20Exchange%20%7C%20Microsoft%20Docs%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2271215%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2271215%22%20slang%3D%22en-US%22%3E%3CP%3EThe%20CU%20URLs%20are%20broken.%26nbsp%3B%20404%20page%20comes%20up.%26nbsp%3B%20As%20of%207%3A36%20EST%20April%2013th%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2271219%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2271219%22%20slang%3D%22en-US%22%3E%3CP%3ELink%20to%20the%20catalog%3A%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fwww.catalog.update.microsoft.com%2FSearch.aspx%3Fq%3D5001779%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3EMicrosoft%20Update%20Catalog%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2271245%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2271245%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F265098%22%20target%3D%22_blank%22%3E%40Keith-Work-711%3C%2FA%3E%26nbsp%3Bthe%20Cab%20files%20are%20available%20through%20Windows%20Catalog%20%3A)%3C%2Fimg%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2272535%22%20slang%3D%22de-DE%22%3ESubject%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2272535%22%20slang%3D%22de-DE%22%3E%3CP%3ESame%20problem%20here%20with%20Paessler%20PRTG%20monitoring%20tool.%20%3CBR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Fkb.paessler.com%2Fen%2Ftopic%2F54353-i-have-problems-with-the-powershell-exchange-sensors-what-can-i-do%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fkb.paessler.com%2Fen%2Ftopic%2F54353-i-have-problems-with-the-powershell-exchange-sensors-what-can-i-do%3C%2FA%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2271241%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2271241%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F304471%22%20target%3D%22_blank%22%3E%40MrOCanada%3C%2FA%3E%26nbsp%3B-%20OMG%20I%20have%20no%20idea%20what%20happened%20there%3B%20The%20KB%20is%20down%3F%20Sigh.%20I%20just%20changed%20all%20the%20links%20to%20point%20directly%20to%20the%20download%20pages%20again.%20Will%20look%20into%20KB%20next.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2273008%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2273008%22%20slang%3D%22en-US%22%3E%3CP%3EIs%20this%20a%20patch%20that%20can%20be%20installed%20like%20a%20regular%20windows%20update%20patch%20or%20is%20it%20more%20like%20a%20CU%20where%20the%20server%20will%20need%20downtime%20while%20the%20patch%20installs%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2273027%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2273027%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%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%3BLooks%20like%20a%20few%20different%20problems%20at%20once%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20see%20advice%20to%20remove%20and%20re-add%20Powershell%20virtual%20directory%20-%20does%20this%20fix%20the%20remote%20powershell%2Fthird%20party%20monitoring%20tool%20issue%20that%20affects%20us%2C%20or%20just%20the%20ECP%20issue%20which%20is%20not%20what%20I%20am%20seeing.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAlso%2C%20recreating%20Powershell%20virtual%20directory%20looks%20more%20complicated%20on%20a%20single%20server%20lab%20node%20because%20its%20a%20single%20server.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20had%20initially%20installed%20via%20Windows%20Update%20powershell%20run%20from%20a%20powershell%20admin%20window.%26nbsp%3B%20%26nbsp%3BI%20tried%20the%20uninstall%20and%20reinstall%20by%20downloading%20the%20.msp%20and%20installing%20from%20command%20prompt%20admin%20window.%26nbsp%3B%20%26nbsp%3Bno%20difference.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHopefully%20this%20will%20be%20resolved%20soon%2C%20it%20looks%20like%20a%20high%20risk%20update%2C%20but%20breaking%20monitoring%20will%20cause%20its%20own%20problems.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%20for%20everyones%20help%20with%20this%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EGreg%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2273089%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2273089%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1026165%22%20target%3D%22_blank%22%3E%40John_Smirnoff%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIf%20outlook%20can't%20connect%2C%20if%20I%20were%20you%2C%20I%20would%20delete%20the%20C%3A%20and%20reinstall%20the%20OS%2C%20fully%20patch%20it%2C%20give%20the%20same%20computer%20name%2C%20reconnect%20exchange%20data%20and%20log%20disks%20and%20assign%20original%20drive%20letters%2C%20and%20install%20exchange%20in%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fexchange%2Fhigh-availability%2Fdisaster-recovery%2Frecover-exchange-servers%3Fview%3Dexchserver-2019%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%22%3Erecovery%20mode%3C%2FA%3E%20using%20the%20latest%20CU.%20It%20can%20be%20done%20in%20a%20few%20hours.%3C%2FP%3E%3CP%3EMaking%20sure%20users%20can%20use%20email%20is%20top%20priority%20in%20my%20mind%2C%20other%20than%20waiting%20for%20M%24%20to%20fix%20the%20issue%20as%20it%20seems%20they%20don't%20have%20a%20QA%20department%20anymore.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2273090%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2273090%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1026299%22%20target%3D%22_blank%22%3E%40RWhitmire%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIt%20requires%20a%20downtime.%3C%2FP%3E%3CP%3EIn%20my%20case%2C%3C%2FP%3E%3CP%3EExchange%202016%20edge%20took%2010%20min.%3C%2FP%3E%3CP%3EExchange%202016%20mailbox%20took%2045%20min%3C%2FP%3E%3CP%3EExchange%202019%20mailbox%20took%201%20hour%20to%20apply%20the%20patch.%3C%2FP%3E%3CP%3EWhile%20it%20is%20applied%20yes%20exchange%20was%20down%2C%20and%20once%20it%20is%20done.%20you%20have%20to%20reboot%20the%20server.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2273107%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2273107%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1025997%22%20target%3D%22_blank%22%3E%40ewilhelm_paessler%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHi%20there%2C%20In%20case%20this%20helps%20you%20I've%20been%20able%20to%20make%20our%20inhouse%20Exchange%20admin%20tool%20work%20with%20remote%20powershell.%3C%2FP%3E%3CP%3EI%20did%20nothing%20to%20change%20the%20setup%20of%20the%20runspace%20but%20changed%20the%20way%20powershell%20commands%20are%20executed%20and%20it%20appears%20to%20be%20working.%3C%2FP%3E%3CP%3EUsing%20AddCommand()%20instead%20of%20AddScript()%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EExample%20code%20that%20is%20not%20working%3A%3C%2FP%3E%3CP%3EPowershell%20ps%20%3D%20GetPowerShellInstance()%3B%3C%2FP%3E%3CP%3Eps.AddScript(%22Get-Mailbox%20-identity%20'testuser%40contoso.com'%22)%3B%3C%2FP%3E%3CP%3ECollection%3CPSOBJECT%3E%20collection%20%3D%20ps.Invoke()%3B%3C%2FPSOBJECT%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EExample%20code%20that%20is%20working%3A%3C%2FP%3E%3CP%3EPowershell%20ps%20%3D%20GetPowerShellInstance()%3B%3C%2FP%3E%3CP%3Eps.AddCommand(%22Get-Mailbox%22)%3B%3C%2FP%3E%3CP%3Eps.AddParameter(%22Identity%22%2C%22testuser%40contoso.com%22)%3B%3C%2FP%3E%3CP%3ECollection%3CPSOBJECT%3E%20collection%20%3D%20ps.Invoke()%3B%3C%2FPSOBJECT%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20hope%20this%20is%20helpful%20for%20others.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2273112%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2273112%22%20slang%3D%22en-US%22%3E%3CP%3EThank%20you%20for%20the%20suggestions%2C%20but%20another%20problem%20is%20the%20hybrid%20environment%20which%20is%20a%20H***%20to%20set%20up.%20We%20are%20considering%20different%20options%2C%20but%20we%20would%20appreciate%20a%20reply%2Fa%20solution%20from%20MS%20very%20VERY%20much.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2273221%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2273221%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%26nbsp%3B%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%20installed%20patches%20on%203%20node%20cluster%20Exchange%202013%20last%20night%20and%20so%20far%20so%20good.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1026124%22%20target%3D%22_blank%22%3E%40jeffc1670%3C%2FA%3E%26nbsp%3Bgo%20to%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%3Band%20it%20will%20tell%20you%20the%20steps%20to%20update%20Exchange%202013%20CU23%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Eif%20you%20have%20applied%20March%20security%20patch%20then%20you%20may%20have%20installed%20net%20framework%204.8%20so%20you%20can%20skip%20that.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EDon't%20get%20download%20from%20windows%20update.%26nbsp%3B%20Download%20the%20patch%2C%20use%20elevated%20command%20prompt%20to%20run%20patch%20.MSP.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAdditional%20step%20that%20I%20did%20before%20installing%20patch%20is%20to%20stop%20ALL%20Exchange%20services%20manually.%26nbsp%3B%20during%20the%20patch%20install%2C%20I%20also%20keep%20checking%20the%20service%20to%20make%20sure%20the%20service%20doesn't%20restart%20automatically.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIt%20took%20me%20about%201%20hour%20per%20server.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2273256%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2273256%22%20slang%3D%22en-US%22%3E%3CP%3EAnother%20frustrated%20engineer%20here.%3C%2FP%3E%3CP%3EMicrosoft%20Exchange%20update%20KB5001779%20broke%20the%20PRTG%20DAG%20sensor.....%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EThe%20sensor%20was%20able%20to%20connect%20to%20the%20device%20using%20Remote%20PowerShell%20but%20could%20not%20retrieve%20access%20to%20Remote%20Exchange%20Management%20Shell.%20Ensure%20that%20remote%20management%20is%20enabled%20on%20the%20Exchange%20Server%20and%20the%20user%20has%20sufficient%20rights.%20See%20%3CA%20href%3D%22https%3A%2F%2Fkb.paessler.com%2Fen%2Ftopic%2F54353%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noreferrer%22%3Ehttps%3A%2F%2Fkb.paessler.com%2Fen%2Ftopic%2F54353%3C%2FA%3E%20for%20details.%20The%20syntax%20is%20not%20supported%20by%20this%20runspace.%20This%20can%20occur%20if%20the%20runspace%20is%20in%20no-language%20mode.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2273292%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2273292%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1026172%22%20target%3D%22_blank%22%3E%40-MeandExchange%3C%2FA%3E%20(for%20some%20reason%20I%20can't%20tag%20you%3F)%20-%20there%20have%20been%20tons%20of%20people%20who%20applied%20updates%20by%20now.%20Every%20time%20we%20release%20any%20kind%20of%20update%20(Su%20or%20CU)%20there%20is%20discussion%20here%20in%20blog%20comments%20about%20issues%20that%20come%20up.%20Every%20time.%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1025378%22%20target%3D%22_blank%22%3E%40GregS410%3C%2FA%3E%26nbsp%3Band%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1026435%22%20target%3D%22_blank%22%3E%40Caspian%3C%2FA%3E%26nbsp%3B-%20I%20got%20no%20updates%20as%20of%20now%20about%203rd%20party%20monitoring%20solutions%20that%20might%20be%20broken%3B%20we%20understand%20that%20this%20is%20important%20to%20folks.%20We%20have%20a%20few%20support%20tickets%20in%20play%20on%20this%20now%2C%20and%20they%20are%20sitting%20with%20someone%20who%20will%20be%20able%20to%20debug%20this%20problem.%20We'd%20call%20this%20'under%20investigation'%20then.%20No%20workarounds%20or%20other%20ideas%20as%20of%20yet.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2273328%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2273328%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%26nbsp%3B%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%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20just%20submitted%20a%20PSS%20case%20as%20well%20-%20hopefully%20this%20will%20get%20linked%20to%20the%20others.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2273329%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2273329%22%20slang%3D%22en-US%22%3E%3CP%3EAfter%20installing%20this%20update%20ems%20stops%20working%20for%20managed%20service%20accounts%2C%20so%20we%20have%20to%20switch%20back%20to%20regular%20users%20that%20have%20no%20automatic%20password%20management%2C%20which%20is%20bad.%20You%20cannot%20remove%20%24%20from%20managed%20account%20username%2C%20since%20install-adserviceaccount%20cannot%20find%20it%20after%20such%20change.%20This%20affects%20exchange%202013%7C2016%7C2019.%20Is%20there%20a%20fix%20for%20it%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2273330%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2273330%22%20slang%3D%22en-US%22%3E%3CP%3EDo%20i%20need%20to%20put%20exchange%20server%20into%20maintenance%20before%20installing%20the%20SU%20for%20CU23%3F%26nbsp%3B%3C%2FP%3E%3CP%3Eany%20ideas%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2273331%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2273331%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%20Probably%20because%20the%20%22-%22%20in%20the%20name.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EDiscussion%2C%20yes..%20But%20these%20types%20of%20issue%20among%20this%20many%20Exchange%20admin's%20no.%20I'm%20concerned%20to%20have%20these%20same%20issues%20even%20when%20following%20the%20proper%20procedure.%20Looking%20for%20additional%20ways%20to%20mitigate%20risk.%20Your%20attention%20is%20appreciated.%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2273334%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2273334%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1026491%22%20target%3D%22_blank%22%3E%40Tbrian5%3C%2FA%3E%26nbsp%3B%20put%20in%20maintenance%20mode%20will%20be%20safer.%26nbsp%3B%26nbsp%3B%3CSPAN%3Eputting%20the%20Exchange%20Server%20into%20the%20maintenance%20mode%20avoid%20any%20disconnectivity%20issues%20from%20the%20clients%20perspective%20and%20a%20seamless%20upgrade%2Fupdate.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2273338%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2273338%22%20slang%3D%22en-US%22%3E%3CP%3EAfter%20many%20hours%20of%20troubleshooting%20and%20finding%20tons%20of%20errors%20(maybe%20because%20of%20our%20setup%20nad%20the%20patch%3F%3F)%20we%20managed%20to%20%22solve%22the%20problem%20somehow%2C%20so%20forget%20about%20my%20issues.%20Time%20to%20hit%20the%20bed.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2273367%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2273367%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1026484%22%20target%3D%22_blank%22%3E%40Vgubin%3C%2FA%3E%26nbsp%3B-%20as%20of%20now%2C%20we%20do%20not%20have%20workaround%20for%20either%20the%20accounts%20with%20%22%24%22%20in%20the%20name%20or%20certain%203rd%20party%20monitoring%20solutions%20that%20cannot%20connect%20to%20Exchange%20PS%2FECP%20after%20April%20updates.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2273456%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2273456%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%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThis%20from%20the%20FAQ%20seems%20conflicting%20to%20me%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSTRONG%3E%3CEM%3EMy%20organization%20is%20in%20Hybrid%20mode%20with%20Exchange%20Online.%20Do%20I%20need%20to%20do%20anything%3F%3C%2FEM%3E%3C%2FSTRONG%3E%3CBR%20%2F%3EWhile%20Exchange%20Online%20customers%20are%20already%20protected%2C%20the%20April%202021%20security%20updates%20do%20need%20to%20be%20applied%20to%20your%20on-premises%20Exchange%20Server%2C%20even%20if%20it%20is%20used%20only%20for%20management%20purposes.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSTRONG%3E%3CEM%3EDo%20I%20need%20to%20install%20the%20updates%20on%20%E2%80%98Exchange%20Management%20Tools%20only%E2%80%99%20workstations%3F%3CBR%20%2F%3E%3C%2FEM%3E%3C%2FSTRONG%3EServers%20or%20workstations%20running%20only%20Microsoft%20Exchange%20Management%20Tools%20(no%20Exchange%20services)%20do%20not%20need%20to%20apply%20these%20updates.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAs%20I%20said%20before%2C%20I%20have%20an%20Exchange%20lite%20(Exchange%20Express)%20install%20because%20it's%20hybrid%2C%20literally%20it's%20just%20got%20management%20tools%20on%20it%20(no%20exchange%20services)%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2273471%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2273471%22%20slang%3D%22en-US%22%3E%3CP%3EBricked%20Exchange%202016.%20Rebooted%2C%20updates%20removed%2C%20all%20Exchange%20services%20disabled.%20All%20were%20re%20enabled%20and%3C%2FP%3E%3CP%3ECurrently%20trying%20to%20fix%20the%20transport%20service.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2273473%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2273473%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1025407%22%20target%3D%22_blank%22%3E%40luke_q7%3C%2FA%3E%26nbsp%3BThing%20is%20-%20there%20is%20no%20such%20thing%20as%20%22Exchange%20express%22.%20If%20your%20organization%20is%20in%20fact%20in%20Hybrid%2C%20then%20you%20have%20an%20Exchange%20Server%20on-premises.%20I%20take%20it%20you%20use%20it%20for%20management%2C%20right%3F%20Which%20means%20that%20EAC%2C%20or%20Exchange%20PowerShell%20have%20to%20connect%20%3CEM%3Esomewhere%3C%2FEM%3E%20on-premises.%20So%20Exchange%20services%20and%20IIS%20virtual%20directories%20are%20running%20%3CEM%3Esomewhere%3C%2FEM%3E.%20Now%2C%20you%20could%20also%20have%20a%20%22Management%20tools%20only%22%20machine%20which%20only%20has%20Exchange%20Management%20Tools%20installed%2C%20but%20in%20that%20case%2C%20those%20management%20tools%20still%20need%20somewhere%20on-premises%20to%20connect%20to.%3C%2FP%3E%0A%3CP%3EI%20am%20making%20an%20assumption%20here%20that%20you%20run%20Exchange%20Admin%20Center%20and%2For%20PowerShell%20on-premises%3F%20If%20yes%20-%20there%20is%20Exchange%20Server%20somewhere.%20That%20is%20the%20machine%20that%20needs%20updating%20if%20you%20are%20in%20hybrid.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2273532%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2273532%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%3C%2FP%3E%3CP%3EThanks%2C%20I%20guess%20when%20I%20say%20Exchange%20express%2C%20I%20meant%20there%20is%20no%20mailboxes%2C%20no%20DAGs%20etc%2C%20literally%20just%20for%20management%20purposes%20but%20yes%2C%20it%20is%20running%20IIS%20etc.%3C%2FP%3E%3CP%3EWhen%20I%20tried%20to%20update%20the%20CU%20in%20March%20from%2016%20to%2019%20(20%20just%20arrived%20-%20I%20tired%20that%20too)%2C%20it%20went%20on%20and%20on%20about%20no%20mailboxes%20(correct)-%20mailbox%20server%20role%20not%20installed%2C%20that's%20because%20everything%20is%20O365%2C%20and%20also%20issues%20around%20not%20being%20able%20to%20talk%20to%20AD%20(doesn't%20exist%20or%20can't%20be%20contacted)%20-%20probably%20because%20AD%20hadn't%20been%20extended.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2273561%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2273561%22%20slang%3D%22en-US%22%3E%3CP%3EAlso%20issue%20with%20management%20shell%20and%20account%20using%20%24%20in%20the%20username.%26nbsp%3B%20I%20don't%20want%20to%20rename%20my%20account%2C%20so%20I%20guess%20we%20wait%20for%20a%20fix.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2273609%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2273609%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%3EThank%20you%20for%20all%20the%20information%20provided%20and%20for%20being%20proactive.%20%26nbsp%3BJust%20wanted%20to%20clarify%20that%20our%20issue%20with%20the%20following%20error%20is%20not%20related%20to%20the%203rd%20Party%20Monitoring%20Tools%20but%20with%20our%20custom%20tool%20we%20have.%20So%20it%20seems%20something%20change%20in%20the%20process%20of%20remote%20management.%20hope%20this%20helps.%20Please%20let%20us%20know%20if%20you%20need%20more%20information.%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FP%3E%3CPRE%3ESystem.Management.Automation.RemoteException%3A%20The%20syntax%20is%20not%20supported%20by%20this%20runspace.%20This%20can%20occur%20if%20the%20runspace%20is%20in%20no-language%20mode.%3C%2FPRE%3E%3CP%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2273910%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2273910%22%20slang%3D%22en-US%22%3E%3CP%3ETo%20give%20positive%20comments%20I%20can%20say%2C%20that%20I%20have%20pathed%20Exchange%20Server%202016%20CU19%20with%20the%20latest%20security%20update%20and%20it%20was%20a%20success.%20No%20issues%20found%20afterwards.%20.MSP%20ran%20from%20elevated%20command%20prompt.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2273964%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2273964%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1026165%22%20target%3D%22_blank%22%3E%40John_Smirnoff%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EPerhaps%20something%20went%20wrong%20with%20the%20web%20part.%3C%2FP%3E%3CP%3EDid%20you%20run%20from%20evelated%20prompt%20like%20alex%20kim%20said%3F%20Otherwise%20run%20it%20again%20from%20elevated%20prompt%20and%20if%20it%20doesn't%20work%20then%20there's%20a%20UpdateCAS.ps1%20in%20the%20bin%20folder%20of%20the%20exchange%20installation.%20Try%20running%20that%20and%20see%20if%20things%20improve.%20You%20can%20run%20it%20from%20regular%20(admin)%20powershell.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1026172%22%20target%3D%22_blank%22%3E%40-MeandExchange%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EYes%2C%20multiple%20environments%20without%20issues%2C%20all%20of%20them%20after%20renaming%20accounts%20with%20%24%20in%20them%20and%20fixing%20powershell%20I%20broke%20whilst%20troubleshooting.%20The%20environment%20with%20issues%20I%20removed%20and%20recreated%20powershell%20VDs%2C%20oddly%20those%20servers%20showed%20a%20VD%20for%20powershell%20on%20both%20the%20front-end%20and%20the%20back-end.%20Removing%20the%20back-end%20one%20broke%20some%20things%20in%20IIS%20I%20presume%20(application%20pool%20was%20gone%20and%20the%20'powershell'%20on%20back-end%20showed%20up%20as%20a%20folder%20instead%20of%20an%20application).%20Threw%20the%20same%20error%20code%20in%20Management%20Shell%20as%20with%20%24%20accounts.%20After%20recreating%20the%20IIS%20config%20manually%20it%20started%20working%20(w%2Fo%20%24%20in%20account%20then%2C%20still%20doesn't%20with%20%24).%20It's%20not%20related%20to%20the%20account%20not%20having%20a%20mailbox.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1025378%22%20target%3D%22_blank%22%3E%40GregS410%3C%2FA%3E%26nbsp%3BI%20thought%20issue%20might%20stem%20from%20some%20non-default%20config%20on%20the%20powershell%20VDs%20(mostly%20them%20appearing%20on%20back-end%20too%20-%20someone%20might%20have%20created%20them%20by%20accident).%20If%20it%20comes%20from%20me%2C%20I'd%20let%20it%20be%2C%20our%20issues%20came%20solely%20from%20%24%20in%20account.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2274073%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2274073%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSPAN%3EThere%E2%80%99s%20any%20workaground%20or%20mitigation%20for%20those%20cve%20%3F%20i%E2%80%99m%20using%20F5%20for%20load%20balancer%20and%20trendmicro%20for%20endpoint%20(IPS%20included).%20I%20cannot%20update%20security%20right%20away%20for%20reason.%20Please%20advice.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2274107%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2274107%22%20slang%3D%22en-US%22%3E%3CP%3EIs%20the%20exchange%202019%20version%20number%20supposed%20to%20bump%20up%20after%20the%20patch%20installation%3F%3C%2FP%3E%3CP%3EMine%20is%20still%20CU9%20version%20number%20(I%20think)%3C%2FP%3E%3CP%3EAdminDisplayVersion%20%3A%20Version%2015.2%20(Build%20858.5)%3CBR%20%2F%3EExchangeVersion%20%3A%200.1%20(8.0.535.0)%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2274441%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2274441%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%2C%20we%20had%20an%20issue%20after%20installing%20the%20patch%20on%20our%20Windows%20Server%202012r2%20box%20with%20Exchange%202013%20where%26nbsp%3B%25ExchangeInstallDir%25%20wasn't%20expanded%20to%20the%20full%20path%20in%20any%20of%20the%20web.config%20files%2C%20with%20the%20result%20that%20assemblies%20wasn't%20loading.%3C%2FP%3E%3CP%3EWe%20fixed%20this%20by%20running%20a%20find%2Freplace%20to%20manually%20change%20to%20full%20paths%20in%20the%20config%20files.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2274503%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2274503%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1026923%22%20target%3D%22_blank%22%3E%40ngtlam1806%3C%2FA%3E%26nbsp%3B-%20we%20have%20not%20released%20any%20mitigations%20for%20those%20particular%20CVEs%2C%20no.%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1026968%22%20target%3D%22_blank%22%3E%40boredoutofmyskull%3C%2FA%3E%26nbsp%3B-%20no%2C%20the%20version%20change%20will%20not%20be%20different%20after%20SU%3B%20you%20can%20either%20check%20add%2Fremove%20(the%20update%20will%20show%20there%20under%20update%20to%20the%20current%20CU)%20or%20the%20Health%20Checker%20script.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2274774%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2274774%22%20slang%3D%22en-US%22%3E%3CP%3EAll%20of%20my%20mailboxes%20are%20in%20the%20cloud%2C%20when%20can%20we%20(officially)%20get%20rid%20of%20this%20on%20prem%20server%20permanently%3F%20Skype%2FTeams%20did%20not%20require%20us%20to%20KEEP%20an%20on%20prem%20server%20to%20manage%20AD%20objects%20once%20moved%20to%20the%20cloud%20in%20hybrid%20AD%20mode%2C%20why%20does%20exchange%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EFYI%3A%20I%20am%20aware%20that%20we%20can%20technically%20get%20rid%20of%20it%20and%20edit%20AD%20objects%20directly%20but%20it%20is%20not%20a%20supported%20config.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2274951%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2274951%22%20slang%3D%22en-US%22%3E%3CP%3ECan%20you%20clarify%20a%20point%20on%20EX%202013%20CU23.%20Your%20wizard%20says%20installs%20.Net%204.8%20yet%20the%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fexchange%2Fplan-and-deploy%2Fsupportability-matrix%3Fview%3Dexchserver-2019%23microsoft-net-framework%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%22%3EComparability%20Matrix%3C%2FA%3E%20says%20both%204.7.2%20and%204.8%20are%20support.%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3CP%3EAny%20issues%20with%20installing%20.Net%204.8%20on%20top%20of%20CU%2023%3F%20%2C%20is%20it%20REQUIRED%20for%20this%20April%20patch%3F%26nbsp%3B%20No%20issues%20in%20previous%20months%20with%20.Net%204.7.2%20(I%20know%2C%20I%20know%20easy%20upgrade%20just%20reviewing%20options)%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIf%20it%20is%20required%2C%20can%20you%20update%20the%20KB%20to%20reflect%20the%20system%20requirement%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2275055%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2275055%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F494113%22%20target%3D%22_blank%22%3E%40David__G%3C%2FA%3E%26nbsp%3B-%20Yeah%2C%20we%20hear%20you.%20No%20immediate%20news%20or%20announcements%20but%20we%20heard%20this%20loud%20and%20clear.%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1027518%22%20target%3D%22_blank%22%3E%40KrisHappe%3C%2FA%3E%26nbsp%3B-%20Unclear%20what%20you%20mean%3B%20I%20mean%20the%20ExchangeUpdateWizard%20will%20suggest%20to%20install%20the%20'latest'%20if%20you%20are%20going%20from%20older%20version%20to%20CU23%3B%20it%20would%20not%20really%20make%20sense%20to%20suggest%20installation%20of%20older%20version%3F%20You%20are%20correct%20that%20both%20are%20supported%20in%20this%20scenario.%20And%20no%2C%20upgrade%20of%20.NET%20is%20NOT%20needed%20to%20install%20the%20April%20update.%20The%20wizard%20is%20really%20geared%20to%20be%20the%20%22steps%20to%20update%20from%20older%20unsupported%20CU%20to%20latest%20supported%20CU%22%20because%20once%20you%20are%20on%20latest%20CU%2C%20you%20can%20simply%20install%20the%20update%20(via%20MU%20or%20manually%2C%20from%20elevated%20CMD%20prompt).%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2275619%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2275619%22%20slang%3D%22en-US%22%3E%3CP%3EAfter%20this%20update%20our%20support%20tool%20does%20not%20work%20any%20more.%20We%20run%20a%20exchange%202016%20server%2C%20and%20the%20tool%20does%20a%20simple%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CPRE%3E%20%20%20%20%20%20%20%20public%20void%20SearchExchangeMailBox()%0A%20%20%20%20%20%20%20%20%7B%0A%20%20%20%20%20%20%20%20%20%20%20%0A%20%20%20%20%20%20%20%20%20%20%20%20PSCredential%20cred%20%3D%20new%20PSCredential(ADtoolUserName%2C%20ADtoolUserPassword)%3B%0A%20%20%20%20%20%20%20%20%20%20%20%20WSManConnectionInfo%20connectionInfo%20%3D%20new%20WSManConnectionInfo(new%20Uri(%22http%3A%2F%2Fexch01%2Fpowershell%3FserializationLevel%3DFull%22)%2C%20%22http%3A%2F%2Fschemas.microsoft.com%2Fpowershell%2FMicrosoft.Exchange%22%2C%20cred)%3B%0A%20%20%20%20%20%20%20%20%20%20%20%20connectionInfo.AuthenticationMechanism%20%3D%20AuthenticationMechanism.Kerberos%3B%0A%0A%0A%0A%0A%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20using%20(Runspace%20runspace%20%3D%20RunspaceFactory.CreateRunspace(connectionInfo))%0A%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%7B%0A%0A%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20using%20(PowerShell%20powershell%20%3D%20PowerShell.Create())%0A%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%7B%0A%0A%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%20powershell.AddScript(%22Get-Mailbox%20%22%20%2B%20SelectedUsername%20%2B%20%22*%22)%3B%0A%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%20runspace.Open()%3B%0A%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%20powershell.Runspace%20%3D%20runspace%3B%0A%0A%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%20Collection%26lt%3BPSObject%26gt%3B%20results%20%3D%20powershell.Invoke()%3B%0A%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%20foreach%20(ErrorRecord%20err%20in%20powershell.Streams.Error)%0A%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%7B%0A%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%20MessageBox.Show(%22Error%22)%3B%0A%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%20MessageBox.Show(err.ToString())%3B%0A%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%7D%3C%2FPRE%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EBut%20that%20now%20throws%20a%20error%20now.%20Nothing%20has%20change%20on%20our%20part.%26nbsp%3B%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FP%3E%3CPRE%3ESystem.Management.Automation.RemoteException%3A%20The%20syntax%20is%20not%20supported%20by%20this%20runspace.%20This%20can%20occur%20if%20the%20runspace%20is%20in%20no-language%20mode.%0A%20%20%20ved%20System.Management.Automation.Runspaces.AsyncResult.EndInvoke()%0A%20%20%20ved%20System.Management.Automation.PowerShell.CoreInvokeRemoteHelper%5BTInput%2CTOutput%5D(PSDataCollection%601%20input%2C%20PSDataCollection%601%20output%2C%20PSInvocationSettings%20settings)%0A%20%20%20ved%20System.Management.Automation.PowerShell.CoreInvoke%5BTInput%2CTOutput%5D(PSDataCollection%601%20input%2C%20PSDataCollection%601%20output%2C%20PSInvocationSettings%20settings)%0A%20%20%20ved%20System.Management.Automation.PowerShell.Invoke(IEnumerable%20input%2C%20PSInvocationSettings%20settings)%0A%20%20%20ved%20ADTool.MainForm.SearchExchangeMailBox()%0A%20%20%20ved%20ADTool.MainForm.searchBtn_Click(Object%20sender%2C%20EventArgs%20e)%0A%20%20%20ved%20System.Windows.Forms.Control.OnClick(EventArgs%20e)%0A%20%20%20ved%20System.Windows.Forms.Button.OnClick(EventArgs%20e)%0A%20%20%20ved%20System.Windows.Forms.Button.PerformClick()%0A%20%20%20ved%20ADTool.MainForm.searchBox_KeyUp(Object%20sender%2C%20KeyEventArgs%20e)%0A%20%20%20ved%20System.Windows.Forms.Control.OnKeyUp(KeyEventArgs%20e)%0A%20%20%20ved%20System.Windows.Forms.Control.ProcessKeyEventArgs(Message%26amp%3B%20m)%0A%20%20%20ved%20System.Windows.Forms.Control.WmKeyChar(Message%26amp%3B%20m)%0A%20%20%20ved%20System.Windows.Forms.Control.WndProc(Message%26amp%3B%20m)%0A%20%20%20ved%20System.Windows.Forms.TextBox.WndProc(Message%26amp%3B%20m)%0A%20%20%20ved%20System.Windows.Forms.NativeWindow.Callback(IntPtr%20hWnd%2C%20Int32%20msg%2C%20IntPtr%20wparam%2C%20IntPtr%20lparam)%3C%2FPRE%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2275641%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2275641%22%20slang%3D%22en-US%22%3E%3CP%3Ei%20can%20also%20confirm%20rewriting%20the%20code%20from%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CPRE%3E%20powershell.AddScript(%22Get-Mailbox%20%22%20%2B%20SelectedUsername%20%2B%20%22*%22)%3B%0A%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%20runspace.Open()%3B%0A%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%20powershell.Runspace%20%3D%20runspace%3B%3C%2FPRE%3E%3CP%3Eto%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CPRE%3E%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%20powershell.AddCommand(%22Get-Mailbox%22)%3B%0A%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%20powershell.AddParameter(%22Identity%22%2C%20SelectedUsername)%3B%0A%0A%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%0A%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%20runspace.Open()%3B%3C%2FPRE%3E%3CP%3Eit%20works%20just%20fine%2C%20but%20we%20use%20the%20addscript%20function%20a%20lot%20of%20place%20in%20the%20code%2C%20so%20its%20a%20big%20tast%20to%20re%20write%20everything.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2275679%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2275679%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1025407%22%20target%3D%22_blank%22%3E%40luke_q7%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3Etry%20this%20link%20to%20get%20updates.%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fexchange%2Fnew-features%2Fbuild-numbers-and-release-dates%3Fview%3Dexchserver-2019%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3EExchange%20Server%20build%20numbers%20and%20release%20dates%20%7C%20Microsoft%20Docs%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2275689%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2275689%22%20slang%3D%22en-US%22%3E%3CP%3EAs%20a%20best%20practice%2C%20should%20I%20install%20windows%20hotfix%20and%20Exchange%20CU%20security%20update%20separately%3F%20For%20example%2C%20Microsoft%20update%20finds%202%20Windows%20server%20April%20hotfix%20and%20Exchange%20update%205001779%2C%20should%20I%20install%20windows%20hotfix%20at%20first%20%2Cthen%20restart%20server%2C%20install%20Exchange%20update%20and%20restart%20server%3F%26nbsp%3B%20Or%20just%20select%20all%20hotfix%20let%20Microsoft%20update%20do%20its%20job%3F%20Thanks.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2275694%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2275694%22%20slang%3D%22en-US%22%3E%3CP%3EI%20suspect%20I'm%20also%20having%20problems%20after%20the%20patch.%20I%20used%20to%20re-link%20Linked%20Mailboxes%20multiple%20times%20a%20week%20but%20today%2C%20suddenly%20today%20(after%20installing%20the%20patch%20yesterday)%20the%20same%20command%20does%20not%20work%20and%20I%20get%20the%20following%20error%20and%20it%20says%20there%20an%20errors%26nbsp%3B%3CSTRONG%3EProxy%20method%20RPS%3C%2FSTRONG%3E%20and%20I%20assume%20RPS%20means%20Remote%20PowerShell%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CPRE%3EError%20on%20proxy%20command%20'Set-Mailbox%20-Identity%3A'Test.User%40domain.com'%20-LinkedDomainController%3A'dc.accountforest.net'%20-LinkedMasterAccount%3A'AF%5Ctestuser'%0A-LinkedCredential%3A'System.Management.Automation.PSCredential'%20-Confirm%3A%24False%20-Force%3A%24True'%20to%20server%20DC.resourceforest.net%3A%20Server%20version%2015.02.0792.0000%2C%20Proxy%20method%20RPS%3A%0ACannot%20process%20argument%20transformation%20on%20parameter%20'LinkedCredential'.%20A%20command%20that%20prompts%20the%20user%20failed%20because%20the%20host%20program%20or%20the%20command%20type%20does%20not%20support%20user%20interaction.%20The%0Ahost%20was%20attempting%20to%20request%20confirmation%20with%20the%20following%20message%3A%20Enter%20your%20credentials..%0A%20%20%20%20%2B%20CategoryInfo%20%20%20%20%20%20%20%20%20%20%3A%20NotSpecified%3A%20(%3A)%20%5BSet-Mailbox%5D%2C%20CmdletProxyException%0A%20%20%20%20%2B%20FullyQualifiedErrorId%20%3A%20Microsoft.Exchange.Configuration.CmdletProxyException%2CMicrosoft.Exchange.Management.RecipientTasks.SetMailbox%0A%20%20%20%20%2B%20PSComputerName%20%20%20%20%20%20%20%20%3A%20exchange.resourceforest.net%3C%2FPRE%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2275730%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2275730%22%20slang%3D%22en-US%22%3E%3CP%3EHello%2C%20after%202016%20Installation%26nbsp%3B%20from%20CU%2018%20to%20CU20%26nbsp%3Bthat%20we%20can%20install%20KB5001779%20completely%26nbsp%3B%20broken%20all%20services.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20have%20no%20idea%20to%20fix%20this%20tried%20many%20nothing%20works.%20%3A(%3C%2Fimg%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20get%20following%20error%20on%20powershell.%20(see%20blow)%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3CP%3EAlso%20in%20eventvwr%3A%3C%2FP%3E%3CP%3Emany%20ASP.NET%26nbsp%3B%20eventID%201310%26nbsp%3B%20for%20all%20different%20virtuall%20directories%20(ECP%2C%20EWS%2COAB%2C%20........)%26nbsp%3B%20e.g.%3C%2FP%3E%3CDIV%20class%3D%22lia-spoiler-container%22%3E%3CA%20class%3D%22lia-spoiler-link%22%20href%3D%22%23%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%20target%3D%22_blank%22%3ESpoiler%3C%2FA%3E%3CNOSCRIPT%3E(Resaltar%20para%20leer)%3C%2FNOSCRIPT%3E%3CDIV%20class%3D%22lia-spoiler-border%22%3E%3CDIV%20class%3D%22lia-spoiler-content%22%3E%26nbsp%3B%3C%2FDIV%3E%3CNOSCRIPT%3E%3CDIV%20class%3D%22lia-spoiler-noscript-container%22%3E%3CDIV%20class%3D%22lia-spoiler-noscript-content%22%3E%26nbsp%3B%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FNOSCRIPT%3E%3C%2FDIV%3E%3C%2FDIV%3E%3CP%3EApplication%20information%3A%3CBR%20%2F%3EApplication%20domain%3A%20%2FLM%2FW3SVC%2F1%2FROOT%2FEWS-82-132630328195781290%3CBR%20%2F%3ETrust%20level%3A%20Full%3CBR%20%2F%3EApplication%20Virtual%20Path%3A%20%2FEWS%3CBR%20%2F%3EApplication%20Path%3A%20C%3A%5CProgram%20Files%5CMicrosoft%5CExchange%20Server%5CV15%5CFrontEnd%5CHttpProxy%5CEWS%5C%3CBR%20%2F%3EMachine%20name%3A%20MS108%3CBR%20%2F%3E%3CBR%20%2F%3EProcess%20information%3A%3CBR%20%2F%3EProcess%20ID%3A%209784%3CBR%20%2F%3EProcess%20name%3A%20w3wp.exe%3CBR%20%2F%3EAccount%20name%3A%20NT%20AUTHORITY%5CSYSTEM%3CBR%20%2F%3E%3CBR%20%2F%3EException%20information%3A%3CBR%20%2F%3EException%20type%3A%20ConfigurationErrorsException%3CBR%20%2F%3EException%20message%3A%20Could%20not%20load%20file%20or%20assembly%20'Microsoft.Exchange.Data.Directory%2C%20Version%3D15.0.0.0%2C%20Culture%3Dneutral%2C%20PublicKeyToken%3D31bf3856ad364e35'%20or%20one%20of%20its%20dependencies.%20The%20system%20cannot%20find%20the%20file%20specified.%20(C%3A%5CProgram%20Files%5CMicrosoft%5CExchange%20Server%5CV15%5CFrontEnd%5CHttpProxy%5CEWS%5Cweb.config%20line%2065)%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ENew-PSSession%20%3A%20%5Bms108.xxxxx%5D%20Connecting%20to%20remote%20server%20ms108.xxxxxx%20failed%20with%20the%20following%20error%3CBR%20%2F%3Emessage%20%3A%20The%20WinRM%20client%20cannot%20process%20the%20request.%20It%20cannot%20determine%20the%20content%20type%20of%20the%20HTTP%20response%20from%3CBR%20%2F%3Ethe%20destination%20computer.%20The%20content%20type%20is%20absent%20or%20invalid.%20For%20more%20information%2C%20see%20the%3CBR%20%2F%3Eabout_Remote_Troubleshooting%20Help%20topic.%3CBR%20%2F%3EAt%20line%3A1%20char%3A1%3CBR%20%2F%3E%2B%20New-PSSession%20-ConnectionURI%20%22%24connectionUri%22%20-ConfigurationName%20Microsoft.Excha%20...%3CBR%20%2F%3E%2B%20~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~%3CBR%20%2F%3E%2B%20CategoryInfo%20%3A%20OpenError%3A%20(System.Manageme....RemoteRunspace%3ARemoteRunspace)%20%5BNew-PSSession%5D%2C%20PSRemotin%3CBR%20%2F%3EgTransportException%3CBR%20%2F%3E%2B%20FullyQualifiedErrorId%20%3A%20-2144108297%2CPSSessionOpenFailed%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2275738%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2275738%22%20slang%3D%22en-US%22%3E%3CP%3EHello%2C%20after%202016%20Installation%26nbsp%3B%20from%20CU%2018%20to%20CU20%26nbsp%3Bthat%20we%20can%20install%20KB500%20completely%26nbsp%3B%20broken%20all%20services.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20get%20following%20error%20on%20powershell.%20(see%20blow)%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3CP%3EAlso%20in%20eventvwr%3A%3C%2FP%3E%3CP%3Emany%20ASP.NET%26nbsp%3B%20eventID%201310%26nbsp%3B%20for%20all%20different%20virtuall%20directories%20(ECP%2C%20EWS%2COAB%2C%20........)%26nbsp%3B%20e.g.%3C%2FP%3E%3CDIV%20class%3D%22lia-spoiler-container%22%3E%3CA%20class%3D%22lia-spoiler-link%22%20href%3D%22%23%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%20target%3D%22_blank%22%3ESpoiler%3C%2FA%3E%3CNOSCRIPT%3E(Highlight%20to%20read)%3C%2FNOSCRIPT%3E%3CDIV%20class%3D%22lia-spoiler-border%22%3E%3CDIV%20class%3D%22lia-spoiler-content%22%3E%26nbsp%3B%3C%2FDIV%3E%3CNOSCRIPT%3E%3CDIV%20class%3D%22lia-spoiler-noscript-container%22%3E%3CDIV%20class%3D%22lia-spoiler-noscript-content%22%3E%26nbsp%3B%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FNOSCRIPT%3E%3C%2FDIV%3E%3C%2FDIV%3E%3CP%3EApplication%20information%3A%3CBR%20%2F%3EApplication%20domain%3A%20%2FLM%2FW3SVC%2F1%2FROOT%2FEWS-82-132630328195781290%3CBR%20%2F%3ETrust%20level%3A%20Full%3CBR%20%2F%3EApplication%20Virtual%20Path%3A%20%2FEWS%3CBR%20%2F%3EApplication%20Path%3A%20C%3A%5CProgram%20Files%5CMicrosoft%5CExchange%20Server%5CV15%5CFrontEnd%5CHttpProxy%5CEWS%5C%3CBR%20%2F%3EMachine%20name%3A%20MS108%3CBR%20%2F%3E%3CBR%20%2F%3EProcess%20information%3A%3CBR%20%2F%3EProcess%20ID%3A%209784%3CBR%20%2F%3EProcess%20name%3A%20w3wp.exe%3CBR%20%2F%3EAccount%20name%3A%20NT%20AUTHORITY%5CSYSTEM%3CBR%20%2F%3E%3CBR%20%2F%3EException%20information%3A%3CBR%20%2F%3EException%20type%3A%20ConfigurationErrorsException%3CBR%20%2F%3EException%20message%3A%20Could%20not%20load%20file%20or%20assembly%20'Microsoft.Exchange.Data.Directory%2C%20Version%3D15.0.0.0%2C%20Culture%3Dneutral%2C%20PublicKeyToken%3D31bf3856ad364e35'%20or%20one%20of%20its%20dependencies.%20The%20system%20cannot%20find%20the%20file%20specified.%20(C%3A%5CProgram%20Files%5CMicrosoft%5CExchange%20Server%5CV15%5CFrontEnd%5CHttpProxy%5CEWS%5Cweb.config%20line%2065)%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ENew-PSSession%20%3A%20%5Bms108.xxxxx%5D%20Connecting%20to%20remote%20server%20ms108.xxxxxx%20failed%20with%20the%20following%20error%3CBR%20%2F%3Emessage%20%3A%20The%20WinRM%20client%20cannot%20process%20the%20request.%20It%20cannot%20determine%20the%20content%20type%20of%20the%20HTTP%20response%20from%3CBR%20%2F%3Ethe%20destination%20computer.%20The%20content%20type%20is%20absent%20or%20invalid.%20For%20more%20information%2C%20see%20the%3CBR%20%2F%3Eabout_Remote_Troubleshooting%20Help%20topic.%3CBR%20%2F%3EAt%20line%3A1%20char%3A1%3CBR%20%2F%3E%2B%20New-PSSession%20-ConnectionURI%20%22%24connectionUri%22%20-ConfigurationName%20Microsoft.Excha%20...%3CBR%20%2F%3E%2B%20~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~%3CBR%20%2F%3E%2B%20CategoryInfo%20%3A%20OpenError%3A%20(System.Manageme....RemoteRunspace%3ARemoteRunspace)%20%5BNew-PSSession%5D%2C%20PSRemotin%3CBR%20%2F%3EgTransportException%3CBR%20%2F%3E%2B%20FullyQualifiedErrorId%20%3A%20-2144108297%2CPSSessionOpenFailed%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2275774%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2275774%22%20slang%3D%22en-US%22%3E%3CP%3EHello%20All%2C%3C%2FP%3E%3CP%3EDoes%20anyone%20know%20if%20we%20nee%20to%20re-apply%20the%20update%20if%20we%20go%20from%20Exchange%202016%20CU19%20to%20CU20%3F%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2275860%22%20slang%3D%22de-DE%22%3ESubject%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2275860%22%20slang%3D%22de-DE%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1028179%22%20target%3D%22_blank%22%3E%40MIJ2021%3C%2FA%3E%26nbsp%3BWe%20had%20the%20exact%20same%20issue.%20Same%20Update-Procedure%20and%20the%20Sec%20Update%20broke%20stuff%20with%20the%20same%20errors%20within%20event%20log%20as%20you%20stated.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20just%20solved%20it%20by%20reinstalling%20the%20CU20%20from%20an%20elevated%20command%20line%20and%20leaving%20the%20Security%20Update%20out%20this%20time%20after%20installing%20the%20CU20.%20Took%20a%20while%2C%20but%20worked.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMaybe%20that%20works%20for%20you%2C%20too!%20%3A)%3C%2Fimg%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2275911%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2275911%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20also%20have%20No%20Language%20support%20when%20we%20try%20to%20connect%20via%20Remote%20PowerShell%20using%20Script%20Blocker.%20Anyone%20has%20solution%20yet%20for%20this%20problem%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2275913%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2275913%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F807082%22%20target%3D%22_blank%22%3E%40kbegg00%3C%2FA%3E%26nbsp%3Byes%2C%20you%20need%20to%20reapply%20everytime%20you%20upgrade%20the%20latest%20CU%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2275951%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2275951%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1027878%22%20target%3D%22_blank%22%3E%40liujun%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%E6%AD%A4%E4%BF%AE%E8%A1%A5%E7%A8%8B%E5%BA%8F%E4%BB%85%E9%80%82%E7%94%A8%E4%BA%8EExchange%E6%9C%8D%E5%8A%A1%E5%99%A8%E3%80%82%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%E5%A6%82%E6%9E%9C%E6%82%A8%E4%B8%8D%E4%BD%BF%E7%94%A8Exchange%EF%BC%8C%E5%88%99%E6%97%A0%E9%9C%80%E4%BF%AE%E8%A1%A5%E3%80%82%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIf%20you%20are%20not%20using%20Exchange%20server%2C%20then%20no%20need%20to%20update.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2275963%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2275963%22%20slang%3D%22en-US%22%3E%3CP%3EThe%20April%202021%20patch%20has%20broken%20our%20cross%20forest%20free%5Cbusy%2C%20is%20anyone%20else%20experiencing%20the%20same%20issue%3F%20We%20are%20now%20seeing%20400%20Bad%20request%20errors%20in%20the%20MSExchange%20Availability%20logs.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2275965%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2275965%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1028131%22%20target%3D%22_blank%22%3E%40fw888888%3C%2FA%3E%20(for%20some%20reason%20I%20can't%20tag%20you)%20-%20Windows%20and%20Exchange%20fixes%20are%20totally%20separate%20so%20I%20do%20not%20know%20that%20it%20matters.%20I%20think%20just%20letting%20MU%20do%20it's%20thing%20is%20OK%20in%20this%20case.%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1028179%22%20target%3D%22_blank%22%3E%40MIJ2021%3C%2FA%3E%26nbsp%3B-%20also%20check%20this%20(linking%20to%20specific%20scenario)%3A%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fexchange%2Ftroubleshoot%2Fclient-connectivity%2Fexchange-security-update-issues%23http-500-errors-in-owa-or-ecp%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fexchange%2Ftroubleshoot%2Fclient-connectivity%2Fexchange-security-update-issues%23http-500-errors-in-owa-or-ecp%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F807082%22%20target%3D%22_blank%22%3E%40kbegg00%3C%2FA%3E%26nbsp%3B-%20As%20already%20mentioned%20-%20yes%2C%20you%20need%20to%20install%20if%20you%20move%20up%20a%20CU.%20That%20is%20because%20currently%20there%20is%20no%20CU%20that%20has%20April%20fixes%20'built%20in%20natively'%20(that%20can%20be%20expected%20in%20June%20CU)%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F928822%22%20target%3D%22_blank%22%3E%40Prasad3435%3C%2FA%3E%26nbsp%3B-%20Have%20you%20seen%20a%20reply%20from%26nbsp%3Bmadsholme1165%20just%20few%20comments%20back%3F%20Basically%20update%20from%20.AddScript()%20to%20.AddCommand()%20will%20unblock%20you.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2275999%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2275999%22%20slang%3D%22en-US%22%3E%3CP%3EAfter%20install%20KB5001779%26nbsp%3Bon%20Exchange%202016%20CU20%2C%20NetApp%20SnapManager%20for%20Exchange%20(7.2.1)%20is%20stopped%20working.%3C%2FP%3E%3CP%3EI%20see%20the%20following%20error%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%5B04%2F15%2022%3A42%3A16%20028%5D%20Getting%20dash%20board%20info...%3CBR%20%2F%3E%5B04%2F15%2022%3A42%3A16%20028%5D%20Calling%20PowerShell%20to%20get%20current%20exchange%20server...%3CBR%20%2F%3E%5B22%3A42%3A16.028%5D%26nbsp%3B%20%5BPowerShell%20Cmdlet%5D%3A%20get-exchangeserver%20-status%20-identity%20HQ-EX1%3CBR%20%2F%3E%5B04%2F15%2022%3A42%3A16%20028%5D%20%5BPowerShell%20Cmdlet%5D%3A%20get-exchangeserver%20-status%20-identity%20HQ-EX1%3CBR%20%2F%3E%5B22%3A42%3A16.075%5D%26nbsp%3B%20%5BRemote%20PowerShell%20Cmdlet%20Error%5D%3AThe%20syntax%20is%20not%20supported%20by%20this%20runspace.%20This%20can%20occur%20if%20the%20runspace%20is%20in%20no-language%20mode.%3CBR%20%2F%3E%5B04%2F15%2022%3A42%3A16%20075%5D%20%5BRemote%20PowerShell%20Cmdlet%20Error%5D%3AThe%20syntax%20is%20not%20supported%20by%20this%20runspace.%20This%20can%20occur%20if%20the%20runspace%20is%20in%20no-language%20mode.%3CBR%20%2F%3E%5B22%3A42%3A16.075%5D%26nbsp%3B%20%5BPowerShell%20Cmdlet%5D%3A%20get-exchangeserver%20-status%20-identity%20HQ-EX1%3CBR%20%2F%3E%5B04%2F15%2022%3A42%3A16%20075%5D%20%5BPowerShell%20Cmdlet%5D%3A%20get-exchangeserver%20-status%20-identity%20HQ-EX1%3CBR%20%2F%3E%5B22%3A42%3A16.106%5D%26nbsp%3B%20%5BRemote%20PowerShell%20Cmdlet%20Error%5D%3AThe%20syntax%20is%20not%20supported%20by%20this%20runspace.%20This%20can%20occur%20if%20the%20runspace%20is%20in%20no-language%20mode.%3CBR%20%2F%3E%5B04%2F15%2022%3A42%3A16%20106%5D%20%5BRemote%20PowerShell%20Cmdlet%20Error%5D%3AThe%20syntax%20is%20not%20supported%20by%20this%20runspace.%20This%20can%20occur%20if%20the%20runspace%20is%20in%20no-language%20mode.%3CBR%20%2F%3E%5B22%3A42%3A16.106%5D%26nbsp%3B%20%5BPowerShell%20Cmdlet%5D%3A%20Get-DatabaseAvailabilityGroup%20-Identity%20HQ-EX1%3CBR%20%2F%3E%5B04%2F15%2022%3A42%3A16%20106%5D%20%5BPowerShell%20Cmdlet%5D%3A%20Get-DatabaseAvailabilityGroup%20-Identity%20HQ-EX1%3CBR%20%2F%3E%5B22%3A42%3A16.169%5D%26nbsp%3B%20%5BRemote%20PowerShell%20Cmdlet%20Error%5D%3AThe%20syntax%20is%20not%20supported%20by%20this%20runspace.%20This%20can%20occur%20if%20the%20runspace%20is%20in%20no-language%20mode.%3CBR%20%2F%3E%5B04%2F15%2022%3A42%3A16%20169%5D%20%5BRemote%20PowerShell%20Cmdlet%20Error%5D%3AThe%20syntax%20is%20not%20supported%20by%20this%20runspace.%20This%20can%20occur%20if%20the%20runspace%20is%20in%20no-language%20mode.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHow%20to%20fix%20that%20%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2276113%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2276113%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1028422%22%20target%3D%22_blank%22%3E%40Alternator%3C%2FA%3E%26nbsp%3B-%20Please%20contact%20the%20vendor%3B%20they%20will%20need%20to%20modify%20how%20PS%20code%20is%20called%20in%20this%20particular%20case%20-%20change%26nbsp%3Bfrom%20.AddScript()%20to%20.AddCommand()%20and%20then%20it%20will%20work.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2276138%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2276138%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_self%22%3E%3CSPAN%3ENino%20Bilic%3C%2FSPAN%3E%3C%2FA%3E%3C%2FP%3E%3CP%3E%3CSPAN%3EThank%20you%20for%20answer.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3EWe%20and%20a%20lot%20of%26nbsp%3Bsysadmins%20are%26nbsp%3BHAPPY%20to%20see%20these%20changes.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3EWe%20double%20happy%2C%20because%20this%20product%20is%26nbsp%3Boutdated%20and%26nbsp%3BEOL.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3ENow%20we%20don't%20have%20working%20backup%20by%20Netapp.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3EThank%20you%20guys%20for%20your%20hard%20work!%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3E%3B-(%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2276151%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2276151%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%3CBR%20%2F%3E%3CBR%20%2F%3Eshould%20this%20be%20read%20as%20ms%20is%20not%20gonna%20change%20it%20back%20to%20ps.AddScript()%20will%20work%20again%3F%3CBR%20%2F%3Eour%20support%20tools%20is%20using%20AddScript%20to%20run%20big%20scripts%2C%20and%20its%20a%20bit%20easyer%20to%20handle%20than%20having%20to%20mess%20with%20addcommand%20on%20all%20those%20diffrent%20commands.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2276163%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2276163%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%3BAny%20update%20on%20multiple%203rd%20party%20monitoring%20tools%20now%20broken%20by%20this%20update%3F%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3BModifying%20powershell%20script%20on%20a%203rd%20party%20monitoring%20platform%20is%20hidden%20inside%20of%20code%20and%20likely%20signed%20so%20not%20easy%20to%20modify.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThis%20puts%20us%20in%20a%20very%20hard%20place%20-%20do%20we%20proceed%20with%20a%20security%20update%20that%20looks%20very%20important%20and%20break%20all%20of%20our%20message%20flow%20and%20database%20monitors%2C%20or%20go%20with%20monitoring%20and%20no%20security%20update.%26nbsp%3B%20Neither%20answer%20is%20satisfactory%20for%202%20platforms%20that%20worked%20well%20together%20when%20we%20started%20this%20week.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EGreg%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2276282%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2276282%22%20slang%3D%22en-US%22%3E%3CP%3EAnyone%20have%20any%20system%20running%20outlook%202013%20or%202016%20on%20windows%207%3F%26nbsp%3B%20After%20this%20update%20was%20applied%20to%20our%20Exchange%20server%2C%20now%20systems%20running%20Outlook%20with%20Windows%207%20can%20not%20connect%20to%20our%20exchange%20server.%26nbsp%3B%20They%20all%20get%20%22The%20Server%20is%20not%20available%22.%26nbsp%3B%20It's%20for%20sure%20related%20to%20Windows%207%2C%20as%20I%20just%20upgraded%20a%20system%20to%20Windows%2010%2C%20and%20now%20no%20issues%20with%20outlook%20connecting%20to%20our%20exchange%20server.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAnyone%20have%20any%20ideas%2C%20yes%20I%20know%20Windows%207%20no%20longer%20supported.%20%3A(%3C%2Fimg%3E%26nbsp%3B%20But%20we%20still%20have%20a%20few%20stragglers%20waiting%20to%20be%20updated.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2276345%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2276345%22%20slang%3D%22en-US%22%3E%3CP%3EAny%20special%20instructions%20for%20rolling%20back%20the%20patch%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2276391%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2276391%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%3BAny%20update%20or%20workarounds%20for%20the%20accounts%20with%20%22%24%22%3F%20Is%20it%20known%20if%20issues%20caused%20when%20patching%20is%20performed%20using%20account%20with%20%24%20or%20after%20the%20upgrade%20all%20accounts%20with%20%24%20will%20experience%20issues%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2276393%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2276393%22%20slang%3D%22en-US%22%3E%3CP%3EAt%20this%20point%2C%20I'm%20leaving%20one%20patched%20server%20facing%20the%20Internet.%26nbsp%3B%20The%20rest%20will%20only%20be%20CU20%20so%20that%20we%20can%20perform%20admin%20tasks%20with%20%24%20accounts.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2276437%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2276437%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSPAN%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1025378%22%20target%3D%22_blank%22%3E%40GregS410%3C%2FA%3E%26nbsp%3B%26nbsp%3B-%20we%20can%20now%20%3CEM%3Econfirm%3C%2FEM%3E%20that%20the%20change%20that%20broke%20several%203rd%20party%20products%20as%20well%20as%20some%20home-grown%20code%20calling%20.AddScript()%20is%20not%20going%20to%20be%20rolled%20back%20and%20.AddCommand()%20is%20a%20way%20forward.%20I%20have%20just%20added%20the%20Known%20Issues%20section%20to%20the%20blog%20post%20to%20reflect%20this%20(a%20KB%20article%20will%20follow%20next%20week)%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%3CSPAN%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F701367%22%20target%3D%22_blank%22%3E%40jsab5%3C%2FA%3E%26nbsp%3B-%20uninstallation%20should%20be%20simple%20via%20the%20add%2Fremove%3B%20why%20would%20you%3F%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%3CSPAN%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1028325%22%20target%3D%22_blank%22%3E%40ddovnar%3C%2FA%3E%26nbsp%3B-%20At%20this%20time%2C%20the%20%24%20issue%20is%20still%20under%20investigation%3B%20we%20know%20what%20the%20work%20around%20is%20(rename%20accounts)%20but%20we%20do%20realize%20it%20is%20a%20workaround.%20It%20is%20unclear%20where%20this%20will%20go%2C%20sorry%20to%20be%20vague%20but%20that%20is%20how%20it%20is%20right%20now.%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%3CSPAN%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F114800%22%20target%3D%22_blank%22%3E%40Corbett%20Enders%3C%2FA%3E%26nbsp%3B-%20we%20definitely%20recommend%20that%20you%20update%20all%20of%20your%20servers%3B%20you%20have%20made%20some%20assumptions%20but%20they%20might%20not%20be%20correct.%20It%20is%20understandable%26nbsp%3Bthat%20it%20is%20really%20bad%20that%20we%20do%20not%20have%20a%20full%20answer%20on%20the%20%24%20situation%20at%20this%20time%20(still%20under%20investigation)%20but%20protecting%20the%20environment%20should%20be%20the%20primary%20concern.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2276444%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2276444%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%20the%20assumption%20that%20the%20other%20unpatched%20servers%20are%20not%20at%20risk%20if%20they%20are%20not%20accessible%20from%20the%20Internet%3F%26nbsp%3B%20Are%20you%20saying%20they%20are%20still%20at%20risk%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20only%20have%20%24%20admin%20accounts%2C%20if%20I%20patch%20them%20all%2C%20how%20do%20I%20manage%20my%20environment%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2276447%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2276447%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%3BCan%20you%20confirm%20if%20you%20will%20fix%20it%20so%20AddScript%20will%20work%20again%2C%20or%20areyou%20saying%20we%20should%20reformat%20all%20our%20tools%20and%20code%20to%20use%20AddCommand%2C%20even%20though%20not%20every%20script%20fits%20inside%20the%20AddCommand..%20(multi%20lines%20scripts%20are%20gonna%20be%20a%20pain%20like%20this)..%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2276452%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2276452%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%3BThis%20is%20really%20ridiculous.%26nbsp%3B%20%26nbsp%3B%20A%20hotfix%20changes%20functionality%20that%20has%20been%20in%20use%20for%20years%20with%20no%20advance%20notice%20breaking%20monitoring%20tools%20that%20enterprises%20use%20to%20keep%20our%20servers%20healthy%20and%20find%20issues%20and%20fix%20them%20proactively.%26nbsp%3B%20%26nbsp%3B%20So%20now%20I%20lose%20all%20of%20this%20with%20no%20notice.%26nbsp%3B%20%26nbsp%3B%20How%20can%20you%20justify%20doing%20this%20to%20your%20customers%3F%26nbsp%3B%20%26nbsp%3BThe%20exchange%20team%20needs%20to%20reconsider%20restoring%20the%20broken%20functionality%20ASAP.%26nbsp%3B%20%26nbsp%3BThis%20is%20not%20a%20way%20to%20treat%20the%20customers%20who%20administer%20your%20products.%26nbsp%3B%20%26nbsp%3BA%20change%20like%20this%20should%20have%20been%20included%20in%20a%20cumulative%20update%20with%20advance%20notice%20so%20that%203rd%20party%20vendors%20have%20time%20to%20fix%20it%20and%20Exchange%20administrators%20can%20make%20better%20decisions.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2276453%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2276453%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%26nbsp%3B%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%3Band%20the%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%3Bfor%20jumping%20on%20getting%20these%20patches%20out%20to%20us%20as%20fast%20as%20you%20can%20and%20supporting%20the%20remainder%20of%20on%20prem%20servers.%20Looking%20forward%20to%20Exchange%202021.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2276463%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2276463%22%20slang%3D%22en-US%22%3E%3CP%3EThank%20you%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1028046%22%20target%3D%22_blank%22%3E%40madsholme1165%3C%2FA%3E%20and%20%40%3CSPAN%20class%3D%22UserName%20lia-user-name%20lia-user-rank-Microsoft%20lia-component-message-view-widget-author-username%22%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F5374%22%20target%3D%22_self%22%3E%3CSPAN%20class%3D%22%22%3ENino%20Bilic%3C%2FSPAN%3E%3C%2FA%3E%20for%20the%20information%20you%20have%20provided.%3CBR%20%2F%3E%3CBR%20%2F%3EWe%20have%20been%20able%20to%20make%20the%20changes%20to%20our%20custom%20application%20to%20start%20using%3A%20%3C%2FSPAN%3E%3C%2FP%3E%3CDIV%3E%3CDIV%3E%3CPRE%3Epowershell.AddCommand%3C%2FPRE%3E%3C%2FDIV%3E%3CP%3EInstead%20of%3A%3C%2FP%3E%3CDIV%3E%3CPRE%3Epowershell.AddScript%3C%2FPRE%3E%3CP%3EThis%20has%20fixed%20the%20original%20issue%20we%20had%3A%3C%2FP%3E%3C%2FDIV%3E%3C%2FDIV%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CPRE%20class%3D%22lia-code-sample%20language-markup%22%3E%3CCODE%3ESystem.Management.Automation.RemoteException%3A%20The%20syntax%20is%20not%20supported%20by%20this%20runspace.%20This%20can%20occur%20if%20the%20runspace%20is%20in%20no-language%20mode.%3C%2FCODE%3E%3C%2FPRE%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CBR%20%2F%3EHope%20this%20is%20helpful%20to%20others%20having%20similar%20issues.%26nbsp%3B%20This%20AddScript%20seems%20related%20to%20the%20vulnerability%20that%20we%20are%20patching.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2276473%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2276473%22%20slang%3D%22en-US%22%3E%3CP%3EAddCommand%20mabye%20be%20a%20work%20around%2C%20but%20i%20dont%20see%20how%20its%20more%20secure%20than%20addscript.%20You%20need%20to%20add%20that%20back%2C%20running%20bigger%20scripts%20remote%20with%20addcommand%20is%20gonna%20be%20a%20mess!%20Admit%20you%20messed%20up%2C%20and%20fix%20it%2C%20rater%20than%20just%20saying%20%22recode%20youre%20stuff%22..%20after%20all%20is%20it%20not%20the%20reason%20we%20pay%20microsoft%20these%20expensive%20licensce%20fees%3F%20so%20that%20we%20can%20trust%20oure%20stuff%20keeps%20running%20%3F%20COuld%20we%20please%20get%20a%20statement%20if%20you%20are%20looking%20into%20to%20readding%20the%20addscript%20function%3F%20or%20is%20it%20gone%20forever%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2276481%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2276481%22%20slang%3D%22en-US%22%3E%3CP%3EI%20Completely%20agree%20with%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1028043%22%20target%3D%22_blank%22%3E%40madsholme%3C%2FA%3E%26nbsp%3B%20this%20needs%20to%20be%20fixed%2C%20and%20not%20through%20your%20system%20admins%20and%203rd%20party%20software%20vendors%20under%20the%20bus%20like%20this%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2276486%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2276486%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20have%20Win%202012%20R2%20w%2F%20Exchange%202016%20CU20%20with%20March%20updates%20installed%20and%20was%20working.%20Just%20used%20Windows%20updates%20to%20download%20new%20patch%20and%20installed.%20Rebooted%20and%20now%20Exchange%20Management%20Shell%20on%20server%20is%20broken.%20We%20get%3C%2FP%3E%3CPRE%3EVERBOSE%3A%20Connecting%20to%20MBX1.host.local.%3CBR%20%2F%3ENew-PSSession%20%3A%20%5Bmbx1.host.local%5D%20Connecting%20to%20remote%20server%20mbx1.host.local%20failed%20with%20the%20following%20error%20message%3CBR%20%2F%3E%3A%20%5BClientAccessServer%3DMBX1%2CBackEndServer%3Dmbx1.host.local%2CRequestId%3D8d98dcd9-de12-4964-8813-d7f731557639%2CTimeStamp%3D4%2F16%2F%3CBR%20%2F%3E2021%208%3A54%3A24%20PM%5D%20%5BFailureCategory%3DCafe-SendFailure%5D%20For%20more%20information%2C%20see%20the%20about_Remote_Troubleshooting%20Help%3CBR%20%2F%3Etopic.%3CBR%20%2F%3EAt%20line%3A1%20char%3A1%3CBR%20%2F%3E%2B%20New-PSSession%20-ConnectionURI%20%22%24connectionUri%22%20-ConfigurationName%20Microsoft.Excha%20...%3CBR%20%2F%3E%2B%20~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~%3CBR%20%2F%3E%2B%20CategoryInfo%20%3A%20OpenError%3A%20(System.Manageme....RemoteRunspace%3ARemoteRunspace)%20%5BNew-PSSession%5D%2C%20PSRemotin%3CBR%20%2F%3EgTransportException%3CBR%20%2F%3E%2B%20FullyQualifiedErrorId%20%3A%20-2144108477%2CPSSessionOpenFailed%3CBR%20%2F%3EFailed%20to%20connect%20to%20an%20Exchange%20server%20in%20the%20current%20site.%3CBR%20%2F%3EEnter%20the%20server%20FQDN%20where%20you%20want%20to%20connect.%3A%3C%2FPRE%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2276488%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2276488%22%20slang%3D%22en-US%22%3E%3CP%3ESnap%20Manager%20for%20Exchange%20broke.%26nbsp%3B%20Had%20to%20backout.%26nbsp%3B%20No%20backups.....%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2276499%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2276499%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1025378%22%20target%3D%22_blank%22%3E%40GregS410%3C%2FA%3E%3A%3C%2FP%3E%0A%3CDIV%3EWe%20totally%20understand%20the%20frustration.%20Unfortunately%2C%20this%20was%20a%20security%20related%20change%20and%20therefore%20we%20were%20not%20able%20to%20go%20through%20the%20normal%20notification%20period%20of%20a%20%22feature%22%20change.%3C%2FDIV%3E%0A%3CDIV%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1028043%22%20target%3D%22_blank%22%3E%40madsholme%3C%2FA%3E%3A%3C%2FDIV%3E%0A%3CDIV%3E%0A%3CDIV%3EAs%20long%20as%20the%20code%20in%20question%20uses%20.invoke()%20to%20run%20the%20command%20on%20the%20server%20and%20not%20on%20the%20client%20then%20yes%20.AddScript()%20will%20no%20longer%20work.%20The%20fact%20.AddScript()%20was%20working%20with%20.Invoke()%20at%20all%20was%20actually%20a%20problem%20that%20was%20corrected%20by%20the%20April%20update.%3C%2FDIV%3E%0A%3CDIV%3E%0A%3CDIV%3E%3CSPAN%20style%3D%22font-family%3A%20inherit%3B%22%3EIf%20script%20still%20needs%20to%20be%20run%20import%20the%20session%20instead%20of%20invoking%20the%20runspace%20and%20the%20scripts%20will%20run%20without%20issues.%3C%2FSPAN%3E%3C%2FDIV%3E%0A%3CDIV%3E%0A%3CDIV%3EReview%20the%20following%20sample%3A%20%3CU%3E%3CA%20tabindex%3D%22-1%22%20title%3D%22https%3A%2F%2Fgithub.com%2Fdavid-barrett-ms%2Fexchangepowershellautomationsample%22%20href%3D%22https%3A%2F%2Fgithub.com%2FDavid-Barrett-MS%2FExchangePowerShellAutomationSample%22%20target%3D%22_blank%22%20rel%3D%22noreferrer%20noopener%22%3EDavid-Barrett-MS%2FExchangePowerShellAutomationSample%3A%20A%20sample%20application%20demonstrating%20how%20to%20connect%20to%20Exchange%20Remote%20PowerShell%20and%20run%20cmdlets%20programmatically.%20(github.com)%3C%2FA%3E%3C%2FU%3E%3C%2FDIV%3E%0A%3CDIV%3E%0A%3CDIV%3E%3CSPAN%20style%3D%22font-family%3A%20inherit%3B%22%3EPlease%20contact%20Microsoft%20Exchange%20Developer%20Support%20and%20they%20will%20be%20more%20than%20happy%20to%20directly%20assist%20in%20converting%20from%20a%20direct%20invoke()%20to%20a%20session%20import%20and%20invoke.%3C%2FSPAN%3E%3C%2FDIV%3E%0A%3C%2FDIV%3E%0A%3C%2FDIV%3E%0A%3C%2FDIV%3E%0A%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2276501%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2276501%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%20link%20and%20the%20explanation.%20i%20will%20look%20into%20it.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2276510%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2276510%22%20slang%3D%22en-US%22%3E%3CP%3EAfter%20installing%20this%20patch%20on%20Windows%20Server%202012R2%20with%20Exchange%202016%20CU20%20with%20March%20update%2C%20OWA%2C%20ECP%20I%20do%20get%20the%20login%20prompt%2C%20but%20after%20entering%20admin%20creds%20I%20get%20HTTP%20ERROR%20503%2C%20along%20with%20Exchange%20Management%20Shell%20Powershell%20being%20broken%2C%20mail%20flow%20is%20now%20effected.%26nbsp%3B%20All%20services%20seem%20to%20be%20up%20and%20running.%26nbsp%3B%20Any%20thoughts%20on%20how%20to%20fix%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2276570%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2276570%22%20slang%3D%22en-US%22%3E%3CP%3ESorry%20for%20the%20repeat%20post%2C%20I%20was%20on%20Exchange%26nbsp%3B15.1.2176.2%20(CU19)%20which%20then%20broke.%20I%20downloaded%20Exchange%20CU20%20and%20installed.%26nbsp%3B%20This%20still%20did%20not%20resolve.%20Digging%20through%20the%20event%20log%2C%20I%20found%20repeatedly%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Eevent%20ID%2015021%20HttpEvent%2C%26nbsp%3BAn%20error%20occurred%20while%20using%20SSL%20configuration%20for%20endpoint%200.0.0.0%3A444.%20The%20error%20status%20code%20is%20contained%20within%20the%20returned%20data.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EDoing%20some%20digging%20I%20found%20this%20article.%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fwww.vcloudnine.de%2Fmicrosoft-exchange-2013-shows-blank-ecp-owa-after-changes-to-ssl-certificates%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fwww.vcloudnine.de%2Fmicrosoft-exchange-2013-shows-blank-ecp-owa-after-changes-to-ssl-certificates%2F%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20followed%20those%20instructions%20and%20got%20my%20server%20back!%20PowerShell%2C%20OWA%20and%20ECP%20and%20mailflow%20are%20working%20now.%26nbsp%3B%20I%20had%20never%20changed%20SSL%20certificates%20in%20the%20last%20year%20and%20I%20know%20OWA%2C%20ECP%2C%20PowerShell%20and%20mailflow%20all%20were%20working%20before%20I%20did%20this%20update.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20think%20I%20should%20hold%20off%20on%20this%20update%20till%20we%20get%20some%20more%20information%20on%20what%20is%20going%20on.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2276585%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2276585%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F91217%22%20target%3D%22_blank%22%3E%40Lyle%20Epstein%3C%2FA%3E%26nbsp%3B-%20great%20that%20you%20were%20able%20to%20solve%20this%20problem!%20Can%20you%20share%20how%20you%20installed%20the%20update%3F%20Was%20it%20installed%20via%20Microsoft%20Update%20(MU)%20or%20a%20manual%20install%20and%20if%20manually%2C%20di%20you%20just%20double-click%20on%20the%20.msp%20file%20after%20download%20or%20did%20you%20run%20it%20from%20the%20elevated%20CMD%20prompt%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2276589%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2276589%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%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.%20I%20installed%20the%20update%20via%20Windows%20Updates.%20Looking%20through%20the%20logs%20now%2C%20I%20had%20the%20following%203%20updates%20to%20be%20installed.%20KB5001382%2C%20KB890830%20and%20KB5001779%20.%20All%203%20were%20installed%20successfully%2C%20but%20when%20I%20rebooted%20and%20logged%20back%20in%2C%20the%20troubles%20began.%26nbsp%3B%20Looking%20back%20in%20Exchange%20logs%20is%20where%20I%20figured%20out%20I%20was%20on%20CU19%20(sorry%20for%20the%20confusion).%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI'll%20monitor%20this%20blog%20to%20see%20when%20update%20progress%20is%20made%20for%20all.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%2C%3C%2FP%3E%3CP%3ELyle%20Epstein%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2276621%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2276621%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%20Hello%20Nino.%26nbsp%3BKB5001779%2C%20just%20like%20KB5000871%20is%20not%20visible%20by%20running%26nbsp%3Bget-hotfix%20or%20by%20looking%20for%20updates%20in%20WAC%20when%20installed%20on%20a%20Windows%202019%20Core%20server.%26nbsp%3B%20%26nbsp%3BThis%20is%20not%20a%20problem%20with%20other%20Windows%20Server%20security%20hotfixes%20-%20only%20with%20Exchange%20hotfixes.%26nbsp%3B%20%26nbsp%3BThis%20is%20an%20issue%20for%20administrators%2C%20installers%2C%20etc.%26nbsp%3B%20When%20will%20this%20be%20addressed%3F%26nbsp%3B%26nbsp%3B%20Do%20you%20see%20the%20same%20thing%20on%20your%20Windows%202019%20Core%20servers%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2276735%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2276735%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%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.%20Could%20you%20please%20confirm%20if%20the%20following%20code%20with%20%22isScript%20%3D%20true%22%20would%20work%20or%20not%3F%3C%2FP%3E%3CPRE%3Epowershell.AddCommand(new%20Command(%22commandText%22%2C%20%3CSTRONG%3EisScript%3C%2FSTRONG%3E))%3B%3C%2FPRE%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2276924%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2276924%22%20slang%3D%22en-US%22%3E%3CP%20class%3D%22p1%22%3E%3CSPAN%20class%3D%22s1%22%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1028305%22%20target%3D%22_blank%22%3E%40Jesper_Lerch%3C%2FA%3E%20yes%20cu%20re%20installation%3C%2FSPAN%3E%3C%2FP%3E%3CP%20class%3D%22p1%22%3E%3CSPAN%20class%3D%22s1%22%3Edon%E2%80%99t%20work%20my%20case%20%3C%2FSPAN%3E%3CSPAN%20class%3D%22s2%22%3E%3Afrowning_face%3A%3C%2FSPAN%3E%3C%2FP%3E%3CP%20class%3D%22p1%22%3E%3CSPAN%20class%3D%22s1%22%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%3C%2FSPAN%3E%3C%2FP%3E%3CP%20class%3D%22p2%22%3E%26nbsp%3B%3C%2FP%3E%3CP%20class%3D%22p1%22%3E%3CSPAN%20class%3D%22s1%22%3EWe%20have%20tried%20all%20the%20steps.%20I%20think%20we%20have%20a%20%22multi%20-%20problem%22%20here.%20Also%20reinstalled%20the%20CU20%20several%20times%20without%20Sec.%20patch.%20Exchange%20services%20are%20all%20running.%20Fortunately%20it%20is%20only%20for%20the%20Hybird%20scenario%20and%20internal%20relay.%20Smtp%20even%20works%20but%20no%20powershell%20no%20single%20web%20service.%20What%20sequence%20in%20the%20individual%20steps%20would%20you%20suggest%20here%201%20CU20%20new%20without%20sec%20patch.%202.%20try%20to%20fix%202012%3C%2FSPAN%3E%3C%2FP%3E%3CP%20class%3D%22p1%22%3E%3CSPAN%20class%3D%22s1%22%3EHTTP%20500.%20does%20this%20also%20apply%20to%20the%20powershell%20not%20working.%20hmmmm%20I%20have%20also%20patched%2010%20exchange%20environments%20not%20a%20single%20problem.%20Have%20a%20nice%20weekend.%20Hope%20i%20get%20this%20server%20running%20again%20don't%20want%20a%20recovery%20installation%20or%20new%20one.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2276934%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2276934%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1028179%22%20target%3D%22_blank%22%3E%40MIJ2021%3C%2FA%3E%26nbsp%3BThat%20sounds%20similar%20to%20the%20issue%20I%20ran%20into%20with%20powershell%20and%20http%20error.%20Did%20you%20check%20the%20certificate%20binding%20on%200.0.0.0%3A444%20%3F%20See%20this%20article%20I%20followed%20that%20fixed%20mine%3A%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fwww.vcloudnine.de%2Fmicrosoft-exchange-2013-shows-blank-ecp-owa-after-changes-to-ssl-certificates%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fwww.vcloudnine.de%2Fmicrosoft-exchange-2013-shows-blank-ecp-owa-after-changes-to-ssl-certificates%2F%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ELyle%20Epstein%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2276949%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2276949%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%3CSPAN%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F91217%22%20target%3D%22_blank%22%3E%40Lyle%20Epstein%3C%2FA%3E%20yes%20try%20this%20also%20and%20much%20more%20things%20but%20nothing%20helps.%20Think%20re%20install%20cu20%20again.%20befor%20i%20deinstall%20latest%20sec%20patch%20and%20run%20all%20known%20fixes%20again.%20When%20this%20not%20help%20i%20must%20run%20a%20recovery%20installation%20or%20new%20one%20br%20Johannes%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2277105%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2277105%22%20slang%3D%22en-US%22%3E%3CP%3EHello%20Everyone%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EDid%20anyone%20of%20you%20received%26nbsp%3BApril%202021%20Exchange%20Server%20Security%20Updates%20via%20windows%20update%20as%20said%20by%20Microsoft%3F%20I%20am%20using%20Win%202019%2FExch%202019%20with%20CU9.%20I%20do%20not%20see%20anything%20related%20to%20Exchange%20yet%20WU.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%22Method%201%3A%20Microsoft%20Update%3C%2FP%3E%3CP%20class%3D%22%22%3EThis%20update%20is%20available%20through%20Windows%20Update.%20When%20you%20turn%20on%20automatic%20updating%2C%20this%20update%20will%20be%20downloaded%20and%20installed%20automatically.%26nbsp%3BFor%20more%20information%20about%20how%20to%20turn%20on%20automatic%20updating%2C%20see%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3CA%20href%3D%22https%3A%2F%2Fsupport.microsoft.com%2Fhelp%2F12373%2Fwindows-update-faq%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3EWindows%20Update%3A%20FAQ%3C%2FA%3E.%3F%7C%22%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2277186%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2277186%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%3BI've%20asked%20my%20vendor%20to%20correct%20the%20code%2C%20possibly%20I%20hope%20to%20get%20positive%20response.%20With%20this%2C%20should%20I%20consider%20there%20is%20no%20further%20update%20or%20a%20fix%20to%20work%20with%20existing%20code%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2277283%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2277283%22%20slang%3D%22en-US%22%3E%3CP%3EI'm%20trying%20to%20update%20from%20CU19%20to%20CU20%20on%20server%202016%20but%20the%20CU20%20setup%20fails%3A%3C%2FP%3E%3CP%3EError%3A%3CBR%20%2F%3EAccess%20to%20the%20path%20'C%3A%5CProgram%20Files%5CMicrosoft%5CExchange%20Server%5CV15%5CBin%5Cperf%5Camd64%5Cdscperf.ini.tmp'%20is%20denied.%3C%2FP%3E%3CP%3EWarning%3A%3CBR%20%2F%3EAn%20unexpected%20error%20has%20occurred%20and%20a%20Watson%20dump%20is%20being%20generated%3A%20Access%20to%20the%20path%20'C%3A%5CProgram%20Files%5CMicrosoft%5CExchange%20Server%5CV15%5CBin%5Cperf%5Camd64%5Cdscperf.ini.tmp'%20is%20denied.%3C%2FP%3E%3CP%3EThis%20file%20doesn't%20exist.%3C%2FP%3E%3CP%3Eupdate%20source%3A%20ExchangeServer2016-x64-CU20.ISO%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2277341%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2277341%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F928822%22%20target%3D%22_blank%22%3E%40Prasad3435%3C%2FA%3E%26nbsp%3B-%20That%20is%20correct%3B%20the%20new%20behavior%20is%20expected%20after%20April%20update%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1029584%22%20target%3D%22_blank%22%3E%40blazegw%3C%2FA%3E%26nbsp%3B-%20have%20you%20rebooted%20the%20machine%20before%20the%20installation%3F%20It%20could%20be%20that%20something%20has%20the%20file%20locked%3B%20could%20you%20try%20to%20temporarily%20pause%20a%20file-level%20AV%20protection%20if%20it%20is%20running%20on%20the%20machine%3F%20Alternatively%2C%20you%20can%20run%20the%20SetupAssist%20script%20which%20will%20help%20you%20validate%20that%20the%20permissions%20are%20all%20in%20order%20when%20trying%20to%20run%20setup%3A%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fgithub.com%2Fmicrosoft%2FCSS-Exchange%2Ftree%2Fmain%2FSetup%23setupassistps1%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3ECSS-Exchange%2FSetup%20at%20main%20%C2%B7%20microsoft%2FCSS-Exchange%20(github.com)%3C%2FA%3E%26nbsp%3B(links%20directly%20to%20that%20script%20description)%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2277427%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2277427%22%20slang%3D%22en-US%22%3E%3CP%3EMailbox%20databases%20were%20not%20enumerated%20by%20the%20backup%20job%20in%3CSTRONG%3E%20HP%20Data%20Protector%3C%2FSTRONG%3E%20backup%20software%2C%20similar%20to%20the%20Netapp%20Snapmanager%20backup%20software%20causing%20Exchange%20backup%20jobs%20to%20fail.%3CBR%20%2F%3EAfter%20removing%26nbsp%3B%20(KB5001779)%26nbsp%3B%20%2C%20exchange%20backups%20began%20working%20again.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2277438%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2277438%22%20slang%3D%22en-US%22%3E%3CP%3ETried%20to%20install%20KB5001779%20on%20Exchange%202013%20Windows%20Server%202012%20today%2C%20it%20failed%20and%20now%20all%20Exchange%20services%20are%20now%20unable%20to%20start%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EDid%20anyone%20experience%20the%20same%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2277590%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2277590%22%20slang%3D%22en-US%22%3E%3CP%3EG'day!%20Was%20this%20change%20to%20a%20basic%20function%20(used%20by%20authorised%203rd%20party%20products)%20advised%20to%20the%203rd%20party%20vendors%20before%20release%20to%20ensure%20that%20stuff%20didn't%20break%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2277599%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2277599%22%20slang%3D%22en-US%22%3E%3CP%3EAnyone%20seen%20an%20issue%20after%20installing%26nbsp%3BApril's%20KB5000871%20security%20update%20%26amp%3B%20Exch2016%20CU20%3F%26nbsp%3B%20First%20of%20all%20if%20you%20do%20it%20in%20that%20order%2C%20then%20you%20have%20to%20install%20KB50000871%20a%20second%20time.%26nbsp%3B%20After%20that%2C%20half%20of%20my%20Exchange%20services%20would%20not%20auto-start%20after%20a%20server%20restart.%26nbsp%3B%20They%20did%20manually%20start%20thank%20goodness.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2277604%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2277604%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1029435%22%20target%3D%22_blank%22%3E%40Amair1608%3C%2FA%3E%26nbsp%3Bre%20hotfix%20via%20Windows%20Update%3C%2FP%3E%3CP%3ENo%2C%20the%20hotfix%20%3CEM%3Edid%20not%3C%2FEM%3E%20show%20up%20via%20Windows%20Update%20for%20me%20on%20Windows%20Server%202019%20Core%20either.%26nbsp%3B%20%26nbsp%3BIt%20%3CEM%3Edid%3C%2FEM%3E%20show%20up%20on%20Windows%20Server%202016.%26nbsp%3B%20Inconsistencies%20and%20quirks%20in%20Exchange%20have%20been%20going%20on%20for%20years%20and%20have%20come%20to%20be%20expected%20with%20every%20new%20CU%20and%20update.%26nbsp%3B%20If%20you%20contact%20Microsoft%20they%20will%20likely%20have%20some%20excuse%20why%20it%20doesn't%20show%20up%20or%20they%20will%20put%20the%20onus%20on%20you%20to%20deal%20with%20it%20or%20workaround%20their%20problem%20somehow.%26nbsp%3B%20Very%20disappointing.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2277680%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2277680%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%3B%3C%2FP%3E%3CP%3EHaving%20installed%20this%20update%20on%20Exchange%202016%20CU19%3B%20will%20we%20need%20to%20reinstall%20after%20upgrading%20to%20E2016%20CU20%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2277730%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2277730%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1030075%22%20target%3D%22_blank%22%3E%40steveallen1977%3C%2FA%3E%26nbsp%3Byes.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2277773%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2277773%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%2F5374%22%20target%3D%22_blank%22%3E%40Nino%20Bilic%2C%3C%2FA%3E%3C%2FP%3E%3CP%3EWe%20are%20running%20two%20Exchange%202013%20CU23%20installations%20on%202012%20R2%20with%20a%20cross%20forest%20configuration.%3C%2FP%3E%3CP%3EUpdate%20KB5001779%20broke%20the%20ability%20to%20see%20the%20free%2Fbusy%20information%20of%20the%20other%20organization%20in%20both%20ways.%3C%2FP%3E%3CP%3EThe%20only%20hints%20in%20the%20logs%20are%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CPRE%20class%3D%22lia-code-sample%20language-markup%22%3E%3CCODE%3EAutodiscover%2Cautodiscoverxxxxxxxxxx%2C%2Fautodiscover%2Fautodiscover.svc%2C%2C%2Cfalse%2C%2C%2C%2CASAutoDiscover%2FCrossForest%2FEmailDomain%2F%2F15.00.1497.015%2C10.20.30.138%2CSERVERNAME%2C401%2C%2CUnauthenticatedRequest%2CPOST%2C%2C%2C%2C%2C%2C%2C%2C%2C1338%2C%2C%2C%2C1%2C%2C%2C0%2C%2C0%2C%2C0%2C0%2C%2C0%2C9%2C0%2C%2C%2C%2C%2C%2C%2C%2C%2C0%2C8%2C0%2C%2C8%2C%2C9%2C9%2C%2C%2C%2CBeginRequest%3D2021-04-19T07%3A20%3A03.518Z%3BCorrelationID%3D%3CEMPTY%3E%3BProxyState-Run%3DNone%3BProxyState-Complete%3DCalculateBackEnd%3BEndRequest%3D2021-04-19T07%3A20%3A03.533Z%3B%2C%0AAutodiscover%2Cautodiscovexxxxxxxxxx%2C%2Fautodiscover%2Fautodiscover.svc%2C%2CNegotiate%2Cfalse%2C%2C%2C%2CASAutoDiscover%2FCrossForest%2FEmailDomain%2F%2F15.00.1497.015%2C10.20.30.138%2CSERVERNAME%2C401%2C%2C%2CPOST%2C%2C%2C%2C%2C%2C%2C%2C%2C0%2C%2C%2C%2C%2C%2C%2C%2C%2C%2C%2C%2C%2C%2C%2C0%2C%2C%2C%2C%2C%2C%2C%2C%2C%2C%2C%2C%2C%2C0%2C%2C0%2C0%2C%2C%2C%2CBeginRequest%3D2021-04-19T07%3A20%3A03.549Z%3BCorrelationID%3D%3CEMPTY%3E%3BEndRequest%3D2021-04-19T07%3A20%3A03.549Z%3B%2C%3C%2FEMPTY%3E%3C%2FEMPTY%3E%3C%2FCODE%3E%3C%2FPRE%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIs%20anyone%20experiencing%20similar%2Fsame%20issues%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2277909%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2277909%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%3CBR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F91217%22%20target%3D%22_blank%22%3E%40Lyle%20Epstein%3C%2FA%3E%3C%2FP%3E%3CP%3E%3CBR%20%2F%3EWe%20have%20now%20solved%20the%20problem.%20I%20think%20it%20was%20a%20follow-up%20error%20or%20several%20different%20errors%20at%20the%20same%20time%20from%20the%20last%20CU%20and%20Sec%20patch%20in%20March.%3C%2FP%3E%3CP%3EThe%20permission%20structure%20was%20no%20longer%20intact%20under%3CBR%20%2F%3EC%3A%5CProgram%20Files%5CMicrosoft%5CExchange%20Server%5CV15%5CClientAccess%3CBR%20%2F%3Eas%20a%20result%20the%20CU20%20installation%20was%20not%20clean.%3C%2FP%3E%3CP%3EPermissions%20restored.%3CBR%20%2F%3ECU20%20installed%20again%3CBR%20%2F%3EUpdateConfigFiles.ps1%3CBR%20%2F%3EUpdateCas.ps1%3CBR%20%2F%3EKB5001779%3C%2FP%3E%3CP%3EHealthcheck%20%3D%26gt%3B%20all%20OK%20All%20functions%20restored.%3C%2FP%3E%3CP%3EAnd%20no%20Recovery%20Setup%20needed%20%3A)%3C%2Fimg%3E%20yeepy%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2277910%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2277910%22%20slang%3D%22en-US%22%3E%3CDIV%20class%3D%22lia-message-author-with-avatar%22%3E%3CSPAN%20class%3D%22UserName%20lia-user-name%20lia-user-rank-Occasional-Visitor%20lia-component-message-view-widget-author-username%22%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1030148%22%20target%3D%22_self%22%3E%3CSPAN%20class%3D%22%22%3E%40Sascha_Z%3C%2FSPAN%3E%3C%2FA%3E%3C%2FSPAN%3E%3C%2FDIV%3E%3CP%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3EHi%26nbsp%3B%40%3C%2FSPAN%3E%3CSPAN%20class%3D%22UserName%20lia-user-name%20lia-user-rank-Occasional-Visitor%20lia-component-message-view-widget-author-username%22%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1030148%22%20target%3D%22_self%22%3E%3CSPAN%20class%3D%22%22%3ESascha_Z%2C%3C%2FSPAN%3E%3C%2FA%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22UserName%20lia-user-name%20lia-user-rank-Occasional-Visitor%20lia-component-message-view-widget-author-username%22%3E%3CSPAN%20class%3D%22%22%3EWe%20also%20run%20a%20cross%20forest%20deployment%20and%20after%20deploying%20the%20April%202021%20update%20it%20has%20broken%20our%20free%5Cbusy%20as%20well.%20We%20have%20an%20urgent%20ticket%20open%20with%20Microsoft%20and%20will%20soon%20escalate%20it%20to%20critical%20as%20our%20institution%20relies%20heavily%20on%20seeing%20each%20others%20availability.%26nbsp%3B%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2278439%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2278439%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%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhen%20attempting%20to%20use%20PSRemoting%20to%20remotely%20manage%20Exchange%20we%20now%20get%20the%20aforementioned%20%22The%20syntax%20is%20not%20supported%20by%20this%20runspace.%20This%20can%20occur%20if%20the%20runspace%20is%20in%20no-language%20mode.%22%20error.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EYou%20mentioned%20in%20your%20post%20that%20we%20should%20use%20the%20%22AddCommand%22%20method%20as%20a%20workaround%2C%20but%20that's%20only%20helpful%20for%20those%20using%20C%23.%20What%20about%20us%20admins%20that%20are%20trying%20to%20use%20PowerShell%20to%20automate%20things%20via%20Invoke-Command%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2278494%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2278494%22%20slang%3D%22en-US%22%3E%3CP%3EIt%20was%20an%20issue%20after%20security%20update%20on%20the%20exchange%202016%20server%2C%20after%20the%20update%20(security%20update%20release%20Apr%2013%2C%202021)%20when%20system%20rebooted%20there%20was%20BSOD%20.%3C%2FP%3E%3CP%3EStop%20code%3A%20BAD%20POOL%20CALLER%3C%2FP%3E%3CP%3EAnyone%20face%20the%20same%20thing%20or%20anyone%20have%20any%20information%20why%20it%20happen.%20Exchange%202016%20restart%20after%20BSOD%20and%20working%20fine%20but%20I%20want%20to%20know%20why%20it's%20happen.%3C%2FP%3E%3CP%3EThanks%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2278669%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2278669%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1028388%22%20target%3D%22_blank%22%3E%40lewis_holyfield%3C%2FA%3E%26nbsp%3B%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI'm%20glad%20that%20we%20are%20not%20the%20only%20ones%20facing%20this%20issue.%20Once%20your%20problem%20has%20been%20solved%20could%20you%20share%20some%20information%20about%20the%20troubleshooting%20steps%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2278708%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2278708%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1028388%22%20target%3D%22_blank%22%3E%40lewis_holyfield%3C%2FA%3E%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1030148%22%20target%3D%22_blank%22%3E%40Sascha_Z%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3ELong%20shot%2C%20but%20I've%20seen%20free%2Fbusy%20break%20between%20servers%20after%20disabling%20TLS%201.0%2F1.1%20(and%20thus%20only%20supporting%201.2%20and%20higher).%3C%2FP%3E%3CP%3EDoubt%20that's%20the%20case%20here%2C%20but%20trying%20doesn't%20hurt%20I%20presume.%3C%2FP%3E%3CP%3EBelow%20registry%20keys%20will%20configure%20.NET%20to%20use%20higher%20TLS%20levels.%20Apparently%20it%20doesn't%20default%20to%20TLS%201.2%20if%20it's%20available%20and%20not%20even%20when%20it's%20the%20only%20stack%20enabled.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWindows%20Registry%20Editor%20Version%205.00%3C%2FP%3E%3CP%3E%5BHKEY_LOCAL_MACHINE%5CSOFTWARE%5CMicrosoft%5C.NETFramework%5Cv2.0.50727%5D%3CBR%20%2F%3E%22SchUseStrongCrypto%22%3Ddword%3A00000001%3CBR%20%2F%3E%22SystemDefaultTlsVersions%22%3Ddword%3A00000001%3C%2FP%3E%3CP%3E%5BHKEY_LOCAL_MACHINE%5CSOFTWARE%5CMicrosoft%5C.NETFramework%5Cv4.0.30319%5D%3CBR%20%2F%3E%22SchUseStrongCrypto%22%3Ddword%3A00000001%3CBR%20%2F%3E%22SystemDefaultTlsVersions%22%3Ddword%3A00000001%3C%2FP%3E%3CP%3E%5BHKEY_LOCAL_MACHINE%5CSOFTWARE%5CWOW6432Node%5CMicrosoft%5C.NETFramework%5Cv2.0.50727%5D%3CBR%20%2F%3E%22SchUseStrongCrypto%22%3Ddword%3A00000001%3CBR%20%2F%3E%22SystemDefaultTlsVersions%22%3Ddword%3A00000001%3C%2FP%3E%3CP%3E%5BHKEY_LOCAL_MACHINE%5CSOFTWARE%5CWOW6432Node%5CMicrosoft%5C.NETFramework%5Cv4.0.30319%5D%3CBR%20%2F%3E%22SchUseStrongCrypto%22%3Ddword%3A00000001%3CBR%20%2F%3E%22SystemDefaultTlsVersions%22%3Ddword%3A00000001%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2278969%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2278969%22%20slang%3D%22en-US%22%3E%3CP%3Efor%20.net%20this%20looks%20solid.%20you%20need%20to%20adjust%20winhttp%2C%20powershell%205.1%20and%20schannel%20(including%20ciphers)%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2279023%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2279023%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F977615%22%20target%3D%22_blank%22%3E%40FreakyNL%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20do%20have%20Exchange%202013%2F2016%2F2019%20so%20we%20had%20to%20configure%20TLS%201.2%20in%20order%20for%20things%20to%20work.%20But%20after%20applying%20the%20patch%20things%20stopped%20working%2C%20so%20at%20this%20point%20it%20is%20worth%20a%20shot%2C%20the%20only%20reg%20keys%20we%20didnt%20have%20were%20the%20DWord%20-%26nbsp%3B%3CSPAN%3ESchUseStrongCrypto%20entries%20and%26nbsp%3Bv2.0.50727%20keys.%20I%20will%20give%20it%20a%20shot%20and%20let%20you%20all%20know.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2279609%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2279609%22%20slang%3D%22en-US%22%3E%3CDIV%20class%3D%22lia-message-author-with-avatar%22%3E%3CSPAN%20class%3D%22UserName%20lia-user-name%20lia-user-rank-Frequent-Visitor%20lia-component-message-view-widget-author-username%22%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F977615%22%20target%3D%22_self%22%3E%3CSPAN%20class%3D%22%22%3EFreakyNL%3C%2FSPAN%3E%3C%2FA%3E%3C%2FSPAN%3E%3C%2FDIV%3E%3CP%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3EI'm%20a%20team%20player...%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3ESo%20I%20applied%20the%20DWord%20entries%20into%20the%20v2.0%2F3.0%20keys%20even%20though%20TLS_1_2%20was%20already%20applied%20before%20the%20Big%20(April)%20Bang%2C%20but%20to%20no%20avail...%20%3A(%3C%2Fimg%3E%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2279806%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2279806%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSPAN%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%3Bwhen%20can%20we%20expect%20april%20security%20patch%20via%20windows%20update%3F%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2280555%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2280555%22%20slang%3D%22en-US%22%3E%3CP%3EWho%20has%20any%20updates%20how%20to%20fix%20free%20busy%20issue%3F%20Facing%20unauthenticated%20error%20on%20availability%20service%20and%20error%20401%20when%20looking%20into%20HttpProxy%20autodiscover%20logs.%3C%2FP%3E%3CP%3EOn%20fiddler%20error%20400%20is%20mentioned.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EDoes%20the%20TLS%201.2%20does%20anything%3F%20What%20is%20the%20impact%20%3F%3C%2FP%3E%3CP%3EWhen%20mention%20that%20its%20not%20stable%20doest%20it%20fix%20it%20at%20all%3F%3C%2FP%3E%3CP%3EI%20saw%20it%20mentioned%20on%20other%20issue%20as%20a%20solution%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftkolber.medium.com%2Fexchange-2019-free-busy-issue-with-exchange-2013-2016-ca902ca543a8%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Ftkolber.medium.com%2Fexchange-2019-free-busy-issue-with-exchange-2013-2016-ca902ca543a8%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EBut%20haven't%20rediscovered%20myself.%3C%2FP%3E%3CP%3EI%20ran%20some%20scripts%20like%20updatecas.ps1%20it%20copied%20some%20owa%20files%20to%20current%20folder%20but%20it%20didnt%20do%20nothing%20to%20the%20availability%20service.%3C%2FP%3E%3CP%3EI%20have%20spent%208%20hours%20today%20with%20microsoft%20with%20no%20progress%20so%20far...%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2280558%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2280558%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F497763%22%20target%3D%22_blank%22%3E%40Shaike%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EFor%20us%2C%20it%20was%20confirmed%20the%20April%202021%20update%20broke%20our%20cross%20forest%20free%2Fbusy.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2280563%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2280563%22%20slang%3D%22en-US%22%3E%3CP%3EYes%20i%20also%20confirm%20that%20ours%20is%20broken%20as%20well.%20Also%20availavility%20check%20from%20microsoft%20connecitivity%20tool%20i%20get%20error%20401%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftestconnectivity.microsoft.com%2Ftests%2FEwsTask%2Finput%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Ftestconnectivity.microsoft.com%2Ftests%2FEwsTask%2Finput%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2280568%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2280568%22%20slang%3D%22en-US%22%3E%3CP%3EAnyone%20here%20any%20good%20at%20refactoring%20scripts%20for%20this%20latest%20update%3F%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20use%20an%20azure%20automation%20hybrid%20runbook%20worker%20that%20drops%20down%20onto%20one%20of%20our%20On%20Premise%20servers%2C%20and%20invokes%20commands.%20Below%20is%20our%20script.%20Would%20love%20some%20help%20here%20if%20anyone%20knows%20what%20to%20change.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CPRE%3E%5BSystem.Management.Automation.PSCredential%5D%24Credential1%20%3D%20Get-AutomationPSCredential%20-Name%20'Redacted'%0A%24SecurePassword%20%3D%20%24LogonSecret%20%7C%20ConvertTo-SecureString%20-AsPlainText%20-Force%0A%24parameters%20%3D%20%40%7B%0A%20%20ConfigurationName%20%3D%20'Microsoft.Exchange'%0A%20%20ConnectionUri%20%3D%20'http%3A%2F%2Fredacted%2FPowerShell'%0A%20%20Credential%20%3D%20%24Credential1%0A%20%20Authentication%20%3D%20'Kerberos'%0A%20%20%0A%7D%0AInvoke-Command%20%40parameters%20-ScriptBlock%20%7B%0A%20%20%20%20New-RemoteMailbox%20-Name%20(%24Using%3AFirstName%20%2B%20%22%20%22%20%2B%20%24Using%3ALastName)%20-FirstName%20%24Using%3AFirstName%20-LastName%20%24Using%3ALastName%20-Password%20%24Using%3ASecurePassword%20-UserPrincipalName%20%24Using%3ALogonName%20-PrimarySMTP%20%24Using%3ALogonName%20-OnPremisesOrganizationalUnit%20%24Using%3AOU%20-Archive%0A%20%20%20%20Set-User%20-Identity%20%24Using%3ALogonName%20-StreetAddress%20%24Using%3AStreetAddress%20-City%20%24Using%3ACity%20-StateOrProvince%20%24Using%3AState%20-PostalCode%20%24Using%3AZip%20-Office%20%24Using%3AOfficeLocation%20-Phone%20%24Using%3APhoneNumber%20-Title%20%24Using%3ATitle%20-Department%20%24Using%3ADepartment%20-Company%20%24Using%3ACompany%20-CountryOrRegion%20%22United%20States%22%0A%20%20%20%20Set-RemoteMailbox%20-Identity%20%24Using%3ALogonName%20-EmailAddressPolicyEnabled%20%24true%0A%20%20%20%20%7D%3C%2FPRE%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2280596%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2280596%22%20slang%3D%22en-US%22%3E%3CP%3EI%20figured%20this%20out.%20Switched%20to%20importing%20the%20module%20as%20described%20in%20the%20blog%20below%2C%20removed%20the%20codeblock%20and%20invoke%20commands%2C%20and%20it%20worked.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fwww.codeisahighway.com%2Fhow-to-use-office-365-exchange-powershell-module-in-azure-automation%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fwww.codeisahighway.com%2Fhow-to-use-office-365-exchange-powershell-module-in-azure-automation%2F%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CPRE%3E%24Session%20%3D%20New-PSSession%20-ConfigurationName%20Microsoft.Exchange%20-ConnectionUri%20http%3A%2F%2Fredacted%2Fpowershell%20-Authentication%20Kerberos%20-Credential%20%24Credential1%0AImport-Module%20(Import-PSSession%20-Session%20%24Session%20-DisableNameChecking%20-AllowClobber)%20-Global%0A%0A%20%20%20%20New-RemoteMailbox%20-Name%20(%24FirstName%20%2B%20%22%20%22%20%2B%20%24LastName)%20-FirstName%20%24FirstName%20-LastName%20%24LastName%20-Password%20%24SecurePassword%20-UserPrincipalName%20%24LogonName%20-PrimarySMTP%20%24LogonName%20-OnPremisesOrganizationalUnit%20%24OU%20-Archive%0A%20%20%20%20Set-User%20-Identity%20%24LogonName%20-StreetAddress%20%24StreetAddress%20-City%20%24City%20-StateOrProvince%20%24State%20-PostalCode%20%24Zip%20-Office%20%24OfficeLocation%20-Phone%20%24PhoneNumber%20-Title%20%24Title%20-Department%20%24Department%20-Company%20%24Company%20-CountryOrRegion%20%22United%20States%22%0A%20%20%20%20Set-RemoteMailbox%20-Identity%20%24LogonName%20-EmailAddressPolicyEnabled%20%24true%3C%2FPRE%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2280885%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2280885%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F497763%22%20target%3D%22_blank%22%3E%40Shaike%3C%2FA%3E%26nbsp%3Band%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1028388%22%20target%3D%22_blank%22%3E%40lewis_holyfield%3C%2FA%3E%26nbsp%3B-%20can%20you%20confirm%3F%20Do%20you%20use%20Federated%20Sharing%20(that%20works)%20or%20-%20if%20not%2C%20do%20you%20use%20OrgWideAccount%20or%20%3CSPAN%3EPerUserAccount%20on%20your%20Availability%20config%3F%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2281149%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2281149%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20use%20availability%20address%20space%20with%20PerUserFB%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2281237%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2281237%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%3EWe%20are%20using%20perUserFB%20as%20well.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2281278%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2281278%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%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ECan%20we%20expect%20Security%20update%20via%20windows%20update%3F%20or%20we%20have%20wait%20till%20next%20CU%20released%3F%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ECurrently%20I%20am%20using%20win2019%2F%20Exchange%202019%20CU9%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2281286%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2281286%22%20slang%3D%22en-US%22%3E%3CP%3EMicrosoft%20recommended%20me%20to%20set%20TLS%201.2%20as%20default%20for%20.NetFramework%204%20.%20I%20didnt%20apply%20yet.%20I%20would%20be%20happy%20to%20hear%20if%20someone%20already%20did%20and%20if%20it%20fixed%20the%20free%20busy%20issue%20or%20might%20make%20others.%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1028388%22%20target%3D%22_blank%22%3E%40lewis_holyfield%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2281522%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2281522%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F5374%3Femcs_t%3DS2h8ZW1haWx8dG9waWNfc3Vic2NyaXB0aW9ufEtOTDBYTzRRTElKQzh8MjI3NjYyMXxTVUJTQ1JJUFRJT05TfGhL%22%20target%3D%22_blank%22%3E%40Nino%20Bilic%3C%2FA%3E%26nbsp%3Band%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F497763%22%20target%3D%22_blank%22%3E%40Shaike%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EPerUserAccount%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2281539%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2281539%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1028388%22%20target%3D%22_blank%22%3E%40lewis_holyfield%3C%2FA%3E%26nbsp%3Bdid%20the%20tls%20fixed%20the%20free%20busy%3For%20impact%20somehow%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2281549%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2281549%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1029435%22%20target%3D%22_blank%22%3E%40Amair1608%3C%2FA%3E%26nbsp%3B-%20The%20April%20security%20update%20should%20be%20on%20Microsoft%20Update%20(MU)%20already.%20Are%20you%20sure%20it%20is%20not%20already%20installed%20if%20you%20are%20not%20seeing%20it%20show%20up%3F%20It%20will%20be%20listed%20in%20add%2Fremove%20under%20%22Microsoft%20Exchange%20Server%202019%20Cumulative%20Update%209%20-%20Software%20Updates%20(1)%22%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2281571%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2281571%22%20slang%3D%22en-US%22%3E%3CP%3EHas%20there%20been%20a%20fix%20released%20for%20administrating%20the%20environment%20with%20accounts%20that%20have%20%24%20in%20the%20username%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2281583%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2281583%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F114800%22%20target%3D%22_blank%22%3E%40Corbett%20Enders%3C%2FA%3E%26nbsp%3B-%20Not%20yet%2C%20no.%20As%20of%20now%2C%20we%20have%20no%20workarounds%20other%20than%20renaming%20the%20accounts%20to%20remove%20the%20%22%24%22%20symbol%20from%20the%20end%20of%20the%20account%20name.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2281586%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2281586%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%3Bwhat's%20the%20state%20of%20fixing%20the%20free%20busy%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2281599%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2281599%22%20slang%3D%22en-US%22%3E%3CDIV%20class%3D%22lia-quilt-column%20lia-quilt-column-16%20lia-quilt-column-left%20lia-quilt-column-header-left%22%3E%3CDIV%20class%3D%22lia-quilt-column-alley%20lia-quilt-column-alley-left%22%3E%3CDIV%20class%3D%22lia-message-post-date%20lia-component-post-date%20lia-component-message-view-widget-post-date%22%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%2C%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F497763%22%20target%3D%22_blank%22%3E%40Shaike%3C%2FA%3E%26nbsp%3B%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1028388%22%20target%3D%22_blank%22%3E%40lewis_holyfield%3C%2FA%3E%3C%2FDIV%3E%3CDIV%20class%3D%22lia-message-post-date%20lia-component-post-date%20lia-component-message-view-widget-post-date%22%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1030148%22%20target%3D%22_blank%22%3E%40Sascha_Z%3C%2FA%3E%26nbsp%3B%3C%2FDIV%3E%3CDIV%20class%3D%22lia-message-post-date%20lia-component-post-date%20lia-component-message-view-widget-post-date%22%3E%26nbsp%3B%3C%2FDIV%3E%3CDIV%20class%3D%22lia-message-post-date%20lia-component-post-date%20lia-component-message-view-widget-post-date%22%3EShameless%20tagging%2C%20sorry%20%3A)%3C%2Fimg%3E%3C%2FDIV%3E%3CDIV%20class%3D%22lia-message-post-date%20lia-component-post-date%20lia-component-message-view-widget-post-date%22%3E%26nbsp%3B%3C%2FDIV%3E%3CDIV%20class%3D%22lia-message-post-date%20lia-component-post-date%20lia-component-message-view-widget-post-date%22%3EHere%20free%2Fbusy%20issues%20as%20well.%202013%20cu23%20with%20peruseraccount%20freebusy%20and%20AD%20trusts%20to%202%20forests.%3C%2FDIV%3E%3CDIV%20class%3D%22lia-message-post-date%20lia-component-post-date%20lia-component-message-view-widget-post-date%22%3E1%20forest%20can%20still%20read%20our%20FB%2C%20I%20am%20waiting%20for%20feedback%20from%20the%202nd.%3CBR%20%2F%3EWe%20cannot%20read%20their%20FB%2C%201%20forest%20returns%20error%20400%20%2C%20the%20other%20%22The%20underlying%20connection%20was%20closed%3A%20An%20unexpected%20error%20occurred%20on%20a%20send..%20%22%3C%2FDIV%3E%3CDIV%20class%3D%22lia-message-post-date%20lia-component-post-date%20lia-component-message-view-widget-post-date%22%3E%26nbsp%3B%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2281609%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2281609%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%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1028388%22%20target%3D%22_blank%22%3E%40lewis_holyfield%3C%2FA%3E%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F497763%22%20target%3D%22_blank%22%3E%40Shaike%3C%2FA%3E%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1030148%22%20target%3D%22_blank%22%3E%40Sascha_Z%3C%2FA%3E%26nbsp%3B%3CBR%20%2F%3Eanother%20broken%20free%2Fbusy%20here%3C%2FP%3E%3CP%3Ecross-forest%20with%202%20forests%2CEX%202013%20on%20our%20end%2CPerUserFB%3C%2FP%3E%3CP%3EForest%201%3A%20They%20can%20see%20our%20FB%20but%20we%20cannot%20see%20theirs.%20HTTP%20400%20bad%20requests%20popping%20up.%3C%2FP%3E%3CP%3EForest%202%3A%20We%20cannot%20see%20their%20FB%2C%20waiting%20for%20feedback%20if%20they%20can%20see%20ours.%26nbsp%3B%20%22Here%20we%20have%20The%20underlying%20connection%20was%20closed%3A%20An%20unexpected%20error%20occurred%20on%20a%20send..%22%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2281623%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2281623%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%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1028388%22%20target%3D%22_blank%22%3E%40lewis_holyfield%3C%2FA%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F497763%22%20target%3D%22_blank%22%3E%40Shaike%3C%2FA%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1030148%22%20target%3D%22_blank%22%3E%40Sascha_Z%3C%2FA%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F213824%22%20target%3D%22_blank%22%3E%40Katrien%20Cornelis%3C%2FA%3E%26nbsp%3B%40Katrien%20Corneli%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWilling%20to%20try%20this%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2F1drv.ms%2Fu%2Fs!AgWXDh9ZFk5oakAR7hljERmlZTo%3Fe%3DWWKwcC%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttps%3A%2F%2F1drv.ms%2Fu%2Fs!AgWXDh9ZFk5oakAR7hljERmlZTo%3Fe%3DWWKwcC%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ERef%3A%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftkolber.medium.com%2Fexchange-2019-free-busy-issue-with-exchange-2013-2016-ca902ca543a8%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Ftkolber.medium.com%2Fexchange-2019-free-busy-issue-with-exchange-2013-2016-ca902ca543a8%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2281679%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2281679%22%20slang%3D%22en-US%22%3E%3CP%3EI%20have%20no%20idea%20how%20to%20apply%20.AddScript()%20or%20.AddCommand().%26nbsp%3B%20The%20script%20I%20am%20running%20(from%20a%20remote%20server)%20is%20as%20follows%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CPRE%3EInvoke-Command%20-Session%20%24ExOSessionVariable%20-ScriptBlock%20%7BGet-RemoteMailbox%20-Identity%20UserName%20%3B%20Get-User%20-Identity%20UserName%7D%3C%2FPRE%3E%3CP%3EAnd%20I'm%20getting%20the%20following%20error%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CPRE%3EThe%20syntax%20is%20not%20supported%20by%20this%20runspace.%20This%20can%20occur%20if%20the%20runspace%20is%20in%20no-language%20mode.%3C%2FPRE%3E%3CP%3EI'm%20just%20an%20amateur%20Powershell%20scripter%20and%20have%20no%20idea%20how%20to%20apply%26nbsp%3B.AddCommand().%26nbsp%3B%20Any%20help%20is%20appreciated.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2281692%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2281692%22%20slang%3D%22en-US%22%3E%3CP%3EFree%20busy%20works%20with%20tls%201.2%20as%20default%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2281772%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2281772%22%20slang%3D%22en-US%22%3E%3CP%3EBut%20tls%201.2%20breaks%20mail%20flow%20with%20exchange%202010.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2282146%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2282146%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F497763%22%20target%3D%22_blank%22%3E%40Shaike%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ENot%20applicable%20as%20we%20are%20on%20Exchange%202013%2F2016%2F2019%20and%20it%20was%20working...%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2282819%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2282819%22%20slang%3D%22en-US%22%3E%3CP%3EOur%20Exchange%20Server%20(2016)%20was%20also%20pretty%20much%20bricked%20by%20these%20April%20updates%2C%20at%20least%20no%20email%20clients%20Outlook%20etc.%20could%20connect.%26nbsp%3B%20Microsoft%20spent%2018%20hours%20over%20night%20on%20our%20server%20getting%20it%20back%20up%20and%20working%2C%20the%20problem%20looks%20to%20have%20been%20a%20corrupt%20self%20signed%20certificate.%26nbsp%3B%20The%20server%20was%20working%20fine%20before%20hand%20and%20had%20had%20March's%20update%20applied%20no%20issues.%26nbsp%3B%20Anyone%20else%20had%20similar%20certificate%20issues%20and%20lost%20server%20functionality%20after%20applying%20these%20updates%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2282889%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2282889%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1034795%22%20target%3D%22_blank%22%3E%40AndyC1969%3C%2FA%3E%26nbsp%3B.%20I%20had%20the%20same%20issue%2C%20which%20I%20documented%20in%20this%20thread.%20For%20me%2C%20after%20installing%20the%20update%20PowerShell%2C%20OWA%2C%20ECP%20and%20mail%20flow%20all%20stopped%20working.%20The%20fix%20I%20documented%20in%20this%20thread%20got%20me%20back%20up%20and%20running%2C%20it%20was%20an%20unknown%20certificate%20that%20I%20had%20to%20remove%20with%20netsh.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2282944%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2282944%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F91217%22%20target%3D%22_blank%22%3E%40Lyle%20Epstein%3C%2FA%3E%26nbsp%3BWhat%20was%20the%20fix%3F%26nbsp%3B%3C%2FP%3E%3CP%3EAnd%20how%20dif%20you%20find%20the%20corrupted%20certificate%20what%20was%20the%20impact%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2282948%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2282948%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F497763%22%20target%3D%22_blank%22%3E%40Shaike%3C%2FA%3E%26nbsp%3BI%20followed%20this%20guide%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fwww.vcloudnine.de%2Fmicrosoft-exchange-2013-shows-blank-ecp-owa-after-changes-to-ssl-certificates%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fwww.vcloudnine.de%2Fmicrosoft-exchange-2013-shows-blank-ecp-owa-after-changes-to-ssl-certificates%2F%3C%2FA%3E%26nbsp%3Bwhich%20lead%20me%20to%20the%20bad%20certificate%20and%20removal%20and%20repair.%20Once%20I%20did%20that%2C%20PowerShell%2C%20ECP%2C%20OWA%20and%20mailflow%20all%20worked%20again%20as%20they%20were%20broken%20after%20I%20installed%20this%20update.%20Even%20re-installing%20CU20%20left%20it%20broken%20until%20I%20fixed%20the%20broken%20certificate.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2284533%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2284533%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_self%22%3E%3CSPAN%20class%3D%22%22%3ENino%20Bilic%3C%2FSPAN%3E%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CBR%20%2F%3EI%20dont%20see%20the%20security%20updated%20nor%20its%20showing%20on%20windows%20update%20I%20have%20been%20look%20since%20the%20day%20its%20out%20but%20until%20now%20its%20not%20showing%20up.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22Amair1608_0-1619247485156.png%22%20style%3D%22width%3A%20400px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F275249i8018C14BBD6985CD%2Fimage-size%2Fmedium%3Fv%3Dv2%26amp%3Bpx%3D400%22%20role%3D%22button%22%20title%3D%22Amair1608_0-1619247485156.png%22%20alt%3D%22Amair1608_0-1619247485156.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-2291455%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2291455%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F91217%22%20target%3D%22_blank%22%3E%40Lyle%20Epstein%3C%2FA%3E%26nbsp%3BHi%20there%2C%20thanks%20for%20your%20comments%2C%20for%20us%20Outlook%20stopped%20working%2C%20everyone's%20Outlook%20showed%20%22Disconnected.%22%2C%20and%20no%20matter%20what%20we%20did%2C%20it%20wouldn't%20connect.%26nbsp%3B%20There%20may%20have%20been%20other%20parts%20of%20the%20system%20that%20also%20weren't%20functioning%2C%20but%20mailflow%20and%20OWA%20seemed%20ok%2C%20as%20that's%20what%20we%20had%20to%20use%20temporarily.%26nbsp%3B%20I'm%20still%20waiting%20for%20the%20full%20RFO%20from%20our%203rd%20Party%20and%20Microsoft%2C%20but%20looking%20at%20the%20current%20certificates%2C%20this%20one%20was%20replaced%2C%20'Issuer%20%3A%20CN%3DMicrosoft%20Exchange%20Server%20Auth%20Certificate%2C%20NotBefore%20%3A%2015%2F04%2F2021%2021%3A52%3A13'.%20Our%20email%20didn't%20start%20working%20again%20until%204%3A01am%20on%20the%2016th%2C%20so%20I%20don't%20think%20this%20was%20the%20only%20work%20that%20was%20carried%20out%20to%20fix%20it.%20I'm%20not%20looking%20forward%20to%20May's%20updated!%20%3Bo)%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2297301%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2297301%22%20slang%3D%22en-US%22%3E%3CP%3EDear%20all%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EDid%20anyone%20make%20progress%20in%20the%20F%2FB%20issue%3F%20Switched%20.NET%204%20to%20TLS1.2.%20It%20didn't%20brake%20something%20but%20F%2FB%20still%20doesn't%20work.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESascha%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2297883%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2297883%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1030148%22%20target%3D%22_blank%22%3E%40Sascha_Z%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3Ewhen%20you%20test%20availability%20thorugh%20-%20what%20do%20you%20get%20%3F%3CA%20href%3D%22https%3A%2F%2Ftestconnectivity.microsoft.com%2Ftests%2FEwsTask%2Finput%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Ftestconnectivity.microsoft.com%2Ftests%2FEwsTask%2Finput%3C%2FA%3E%3C%2FP%3E%3CP%3Ewhich%20changes%20did%20you%20apply%20on%20TLS%20%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2297959%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2297959%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F497763%22%20target%3D%22_blank%22%3E%40Shaike%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EUnfortunately%20this%20test%20isn't%20applicable%20for%20our%20environment%20because%20our%20cross%20domain%20setup%20works%20with%20a%20separate%20EWS%20connector%20which%20isn't%20accessible%20through%20public%20internet.%3C%2FP%3E%3CP%3EI've%20applied%20all%20of%20them%20mentioned%20in%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftkolber.medium.com%2Fexchange-2019-free-busy-issue-with-exchange-2013-2016-ca902ca543a8%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Ftkolber.medium.com%2Fexchange-2019-free-busy-issue-with-exchange-2013-2016-ca902ca543a8%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2298038%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2298038%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1030148%22%20target%3D%22_blank%22%3E%40Sascha_Z%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3ETry%20to%20change%20only%20the%20following%20and%20not%20as%20described%20in%20the%20link...%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ECreate%20below%20registry%20key%20for%20the%20exchange%202016%20servers%20and%20reboot%20the%20servers%26nbsp%3B%3C%2FP%3E%3CP%3E%3CBR%20%2F%3E%5BHKEY_LOCAL_MACHINE%5CSOFTWARE%5CMicrosoft%5C.NETFramework%5Cv4.0.30319%5D%3C%2FP%3E%3CP%3E%22SystemDefaultTlsVersions%22%3Ddword%3A00000001%3C%2FP%3E%3CP%3E%5BHKEY_LOCAL_MACHINE%5CSOFTWARE%5CWow6432Node%5CMicrosoft%5C.NETFramework%5Cv4.0.30319%5D%3C%2FP%3E%3CP%3E%22SystemDefaultTlsVersions%22%3Ddword%3A00000001%3C%2FP%3E%3CP%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2298055%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2298055%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F497763%22%20target%3D%22_blank%22%3E%40Shaike%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThey%20are%20already%20set%20to%20these%20values%20%3A(%3C%2Fimg%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2298070%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2298070%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1030148%22%20target%3D%22_blank%22%3E%40Sascha_Z%3C%2FA%3E%26nbsp%3Bare%20you%20sure%3F%20They%20are%20not%20set%20as%20default%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2298088%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2298088%22%20slang%3D%22en-US%22%3E%3CP%3EWhat%20error%20do%20you%20get%20on%20FB%20query%3F%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1030148%22%20target%3D%22_blank%22%3E%40Sascha_Z%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2299279%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2299279%22%20slang%3D%22en-US%22%3E%3CP%3EFor%20the%20F%2FB%20issue%20we%20only%20get%20error%20400%20%22bad%20content%22%2C%20even%20when%20errortracing%20on%20other%20forest%20we%20didn't%20get%20anything%20more%20to%20go%20on.Haven't%20tried%20the%20TLS%20regkeys%20yet%20but%20I%20was%20making%20a%20status%20and%20thought%20of%20something.%3C%2FP%3E%3CP%3Eerror%20400%20%22bad%20content%22%20doesn't%20really%20say%20anything%20but%3CBR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fexchange%2Ftroubleshoot%2Fclient-connectivity%2Fexchange-security-update-issues%23http-400-errors-in-owa-and-ecp-and-connection-failure-error-in-powershell%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fexchange%2Ftroubleshoot%2Fclient-connectivity%2Fexchange-security-update-issues%23http-400-errors-in-owa-and-ecp-and-connection-failure-error-in-powershell%3C%2FA%3E%26nbsp%3B%20%2B%20%22Cannot%20serialize%20context%22%20in%20event%20viewer%204001%20events%26nbsp%3B%20%2B%20this%20part%20of%20the%20tracelog%3CBR%20%2F%3E%3CBR%20%2F%3E%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20userName%3D%22domain%5Cservername%24%22%3CBR%20%2F%3E%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20tokenUserName%3D%22domain%5Cservername%24%22%3CBR%20%2F%3E%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20authenticationType%3D%22Negotiate%22%3CBR%20%2F%3E%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20activityId%3D%22%7B80003616-0007-EF00-B63F-84710C7967BB%7D%22%3CBR%20%2F%3E%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20failureReason%3D%22STATUS_CODE%22%3CBR%20%2F%3E%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20statusCode%3D%22400%22%3CBR%20%2F%3E%3CBR%20%2F%3Emakes%20me%20think%20they%20might%20be%20related.%20Because%20there%20are%20people%20having%20issues%20authenticating%20with%20account%20names%20with%20%24%20in%2C%20and%20because%20it%20would%20fit%20the%20'bad%20content'%20reply.%20Not%20sure%20how%20I%20can%20test%20this%20hypothesis%20though%20but%20thought%20I'd%20share%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2299458%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2299458%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F213824%22%20target%3D%22_blank%22%3E%40Katrien%20Cornelis%3C%2FA%3E%26nbsp%3B%20waiting%20for%20your%20updates.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2300554%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2300554%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F497763%22%20target%3D%22_blank%22%3E%40Shaike%3C%2FA%3E%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F213824%22%20target%3D%22_blank%22%3E%40Katrien%20Cornelis%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20experience%20pretty%20much%20the%20same%20error%20as%20Katrien%20and%20I'm%20also%20of%20the%20opinion%20that%20the%20dollar%20sign%20at%20the%20end%20of%20the%20username%20is%20the%20culprit.%20In%20one%20of%20our%20tests%20we%20changed%20the%20user%20to%20a%20new%20one%20without%20%22%24%22%20and%20we%20saw%20different%20kind%20of%20problems%20but%20the%20error%20400%20was%20gone.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2300555%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2300555%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1030148%22%20target%3D%22_blank%22%3E%40Sascha_Z%3C%2FA%3E%26nbsp%3B%40I%20am%20curious%2C%20why%20do%20you%20have%20dollar%20sign%20in%20the%20user%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2300568%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2300568%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F497763%22%20target%3D%22_blank%22%3E%40Shaike%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIt's%20the%20computer%20account%3A%20CROSS_DOMAIN%3CSPAN%3E%5CexchangeserverA%24%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2300732%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2300732%22%20slang%3D%22en-US%22%3E%3CP%3EDid%20you%20check%26nbsp%3B%3CSPAN%3E%E2%80%9Cms-exch-epi-token-serialization%E2%80%9D%20permission%20to%20the%20Source%20Exchange%20Servers%20over%20the%20Target%20Forest%3F%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2300866%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2300866%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1030148%22%20target%3D%22_blank%22%3E%40Sascha_Z%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CBLOCKQUOTE%3E%3CP%3E%3CSPAN%3EI'm%20also%20of%20the%20opinion%20that%20the%20dollar%20sign%20at%20the%20end%20of%20the%20username%20is%20the%20culprit.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FBLOCKQUOTE%3E%3CP%3E%3CSPAN%3EIf%20you%20read%20through%20the%20replies%20here%20you%20would%20have%20noticed%20this%20is%20a%20confirmed%20issue.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2300867%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2300867%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1030148%22%20target%3D%22_blank%22%3E%40Sascha_Z%3C%2FA%3E%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F497763%22%20target%3D%22_blank%22%3E%40Shaike%3C%2FA%3E%26nbsp%3B%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FP%3E%3CP%3ESascha%20I'm%20curious%2C%20what%20issues%20did%20you%20experience%20after%20changing%20to%20a%20non-dollar%20account%20and%20further%20more%20%2C%20how%20did%20you%20do%20that%3F%20It's%20not%20something%20we've%20chosen%2C%20it%20just%20presents%20itself%20like%20this.Probably%20related%20to%20machine%20acc%20or%20managed%20acc%20%2Fimpersonation.%3CBR%20%2F%3EWondering%20if%20you%20tried%20logging%20on%20to%20ecp%20or%20owa%20with%20a%20%24%20account%20%2C%20and%20if%20it%20also%20gave%20issues%3F%20That%20would%20be%20easier%20to%20verify%20but%20I%20don't%20know%20if%20it%20would%20be%20reflecting%20the%20same%20issue%20or%20not.%20I'll%20try%20anyway.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EShaike%20not%20sure%20to%20whom%20it%20was%20addressed%20but%20epi-token%20was%20checked%20here%2C%20as%20were%20addressspaces.Might%20re-export%20autodiscover%20info%20but%20that%20part%20'pur%20sang'%20seems%20to%20be%20working%20in%20that%20for%20example%20the%20outlook-test%20autodiscover%20succeeds%20for%20the%20people%20from%20the%20other%20forest%20on%20first%20hit.%20However%2C%20the%20messages%20in%20E.V%20are%20about%20F%2FB%20but%20also%20Mailtips%2C%20Photos%2C..%20and%20I%20think%20they%20all%20use%20autodiscover.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2300907%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2300907%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_self%22%3E%3CSPAN%20class%3D%22%22%3ENino%20Bilic%3C%2FSPAN%3E%3C%2FA%3E%3CSPAN%3E%26nbsp%3B%20any%20update%3F%20please%20let%20me%20know%20as%20its%20already%2015%20days%20we%20did%20not%20apply%20the%20patch%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2304294%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2304294%22%20slang%3D%22en-US%22%3E%3CP%3Eunfortanetly%20cross%20forest%20free%20busy%20still%20gives%20401%20unauthorized%2C%20the%20intresting%20part%20is%20that%20using%20microsoft%20test%20connectivity%20tool%20i%20can%20see%20that%20availability%20is%20working.%3C%2FP%3E%3CP%3EI%20have%20found%20in%20a%20site%20mentioned%20that%20setting%20registry%20key%26nbsp%3B%3CSPAN%3EDisableLoopbackCheck%3C%2FSPAN%3E%26nbsp%3Bto%201.%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fserver-essentials.com%2Fsupport%2Fautodiscover-outlook-and-soap-provider-failure-the-remote-server-returned-an-error-401-unauthorized%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fserver-essentials.com%2Fsupport%2Fautodiscover-outlook-and-soap-provider-failure-the-remote-server-returned-an-error-401-unauthorized%3C%2FA%3E%3C%2FP%3E%3CP%3Eis%20any%20of%20you%20fixed%20the%20free%20busy%20cross%20forest%20%3F%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1030148%22%20target%3D%22_blank%22%3E%40Sascha_Z%3C%2FA%3E%26nbsp%3B%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%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2304300%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2304300%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F213824%22%20target%3D%22_blank%22%3E%40Katrien%20Cornelis%3C%2FA%3E%26nbsp%3B%20i%20have%20just%20noticed%20that%20you%20mentioned%20that%20you%20fix%20cross%20forest%3C%2FP%3E%3CP%3Ecan%20you%20explained%20what%20exactly%20did%20you%20exported%20as%20the%20following%3C%2FP%3E%3CP%3EExport-AutodiscoverConfig%20-TargetForestDomainController%20%22dc.contoso.com%22%20-TargetForestCredential%20(Get-Credential)%20-MultipleExchangeDeployments%20%24true%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Ei%20had%20mailtips%20issue%20as%20well%20but%20once%20i%20restarted%20the%20application%20pool%20of%20autodiscover%2C%20is%20that%20what%20you%20did%20on%20your%20side%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2305465%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2305465%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%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%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%3CSPAN%3E%26nbsp%3B%3A%20Please%20let%20us%20know%20in%20advance%20in%20case%20Microsoft%20is%20planning%20to%20stop%20Addscript(..)%20support%20from%20Skype%20and%20Lync%20too.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2306344%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2306344%22%20slang%3D%22en-US%22%3E%3CP%3EUpdate%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESo%20I%20was%20apparently%20%3CSTRONG%3Eunder%20the%20misconception%20we%20also%20installed%20the%20patch%3C%2FSTRONG%3E%20(it%20was%20planned%20but%20didn%E2%80%99t%20go%20through%20because%20of%20scheduling%20issues%2Capologies%20for%20the%20confusion).%3CBR%20%2F%3EThis%20does%20explain%20some%20things%2C%20like%20the%20fact%20that%20OUR%20f%2Fb%20is%20still%20visible%20to%20the%20other%20forests%2C%20whereas%20the%20other%20forests%20did%20do%20the%20patch%20and%20THEIR%20f%2Fb%20is%20not%20working%20for%20us.%3C%2FP%3E%3CP%3EI%20created%20two%20test%20users%2C%20identical%20aside%20from%20one%20having%20a%20%24%20as%20last%20character%20in%20his%20samaccountname.%3C%2FP%3E%3CP%3ETestexfb%20%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20to%20A%20and%20B%20Autodiscover%20link%20%3D%20Status%20200%20after%20auth%3C%2FP%3E%3CP%3ETestexfb%24%20%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20to%20A%20and%20B%20Autodiscover%20link%20%3D%20Status%20400%20after%20auth%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Elogging%20on%20to%20our%20owa%20with%20the%20testexfb%24%20account%20doesn't%20pose%20any%20issue%2C%20I'm%20going%20to%20ask%20the%20other%20forests%20to%20try%20this%20to%20see%20if%20they%20get%20an%20error%20or%20not.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESo%20despite%20status%20400%20pointing%20to%20the%20client%20%3CSTRONG%3E(us%3C%2FSTRONG%3E%20in%20this%20case)%20it%E2%80%99s%20imho%20not%20a%20matter%20of%20sending%20different%20data%20but%20rather%20of%20the%20domains%20(A%20and%20B)%20no%20longer%20being%20able%20to%20read%20%2Faccept%20the%20data.%3C%2FP%3E%3CTABLE%3E%3CTBODY%3E%3CTR%3E%3CTD%20width%3D%2240px%22%20height%3D%2285px%22%3E%3CP%3E400%3C%2FP%3E%3C%2FTD%3E%3CTD%20width%3D%2275px%22%20height%3D%2285px%22%3E%3CP%3EBad%20request%3C%2FP%3E%3C%2FTD%3E%3CTD%20width%3D%22906px%22%20height%3D%2285px%22%3E%3CP%3EThe%20Hypertext%20Transfer%20Protocol%20Stack%20(Http.sys)%20file%20blocks%20IIS%207.0%20and%20later%20versions%20from%20processing%20the%20request%20because%20of%20a%20problem%20in%20the%20request.%20Typically%2C%20this%20HTTP%20status%20code%20means%20that%20the%20request%20contains%20characters%20or%20sequences%20that%20are%20not%20valid%20or%20that%20the%20request%20contradicts%20the%20security%20settings%20in%20the%20Http.sys%20file.%3C%2FP%3E%3C%2FTD%3E%3C%2FTR%3E%3C%2FTBODY%3E%3C%2FTABLE%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F497763%22%20target%3D%22_blank%22%3E%40Shaike%3C%2FA%3EI%20think%20there%20was%2Fis%20a%20misunderstanding.%20If%20I%20do%20test-autoconfig%20via%20outlook%20i%20get%20Status%20200%20on%20first%20try%20or%20second.%3CBR%20%2F%3EI%20can%20obvi%20be%20mistaken%20but%20I%20have%20the%20idea%20that%20autodiscover%20as%20a%20service%20is%20working%20and%20was%20always%20working%2C%20it's%20only%20when%20the%20impersonation%20comes%20in%20play%20that%20stuff%20stops%20working.%20Which%20again%2C%20would%20support%20the%20hypothesis%20of%20the%20servername%24%20problem.%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CDIV%20class%3D%22mceNonEditable%20lia-copypaste-placeholder%22%3E%26nbsp%3B%3C%2FDIV%3E%3CDIV%20class%3D%22mceNonEditable%20lia-copypaste-placeholder%22%3E%26nbsp%3B%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2306368%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2306368%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F213824%22%20target%3D%22_blank%22%3E%40Katrien%20Cornelis%3C%2FA%3E%26nbsp%3Bwe%20dont%20have%20users%20with%20%24%20%2Chonestly%20i%20dont%20understand%20for%20what%20purpose%20but%20following%20the%20case%20test-webservicesconnectivity%20gives%20your%20what%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2307485%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2307485%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%222021-04-29%2017_56_55.png%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F276846iA7FED1AD2FED6E15%2Fimage-size%2Flarge%3Fv%3Dv2%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%222021-04-29%2017_56_55.png%22%20alt%3D%222021-04-29%2017_56_55.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAs%20already%20said%2C%20we%20do%20not%20use%20users%20with%20%24%20in%20the%20name.%20I%20only%20created%20a%20test%20user%20like%20that%20to%20see%20if%20this%20was%20causing%20issues%20on%20the%20other%20forests%20side%20because%20the%20samaccountname%20of%20the%20%3CSTRONG%3Ecomputerobjects%3C%2FSTRONG%3E%20have%20a%20%3CSTRONG%3E%24%3C%2FSTRONG%3E%20at%20the%20end.%20Which%20is%20the%20account%20being%20used%20when%20using%20epi-serial...%20access%20you%20configure%20for%20the%20f%2Fb.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2307545%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2307545%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F213824%22%20target%3D%22_blank%22%3E%40Katrien%20Cornelis%3C%2FA%3E%26nbsp%3Byes%20i%20understand%20that%20but%20for%20epi%20serializarion%20you%20give%20access%20just%20to%20exchange%20servers%24%20and%20not%20end%20users%20becsuse%20the%20crossforest%20request%20is%20coming%20in%20behalf%20of%20the%20server.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2308546%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2308546%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1028179%22%20target%3D%22_blank%22%3E%40MIJ2021%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3ECan%20you%20elaboratw%20which%20permissions%20needs%20ti%20be%20fixed%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EThe%20permission%20structure%20was%20no%20longer%20intact%20under%3C%2FSPAN%3E%3CBR%20%2F%3E%3CSPAN%3EC%3A%5CProgram%20Files%5CMicrosoft%5CExchange%20Server%5CV15%5CClientAccess%3C%2FSPAN%3E%3CBR%20%2F%3E%3CSPAN%3Eas%20a%20result%20the%20CU20%20installation%20was%20not%20clean.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2308734%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2308734%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%3B%20%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%3Bpeople%20here%20were%20complaining%20that%20once%20an%20account%20with%20%24%20sign%20cannot%20get%20free%20busy%20or%20reach%20owa.%3C%2FP%3E%3CP%3EWhen%20a%20crossforest%20free%20busy%20is%20done%20the%20request%20comes%20from%20domain%5Cexchange%20server%24%3C%2FP%3E%3CP%3EIsnt%20it%20the%20same%20behavior%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2310272%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2310272%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSPAN%3EJust%20had%20a%20call%20with%20microsoft%20support%20yesterday%20and%20wanted%20to%20share%20my%20info%20with%20you.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E-----------------------------------------------------------------------------------------------------------------------------%3C%2FP%3E%3CP%3E%3CSTRONG%3EIssue%20description%3C%2FSTRONG%3E%3A%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EPer-User%20Free%20busy%20information%20in%20a%20trusted%20cross-forest%20topology%20not%20visible%20after%20security%20update%20%3CSTRONG%3EKB5001779%3C%2FSTRONG%3E.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EFree%2FBusy%20lookups%20based%20on%20the%20%3CSTRONG%3EPerUser%20Availability%3C%2FSTRONG%3E%20Address%20Space%20mechanism%20do%20not%20work%20between%20trusted%20organizations%20(cross-forest)%20-%20Exchange%202013%20On-premises%20organizations.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAs%20we%20discussed%2C%20we%20are%20aware%20of%20issues%20with%20cross-forest%20Free%2FBusy%20requests%20appearing%20in%20some%20configurations%20after%20installation%20of%20the%20KB5001779%20Security%20Update%2C%20released%3A%20April%202021%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSTRONG%3EDescription%20of%20the%20security%20update%20for%20Microsoft%20Exchange%20Server%202019%2C%202016%2C%20and%202013%3A%20April%2013%2C%202021%20(KB5001779)%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Ftopic%2Fdescription-of-the-security-update-for-microsoft-exchange-server-2019-2016-and-2013-april-13-2021-kb5001779-8e08f3b3-fc7b-466c-bbb7-5d5aa16ef064%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Ftopic%2Fdescription-of-the-security-update-for-microsoft-exchange-server-2019-2016-and-2013-april-13-2021-kb5001779-8e08f3b3-fc7b-466c-bbb7-5d5aa16ef064%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20issue%20appears%20in%20configurations%20using%20the%20%E2%80%9Cper-user%20free%2Fbusy%20information%20in%20a%20trusted%20cross-forest%20topology%3A%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fexchange%2Farchitecture%2Fclient-access%2Favailability-service-for-cross-forest-topologies%3Fview%3Dexchserver-2016%23use-the-exchange-management-shell-to-configure-per-user-freebusy-information-in-a-trusted-cross-forest-topology%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fexchange%2Farchitecture%2Fclient-access%2Favailability-service-for-cross-forest-topologies%3Fview%3Dexchserver-2016%23use-the-exchange-management-shell-to-configure-per-user-freebusy-information-in-a-trusted-cross-forest-topology%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20issue%20has%20already%20been%20reported%20to%20Our%20Product%20Group%20(developers%20of%20Exchange).%3C%2FP%3E%3CP%3EThe%20problem%20is%20still%20under%20investigation.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSTRONG%3EAction%20plan%20(Workaround)%3A%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E*Use%20the%20%E2%80%9Corganization-wide%20free%2Fbusy%20information%20in%20an%20untrusted%20cross-forest%20topology%E2%80%9D%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E*Use%20the%20Exchange%20Management%20Shell%20to%20configure%20organization-wide%20free%2Fbusy%20information%20in%20an%20untrusted%20cross-forest%20topology%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fexchange%2Farchitecture%2Fclient-access%2Favailability-service-for-cross-forest-topologies%3Fview%3Dexchserver-2016%23use-the-exchange-management-shell-to-configure-organization-wide-freebusy-information-in-an-untrusted-cross-forest-topology%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fexchange%2Farchitecture%2Fclient-access%2Favailability-service-for-cross-forest-topologies%3Fview%3Dexchserver-2016%23use-the-exchange-management-shell-to-configure-organization-wide-freebusy-information-in-an-untrusted-cross-forest-topology%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E*Instead%20of%20using%20the%20Availability%20Address%20Space%20mechanism%2C%20configure%20federation%20trusts%20in%20both%20the%20Exchange%20organizations%20and%20then%20configure%20organization%20relationships%20between%20the%20organizations%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B*Configure%20a%20federation%20trust%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fexchange%2Fconfigure-a-federation-trust-exchange-2013-help%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fexchange%2Fconfigure-a-federation-trust-exchange-2013-help%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E*Create%20an%20organization%20relationship%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fexchange%2Fcreate-an-organization-relationship-exchange-2013-help%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fexchange%2Fcreate-an-organization-relationship-exchange-2013-help%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E*Managing%20Federated%20Sharing%20with%20the%20EAC%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fexchange-team-blog%2Fmanaging-federated-sharing-with-the-eac%2Fba-p%2F598111%22%20target%3D%22_blank%22%3Ehttps%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fexchange-team-blog%2Fmanaging-federated-sharing-with-the-eac%2Fba-p%2F598111%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E------------------------------------------------------------------------------------------------------------------------------------------------------%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20did%20not%20test%20the%20workaround%20yet%20so%20i%20cannot%20tell%20if%20it%20is%20working.%3C%2FP%3E%3CP%3EMaybe%20this%20will%20help%20some%20of%20you.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2324178%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2324178%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F213824%22%20target%3D%22_blank%22%3E%40Katrien%20Cornelis%3C%2FA%3E%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F497763%22%20target%3D%22_blank%22%3E%40Shaike%3C%2FA%3E%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1041689%22%20target%3D%22_blank%22%3E%40HeinrichsSven%3C%2FA%3E%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1029435%22%20target%3D%22_blank%22%3E%40Amair1608%3C%2FA%3E%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1030148%22%20target%3D%22_blank%22%3E%40Sascha_Z%3C%2FA%3E%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1028388%22%20target%3D%22_blank%22%3E%40lewis_holyfield%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EWe%20have%20just%20published%20a%20KB%20article%20on%20the%20Free%2FBusy%20issue%2C%20talking%20about%20two%20ways%20that%20this%20can%20be%20worked%20around%20at%20this%20time%3B%20please%20see%20here%3A%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Ftopic%2F-400-bad-request-error-during-autodiscover-for-per-user-free-busy-in-a-trusted-cross-forest-topology-a1d6296b-1b2b-4ecd-9ab6-d8637fe20a21%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3E%22(400)%20Bad%20Request%22%20error%20during%20Autodiscover%20for%20per-user%20free%2Fbusy%20in%20a%20trusted%20cross-forest%20topology%20(microsoft.com)%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2324832%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2324832%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%3C%2FP%3E%3CP%3EI%20was%20suspecting%20that%20once%20the%20account%20that%20being%20authenticate%20in%20cross%20forest%20is%20the%20exchange%20server%20computer%20name%24%20and%20thats%20the%20reason%20we%20get%20the%20401%20unauthorized.%20Once%20i%20changed%20to%26nbsp%3B%3CSPAN%3EUseServiceAccount%20%24false%26nbsp%3B%20instead%20to%20%24true%20it%20WORKS!%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3ENow%20microsoft%20needs%20to%20update%20the%20document%20on%3A%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fexchange%2Farchitecture%2Fclient-access%2Favailability-service-for-cross-forest-topologies%3Fview%3Dexchserver-2019%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fexchange%2Farchitecture%2Fclient-access%2Favailability-service-for-cross-forest-topologies%3Fview%3Dexchserver-2019%3C%2FA%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThank%20you!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2326281%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2326281%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%3B%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%3EThe%20linked%20workaround%20solved%20our%20issue.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThank%20you%20very%20much!%3C%2FP%3E%3CP%3ESascha%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2271262%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2271262%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%3BThe%20back-end%20seems%20fine%20to%20me.%20%2Fowa%20works%20for%20a%20regular%20user%20with%20mailbox.%20Neither%20%2Fowa%20nor%20%2Fecp%20works%20for%20my%20admin%20account%20but%20it%20doesn't%20have%20a%20mailbox.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAs%20stated%20Microsoft%20Exchange%20Shell%20fails%20with%20the%20errors%20in%20my%20previous%20post%20for%20both%20the%20Exchange%202016%20servers%20after%20installing%20the%20patch.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhilst%20that%20seems%20to%20imply%20there%20are%20issues%20with%20new-pssession%2C%20neither%20that%20nor%20enter-pssession%20throws%20errors%20when%20ran%20with%20-computername%20against%20either%20of%20them.%3C%2FP%3E%3CP%3E%3CSPAN%3E'Add-PSSnapin%20Microsoft.Exchange.Management.PowerShell.SnapIn'%20seems%20to%20load%20fine%20on%20both%20of%20them%20as%20well%20and%20was%20able%20to%20run%20the%20StopDagServerMaintenance.ps1%20script%20with%20that%20after%20loading%26nbsp%3BMicrosoft.Exchange.Management.PowerShell.SnapIn%20just%20fine.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EHave%20compared%20output%20of%26nbsp%3BGet-PowerShellVirtualDirectory%20with%20another%20customer's%202016%20(patched%20too)%20and%20didn't%20really%20notice%20any%20differences%20with%20regards%20to%20authentication%20settings%20etc.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3EDid%20note%20some%20additional%20output%20on%20the%20customer%20with%20issues%20and%20both%20the%20default%20website%20and%20the%20back-end%20listed%20powershell%20virtual%20directories%20on%20it.%20The%20Get-PowerShellVirtualDirectory%20command%20returns%20a%20'SerializationData'%20line%20on%20the%202016's%20powershell%20virtual%20directories.%20This%20doesn't%20happen%20at%202%20other%20customers.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2271272%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2271272%22%20slang%3D%22en-US%22%3E%3CP%3Ewe%20are%20also%20having%20the%20same%20issue%20after%20the%20patch%20update%20on%20Exchange%202016%20CU%2019%2C%20Exchange%20management%20won't%20load%20Queue%20viewer%20not%20loading%2C%20after%20uninstalling%20the%20patch%20from%20the%20server%20everything%20works%20fine%2C%20is%20there%20any%20solution%20for%20this%20issue.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2271274%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2271274%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%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2271278%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2271278%22%20slang%3D%22en-US%22%3E%3CP%3EWe%E2%80%99re%20running%20Exchange%202016%20CU19%20and%20are%20planning%20to%20upgrade%20to%20CU20%20in%20several%20weeks.%20Do%20we%20need%20to%20reapply%20this%20patch%20after%20installing%20CU20%20if%20we%20patch%20CU19%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2271281%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2271281%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%3Bcan%20anyone%20help%20with%20this%20issue%2C%20I%20am%20trying%20to%20call%20support%20and%20waiting%20for%20the%20last%2030%20mins%20for%20the%20call%20to%20answer.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2271283%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2271283%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F499412%22%20target%3D%22_blank%22%3E%40alabkrishnan%3C%2FA%3E%26nbsp%3Bdo%20you%20get%20the%20same%20error%20as%20I%20do%3F%3C%2FP%3E%3CP%3EWhat%20do%20you%20get%20if%20you%20start%20normal%20powershell%20as%20admin%20on%20one%20of%20the%202016%20boxes%20and%20run%3A%3C%2FP%3E%3CPRE%3EAdd-PSSnapin%20Microsoft.Exchange.Management.PowerShell.SnapIn%0AGet-PowerShellVirtualDirectory%20%7C%20fl%3C%2FPRE%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2271288%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2271288%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%3B%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%3Bif%20I%20start%20Exchange%20Toolbox%20it%20throws%20this%2C%20might%20be%20the%20root%20cause%3C%2FP%3E%3CPRE%3EDeserialization%20fails%3A%20System.IO.FileLoadException%3A%20Could%20not%20load%20file%20or%20assembly%20'Microsoft.Exchange.Data.Directory%2C%20Version%3D14.0.0.0%2C%20Culture%3Dneutral%2C%20PublicKeyToken%3D31bf3856ad364e35'%20or%20one%20of%20its%20dependencies.%20The%20located%20assembly's%20manifest%20definition%20does%20not%20match%20the%20assembly%20reference.%20(Exception%20from%20HRESULT%3A%200x80131040)%0AFile%20name%3A%20'Microsoft.Exchange.Data.Directory%2C%20Version%3D14.0.0.0%2C%20Culture%3Dneutral%2C%20PublicKeyToken%3D31bf3856ad364e35'%0A%20%20%20at%20System.Reflection.RuntimeAssembly._nLoad(AssemblyName%20fileName%2C%20String%20codeBase%2C%20Evidence%20assemblySecurity%2C%20RuntimeAssembly%20locationHint%2C%20StackCrawlMark%26amp%3B%20stackMark%2C%20IntPtr%20pPrivHostBinder%2C%20Boolean%20throwOnFileNotFound%2C%20Boolean%20forIntrospection%2C%20Boolean%20suppressSecurityChecks)%0A%20%20%20at%20System.Reflection.RuntimeAssembly.InternalLoadAssemblyName(AssemblyName%20assemblyRef%2C%20Evidence%20assemblySecurity%2C%20RuntimeAssembly%20reqAssembly%2C%20StackCrawlMark%26amp%3B%20stackMark%2C%20IntPtr%20pPrivHostBinder%2C%20Boolean%20throwOnFileNotFound%2C%20Boolean%20forIntrospection%2C%20Boolean%20suppressSecurityChecks)%0A%20%20%20at%20System.Reflection.RuntimeAssembly.InternalLoad(String%20assemblyString%2C%20Evidence%20assemblySecurity%2C%20StackCrawlMark%26amp%3B%20stackMark%2C%20IntPtr%20pPrivHostBinder%2C%20Boolean%20forIntrospection)%0A%20%20%20at%20System.Reflection.RuntimeAssembly.InternalLoad(String%20assemblyString%2C%20Evidence%20assemblySecurity%2C%20StackCrawlMark%26amp%3B%20stackMark%2C%20Boolean%20forIntrospection)%0A%20%20%20at%20System.Reflection.Assembly.Load(String%20assemblyString)%0A%20%20%20at%20System.UnitySerializationHolder.GetRealObject(StreamingContext%20context)%0A%20%20%20at%20System.Runtime.Serialization.ObjectManager.ResolveObjectReference(ObjectHolder%20holder)%0A%20%20%20at%20System.Runtime.Serialization.ObjectManager.DoFixups()%0A%20%20%20at%20System.Runtime.Serialization.Formatters.Binary.ObjectReader.Deserialize(HeaderHandler%20handler%2C%20__BinaryParser%20serParser%2C%20Boolean%20fCheck%2C%20Boolean%20isCrossAppDomain%2C%20IMethodCallMessage%20methodCallMessage)%0A%20%20%20at%20System.Runtime.Serialization.Formatters.Binary.BinaryFormatter.Deserialize(Stream%20serializationStream%2C%20HeaderHandler%20handler%2C%20Boolean%20fCheck%2C%20Boolean%20isCrossAppDomain%2C%20IMethodCallMessage%20methodCallMessage)%0A%20%20%20at%20Microsoft.Exchange.Data.SerializationTypeConverter.DeserializeObject(Object%20sourceValue%2C%20Type%20destinationType)%0A%0AWRN%3A%20Assembly%20binding%20logging%20is%20turned%20OFF.%0ATo%20enable%20assembly%20bind%20failure%20logging%2C%20set%20the%20registry%20value%20%5BHKLM%5CSoftware%5CMicrosoft%5CFusion!EnableLog%5D%20(DWORD)%20to%201.%0ANote%3A%20There%20is%20some%20performance%20penalty%20associated%20with%20assembly%20bind%20failure%20logging.%0ATo%20turn%20this%20feature%20off%2C%20remove%20the%20registry%20value%20%5BHKLM%5CSoftware%5CMicrosoft%5CFusion!EnableLog%5D%3C%2FPRE%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2330441%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2330441%22%20slang%3D%22en-US%22%3E%3CP%3EWorkaround%20fixed%20it%20for%20us%20as%20well%2C%20great.%20Because%20federation%20wasn't%20an%20option.Thx%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2271304%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2271304%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F790194%22%20target%3D%22_blank%22%3E%40vmilanov%3C%2FA%3E%26nbsp%3B%26nbsp%3B-%20Make%20sure%20you%20have%20the%20correct%20download%20for%20CU19.%26nbsp%3B%20The%20CU20%20and%20CU19%20patches%20are%20different%20files%2C%20though%20the%20sizes%20are%20very%20similar.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2272244%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2272244%22%20slang%3D%22en-US%22%3E%3CDIV%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%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%3BThank%20you%20for%20the%20nice%20information.%20We%20just%20wanted%20to%20make%20you%20aware%20that%20we%20are%20also%20having%20issues%20with%20the%20security%20update%20and%20remote%20powershell.%20This%20is%20the%20error%20that%20we%20are%20getting%3A%3CBR%20%2F%3E%3CBR%20%2F%3E%3CPRE%3ESystem.Management.Automation.RemoteException%3A%20The%20syntax%20is%20not%20supported%20by%20this%20runspace.%20This%20can%20occur%20if%20the%20runspace%20is%20in%20no-language%20mode.%3C%2FPRE%3EIt%20seems%20we%20are%20still%20waiting%20for%20an%20official%20response.%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2271313%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2271313%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F499412%22%20target%3D%22_blank%22%3E%40alabkrishnan%3C%2FA%3E%26nbsp%3B-%20it%20is%20SUPER%20important%20that%20you%20install%20from%20elevated%20CMD%20prompt%3B%20I%20really%20want%20to%20make%20sure%20that%20this%20was%20done%20(it%20is%20unclear%20what%20the%20error%20was)%20-%20I%20just%20helped%20someone%20on%20Reddit%20with%20the%20same%20problem.%20This%20is%20exactly%20the%20symptom%20and%20resolution%3A%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fexchange%2Ftroubleshoot%2Fclient-connectivity%2Fexchange-security-update-issues%23http-500-errors-in-owa-or-ecp%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3ERepair%20failed%20installations%20of%20Exchange%20Cumulative%20and%20Security%20updates%20-%20Exchange%20%7C%20Microsoft%20Docs%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2271317%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2271317%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%3Bhe%20seems%20to%20be%20having%20the%20same%20issue%20as%20I%20do%20on%202%20servers%20and%20I%20use%20elevated%20cmd%20prompt%20with%20'start%26nbsp%3BExchange2016-KB5001779-x64-en.msp'%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2271321%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2271321%22%20slang%3D%22en-US%22%3E%3CP%3ECan%20someone%20on%20the%20Exchange%20team%20PLEASE%20tell%20us%20why%20the%20%22run%20from%20admin%22%20hasn't%20either%20been%20corrected%20or%20coded%20to%20be%20detected%20yet%3F%26nbsp%3B%20Absurd.%20.%20.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2271322%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2271322%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F977615%22%20target%3D%22_blank%22%3E%40FreakyNL%3C%2FA%3E%26nbsp%3B-%20I%20am%20thinking%20that%20something%20might%20be%20going%20on%20with%20the%20Arbitration%20mailbox%20(because%20your%20Admin%20account%20does%20not%20have%20a%20mailbox).%20What%20you%20see%20is%20probably%20because%20of%20the%20mailbox%20anchoring%20behavior%20change%20in%20Exchange%202013.%20See%20%3CA%20href%3D%22https%3A%2F%2Fexchangemaster.wordpress.com%2F2016%2F01%2F06%2Fmailbox-anchoring-affecting-new-deployments-upgrades%2F%22%20target%3D%22_self%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ethis%3C%2FA%3E%20(I%20am%20pretty%20sure%20we%20had%20a%20KB%20on%20this%2C%20looking...)%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2271329%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2271329%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'm%20quite%20convinced%20it's%20something%20with%20the%20.net%20assemblies%20causing%20issues.%20The%20toolbox%20error%20seems%20to%20indicate%20that%20and%20considering%20the%20other%20parts%20are%20throwing%20serialization%20errors%20seems%20highly%20likely.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ERunning%3A%3C%2FP%3E%3CPRE%3Emsiexec%20%2Fp%20Exchange2016-KB5001779-x64-en.msp%20%2Fl*%20c%3A%5Ctt%5CKB5001779.log%3C%2FPRE%3E%3CP%3EBut%20it's%20slow.%20As%20in%2010%20mins%20to%20detect%20space%20requirements%20and%20hanging%20in%20stopping%20services%20for%20almost%2020%20mins.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2271340%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2271340%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F499412%22%20target%3D%22_blank%22%3E%40alabkrishnan%3C%2FA%3E%26nbsp%3BAre%20you%20also%20running%20Exchange%202013%3F%20Does%20your%20admin%20account%20also%20%3CEM%3Enot%3C%2FEM%3E%20have%20a%20mailbox%3F%20If%20so%20-%20can%20you%20verify%20that%20the%20database%20that%20hosts%20the%20SystemMailbox%7Bbb558c35-97f1-4cb9-8ff7-d53741dc928c)%20mailbox%20is%20online%20and%20accessible%3F%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F977615%22%20target%3D%22_blank%22%3E%40FreakyNL%3C%2FA%3E%26nbsp%3BDid%20you%20check%20the%20location%20of%20SystemMailbox%7Bbb558c35-97f1-4cb9-8ff7-d53741dc928c)%20and%20if%20the%20database%20is%20online%3F%3C%2FP%3E%0A%3CP%3EIf%20that%20mailbox%20is%20gone%20for%20whatever%20reason%2C%20this%20article%20explains%20how%20to%20get%20it%20back%3A%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fexchange%2Frecreating-arbitration-mailboxes-exchange-2013-help%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3ERecreating%20arbitration%20mailboxes%3A%20Exchange%202013%20Help%20%7C%20Microsoft%20Docs%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2271352%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2271352%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%3CPRE%3EPS%20D%3A%5CProgram%20Files%5CMicrosoft%5CExchange%20Server%5CV15%5Cbin%26gt%3B%20get-mailbox%20-arbitration%20%7C%20ft%20Name%2C%20Database%0A%0AName%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%20Database%0A----%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--------%0ASystemMailbox%7Bbb558c35-97f1-4cb9-8ff7-d53741dc928c%7D%20UserMailboxDB_1%0ASystemMailbox%7B1f05a927-8901-4be2-a0cc-0b072049efb5%7D%20UserMailboxDB_1%0AFederatedEmail.4c1f4d8b-8179-4148-93bf-00a95fa1e042%20UserMailboxDB_1%0ASystemMailbox%7B2CE34405-31BE-455D-89D7-A7C7DA7A0DAA%7D%20UserMailboxDB_1%0ASystemMailbox%7BD0E409A0-AF9B-4720-92FE-AAC869B0D201%7D%20UserMailboxDB_1%0ASystemMailbox%7Be0dc1c29-89c3-4034-b678-e6c29d823ed9%7D%20UserMailboxDB_1%0AMigration.8f3e7716-2011-43e4-96b1-aba62d229136%20%20%20%20%20%20UserMailboxDB_1%3C%2FPRE%3E%3CP%3EAnd%20yes%2C%20the%20database%20is%20online%20(DAG%20too).%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2271390%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2271390%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F499412%22%20target%3D%22_blank%22%3E%40alabkrishnan%3C%2FA%3E%26nbsp%3Bhey%2C%20you%20got%20a%20%24%20or%20other%20special%20chars%20in%20your%20username%3F%3C%2FP%3E%3CP%3ECopied%20my%20admin%20account%20to%20one%20without%20%24%20in%20the%20names%20-%20%3CSTRONG%3Eproblems%20be%20gone.%3C%2FSTRONG%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2271397%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2271397%22%20slang%3D%22en-US%22%3E%3CP%3EHmm%20problems%20only%20disappeared%20on%20%2Fecp.%20Exchange%20Management%20Shell%20and%20the%20Exchange%20Toolbox%20still%20don't%20work.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2272268%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2272268%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSPAN%3EWe%20are%20using%20PRTG%20to%20monitor%20our%20Exchange%20Servers%202013%20C23%20and%20it%20can't%20do%20remote%20powershell%20with%20remote%20exchange%20management%20shell%20with%20the%20Exchange%20server%20after%20I%20installed%20the%20April%20Security%20update.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2271407%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2271407%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20use%20Quest%20Unified%20Communications%20Command%20Suite%20Diagnostics%20to%20monitor%20our%20Exchange%202016CU20%20servers%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EInstall%26nbsp%3B%3CSPAN%3EKB5001779%20-%20most%20of%20the%20tests%20fail%20to%20run.%26nbsp%3B%20remove%20it%2C%20all%20works%20well.%26nbsp%3B%20%26nbsp%3Bsomething%20is%20up%20with%20the%20ability%20to%20remotely%20monitor%20Exchange%202016%20with%26nbsp%3BKB5001779%20installed%20-%26nbsp%3B%20%26nbsp%3Bmy%20testing%20is%20just%20in%20lab%20so%20far%2C%20hoping%20MS%20pulls%20and%20re-issues%20this%20one%2C%20something%20isn't%20right%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2271413%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2271413%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F977615%22%20target%3D%22_blank%22%3E%40FreakyNL%3C%2FA%3E%26nbsp%3Byes%20we%20do%20have%20%24%20in%20the%20admin%20account%2C%20as%20suggested%20after%20removing%20all%20issues%20are%20resolved%20for%20us.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2272328%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2272328%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F233448%22%20target%3D%22_blank%22%3E%40niels%20haaijer%3C%2FA%3E%26nbsp%3B-%20Yes%2C%20apply%20to%20Edge%20servers%20too%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F154015%22%20target%3D%22_blank%22%3E%40Alex%20Sanin%3C%2FA%3E%26nbsp%3B-%20There%20is%20a%20specifici%20FAQ%20about%20Hybrid%20in%20the%20post%3B%20but%20if%20you%20are%20running%20hybrid%2C%20you%20are%20running%20Exchange%20on-premises.%20If%20you%20are%20on%20CU23%20for%20Exchange%202013%2C%20you%20simply%20need%20to%20either%20install%20the%20April%20update%20from%20Microsoft%20Update%20or%20if%20you%20are%20downloading%20it%2C%20you%20MUST%20install%20the%20update%20from%20the%20elevated%20CMD%20prompt.%20The%20KB%20article%20tells%20you%20what%20to%20do%20(in%20known%20issues)%20and%20download%20instructions%20tell%20you%20also.%20It%20should%20be%20~30%20minutes.%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F92746%22%20target%3D%22_blank%22%3E%40Vincent%20Lohest%3C%2FA%3E%26nbsp%3B-%20yes%2C%20best%20is%20to%20reboot%20after%20done!%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F977615%22%20target%3D%22_blank%22%3E%40FreakyNL%3C%2FA%3E%26nbsp%3B-%20unknown%20at%20this%20time%3B%20we%20do%20have%20a%20repro%20of%20this%20and%20engineering%20is%20looking%20into%20it.%20Sorry%2C%20no%20better%20answer%20right%20now!%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F88801%22%20target%3D%22_blank%22%3E%40Michael%20Hincapie%3C%2FA%3E%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F997517%22%20target%3D%22_blank%22%3E%40anthonytenherkel%3C%2FA%3E%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1025691%22%20target%3D%22_blank%22%3E%40JazDotKiwi650%3C%2FA%3E%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F739649%22%20target%3D%22_blank%22%3E%40nickvp%3C%2FA%3E%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1025378%22%20target%3D%22_blank%22%3E%40GregS410%3C%2FA%3E%26nbsp%3B-%20at%20this%20time%2C%20I%20do%20not%20have%20an%20answer%20for%20you%3B%20I%20think%20based%20on%20error%20samples%20you%20have%20provided%20(thank%20you!)%2C%20we%20have%20a%20good%20idea%20where%20to%20look%3B%20engineering%20has%20been%20engaged%20on%20this.%203rd%20party%20monitoring%20is%20something%20that%20we%20cannot%20test%20for%20in%20our%20test%20passes%20but%20still%20-%20if%20we%20have%20deliberately%20changed%20something%20here%2C%20we%20need%20to%20document%20it%20for%20sure.%20Consider%20this%20under%20investigation.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2271471%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2271471%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F977615%22%20target%3D%22_blank%22%3E%40FreakyNL%3C%2FA%3E%26nbsp%3Band%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F499412%22%20target%3D%22_blank%22%3E%40alabkrishnan%3C%2FA%3E%26nbsp%3B-%20thanks%2C%20we%20are%20trying%20to%20figure%20out%20what%20is%20going%20on%20here%3B%20good%20to%20know!!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2271534%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2271534%22%20slang%3D%22en-US%22%3E%3CP%3EAnyone%20else%20besides%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F977615%22%20target%3D%22_blank%22%3E%40FreakyNL%3C%2FA%3E%3CSPAN%3E%26nbsp%3Band%26nbsp%3B%3C%2FSPAN%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F499412%22%20target%3D%22_blank%22%3E%40alabkrishnan%3C%2FA%3E%26nbsp%3Bhad%20successful%20installation%3F%26nbsp%3B%20I%20am%20wondering%20if%20I%20should%20wait%20until%20weekend%20before%20doing%20the%20install.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%20for%20your%20response.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2271540%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2271540%22%20slang%3D%22en-US%22%3E%3CP%3EPlease%20release%20this%20for%20older%20CUs%20like%20the%20March%20vulnerability%2C%20I%20am%20unable%20to%20upgrade%20to%20CU%2018%2C%2019%20or%2020%20because%20the%20Exchange%202016%20I%20have%20inherited%20is%20only%20installed%20as%20part%20of%20Hybrid%20and%20is%20just%20setup%20as%20a%20management%20console%20(Exchange%20express%20if%20you%20will).%20The%20March%20security%20update%20was%20released%20for%20customers%20who%20are%20unable%20to%20upgrade%20for%20one%20reason%20or%20another%2C%20and%20I%20know%20of%20at%20least%20one%20other%20who%20ran%20into%20the%20issues%20I%20ran%20into%20whilst%20attempting%20to%20upgrade.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2271556%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2271556%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F987501%22%20target%3D%22_blank%22%3E%40itsupport-bhms%3C%2FA%3E%26nbsp%3BJust%20to%20give%20you%20an%20idea%20-%20this%20post%20has%20%26gt%3B55%2C000%20views%20right%20now%2C%20in%20just%20under%2012%20hours.%20I%20guarantee%20you%20there%20are%20a%20ton%20of%20people%20who%20have%20done%20installations%20by%20now%20(I%20have%20seen%20multiple%20threads%20on%20Reddit%20also).%20Things%20come%20up%20sometimes%2C%20yes%2C%20but%20-%20I'd%20say%20do%20it.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2271560%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2271560%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1025407%22%20target%3D%22_blank%22%3E%40luke_q7%3C%2FA%3E%26nbsp%3B-%20the%20installation%20that%20you%20have%20should%20be%20a%20'regular'%20Exchange%20installation%3B%20it%20is%20simply%20an%20on-premises%20install%20and%20you%20should%20update%20it.%20At%20this%20point%2C%20we%20do%20not%20have%20any%20plans%20to%20release%20fixes%20for%20older%20CUs.%3C%2FP%3E%0A%3CP%3EMarch%20was%20the%20%3CEM%3EONLY%3C%2FEM%3E%20time%20that%20we%20have%20done%20such%20a%20thing%20(and%20we%20release%20security%20updates%20often%2C%20not%20every%20single%20month%20but%20often)%20-%20and%20it%20was%20because%20of%20active%20exploits%20by%20a%20particular%20actor%20(it%20was%20a%20very%20unique%20situation).%20Released%20updates%20for%20older%20CUs%20were%20not%20full%20updates%20either%3B%20those%20updates%20only%20addressed%204%20March%20vulnerabilities.%20They%20were%20not%20'cumulative'%20security%20updates%20like%20we%20release%20usually.%26nbsp%3BPlease%20update...%20Exchange%20Update%20Wizard%20will%20give%20you%20the%20steps%20that%20you%20need%20to%20follow.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2271633%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2271633%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F977615%22%20target%3D%22_blank%22%3E%40FreakyNL%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESame%20here%2C%20I%20have%20exchange%20admin%20account%20with%20%24%20at%20the%20end%2C%20I%20got%20HTTP%20400%20error%20and%2For%20serialization%20error.%3C%2FP%3E%3CP%3EAccessed%20ECP%20with%20an%20account%20w%2Fo%20%24%2C%20now%20I%20can%20access%20the%20ECP.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThank%20you%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2348669%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2348669%22%20slang%3D%22en-US%22%3E%3CP%3EHas%20there%20been%20a%20fix%20to%20administrating%20Exchange%20using%20an%20account%20with%20%24%20at%20the%20end%20of%20the%20username%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2353158%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2353158%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%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%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EHow%20does%20one%20access%20Microsoft%20Exchange%20Developer%20Support%3F%26nbsp%3B%20I%20tried%20opening%20a%20developer%20case%20using%20all%20of%20our%20MS%20Silver%20Partner%20avenues%20and%20could%20not%20get%20the%20right%20answer.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2271635%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2271635%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20are%20using%20PRTG%20to%20monitor%20our%20Exchange%20Servers%20and%20it%20can't%20do%20remote%20powershell%20with%20remote%20exchange%20management%20shell%20with%20the%20Exchange%20server%20after%20I%20installed%20the%20April%20Security%20update.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EI%20upgraded%20from%20CU18%20to%20CU20%20successfully%20(cmd%20prompt%20elevated%20as%20administrator)%2C%20monitoring%20was%20still%20fine%20at%20that%20point.%20Like%20I%20have%20done%20numerous%20times%20for%20both%20CUs%20and%20security%20updates.%26nbsp%3B%3C%2FSPAN%3EThen%20when%20I%20applied%20April%20security%20update%20for%20CU20%20(cmd%20prompt%20elevated%20as%20admin)%2C%20powershell%20is%20failing%20with%20this%20message%20below%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EThe%20sensor%20was%20able%20to%20connect%20to%20the%20device%20using%20Remote%20PowerShell%20but%20could%20not%20retrieve%20access%20to%20Remote%20Exchange%20Management%20Shell.%20Ensure%20that%20remote%20management%20is%20enabled%20on%20the%20Exchange%20Server%20and%20the%20user%20has%20sufficient%20rights.%20See%20%3CA%20href%3D%22https%3A%2F%2Fkb.paessler.com%2Fen%2Ftopic%2F54353%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fkb.paessler.com%2Fen%2Ftopic%2F54353%3C%2FA%3E%20for%20details.%20The%20syntax%20is%20not%20supported%20by%20this%20runspace.%20This%20can%20occur%20if%20the%20runspace%20is%20in%20no-language%20mode.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EIt%20has%20the%20appropriate%20permissions%2C%20nothing%20has%20changed%20there%2C%20confirmed%20its%20still%20good.%20It%20was%20working%20fine%20before%20the%20security%20update.%20I%20got%20this%20same%20behavior%20on%20both%20my%20DR%20exchange%20servers%2C%20so%20not%20proceeding%20with%20my%20production%20ones%20until%20I%20know%20what's%26nbsp%3Bgoing%20on%20or%20hear%20from%20someone%20at%20Microsoft.%20Did%20the%20security%20update%20change%20something%20with%20remote%20exchange%20management%20shell%20and%20that%20was%20the%20vulnerability%20fix%3F%20Perhaps%20PRTG%20vendor%20needs%20to%20supply%20and%20update%20and%20adjust%20their%20sensor%20accordingly%20if%20by%20Microsoft%20design%20this%20was%20changed%3F%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EI've%20validated%20all%20the%20services%20automatic%20are%20running%2C%20test-servicehealth%2C%20test-replicationhealth%2C%20virtual%20powershell%20directory%2C%20exchange%20management%20shell%20works%20fine%20on%20server%2C%20get-mailboxdatabasecopystatus%2C%20reviewed%20application%20logs%20and%20no%20issues.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EHope%20you%20can%20help%20%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%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%3Bor%20someone%3F%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2271653%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2271653%22%20slang%3D%22en-US%22%3E%3CP%3EIs%20the%20patch%20applicable%20to%20Exchange%20Edge%20Servers%20as%20well%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2271721%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2271721%22%20slang%3D%22en-US%22%3E%3CP%3EFirst%203%20steps%20to%20install%20april%20security%20update%3A%3C%2FP%3E%3CP%3E1.%20Put%20the%20server%20in%20maintenance%20mode.%3CBR%20%2F%3E2.%20Reboot%20the%20server.%3CBR%20%2F%3E3.%20Install%20security%20update%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIs%20it%20required%20to%20reboot%20the%20server%20after%20placing%20the%20server%20in%20maintenance%20mode%3F%20And%20if%20so%2C%20why%20is%20it%20required%20to%20first%20reboot%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fexchange%2Fhigh-availability%2Fmanage-ha%2Fmanage-dags%3Fview%3Dexchserver-2019%23performing-maintenance-on-dag-members%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3EManage%20database%20availability%20groups%20%7C%20Microsoft%20Docs%3C%2FA%3E%26nbsp%3Bstates%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EInstalling%20updates%20on%20DAG%20members%3C%2FP%3E%3CP%3E1.%20Use%20the%20steps%20described%20above%20to%20put%20the%20DAG%20member%20in%20maintenance%20mode.%3CBR%20%2F%3E2.%20Install%20the%20update.%3CBR%20%2F%3E3.%20Use%20the%20steps%20described%20above%20to%20take%20the%20DAG%20member%20out%20of%20maintenance%20mode%20and%20put%20it%20back%20into%20production.%3CBR%20%2F%3E4.%20Optionally%2C%20use%20the%20RedistributeActiveDatabases.ps1%20script%20to%20rebalance%20the%20active%20database%20copies%20across%20the%20DAG.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2272350%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2272350%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%3BDo%20you%20know%20if%20we%20apply%20the%20April%20update%20and%20then%20update%20from%20Exchange%20CU19%20to%20CU20%2C%20do%20we%20have%20to%20reapply%20the%20patch%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2271746%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2271746%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20MS%20Moderator%20or%20Premier%20MS%20Engineer%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EExchnage%202016%20CU19%20Since%20the%20Security%20update%20is%20compatible%20with%20it%20after%20i%20install%20it%2C%20When%20i%20Upgrade%20to%20CU20%20Do%20i%20need%20to%20reinstall%20this%20Update%20again%26nbsp%3B%3C%2FP%3E%3CP%3Esince%20CU20%20was%20relased%20on%20March%2015%20and%20dont%20include%20this%20update%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2271944%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2271944%22%20slang%3D%22en-US%22%3E%3CP%3EIf%20you%20cannot%20login%20after%20applying%20latest%20CUs%20most%20likely%20cause%20is%20broken%20Certificate%20bindings%20for%20HTTP.%3C%2FP%3E%3CP%3EUse%20NETSH%20as%20detailed%20in%20this%20excellent%20article%20for%20a%20relatively%20easy%20fix.%26nbsp%3B%3CA%20href%3D%22http%3A%2F%2Fwww.stormbreaker.tech%2F%3Fp%3D173%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noreferrer%22%3Ehttp%3A%2F%2Fwww.stormbreaker.tech%2F%3Fp%3D173%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ERayC%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2271955%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2271955%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%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%3CBR%20%2F%3EFollowing%20FAQ%20statement%20%22%3CSPAN%3EWhile%20Exchange%20Online%20customers%20are%20already%20protected%2C%20the%20April%202021%20security%20updates%20do%20need%20to%20be%20applied%20to%20your%20on-premises%20Exchange%20Server%22%3CBR%20%2F%3E%3CBR%20%2F%3EI%20kind%26nbsp%3Ba%20bit%20confused.%20Do%20I%20need%20to%20patch%20my%20%22Hybrid%22%20EXC%202013%20CU23%20or%20follow%20FAQ%20statement%3F%3CBR%20%2F%3EIs%20there%20any%20detail%20how%20Hybrid%20is%20protected%20%3F%26nbsp%3B%3CBR%20%2F%3E%3C%2FSPAN%3E%3CBR%20%2F%3ERegards%2C%3CBR%20%2F%3EAlex%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2271996%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2271996%22%20slang%3D%22en-US%22%3E%3CP%3EHello%2C%3C%2FP%3E%3CP%3EDo%20we%20need%20to%20reboot%20Exchange%20after%20applying%20the%20update%20only%20(%20not%20the%20CU)%20%3F%3C%2FP%3E%3CP%3EThanks%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2271997%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2271997%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F119325%22%20target%3D%22_blank%22%3E%40alex%20kim%3C%2FA%3E%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F499412%22%20target%3D%22_blank%22%3E%40alabkrishnan%3C%2FA%3E%26nbsp%3Bdid%20it%20also%20resolve%20the%20issues%20with%20the%20Exchange%20Management%20Shell%20and%20Exchange%20Toolbox%20for%20you%3F%20Those%20seem%20to%20persist%20here%2C%20but%20maybe%20we%20should%20try%20re-applying%20the%20update%20with%20an%20account%20without%20a%20%24%20in%20the%20name.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F987501%22%20target%3D%22_blank%22%3E%40itsupport-bhms%3C%2FA%3E%26nbsp%3BI%20presume%20you%20mean%20unsuccessful%2C%20technical%20the%20installation%20succeeded%20and%20other%20than%20some%20management%20tooling%20everything%20works.%20Have%20no%20issues%20whatsoever%20at%202%20other%20customers%20where%20I%20applied%20it.%20This%20specific%20customer%20we%20only%20obtained%20recently%20and%20has%20had%20many%20people%20messing%20around%20in%20settings.%20They%20somewhat%20regularly%20have%20odd%20issues.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2271998%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2271998%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20I've%20installed%20the%20patch%20to%20an%20Exchange%202016%20server%2C%20the%20installation%20seemed%20to%20go%20fine%20and%20Exchange%20appears%20to%20is%20operating%20normally%20post%20reboot%2C%20however%20i've%20got%20an%20issue%20with%20a%20couple%20of%203rd%20party%20applications%20that%20connect%20to%20exchange%20via%20remote%20powershell%20and%20they%20are%20both%20broken.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EOne%20is%20our%20monitoring%20application%20called%20PRTG%2C%20and%20appears%20to%20be%20the%20same%20issue%20as%20mentioned%20by%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F739649%22%20target%3D%22_blank%22%3E%40nickvp%3C%2FA%3E.%3C%2FP%3E%3CP%3EI've%20enabled%20sensor%20debug%20logging%20and%20can%20see%20the%20following%20error%20message%20in%20the%20PRTG%20sensor%20logs.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E2021-04-14%2020%3A03%3A32%2C457%20%5BDEBUG%5D%20-%20Running%20script%3A%20'Get-ExchangeServer'%3CBR%20%2F%3E2021-04-14%2020%3A03%3A32%2C490%20%5BERROR%5D%20-%20Error%20in%20RunRequest%20Get-ExchangeServer%3CBR%20%2F%3E2021-04-14%2020%3A03%3A32%2C490%20%5BERROR%5D%20-%20Exception%20occured%3CBR%20%2F%3ESystem.Management.Automation.RemoteException%3A%20The%20syntax%20is%20not%20supported%20by%20this%20runspace.%20This%20can%20occur%20if%20the%20runspace%20is%20in%20no-language%20mode.%3CBR%20%2F%3Eat%20System.Management.Automation.Runspaces.AsyncResult.EndInvoke()%3CBR%20%2F%3Eat%20System.Management.Automation.PowerShell.CoreInvokeRemoteHelper%5BTInput%2CTOutput%5D(PSDataCollection%601%20input%2C%20PSDataCollection%601%20output%2C%20PSInvocationSettings%20settings)%3CBR%20%2F%3Eat%20System.Management.Automation.PowerShell.CoreInvoke%5BTInput%2CTOutput%5D(PSDataCollection%601%20input%2C%20PSDataCollection%601%20output%2C%20PSInvocationSettings%20settings)%3CBR%20%2F%3Eat%20System.Management.Automation.PowerShell.CoreInvoke%5BTOutput%5D(IEnumerable%20input%2C%20PSDataCollection%601%20output%2C%20PSInvocationSettings%20settings)%3CBR%20%2F%3Eat%20System.Management.Automation.PowerShell.Invoke(IEnumerable%20input%2C%20PSInvocationSettings%20settings)%3CBR%20%2F%3Eat%20System.Management.Automation.RemotePipeline.Invoke(IEnumerable%20input)%3CBR%20%2F%3Eat%20ExchangeSensorPS.ExchangeSensorProgram.RunRequest(String%20script)%3CBR%20%2F%3Eat%20ExchangeSensorPS.ExchangeSensorProgram.GetExchangeProductVersion(Collection%601%20result)%3CBR%20%2F%3Eat%20ExchangeSensorPS.ExchangeSensorProgram.Main(String%5B%5D%20args)%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EOur%20other%20application%20that%20is%20also%20broken%20is%20an%20in%20house%20tool%20we%20use%20for%20Exchange%20admin%20tasks%20is%20producing%20a%20similar%20error%20message%2C%20the%20keywords%20are%20%22System.Management.Automation.RemoteException%3A%20The%20syntax%20is%20not%20supported%20by%20this%20runspace.%20This%20can%20occur%20if%20the%20runspace%20is%20in%20no-language%20mode.%22%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAny%20ideas%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2272008%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2272008%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%3B%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%3Bany%20chance%20for%20a%20fix%20on%20the%20%24%20in%26nbsp%3B%20user%20account%20name%20issue%3F%20Customer%20has%20quite%20a%20few%20admin%20accounts%20spread%20amongst%20several%20parties.%20They%20all%20end%20in%20%24%2C%20it%20being%20one%20of%20their%20policies.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2360469%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2360469%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F114800%22%20target%3D%22_blank%22%3E%40Corbett%20Enders%3C%2FA%3Enot%20afaik%2C%20the%20suggested%20solution%20is%20'don't%20use%20a%20%24'%20atm%20I%20think.%20Because%20that's%20in%20part%20what%20was%20causing%20the%20free%20busy%20problem%20and%20the%20workaround%2Ffix%20is%20federation%20OR%20use%20dedicated%20svc%20account%20instead%20of%20computernames%20with%20%24%20at%20the%20end%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2272044%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2272044%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1025691%22%20target%3D%22_blank%22%3E%40JazDotKiwi650%3C%2FA%3E%26nbsp%3BI%20reached%20out%20to%20PRTG%20support%20and%20they%20said%20several%20customers%20have%20already%20reported%20this%20remote%20powershell%20issue.%20Their%20dev%20team%20is%20working%20on%20a%20hotfix%2Fupdate%20to%20remediate%20due%20to%20the%20changes%20in%20Microsoft%20code.%20Hopefully%20its%20a%20quick%20turnaround%20and%20fixed%20soon%20and%20not%20have%20to%20wait%20for%20a%20Microsoft%20update.%20Looking%20like%20they%20changed%20it%20to%20fix%20the%20vulnerability%2C%20unless%20they%20accidentally%20broke%20it%2C%20which%20then%20we'll%20have%20to%20wait%20for%20an%20update%20or%20some%20combination.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EGood%20luck%20with%20your%20other%20app.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2272359%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2272359%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%26nbsp%3B%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%3C%2FP%3E%3CP%3EI%20installed%20correct%20security%20patch%20on%20my%20Exchange%20and%20it%20messed%20ECP.%26nbsp%3B%20Not%20sure%20why%20it%20happened.%26nbsp%3B%3C%2FP%3E%3CP%3EFinally%20i%20could%20recover%20it%20using%20following%20link.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fanswers%2Fquestions%2F116565%2Fevent-id-1310-aspnet-40-exchange-2016.html%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fanswers%2Fquestions%2F116565%2Fevent-id-1310-aspnet-40-exchange-2016.html%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2272052%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2272052%22%20slang%3D%22en-US%22%3E%3CP%3EOk%20great%20thanks%20for%20letting%20me%20know%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F739649%22%20target%3D%22_blank%22%3E%40nickvp%3C%2FA%3E%26nbsp%3B.%3C%2FP%3E%3CP%3EGlad%20to%20know%20its%20not%20just%20us%2C%20I'm%20logging%20a%20case%20with%20PRTG%20support%20aswell.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAh%20so%20if%20code%20changes%20are%20needed%20for%20PRTG%20then%20I'll%20also%20need%20to%20find%20out%20the%20details%20of%20that%20so%20I%20can%20update%20our%20other%20inhouse%20tool.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%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%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%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%3BIs%20there%20any%20guidance%20for%20developers%20on%20what%20changes%20are%20needed%20when%20programmatically%20connecting%20to%20Exchange%20power%20shell%20using%20C%23%20%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2272385%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2272385%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F779432%22%20target%3D%22_blank%22%3E%40nick_ap%3C%2FA%3E%26nbsp%3BIf%20you%20update%20the%20CU%2C%20you%20will%20need%20to%20install%20the%20April%20SU%20post%20CU20.%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1025929%22%20target%3D%22_blank%22%3E%40Prashant_A-Rookie%3C%2FA%3E%26nbsp%3BThis%20can%20happen%20if%20the%20update%20was%20downloaded%20for%20manual%20installation%20and%20then%20.msp%20was%20double-clicked%20on%20(vs.%20installed%20from%20elevated%20CMD%20prompt).%20We%20are%20working%20on%20long%20term%20solution%20for%20this%20but%20until%20then%2C%20.msp%20%3CSTRONG%3EMUST%3C%2FSTRONG%3E%20be%20installed%20from%20elevated%20CMD%20prompt!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2377497%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2377497%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%2F5374%22%20target%3D%22_self%22%3E%3CSPAN%20class%3D%22%22%3ENino%20Bilic%3C%2FSPAN%3E%3C%2FA%3E%3C%2FP%3E%3CP%3E%3CBR%20%2F%3Eafter%20not%20hearing%20from%20you%20for%20so%20long%20I%20finally%20applied%20security%20path%20of%20April%2013th%26nbsp%3B%20on%20my%20staging%20and%20production%20Exchange%202019%20CU19%20this%20Thursday%20and%20everything%20works%20fine.%3C%2FP%3E%3CP%3EOne%20common%20event%20warning%20I%20noticed%20before%20and%20after%20applying%20the%20patch%20is%20this.%20If%20you%20anyone%20experienced%20the%20same%20then%20please%20update.%3C%2FP%3E%3CP%3EEvent%20code%3A%203005%3CBR%20%2F%3EEvent%20message%3A%20An%20unhandled%20exception%20has%20occurred.%3CBR%20%2F%3EEvent%20time%3A%205%2F22%2F2021%207%3A46%3A56%20AM%3CBR%20%2F%3EEvent%20time%20(UTC)%3A%205%2F22%2F2021%203%3A46%3A56%20AM%3CBR%20%2F%3EEvent%20ID%3A%20c2abd3c344584b7599413857078a5301%3CBR%20%2F%3EEvent%20sequence%3A%206%3CBR%20%2F%3EEvent%20occurrence%3A%205%3CBR%20%2F%3EEvent%20detail%20code%3A%200%3CBR%20%2F%3E%3CBR%20%2F%3EApplication%20information%3A%3CBR%20%2F%3EApplication%20domain%3A%20%2FLM%2FW3SVC%2F1%2FROOT%2Fowa-1-132659982733500338%3CBR%20%2F%3ETrust%20level%3A%20Full%3CBR%20%2F%3EApplication%20Virtual%20Path%3A%20%2Fowa%3CBR%20%2F%3EApplication%20Path%3A%20C%3A%5CProgram%20Files%5CMicrosoft%5CExchange%20Server%5CV15%5CFrontEnd%5CHttpProxy%5Cowa%5C%3CBR%20%2F%3EMachine%20name%3A%20EXMAILSVR%3CBR%20%2F%3E%3CBR%20%2F%3EProcess%20information%3A%3CBR%20%2F%3EProcess%20ID%3A%20812%3CBR%20%2F%3EProcess%20name%3A%20w3wp.exe%3CBR%20%2F%3EAccount%20name%3A%20NT%20AUTHORITY%5CSYSTEM%3CBR%20%2F%3E%3CBR%20%2F%3EException%20information%3A%3CBR%20%2F%3EException%20type%3A%20ArgumentException%3CBR%20%2F%3EException%20message%3A%20Invalid%20input%20value%3CBR%20%2F%3EParameter%20name%3A%20input%3CBR%20%2F%3Eat%20Microsoft.Exchange.Data.ApplicationLogic.Cafe.BackEndServer.FromString(String%20input)%3CBR%20%2F%3Eat%20Microsoft.Exchange.HttpProxy.OwaResourceProxyRequestHandler.ResolveAnchorMailbox()%3CBR%20%2F%3Eat%20Microsoft.Exchange.HttpProxy.ProxyRequestHandler.InternalBeginCalculateTargetBackEnd(AnchorMailbox%26amp%3B%20anchorMailbox)%3CBR%20%2F%3Eat%20Microsoft.Exchange.HttpProxy.ProxyRequestHandler.%3CBEGINCALCULATETARGETBACKEND%3Eb__278_0()%3CBR%20%2F%3Eat%20Microsoft.Exchange.Common.IL.ILUtil.DoTryFilterCatch(Action%20tryDelegate%2C%20Func%602%20filterDelegate%2C%20Action%601%20catchDelegate)%3CBR%20%2F%3Eat%20Microsoft.Exchange.HttpProxy.ProxyRequestHandler.CallThreadEntranceMethod(Action%20method)%3C%2FBEGINCALCULATETARGETBACKEND%3E%3C%2FP%3E%3CP%3E%3CBR%20%2F%3E%3CBR%20%2F%3ERequest%20information%3A%3CBR%20%2F%3ERequest%20URL%3A%20%3CA%20href%3D%22https%3A%2F%2Fpublic%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noreferrer%22%3Ehttps%3A%2F%2F85.68.45.35%3C%2FA%3E%3A443%2Fowa%2Fauth%2Fx.js%3CBR%20%2F%3ERequest%20path%3A%20%2Fowa%2Fauth%2Fx.js%3CBR%20%2F%3EUser%20host%20address%3A%20192.168.1.1%3CBR%20%2F%3EUser%3A%3CBR%20%2F%3EIs%20authenticated%3A%20False%3CBR%20%2F%3EAuthentication%20Type%3A%3CBR%20%2F%3EThread%20account%20name%3A%20NT%20AUTHORITY%5CSYSTEM%3CBR%20%2F%3E%3CBR%20%2F%3EThread%20information%3A%3CBR%20%2F%3EThread%20ID%3A%20121%3CBR%20%2F%3EThread%20account%20name%3A%20NT%20AUTHORITY%5CSYSTEM%3CBR%20%2F%3EIs%20impersonating%3A%20False%3CBR%20%2F%3EStack%20trace%3A%20at%20Microsoft.Exchange.Data.ApplicationLogic.Cafe.BackEndServer.FromString(String%20input)%3CBR%20%2F%3Eat%20Microsoft.Exchange.HttpProxy.OwaResourceProxyRequestHandler.ResolveAnchorMailbox()%3CBR%20%2F%3Eat%20Microsoft.Exchange.HttpProxy.ProxyRequestHandler.InternalBeginCalculateTargetBackEnd(AnchorMailbox%26amp%3B%20anchorMailbox)%3CBR%20%2F%3Eat%20Microsoft.Exchange.HttpProxy.ProxyRequestHandler.%3CBEGINCALCULATETARGETBACKEND%3Eb__278_0()%3CBR%20%2F%3Eat%20Microsoft.Exchange.Common.IL.ILUtil.DoTryFilterCatch(Action%20tryDelegate%2C%20Func%602%20filterDelegate%2C%20Action%601%20catchDelegate)%3CBR%20%2F%3Eat%20Microsoft.Exchange.HttpProxy.ProxyRequestHandler.CallThreadEntranceMethod(Action%20method)%3CBR%20%2F%3E%3CBR%20%2F%3E%3CBR%20%2F%3ECustom%20event%20details%3A%3C%2FBEGINCALCULATETARGETBACKEND%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2381093%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20April%202021%20Exchange%20Server%20Security%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2381093%22%20slang%3D%22en-US%22%3E%3CP%3EHas%20anyone%20running%20Exchange%202013%20noticed%20their%20eDiscovery%20is%20broken%20after%20the%20April%20update%3F%20We've%20been%20running%20on%20the%20April%20update%20since%20right%20after%20it%20was%20released%20but%20just%20today%20I%20went%20to%20run%20a%20new%20eDiscovery%20and%20I%20am%20now%20getting%20an%20Error%20400%20Bad%20Request%20error%20for%20just%20those%20functions.%20The%20last%20time%20I%20ran%20one%20of%20these%20searches%20was%20just%20before%20the%20update%20so%20it%20seems%20to%20be%20related%20to%20the%20patch.%20Any%20thoughts%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E
Co-Authors
Version history
Last update:
‎May 04 2021 05:18 PM
Updated by: