Issue with Exchange 2019 on premise management shell after server 2025 "upgrade"

Darren Woolley 0 Reputation points
2025-02-10T11:51:41.78+00:00

User's image

User's image

This is occurring on 2 sites that we are trying to migrate from on premise exchange and since the "auto" upgrade of server 2025 happened we are unable to access the management console

The Exchange Admin Centre appears to be working fine and the SSL certificate is up to date

Any help is appreciated

Exchange Server
Exchange Server
A family of Microsoft client/server messaging and collaboration software.
1,448 questions
Microsoft Exchange Hybrid Management
Microsoft Exchange Hybrid Management
Microsoft Exchange: Microsoft messaging and collaboration software.Hybrid Management: Organizing, handling, directing or controlling hybrid deployments.
2,238 questions
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Xintao Qiao-MSFT 6,425 Reputation points Microsoft Vendor
    2025-02-11T09:08:50+00:00

    Hi, @Darren Woolley

    Welcome to the Microsoft Q&A platform!

    Today Exchange Server 2019 releases CU15. with the release of CU15, CU13 is now no longer supported due to the “N-1” policy. If you are using an older version, please update it and try again.

    Released: 2025 H1 Cumulative Update for Exchange Server | Microsoft Community Hub

    If you are a supportable version. Depending on the error message, this could be that WinRM is not enabled or the listener is not configured. Run the following command as administrator:

    winrm quickconfig
    winrm enumerate winrm/config/listener
    

    This will start the WinRM service, set it to start automatically, and configure a listener for WS-Management protocol messages.

    User's image

    Installation and configuration for Windows Remote Management - Win32 apps | Microsoft Learn

    If you are using a non-domain member, you must use Basic Authentication, and you must also set Basic Authentication on the virtual directory, as shown below:

    Get-PowerShellVirtualDirectory -Server ServerName | Set-PowerShellVirtualDirectory -BasicAuthentication:$TRUE
    

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


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.