Share via

Exchange Server Cluster not connecting in Outlook

Rick Agnew 0 Reputation points
2026-02-24T02:14:25.76+00:00

Exchange Server Cluster not connecting in Outlook. OWA is down. Preparing for ES upgrade. Certificate expired but has been renewed and appears to be working properly. Receiving MX19-1 server appears ok, MX19-2 giving error on Exchange Manangement Shell launch: "VERBOSE: Connecting to MX19-2.MyWS.local.

New-PSSession : [mx19-2.myws.local] Connecting to remote server mx19-2.myws.local failed with the following error

message : The WinRM client sent a request to an HTTP server and got a response saying the requested HTTP URL was not

available. This is usually returned by a HTTP server that does not support the WS-Management protocol. For more

information, see the about_Remote_Troubleshooting Help topic.

At line:1 char:1

  • New-PSSession -ConnectionURI "$connectionUri" -ConfigurationName Micr ...
  • 
    + CategoryInfo          : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin

   gTransportException

    + FullyQualifiedErrorId : URLNotAvailable,PSSessionOpenFailed

VERBOSE: Connecting to MX19-1.MyWS.local.

VERBOSE: Connected to MX19-1.MyWS.local."

Exchange | Exchange Server | Management
Exchange | Exchange Server | Management

The administration and maintenance of Microsoft Exchange Server to ensure secure, reliable, and efficient email and collaboration services across an organization.

0 comments

3 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Rick Agnew 0 Reputation points
    2026-02-24T06:07:51.8833333+00:00

    Everything looks ok but issue still not resolved

  2. Steven-N 21,805 Reputation points Microsoft External Staff Moderator
    2026-02-24T03:49:19.6633333+00:00

    Hi Rick Agnew

    Thank you for reaching out to Microsoft Q&A

    As far as I know, Exchange Management Shell uses WinRM to connect to the Exchange server through IIS. After renewing an Exchange SSL certificate, IIS does not always update the HTTPS bindings for the Default Web Site (port 443) and the Exchange Back End site (port 444).

    Since WinRM requires a valid, correctly bound SSL certificate to establish a secure connection, any expired or incorrect certificate binding causes the connection to fail, resulting in the “URL was not available” error.

    Given this, I recommend you can follow the below instructions:

    Open Internet Information Services (IIS) Manager. Under your server's Sites list, you need to edit the bindings for both the "Exchange Back End" (port 444) and the "Default Web Site" (port 443). Ensure that the HTTPS bindings on these two sites are explicitly pointing to your newly renewed Exchange certificate instead of showing as "Not selected" or pointing to the expired one.

    Once the bindings are updated, navigate to Application Pools in IIS Manager. Locate MSExchangePowerShellAppPool and ensure it is currently started. Even if it is running, recycle this application pool so that it re-initializes and picks up the new certificate bindings.

    Finally, open an elevated command prompt and execute iisreset to finalize the changes and ensure the web server restarts cleanly. You should now be able to open the Exchange Management Shell successfully.

    If issues persist, double-check that the "Windows Remote Management" service is actively running and you can run winrm quickconfig to reset its default listener settings.

    You can read here for more insight: https://techcommunity.microsoft.com/blog/exchange/resolving-winrm-errors-and-exchange-2010-management-tools-startup-failures/588661

    Hope my answer will help you, for any further concern, kindly let me know in the comment section.

    Regards

    If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".     

    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.

    0 comments
  3. Q&A Assist
    2026-02-24T02:14:40.3533333+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    The issue you're experiencing with the Exchange Server Cluster not connecting in Outlook and the error message regarding the WinRM client suggests that there may be a problem with the WS-Management service on the MX19-2 server. Here are some steps you can take to troubleshoot this issue:

    1. Verify WS-Management Service: Ensure that the WS-Management service is running on MX19-2. You can check this by running the command winrm quickconfig in a command prompt on the server to see if it is configured correctly.
    2. Check IIS Configuration: Since the error mentions the HTTP server, make sure that the IIS (Internet Information Services) is properly configured and that the necessary endpoints for WS-Management are available.
    3. Firewall Settings: Check if there are any firewall rules that might be blocking the necessary ports for WS-Management (default is TCP 5985 for HTTP and TCP 5986 for HTTPS).
    4. Certificate Issues: Although you mentioned that the certificate has been renewed, ensure that it is installed correctly and that the server trusts the certificate chain. Also, verify that the certificate is correctly bound to the appropriate site in IIS.
    5. Run EMTshooter: You can use the Exchange Management Troubleshooter (EMTshooter) to diagnose connection issues. This tool can help identify problems affecting the management tools connected to the Exchange server.
    6. Review Logs: Check the event logs on MX19-2 for any related errors that might provide more context on the failure.

    By following these steps, you should be able to identify and resolve the connectivity issues with your Exchange Server Cluster.

    References:

    0 comments

Your answer

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