Bump, has anyone seen CM12 Internet-based clients showing WindowsUpdate.log errors downloading EULA .txt files?
On Tue, Jul 9, 2013 at 8:28 AM, Benjamin Monrad <[email protected]>wrote: > Here is a snippet of WindowsUpdate.log showing the scan initializing > against the Internet-facing URL on 8531 and then requesting the EULA .txt > from an internal URL on 8530. > > 2013-07-09 02:36:39:176 788 14e0 PT +++++++++++ PT: > Synchronizing server updates +++++++++++ > 2013-07-09 02:36:39:176 788 14e0 PT + ServiceId = > {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = > HTTPS://INTERNET.FACING.COM:8531/ClientWebService/client.asmx > 2013-07-09 02:36:39:191 788 14e0 PT WARNING: Cached cookie > has expired or new PID is available > 2013-07-09 02:36:39:191 788 14e0 PT Initializing simple > targeting cookie, clientId = 5af5c5fa-2fde-4a9e-8dc3-7d05daf8c640, target > group = , DNS name = irvdigweb03 > 2013-07-09 02:36:39:191 788 14e0 PT Server URL = > HTTPS://INTERNET.FACING.COM:8531/SimpleAuthWebService/SimpleAuth.asmx > 2013-07-09 02:36:42:707 788 14e0 PT +++++++++++ PT: > Synchronizing extended update info +++++++++++ > 2013-07-09 02:36:42:707 788 14e0 PT + ServiceId = > {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = > HTTPS://INTERNET.FACING.COM:8531/ClientWebService/client.asmx > 2013-07-09 02:37:06:551 788 14e0 Misc WARNING: Send failed > with hr = 80072ee2. > 2013-07-09 02:37:06:551 788 14e0 Misc WARNING: SendRequest > failed with hr = 80072ee2. Proxy List used: <(null)> Bypass List used : > <(null)> Auth Schemes used : <> > 2013-07-09 02:37:06:551 788 14e0 Misc WARNING: WinHttp: > SendRequestUsingProxy failed for < > http://internal.domain.lcl:8530/Content/AE/C3248EB572CB5F82E63CE9C6D73CFBF39B1052AE.txt>. > error 0x80072ee2 > 2013-07-09 02:37:06:551 788 14e0 Misc WARNING: WinHttp: > SendRequestToServerForFileInformation MakeRequest failed. error 0x80072ee2 > 2013-07-09 02:37:06:551 788 14e0 Misc WARNING: WinHttp: > SendRequestToServerForFileInformation failed with 0x80072ee2 > 2013-07-09 02:37:06:551 788 14e0 Misc WARNING: WinHttp: > ShouldFileBeDownloaded failed with 0x80072ee2 > 2013-07-09 02:37:30:129 788 14e0 Misc WARNING: Send failed > with hr = 80072ee2. > 2013-07-09 02:37:30:129 788 14e0 Misc WARNING: SendRequest > failed with hr = 80072ee2. Proxy List used: <(null)> Bypass List used : > <(null)> Auth Schemes used : <> > 2013-07-09 02:37:30:129 788 14e0 Misc WARNING: WinHttp: > SendRequestUsingProxy failed for < > http://internal.domain.lcl:8530/Content/AE/C3248EB572CB5F82E63CE9C6D73CFBF39B1052AE.txt>. > error 0x80072ee2 > 2013-07-09 02:37:30:129 788 14e0 Misc WARNING: WinHttp: > SendRequestToServerForFileInformation MakeRequest failed. error 0x80072ee2 > > > > On Tue, Jul 9, 2013 at 8:19 AM, Benjamin Monrad <[email protected]>wrote: > >> Hi, >> >> We've been using IBCM successfully for a few years under CM07 and CM12. >> Server is internal, behind TMG. (DirectAccess is not an option for me >> today, thanks!) >> >> With the CM12 SP1 upgrade, we saw all internet clients start to fail >> scanning, which turned out to be because our internet-enabled SUP stopped >> syncing until we reconfigured it after the SP1 upgrade. So, we figured that >> out and got synchronization running again and now our Server 2003 internet >> clients are scanning with success, but our 2008 R2 boxes are getting scan >> errors around the EULA .txt files. >> >> I am pretty sure these EULA .txt errors were not a problem before the >> upgrade (we had been patching successfully), but since the logs have rolled >> over I don't have a history to be certain. >> >> The EULA .txt errors have two issues: >> 1) they are making the request over 8530 HTTP rather than 8531 HTTPS >> (unreachable because we have only ever had HTTPS ports open on TMG and core >> firewall) >> >> 2) even though they are scanning against the correct Internet host name, >> the EULA .txt URLs are being returned with the Intranet host name >> (unreachable because... Internet). >> >> MS Support is sort of pushing back to say 8530 must be open, which I >> didn't think should the case, and even if we did open 8530 the clients >> would still be trying to get the EULA .txt files from the wrong host name >> and the MS System Center support engineer is kind of stuck, stating that he >> can't reproduce the issue and that it is more of a WSUS-related issue than >> a CM12 issue. >> >> Any ideas? Thanks. >> >> -ben >> >> > >
