Error "WinRM cannot process the request..." while trying to run PowerShell (Exchange 2019 CU4)

Evgeny Shupik 191 Reputation points
2022-11-22T14:11:34.287+00:00

Hello to everyone! :-) Need some help with Exchange 2019 - can't connect to itself via PowerShell (just after fresh install of Exchange 2019 CU4). This looks like:
263085-powershell.jpg

I already checked date & time (all the same with DC), DNS-server (DC's IP-address is using as DNS for my Exchange). Also Exchange is a member of domain so I have no idea what does it mean... Please help.

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,481 questions
{count} votes

Accepted answer
  1. LilyLi2-MSFT 1,981 Reputation points
    2022-11-25T09:47:58.333+00:00

    Hi @Evgeny Shupik ,

    Great to know that you've already thought of a solution and really appreciate it for your sharing!
    By the way, since the Microsoft Q&A community has a policy that "The question author cannot accept their own answer. They can only accept answers by others." and according to the scenario introduced here: Answering your own questions on Microsoft Q&A, I would make a brief summary of this thread:

    [Error "WinRM cannot process the request..." while trying to run PowerShell (Exchange 2019 CU4)]

    Issue Symptom:

    1. PowerShell cannot to connect to Exchange 2019 with the error “The WinRM client cannot process the request because the input XML contains a syntax error.”
    2. DC and Exchange are in different networks

    The Solution:
    Finally resolved; the problem was because of time shift (7 mins) between DC and Exchange.

    You could click the "Accept Answer" button for this summary to close this thread, and this can make it easier for other community member's to see the useful information when reading this thread.
    Thanks!

    0 comments No comments

4 additional answers

Sort by: Most helpful
  1. vimalsingh 1 Reputation point
    2022-11-22T21:11:08.99+00:00

    As per given description it seems you are executing script from the exchange server, as it is using powershell remoting and powershell remoting uses WINRM to connect remote computer.

    so use any other computer like your workstation or member server to execute this script.

    0 comments No comments

  2. Amit Singh 4,866 Reputation points
    2022-11-23T11:22:18.6+00:00

    You need to add the host to your TrustedHosts list. You can do so with a command such as:
    set-item wsman:\localhost\client\trustedhosts -Concatenate -value 'hostname'

    0 comments No comments

  3. Evgeny Shupik 191 Reputation points
    2022-11-23T13:21:34.927+00:00

    You know - there is a small nuance - DC and Exchange are in different networks: 192.168.10.11 (DC) and 10.10.0.10 (Exchange). Could this be causing the problem?

    263427-dc-ip.jpg

    263463-exchange-ip.jpg

    0 comments No comments

  4. Evgeny Shupik 191 Reputation points
    2022-11-24T19:40:26.83+00:00

    Finally resolved; the problem was because of time shift (7 mins) between DC and Exchange.

    0 comments No comments