Forums on Intune, SCCM, and Windows 11

Welcome to the forums. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your topics and posts, as well as connect with other members through your own private inbox!

SOLVED Server 2016 Clients not receiving Updates

Status
Not open for further replies.

PKSCCM

Member
Messages
22
Reaction score
0
Points
1
Hi,

I've built a new SCCM environment which consists of Server 2016 with SCCM installed and updated to 1702.

I've also used the migration to get a few bits and pieces from the old SCCM server like collections and packages etc.

The issue I have is where the client won't receive windows updates. I've created a SUG and Deployment like normal and that all works fine but the client does nothing much.

WUAHandler.log from the client gives the following errors

OnSearchComplete - Failed to end search job. Error = 0x8024401c. WUAHandler 31/07/2017 11:11:31 AM 580 (0x0244)
Scan failed with error = 0x8024401c. WUAHandler 31/07/2017 11:11:31 AM 580 (0x0244)

I've googled it so many times and tried all the recommended solutions but still the same issue persists. I've even removed WSUS and SUP and reinstalled them but to no avail.

In addition to this IIS Worker Process is still consuming high CPU.

I can see Requests under the WSUS App Pool in IIS.

It seems that WSUS uses maximum CPU then the App Pool stops and has to be manually restarted.

I'm a bit lost as to what to try now. Any help would be greatly appreciated.
 
Last edited:
I've tried the following steps

  1. Go to IIS

  2. Right click on WsusPool (or whatever you named it) and click on "Advanced Settings..."

  3. Under the "General" section, change the "Start Mode" to "Always Running"

  4. Scroll down to the "Process Model" section and change the "Maximum Worker Processes" to 0

  5. Scroll all the way down to the "Recycling" section and up your "Private Memory Limit (KB)" to a minimum of 6000000

  6. Change "Virtual Memory Limit (KB)" to 0
as well as

but still I get the errors and WSUS IIS Worker Process shots up to 90% + CPU
 
Did you try cleaning up WSUS ?. What's the client polling policy (in minutes) set to ?. Perform a full clean and re-index of WSUS and let me know how it goes.
 
Did you try cleaning up WSUS ?. What's the client polling policy (in minutes) set to ?. Perform a full clean and re-index of WSUS and let me know how it goes.

Hi Prajwal, thanks for your response. I have been following your SCCM posts for years now and I really appreciate the effort you put into helping others.

The polling interval is currently set to 10 minutes.

I have now performed a full clean of WSUS as you suggested. The only thing it seems to have done is deleted 716 unused update revisions.

WSUS seems to be sync'ing now, after once again removing WSUS and the SUP and reinstalling them. I did keep the same SQL DB when doing this but I let it recreate its own WSUS content. If I left the WSUS content there the post installation setup failed.

I did receiver errors when trying to sync with MS for updates but I did some googling and found an article mentioning that I should untick all classifications...sync .....reticked them and since doing this it seems to be working OK.

The errors on the client which I was receiving before (OnSearchComplete - Failed to end search job) seem to have gone away.

And now my Server 2016 machine is receiving updates. It must have been as you mentioned the WSUS cleanup? I would have thought that once I create a SUG and distribute it that it no longer uses WSUS and deploys them similar to how a package would be deployed, is that not the case?
 
It seems to have resolved the issue. I've tested on Server 2016 and Server 2012 so far, about to test on 2008. So far so good though.

Seems strange that that's what caused the issue though, since it was a client error and should have nothing to do with WSUS?
 
It looks like BITS on my server stops its self after a few minutes. It starts fine when started manually, but then stops after about one minute. I can't seem to find any information around on this issue. Has anyone else ran into this issue on Windows Server 2016?

No information in event viewer even after enabling analytic logs. This seems to be affecting my 2008R2 box (testing updates on all Server Operating Systems).

In the DataTransferService.log I'm getting a lot of these warnings

CDTSJob::HandleErrors: DTS Job '{3D82BEEC-B047-458C-A105-8F7319023AD1}' BITS Job '{B571038D-7215-45E9-A349-C75C42120CB1}' under user 'S-1-5-18' OldErrorCount 250 NewErrorCount 251 ErrorCode 0x80070003 DataTransferService 7/08/2017 2:16:09 PM 944 (0x03B0)

I'm guessing this would be related to BITS being stopped on the SCCM Server.
 
It may not be BITS related issue. I see the error code is 0x80070003 which translates to path not found. I suspect if the client machines are able to find the path to these updates. Could you check this thread and let me know if it helped ?.
 
I'm not able to give permissions to the .net folder as I have the same issue as the last poster in that thread. SMS Distribution Points Pool is running as LocalService in IIS.

The SUG that I'm testing with has over 1000 updates and the machine did download about 200 of them (that may be all that is applicable to this machine) but nothing ever showed up in Software Center, the files only downloaded to ccmcache folder and sat there. That's why I checked the datatransfer logs etc and found the CDTSJob Handle Errors - BITS job error.

I have now ticked "allow non users" on my DP settings. I've also tried reinstalling the client on the machine and will see how that goes.

My main concern is that BITS on the SCCM server stops after a minute and I can't find any info in the event viewer or anywhere. I've tried stopping WSUS service as well as IIS and still BITS will run for one minute and then stop so it seems like it's not related to WSUS or IIS.
 
It downloaded the updates again into its ccmcache folder and now Software Center has picked up and is installing updates. Thanks so much for your help, it means a lot. I guess the issue was the last step which was "allow anon" on the DP settings as that and reinstalling the client on the machine are the two only things I've done.

Now to find out why BITS on my Server 2016 SCCM server is stopping after one minute.

Thank you so much Prajwal !!
 
Status
Not open for further replies.
Back
Top