Exchange Management Shell not working after Exchange 2019 CU14 install

Kenny Stern 141

Installed CU14 on a 2019 Exchange server. It is only used for SMTP relay and does not host any mailboxes. I am now getting this error when attempting to go into the management shell:

New-PSSession : [server.domain.com] Connecting to remote server server.domain.com failed with the following error message : The WinRM client cannot process the request. It cannot determine the content type of the HTTP response from the destination computer. The content type is absent or invalid. For more information, see the about_Remote_Troubleshooting Help topic.

Also getting error from ECP:
The following information can be helpful to determine why the assembly 'Microsoft.Exchange.Clients.Strings, Version=15.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' could not be loaded.

I've confirmed the certificate is in the IIS bindings on the Backend Web Site. Also ran UpdateCAS.ps1 and UpdateConfigFiles.ps1 but still having the issue. Hoping someone here can help before opening a ticket with Microsoft.

Thanks

JimmyYang-MSFT 52,801 Reputation points Microsoft Vendor

2024-03-04T09:48:33.0133333+00:00

Hi @Kenny Stern

According to your error message, this problem occurs because one or more of the following conditions are true:

1)The Kerbauth module is configured incorrectly in Internet Information Services (IIS) in one of the following ways:

o The Kerbauth module is displayed as a Managed module instead of as a Native module.

o The Kerbauth module has been loaded on the Default website level (instead of, or in addition to, the PowerShell virtual directory).

2)The user does not have Remote PowerShell Enabled status.

3)The WSMan module entry is missing from the Global modules section of the ApplicationHost.config file that is in the following location: C:\Windows\System32\Inetsrv\config\ApplicationHost.config

For more details about its methods of this problem, you could refer to this article.
Kenny Stern 141 Reputation points

2024-03-05T15:24:56.1933333+00:00

Microsoft support recommended reinstalling the CU, which I did. Now EMS is working but ECP is still getting the same error. I have looked at all the troubleshooting steps you provided and everything is configured correctly.
JimmyYang-MSFT 52,801 Reputation points Microsoft Vendor

2024-03-11T10:13:58.0433333+00:00

Can you check the event viewer for the errors and validate the certificate?

Also, i would recommend to go through the below article and check whether your are facing similar issue.

https://jaapwesselius.com/2021/12/01/exchange-server-owa-and-ecp-not-working/
JimmyYang-MSFT 52,801 Reputation points Microsoft Vendor

2024-03-28T05:15:48.5933333+00:00

@Kenny Stern

It has been a while, how is everything going?

If you have any update about this issue, please feel free to post back.

1 answer

Andy David - MVP 147.9K Reputation points MVP

2024-03-01T18:55:52.88+00:00

Did you ensure that you met all the EP requirements before applying CU14?

https://techcommunity.microsoft.com/t5/exchange-team-blog/released-2024-h1-cumulative-update-for-exchange-server/ba-p/4047506
Please sign in to rate this answer.
Kenny Stern 141 Reputation points

2024-03-01T21:13:02.38+00:00

Yes, EP is enabled. I ran the HealthChecker script and it shows that it is enabled. It also showed that the SharedWebConfig.config file was missing from C:\Program Files\Microsoft\Exchange Server\V15\FrontEnd\HttpProxy. However, when I checked the file is indeed there.
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

Exchange Management Shell not working after Exchange 2019 CU14 install

1 answer

Your answer