Microsofthey Paul_Huijbregts
After setting the winhttp proxy, the system was able to perform the necessary checks. And the log from the ClientAnalyzer is stating the following:
Connectivity output, using psexec -s:
Proxy config: Method=TelemetryProxyServer, address=xxxxx.ads:3128
********************************************************************
********************************************************************
Testing URL : https://winatp-gw-weu.microsoft.com/commands/test
1 - Default proxy: Succeeded (200)
2 - Proxy auto discovery (WPAD): Succeeded (200)
3 - Proxy disabled: Failed (12002: WinHttpSendRequest: 12002: The operation timed out)
4.1 - Named proxy ( xxxxx:3128): Succeeded (200)
5 - Command line proxy: Doesn't exist
********************************************************************
Eventlog now also shows successful connections for SENSE:
Contacted server 8 times, all succeeded, URI: https://winatp-gw-weu.microsoft.com/.
I've removed the winhttp again now and rebooted the server to see if it's now still working or back to where it was before. Result: it's back to being unable to connect and SENSE reporting errors. So it seems there might be some work todo?
My goal would be not to configure winhttp proxy since this can be used by other services on the system, I might not want to communicate. Is this something you have to check with the Team?
You help so far is really appreciated. Thank you. If you need something or if there is something I can help with, please let me know.