SCCM 2012 Software Updates - clients stuck Active/Passed

I've tried deploying some Windows updates to a collection which has no maintenance window. but they're not getting the updates.
Interestingly even my own system, which is a member of said collection, is also not getting any updates.

Deadline of deployment was "As soon as possible" but the clients in the Deployment Monitoring area just show "Unknown" (Client check passed/Active).
Can't speed it up by running actions locally, does nothing.

Only things I can gather so far which might indicate a problem are from the following areas, and I'm still not sure what these mean or if they have any bearing on this issue:

UpdateTrustedSites.log, just repeatedly shows:
Starting UpdateTrustedSites with   S-1-5-21-3601230794-2690829250-819315581-7378
AddDefaultPortalToTrustedSites: Existing URL is empty or add to trusted sites is true and the default URL hasn't changed. Not deleting the existing URL from trusted sites list.
AddDefaultPortalToTrustedSites: It was determined that catalog Url should not be added to the trusted sites zone.

So I ran "Deployment Monitoring Tool" on my local system, and I indeed show the Microsoft Software Updates deployment as a deployment to my system, but the "State" column shows "ASSIGNMENT_EVALUATION_ASSIGNMENT_EVALUATE_FAILED".

Again, I don't know if these 2 areas are related, and/or if either of them have any bearing on my issue of updates not being deployed, so I'm checking here for help!

I've also tried uninstalling my client and re-installing, but no luck.
Who is Participating?
Nagendra Pratap SinghConnect With a Mentor Commented:
Please upload WUAHandler.log from your machine here as an attachment.
garryshapeAuthor Commented:
The WUAHandler on my client appears to only contain the following:

CWuaHandler::SetCategoriesForStateReportingExclusion called with E0789628-CE08-4437-BE74-2495B842F43B;E0789628-CE08-4437-BE74-2495B842F43B,A38C835C-2950-4E87-86CC-6911A52C34A3; for leaves and E0789628-CE08-4437-BE74-2495B842F43B,A38C835C-2950-4E87-86CC-6911A52C34A3; for bundles      WUAHandler      12/23/2014 4:01:29 PM      19544 (0x4C58)
Nagendra Pratap SinghCommented:
Is any collection getting updates at all?
The 14th Annual Expert Award Winners

The results are in! Meet the top members of our 2017 Expert Awards. Congratulations to all who qualified!

garryshapeAuthor Commented:
I have a baseline that's deployed and is working fine
But as for this Software Updates deployment, the collection is 11 computers and they've deployed to in the past just fine. But now they just sit in unknown state indefinitely it seems.

The last thing I remember happening before this was WSUS was uninstalled for some reason, then re-installed. Then WSUS reset command was run to reset all meta deta because the updates weren't showing up in SCCM.
But I created this Software Update package after that so it's definitely the right updates that are needed
Nagendra Pratap SinghCommented:
So what happens if you put a totally fresh machine in this collection?

I guess your SCCM DB is out of sync. You are offering version 11 or so and the clients expect version 670 or similar.

I have seen issues like this earlier.

Please see the following thread and also post ScanAgent.log after enabling debug logging

garryshapeAuthor Commented:
Thanks for follow-up. Do I still need to enable debug logging somewhere?
I did check ScanAgent.log on my system and it shows:

Warning: No valid source found for the update with SourceId = {D6192AA5-3B5E-4481-BB38-01368E4902A5}      ScanAgent      12/23/2014 6:34:04 PM      8320 (0x2080)
Found CategoryID of :bfe5b177-a086-47a0-b102-097e4fa1f807 for Update:fea97a5b-09b9-42f9-9a76-f797494e7f9f      ScanAgent      12/23/2014 6:34:04 PM      8320 (0x2080)
CScanAgent::ScanByUpdates - Found UpdateClassification 0fa1201d-4330-4fa8-8ae9-b877473b6441 for Update:fea97a5b-09b9-42f9-9a76-f797494e7f9f      ScanAgent      12/23/2014 6:34:04 PM      8320 (0x2080)
Warning: No valid source found for the update with SourceId = {D6192AA5-3B5E-4481-BB38-01368E4902A5}      ScanAgent      12/23/2014 6:34:04 PM      8320 (0x2080)
Found CategoryID of :bfe5b177-a086-47a0-b102-097e4fa1f807 for Update:fecc2a9c-8b48-4c42-95d9-3109977b5b6d      ScanAgent      12/23/2014 6:34:04 PM      8320 (0x2080)
CScanAgent::ScanByUpdates - Found UpdateClassification 0fa1201d-4330-4fa8-8ae9-b877473b6441 for Update:fecc2a9c-8b48-4c42-95d9-3109977b5b6d      ScanAgent      12/23/2014 6:34:04 PM      8320 (0x2080)
Warning: No valid source found for the update with SourceId = {D6192AA5-3B5E-4481-BB38-01368E4902A5}      ScanAgent      12/23/2014 6:34:04 PM      8320 (0x2080)
CScanAgent::ScanByUpdates - Update Source Policies not found no scan will be performed, returning E_FAIL_POLICY_NOT_FOUND      ScanAgent      12/23/2014 6:34:04 PM      8320 (0x2080)
CUpdatesScan::ScanByUpdates - failed at call to CScanAgent::ScanByUpdates(), error=0x87d00600      ScanAgent      12/23/2014 6:34:04 PM      8320 (0x2080)
garryshapeAuthor Commented:
I am trying it now but I'm getting different instructions from this site

I'm not sure how long I need to wait before the log files starts showing more details
garryshapeAuthor Commented:
Still waiting on this log file to show some more activity but I did find this on one of the SCCM Components SMS_WSUS_SYNC_MANAGER:

Severity      Type      Site code      Date / Time      System      Component      Message ID      Description
      SMS_WSUS_SYNC_MANAGER      6703       WSUS Synchronization failed.   Message: UssNotFound: WebException: The request failed with HTTP status 404: Not Found.  at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall).   Source: Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WsusSyncAction.WSyncAction.SyncWSUS.
garryshapeAuthor Commented:
How can I just completely remove the Software Update and WSUS stuff?

I'm on Server 2012

I'd rather just do that because the log files aren't showing any up to date stuff and I got that critical error for WSUS Sync in SCCM logs. I never meant for this to be a complicated setup I just want it to start over and work like it did before.
Nagendra Pratap SinghConnect With a Mentor Commented:
Remove SUP role.
Remove WSUS

Install WSUS
Install SUP.
I had this issue with my latest software update group.  I deployed the SUG to the following collections:
1. Collection 1 for beta - successful
2. Smaller group of business units - successful
3. Production computers - partially successful

I removed some expired updates from the software update group before all the computers were compliant.  THis seems to have corrupted the deployment.  I deleted the deployments and created and deployed a new software update group containing the same updates and it seems to be working now.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.