Current User: '%1' Client Access server "%2", running Microsoft Exchange version "%3", is proxying Web management traffic ...

Current User: '%1'
Client Access server "%2", running Microsoft Exchange version "%3", is proxying Web management traffic to Client Access server "%4", which runs Exchange version "%5".
%6
To ensure reliable interoperability, the proxying Client Access server has to be running a newer version of Exchange than the Client Access server it is proxying to. If the proxying Client Access server is running a newer version of Exchange than the Client Access server it is proxying to, the proxying Client Access server has to have an Web management resource folder, such as "...\ClientAccess\ecp\%5", which contains the same versioned resource files as the Client Access server it is proxying to. If you will be running Web management proxying with mismatched server versions, you can manually copy this resource folder to the proxying Client Access server. After you copy this resource folder to the proxying Client Access server, you have to restart IIS before proxying will work.

Current User: '%1' Client Access server "%2" tried to proxy Web management traffic to Client Access server "%3". This failed ... Current User: '%1' Client Access server "%2" tried to proxy Web management traffic to Client Access server "%3". This failed ... Current User: '%1' Client Access server "%2" tried to proxy Web management traffic to Client Access server "%3". This failed ... Current User: '%1' Client Access server "%2" tried to proxy Web management traffic to Client Access server "%3". This failed ... Current User: '%1' Client Access server "%2", running Microsoft Exchange version "%3", is proxying Web management traffic ... Current User: '%1' Client Access server "%2", running Microsoft Exchange version "%3", is proxying Web management traffic ... Current User: '%1' Exchange Control Panel detected an invalid canary from request for URL '%2'. Canary in cookie: '%3' mismatch ... Current User: '%1' Exchange Control Panel detected an invalid canary from request for URL '%2'. Canary in cookie: '%3' mismatch ... Current User: '%1' Microsoft Exchange Control Panel started serving uploading request. Upload Handler: '%2' Parameter: '%3 ...