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

Question

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:

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.

Answer 1

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!

Answer 2

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.

Answer 3

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'

Answer 4

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?

Answer 5

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