Exchange Management Shell not connecting after Installed Exchange Server CU 23 update

Md. Rubiat Haque 151 Reputation points
2021-06-09T06:48:22.137+00:00

Hi, I am Rubiat,

Few months ago, I was updated Exchange Server 2013 CU 23. After installation done, I couldn't connect to exchange management shell to revert maintenance mode. I have 4 mailbox servers. Two servers in DC site and another 2 in DR site. The problematic server is in DR site and rest of the servers are ok after CU 23 installed. When I open exchange management shell, it takes few seconds and then prompt an error and then connect to another server management shell which is in my DR site.

The prompt error is "Connecting to remote server 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."

I have tried almost all basic solutions like recycle MsExchangePowerShellAppPoll, webconfig file checking, directory path checking etc. Now, please provide me an appropriate solution to fix it. It is very urgent for me.

Note: Problematic server is still in maintenance mode.

Thank you.

Exchange Server Management
Exchange Server Management
Exchange Server: A family of Microsoft client/server messaging and collaboration software.Management: The act or process of organizing, handling, directing or controlling something.
7,606 questions
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Eric Yin-MSFT 4,386 Reputation points
    2021-06-10T06:57:20.58+00:00

    Hi,
    Have you tried taking the problematic server out of maintenance mode with the other server's EMS?
    Set-ServerComponentState "EX01" -Component ServerWideOffline -State Active -Requester Maintenance
    Set-ServerComponentState "EX01" -Component HubTransport -State Active -Requester Maintenance

    Or run EMS via windows powershell:

    Add-PSSnapin Microsoft.Exchange.Management.PowerShell.SnapIn  
    

    Then restart MSExchangeTransport and MSExchangeFrontEndTransport service on the problematic server.


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


Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.