I did have exactly the same issue and did, exactly the same thing, until I realized, I had to do it on a server that did report in, after that all of them started reporting in.
__________________________________ Stefan Jafs From: listsadmin@lists.myitforum.com [mailto:listsadmin@lists.myitforum.com] On Behalf Of Michael Leone Sent: September 14, 2015 09:34 To: ntsys...@lists.myitforum.com Subject: [NTSysADM] Fwd: Some Win2012 R2 WSUS clients slow to check in This is starting to drive me crazy. I have 3 Win2012 R2 clients that are slow to check in with my WSUS server (Win 2008 R2, WSUS 3.0 SP2, fully patched). By "slow", I mean today, 2015-09-14, 2 of them show last status report of 2015-09-10 (3 days), and the other shows 2015-09-11 (2 days). All my other clients (158) show last status report of either 2015-09-13 or 2015-09-14 (all understandable). GPO is set to use option 2 - Notify for download and install. [cid:image001.png@01D0EEDC.A19AFFD0] I don't know what is up with these 3. All are set by GPO (the same GPO, shown above); all know that they are managed by a WSUS server (and the windowsupdate.log does show the correct WSUS server, at least at first). I've tried the standard "/resetnow and /detectnow" switches on WUAUCLT; I've tried deleting the entries in WSUS and letting them check in again (either after a "/resetnow" or by manually telling them to check for updates using the "Windows Update" applet in Control Panel [not check online]). Let's look at windowsupdate.log on one of them. Originally, it knows where my WSUS server is, if I understand this log entry correctly: 2015-09-10 09:27:37:154 1324 2860 EP Got WSUS Client/Server URL: "http://dctrman001.wrk.ads.pha.phila.gov/ClientWebService/client.asmx"; 2015-09-10 09:27:37:154 1324 2860 Setup Checking for agent SelfUpdate 2015-09-10 09:27:37:154 1324 2860 Setup Client version: Core: 7.9.9600.17930 Aux: 7.9.9600.17930 2015-09-10 09:27:37:154 1324 2860 EP Got WSUS SelfUpdate URL: "http://dctrman001.wrk.ads.pha.phila.gov/selfupdate"; But later, it seems to be trying to get updates direct from MS, even though I didn't tell it to check online for updates: 2015-09-11 05:15:02:177 1324 1384 AU ############# 2015-09-11 05:15:02:177 1324 1384 AU ## START ## AU: Search for updates 2015-09-11 05:15:02:177 1324 1384 AU ######### 2015-09-11 05:15:02:177 1324 1384 SLS Retrieving SLS response from server using ETAG "4V8nqvoeoxgpu+6kKNNNGpLr4BCvPTmaz82CIDm5o5g=_1440"... 2015-09-11 05:15:02:177 1324 1384 SLS Making request with URL HTTPS://sls.update.microsoft.com/SLS/{9482F4B4-E343-43B6-B170-9A65BC822C77}/x64/6.3.9600.0/0?CH=585&L=en-US&P=&PT=0x7&WUA=7.9.9600.17930<HTTPS://sls.update.microsoft.com/SLS/%7B9482F4B4-E343-43B6-B170-9A65BC822C77%7D/x64/6.3.9600.0/0?CH=585&L=en-US&P=&PT=0x7&WUA=7.9.9600.17930> 2015-09-11 05:15:02:552 1324 1384 EP Got 9482F4B4-E343-43B6-B170-9A65BC822C77 redir SecondaryServiceAuth URL: "117cab2d-82b1-4b5a-a08c-4d62dbee7782" 2015-09-11 05:15:02:552 1324 1384 SLS FATAL: SLS:CSLSRequest::RetrieveAdditionalAttributesIfRequired: CoCreateInstance failed with 0x80040154. 2015-09-11 05:15:02:552 1324 1384 Agent WARNING: Failed to retrieve SLS response data for service 117cab2d-82b1-4b5a-a08c-4d62dbee7782, error = 0x80040154 2015-09-11 05:15:02:552 1324 1384 Agent FATAL: Caller Service Recovery failed to opt in to service 117cab2d-82b1-4b5a-a08c-4d62dbee7782, hr=0X80040154 So what's up with that? Is this why it hasn't checked in in a few days? It's very frustrating ...
