Exchange Powershell IIS logs full with Active Monitor

[aborgeld]

Good afternoon,

We've finished a migration to Exchange 2019 CU 11  latest security update (march 8)

Now we want to look at hybrid (exchange online/Teams) integration.

We have a proxy server and when i connect the proxy I get the following error in the Exchange management shell 

New-PSsession connecting to remote server (itself) failed with the following reasons: Connection to the remote host refused. Verify that the WS-management (Web Services-Management) service is running. 

When i look in my IIS logs I see logs of 3 gig with the following messages:

2022-03-22 13:27:30 <ip exchange> POST /powershell clientApplication=ActiveMonitor;PSVersion=5.1.17763.2268&CorrelationID=<empty>;&cafeReqId=fd61ce2d-96ec-4ccc-886e-664820b31e65; 80 - <IP Proxy> Microsoft+WinRM+Client - 200 0 0 2
2022-03-22 13:27:30 <ip exchange> POST /powershell clientApplication=ActiveMonitor;PSVersion=5.1.17763.2268&CorrelationID=<empty>;&cafeReqId=d8fe6573-e598-4698-8835-e074b1dc7d17; 80 - <IP Proxy> Microsoft+WinRM+Client - 200 0 0 2
2022-03-22 13:27:30 <ip exchange> POST /powershell clientApplication=ActiveMonitor;PSVersion=5.1.17763.2268&CorrelationID=<empty>;&cafeReqId=67d16495-355c-4cc0-96b4-17e7bd8136c8; 80 - <IP Proxy> Microsoft+WinRM+Client - 200 0 0 2
2022-03-22 13:27:30 <ip exchange> POST /powershell clientApplication=ActiveMonitor;PSVersion=5.1.17763.2268&CorrelationID=<empty>;&cafeReqId=d64c6728-9697-4c63-973e-8e1bc911f164; 80 - <IP Proxy> Microsoft+WinRM+Client - 200 0 0 2
2022-03-22 13:27:30 <ip exchange> POST /powershell clientApplication=ActiveMonitor;PSVersion=5.1.17763.2268&CorrelationID=<empty>;&cafeReqId=97fa7d4c-5af1-4418-aa1b-44216a25d91e; 80 - <IP Proxy> Microsoft+WinRM+Client - 200 0 0 2
2022-03-22 13:27:30 <ip exchange> POST /powershell clientApplication=ActiveMonitor;PSVersion=5.1.17763.2268&CorrelationID=<empty>; 80 - <IP Proxy> Microsoft+WinRM+Client - 401 111 0 1
2022-03-22 13:27:30 <ip exchange> POST /powershell clientApplication=ActiveMonitor;PSVersion=5.1.17763.2268&CorrelationID=<empty>; 80 - <IP Proxy> Microsoft+WinRM+Client - 401 111 0 1
2022-03-22 13:27:30 <ip exchange> POST /powershell clientApplication=ActiveMonitor;PSVersion=5.1.17763.2268&CorrelationID=<empty>; 80 - <IP Proxy> Microsoft+WinRM+Client - 401 111 0 1
2022-03-22 13:27:30 <ip exchange> POST /powershell clientApplication=ActiveMonitor;PSVersion=5.1.17763.2268&CorrelationID=<empty>; 80 - <IP Proxy> Microsoft+WinRM+Client - 401 111 0 2
2022-03-22 13:27:30 <ip exchange> POST /powershell clientApplication=ActiveMonitor;PSVersion=5.1.17763.2268&CorrelationID=<empty>; 80 - <IP Proxy> Microsoft+WinRM+Client - 401 111 0 2

It hangs the Exchange powershell and finally it writes the disk literally full. 
What's going on here?

Kind regards,

Andre

[#2]

Are these health active monitoring features, that are reported in the IIS log?
And is the routing not right? Because it tries to pol a proxy server instead of the second Exchange server.

And why does it pol every second instead of 5 minutes or every hour?

[#3]

Microsoft says that it could have a relation with the Crl checking. But I would like to know if that's the case how do i control the time interval and prevent the polling on my proxyserver.
Even when i disable proxy it keeps on trying to reach it.

I hope my questions and directions can help you a bit with understanding the issue.

[#4 · Accepted solution]

Solution was a wrong proxy configuration:

set-exchangeserver Exch1 -internetwebproxy http://yourproxy:80 -InternetWebProxyBypassList @("local","domain.local")

Now you let you local traffic go local and only proxy traffic via proxy