Hi,

I've got a new Windows 2012 R2 server I've setup and I've installed the SCCM 2012 SP1 client on the system. The new Windows 2012 R2 server seems to report it's status fine to my SCCM 2012 SP1 server but the new Windows 2012 R2 server doesn't seem to be pulling down the nightly updates to Endpoint Protection.

The strange thing is if I reboot the server then the update to Endpoint Protection is pulled down and installed and that may happen again for a second day but after that the updates stop getting installed. 

The WindowsUpdate.log seems to show lots of these messages:

2015-07-14 09:05:55:071  496 1c8 AU WARNING: Failed to get Wu Exemption info from NLM, assuming not exempt, error = 0x80240037
2015-07-14 09:05:55:071  496 1c8 AU WARNING: Failed to get Network Cost info from NLM, assuming network is NOT metered, error = 0x80240037
2015-07-14 09:05:55:075  496 1c8 AU AU finished delayed initialization
2015-07-14 09:05:55:075  496 1c8 AU WARNING: Failed to get Network Cost info from NLM, assuming network is NOT metered, error = 0x80240037
2015-07-14 09:05:55:077  496 1c8 AU WARNING: Failed to get Network Cost info from NLM, assuming network is NOT metered, error = 0x80240037
2015-07-14 09:05:55:081  496 dd0 DnldMgr Asking handlers to reconcile their sandboxes
2015-07-14 09:07:45:695  496 1c8 AU Adding timer:
2015-07-14 09:07:45:695  496 1c8 AU     Timer: CF1ABEC6-7887-4964-BB93-B2E21B31CEC1, Expires 2015-07-15 16:07:45, not idle-only, not network-only
2015-07-14 09:07:45:695  496 1c8 AU Adding timer:
2015-07-14 09:07:45:695  496 1c8 AU     Timer: 29A863E7-8609-4D1E-B7CD-5668F857F1DB, Expires 2015-07-15 16:07:45, not idle-only, not network-only
2015-07-14 09:15:55:093  496 414 AU Earliest future timer found:
2015-07-14 09:15:55:093  496 414 AU     Timer: 31DA7559-FE27-4810-8FF6-987195B1FD98, Expires 2015-07-14 23:01:21, not idle-only, not network-only

2015-07-14 10:49:51:123  496 414 Misc WARNING: Network Cost is assumed to be not supported as something failed with trying to get handles to wcmapi.dll
2015-07-14 10:49:51:135  496 414 WuTask WuTaskManager delay initialize completed successfully..
2015-07-14 10:49:51:135  496 414 AU     Timer: 31DA7559-FE27-4810-8FF6-987195B1FD98, Expires 2015-07-14 23:01:21, not idle-only, not network-only
2015-07-14 10:49:51:135  496 414 AU     Timer: CF1ABEC6-7887-4964-BB93-B2E21B31CEC1, Expires 2015-07-15 16:07:45, not idle-only, not network-only
2015-07-14 10:49:51:135  496 414 AU     Timer: 29A863E7-8609-4D1E-B7CD-5668F857F1DB, Expires 2015-07-15 16:07:45, not idle-only, not network-only

2015-07-14 12:50:03:690  496 1274 Service *********
2015-07-14 12:50:03:690  496 1274 Service **  END  **  Service: Service exit [Exit code = 0x240001]

2015-07-14 16:01:21:013  496 708 SLS Retrieving SLS response from server using ETAG "4V8nqvoeoxgpu+6kKNNNGpLr4BCvPTmaz82CIDm5o5g=_1440"...
2015-07-14 16:01:21:013  496 708 SLS Making request with URL HTTPS://sls.update.microsoft.com/SLS/{9482F4B4-E343-43B6-B170-9A65BC822C77}/x64/6.3.9600.0/0?CH=242&L=en-US&P=&PT=0x8&WUA=7.9.9600.17831
2015-07-14 16:01:21:128  496 708 EP Got 9482F4B4-E343-43B6-B170-9A65BC822C77 redir SecondaryServiceAuth URL: "117cab2d-82b1-4b5a-a08c-4d62dbee7782"
2015-07-14 16:01:21:129  496 708 SLS FATAL: SLS:CSLSRequest::RetrieveAdditionalAttributesIfRequired: CoCreateInstance failed with 0x80040154.
2015-07-14 16:01:21:129  496 708 Agent WARNING: Failed to retrieve SLS response data for service 117cab2d-82b1-4b5a-a08c-4d62dbee7782, error = 0x80040154
2015-07-14 16:01:21:129  496 708 Agent FATAL: Caller Service Recovery failed to opt in to service 117cab2d-82b1-4b5a-a08c-4d62dbee7782, hr=0X80040154
2015-07-14 16:01:21:130  496 708 IdleTmr WU operation (CSearchCall::Init ID 2) started; operation # 7; does use network; is at background priority

Any clue as to what's wrong?

Thanks

Nick

Hi Joyce,

The WSUS server running on my SCCM 2012 SP1 CU4 server and is I believe WSUS 3.0 SP2. 

The server does appear to get other updates when I have pushed them out thru SCCM but it hasn't been around long enough to get a full patch Tuesday push which I will be doing this week with the latest July patch Tuesday updates so I will find out more then.

Strangely it appears that it did successfully pull down the Endpoint update on Friday and then on Sunday. 

The windowsupdate.log still shows the errors that I reported originally and also these:2015-07-20 04:02:09:886 1976 1780 COMAPI <<-- SUBMITTED -- COMAPI: Search [ClientId = CcmExec]
2015-07-20 04:02:09:886  496 cf8 Agent   * WARNING: Exit code = 0x8024000B
2015-07-20 04:02:09:886  496 cf8 Agent *********
2015-07-20 04:02:09:886  496 cf8 Agent **  END  **  Agent: Finding updates [CallerId = AutomaticUpdates  Id = 6]
2015-07-20 04:02:09:886  496 cf8 Agent *************
2015-07-20 04:02:09:886  496 cf8 Agent WARNING: WU client failed Searching for update with error 0x8024000b

Are there some SCCM client logs that I can look at to check for errors? 

It seems like the server is pulling down updates but not sure why I have all these errors in the windowsupdate.log?

Also I reviewed the windowsupdate.log on another Windows 2012 R2 server that has no issues with updates or endpoint definition updates and I see a lot of the same error messages about NLM so maybe that's normal for 2012 R2 servers?

Nick

Hi,

What's the version of your WSUS? Is there a client receiving updates without a problem? Does this issue happen on all updates or just definition updates?

Yes, I know this is an old post, but Im trying to clean them up. Did you solve this problem, if so what was the solution?

Hi Garth,

The server pulls down the packages and updates that I push out from SCCM right on schedule but the server is still not consistently pulling down the SCEP updates that I publish daily but the SCEP client on the new server does get updated every couple of days.

So I'm not sure if there ever was a problem and if there was/is I never really found a way to resolve it.

Thanks

Nick

if the SCEP updated are coming down every few days, then it means there is a problem. If I remember right every 3 days, the SCEP client will download the latest update directly from MS, if it can't get it from WSUS.

I would dig deeper into this and check our ADR rules.

I was actually wondering about that.

What's so strange is this server and actually another one pull down all the other security and other updates I publish thru SCCM with no issues.

And the ADR rules look to be running correctly and 99% of my other SCEP and SCCM clients don't have any issues. 

I'm not sure where the problem is at this point.