Skip to main content

SCCM Software Update - Job error 0x80004005 Failed to Add Update Source for WUAgent

By

SCCM Software Updates - Failed to Add Update Source for WUAgent 

Today I have been looking at a range of servers (Server 2008 /R2 2012 /R2) that were failing to communicate with the Software Update Point (SUP) in SCCM and retrieve deployment policy.

The UpdateDeployment.log was reporting the Job error 0x80004005
Job error (0x80004005) received for assignment ({af7a48e6-d550-4070-dd9b-ecc234567584}) action UpdatesDeploymentAgent 12/6/2017 10:32:27 AM 2096 (0x0830)

The WUAHandler.log  was reporting "Unable to read existing WUA Group Policy object" and "Failed to Add Update Source for WUAgent "


Unable to read existing WUA Group Policy object. Error = 0x80004005. WUAHandler 12/6/2017 3:41:00 AM 2828 (0x0B0C)Failed to Add Update Source for WUAgent of type (2) and id ({3AAB6A76-CE2D-4E8A-9F11-123AE69612A1}). Error = 0x80004005. WUAHandler 12/6/2017 11:03:31 AM 2276 (0x08E4)


Until the agent can report back to the SUP, SCCM will not be able to summarize Software Update status and offer the appropriate updates via Software Center. 

The resolution was to stop the "Windows update" service and remove the Registry.pol file and the comment.cmtx file if present as well as the SoftwareDistribution folder.
(C:\Windows\System32\GroupPolicy\Machine\Registry.pol)
(C:\Windows\System32\GroupPolicy\Machine\comment.cmtx)
(C:\Windows\SoftwareDistribution)

After restarting the "Windows update" service the SoftwareDistribution folder is created.
After the next SCCM "Update Deployment Cycle" the Registry.pol is created.

The WUAHandler.log will now state the scan completed successfully.

Waiting for 2 mins for Group Policy to notify of WUA policy change...Waiting for 30 secs for policy to take effect on WU Agent.
Added Update Source ({abc123abc123abc123abc123}) of content type: 2
Async searching of updates using WUAgent started.
Async searching completed.
Successfully completed scan
I have scripted the process to help others deploy a solution. If you think there is a better way to address this problem please leave a comment.




Labels:

Comments

  1. UnknownNovember 1, 2018 at 6:08 AM

    Worked like charmed.

    ReplyDelete
  2. shopifyDecember 14, 2020 at 7:57 AM

    vision direct promo code is available only for limited time period.

    ReplyDelete
  3. mshahidJuly 10, 2021 at 4:56 AM

    Your article has proven useful to me. It’s very informative and you are obviously very knowledgeable in this area. You have opened my eyes to varying views on this topic with interesting and solid content. Unique Dofollow Backlinks

    ReplyDelete
  4. James SmithSeptember 6, 2022 at 10:24 PM

    You can finally submit an impressive copy with our employee motivation assignment help. There will no late submission with our employee motivation assignment help.

    ReplyDelete

Post a Comment

Popular posts from this blog

SCCM Unknown computer not able to see Task Sequences after installing Current Branch 1702

By
Soon after installing SCCM CB 1702 we were unable to see Task Sequences deployed to the unknown collection. This issue was identified as a random system taking the GUID of the 'x64 Unknown Computer (x64 Unknown Computer)' record. As a result it was now a known GUID; as we were only deploying Task Sequences to the Unknown collection none were made available. 'x64 Unknown Computer (x64 Unknown Computer)' record 'x86 Unknown Computer (x86 Unknown Computer)' record To get the GUID of your unknown systems open SQL management studio and run the following command: --Sql Command to list the name and GUID for UnknownSystems record data select ItemKey, Name0,SMS_Unique_Identifier0 from UnknownSystem_DISC Using the returned GUID (SMS_Unique_Identifier0) we can find the hostname that has been assigned the 'x64 Unknown Computer (x64 Unknown Computer)' GUID by running the query below. --x64 Unknown Computers select Name0,SMS_Unique_Identifier0,Decommissioned0 from Sys
159 comments
Read more

Windows 7 Offline files will not go Online when connected to network

By
Issue Several laptop users move between networks, domain, home, etc and when they attempt to access DFS shares explorer status is working offline.  The issue only resolves it self after a reboot. Connecting directly to the share works and i am able to ping network resources.  This behavior occurs for VPN users as well. Possible Causes "slow-link mode". In win7 (with default settings) a client will enter slow-link mode if the latency to the server is above 80ms. In slow-link mode all writes are made to the local cache and a background sync only happens every 6 hours.  Depending on your connection the default slow link detection speed is 64,000 bps On client computers running Windows 7 or Windows Server 2008 R2, a shared folder automatically transitions to the slow-link mode if the round-trip latency of the network is greater than 80 milliseconds, or as configured by the "Configure slow-link mode" policy. After transitioning a folder to the slow-link mode, Offline Fil
150 comments
Read more