Does anybody remember the proxy issue with Endpoint Protection? Some of my clients are trying to hit Microsoft via proxy when trying to update. My policies only have SCCM as the update source and I've got ADR's that get the definitions regularly and it's deployed. But I have bunches of clients today that are a week behind in definitions and windowsupdate.log all have stuff that looks like this: It's worked in the past, obviously, up to a week ago.
2015-05-15 09:02:02:785 684 7b4 Misc WARNING: WinHttp: SendRequestUsingProxy failed for <http://download.microsoft.com/v11/2/windowsupdate/redir/v6-win7sp1-wuredir.cab>. error 0x80072ee2 2015-05-15 09:02:02:785 684 7b4 Misc WARNING: WinHttp: SendRequestToServerForFileInformation MakeRequest failed. error 0x80072ee2 2015-05-15 09:02:02:785 684 7b4 Misc WARNING: WinHttp: SendRequestToServerForFileInformation failed with 0x80072ee2 2015-05-15 09:02:02:785 684 7b4 Misc WARNING: WinHttp: ShouldFileBeDownloaded failed with 0x80072ee2 2015-05-15 09:02:02:785 684 7b4 Misc WARNING: DownloadFileInternal failed for http://download.microsoft.com/v11/2/windowsupdate/redir/v6-win7sp1-wuredir.cab: error 0x80072ee2 2015-05-15 09:04:11:058 684 7b4 Misc WARNING: Send failed with hr = 80072ee2. 2015-05-15 09:04:11:058 684 7b4 Misc WARNING: SendRequest failed with hr = 80072ee2. Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes used : <> Wasn't this fixed, or am I remembering this wrong? Todd
