SOLVED

WSUS and Software updates deployment

%3CLINGO-SUB%20id%3D%22lingo-sub-660601%22%20slang%3D%22en-US%22%3EWSUS%20and%20Software%20updates%20deployment%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-660601%22%20slang%3D%22en-US%22%3E%3CP%3EHello%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EDo%20you%20guys%20have%20any%20idea%20why%20our%20SCCM%20could%20not%20sync%20with%20WSUS%20and%20Deploy%20Software%20Updates%3F%3C%2FP%3E%3CP%3EHere's%20the%20log%20I%20found%20from%20our%20SCCM%20and%20one%20of%20our%20PC.%20Your%20response%20will%20be%20greatly%20appreciated.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWCM%20LOG%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESystem.Security.SecurityException%3A%20Request%20for%20principal%20permission%20failed.~~%20at%20Microsoft.UpdateServices.Administration.AdminProxy.CreateUpdateServer(Object%5B%5D%20args)~~%20at%20Microsoft.SystemsManagementServer.WSUS.WSUSServer.ConnectToWSUSServer(String%20ServerName%2C%20Boolean%20UseSSL%2C%20Int32%20PortNumber)~~The%20Zone%20of%20the%20assembly%20that%20failed%20was%3A~~MyComputer%20SMS_WSUS_CONFIGURATION_MANAGER%2024%2F05%2F2019%2012%3A10%3A08%20AM%207792%20(0x1E70)%3C%2FP%3E%3CP%3ERemote%20configuration%20failed%20on%20WSUS%20Server.%20SMS_WSUS_CONFIGURATION_MANAGER%2024%2F05%2F2019%2012%3A10%3A08%20AM%207792%20(0x1E70)%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWSYNCMGR%20LOG%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESync%20failed%3A%20WSUS%20server%20not%20configured.%20Please%20refer%20to%20WCM.log%20for%20configuration%20error%20details..%20Source%3A%20CWSyncMgr%3A%3ADoSync%20SMS_WSUS_SYNC_MANAGER%2024%2F05%2F2019%2011%3A50%3A05%20AM%207832%20(0x1E98)%3C%2FP%3E%3CP%3ESTATMSG%3A%20ID%3D6703%20SEV%3DE%20LEV%3DM%20SOURCE%3D%22SMS%20Server%22%20COMP%3D%22SMS_WSUS_SYNC_MANAGER%22%20SYS%3DSCCMSVR.Domain.com%20SITE%3DATC%20PID%3D3668%20TID%3D7832%20GMTDATE%3DFri%20May%2024%2003%3A50%3A05.331%202019%20ISTR0%3D%22CWSyncMgr%3A%3ADoSync%22%20ISTR1%3D%22WSUS%20server%20not%20configured.%20Please%20refer%20to%20WCM.log%20for%20configuration%20error%20details.%22%20ISTR2%3D%22%22%20ISTR3%3D%22%22%20ISTR4%3D%22%22%20ISTR5%3D%22%22%20ISTR6%3D%22%22%20ISTR7%3D%22%22%20ISTR8%3D%22%22%20ISTR9%3D%22%22%20NUMATTRS%3D0%20SMS_WSUS_SYNC_MANAGER%2024%2F05%2F2019%2011%3A50%3A05%20AM%207832%20(0x1E98)%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EUPDATESHANDLER%20LOG%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ECUpdatesAgent%3A%3AFinalConstruct%20entered%20UpdatesHandler%2024%2F05%2F2019%202%3A23%3A36%20PM%2010564%20(0x2944)%3CBR%20%2F%3EInitiating%20updates%20scan%20for%20checking%20applicability.%20UpdatesHandler%2024%2F05%2F2019%202%3A23%3A36%20PM%209088%20(0x2380)%3CBR%20%2F%3ESuccessfully%20initiated%20scan.%20UpdatesHandler%2024%2F05%2F2019%202%3A23%3A37%20PM%209088%20(0x2380)%3CBR%20%2F%3EUpdates%20scan%20completion%20received%2C%20result%20%3D%200x0.%20UpdatesHandler%2024%2F05%2F2019%202%3A24%3A01%20PM%2010564%20(0x2944)%3CBR%20%2F%3EMethod%20(Discover)%20called%20from%20SDM.%20UpdatesHandler%2024%2F05%2F2019%202%3A24%3A01%20PM%2010796%20(0x2A2C)%3CBR%20%2F%3EStarting%20job%20with%20id%20%3D%20%7BDCB79C1C-A1C5-4593-A175-044A5F35C3C0%7D%20UpdatesHandler%2024%2F05%2F2019%202%3A24%3A01%20PM%2010796%20(0x2A2C)%3CBR%20%2F%3EInitiating%20Scan.%20Forced%20%3D%20(2)%20UpdatesHandler%2024%2F05%2F2019%202%3A24%3A02%20PM%2010796%20(0x2A2C)%3CBR%20%2F%3ESuccessfully%20initiated%20scan%20for%20job%20(%7BDCB79C1C-A1C5-4593-A175-044A5F35C3C0%7D).%20UpdatesHandler%2024%2F05%2F2019%202%3A24%3A02%20PM%2010796%20(0x2A2C)%3CBR%20%2F%3EScan%20completion%20received%20for%20job%20(%7BDCB79C1C-A1C5-4593-A175-044A5F35C3C0%7D).%20UpdatesHandler%2024%2F05%2F2019%202%3A24%3A11%20PM%2010564%20(0x2944)%3CBR%20%2F%3EEvaluating%20status%20of%20the%20updates%20for%20the%20job%20(%7BDCB79C1C-A1C5-4593-A175-044A5F35C3C0%7D).%20UpdatesHandler%2024%2F05%2F2019%202%3A24%3A11%20PM%2010564%20(0x2944)%3CBR%20%2F%3ESuccessfully%20sent%20job%20(%7BDCB79C1C-A1C5-4593-A175-044A5F35C3C0%7D)%20success%20completion%20to%20the%20SdmAgent%20UpdatesHandler%2024%2F05%2F2019%202%3A24%3A11%20PM%209088%20(0x2380)%3CBR%20%2F%3ECompleteJob%20received%20from%20SDM.%20UpdatesHandler%2024%2F05%2F2019%202%3A24%3A11%20PM%2010564%20(0x2944)%3CBR%20%2F%3EComplete%20-%20Job%20(%7BDCB79C1C-A1C5-4593-A175-044A5F35C3C0%7D)%20Cleanup.%20UpdatesHandler%2024%2F05%2F2019%202%3A24%3A11%20PM%2010564%20(0x2944)%3CBR%20%2F%3ECompleteJob%20-%20Job%20(%7BDCB79C1C-A1C5-4593-A175-044A5F35C3C0%7D)%20removed%20from%20job%20manager%20list.%20UpdatesHandler%2024%2F05%2F2019%202%3A24%3A11%20PM%2010564%20(0x2944)%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESCANAGENT%20LOG%3C%2FP%3E%3CP%3E*****ScanByUpdates%20request%20received%20with%20ForceReScan%3D2%2C%20ScanOptions%3D0x00000002%2C%20WSUSLocationTimeout%20%3D%20604800%20ScanAgent%2024%2F05%2F2019%202%3A24%3A02%20PM%2010796%20(0x2A2C)%3CBR%20%2F%3E-%20-%20-Evaluating%20Update%20Status...%20ScanAgent%2024%2F05%2F2019%202%3A24%3A02%20PM%2010796%20(0x2A2C)%3CBR%20%2F%3EFound%20CategoryID%20of%20%3Ae6cf1350-c01b-414d-a61f-263d14d133b4%20for%20Update%3Ac2ea7fb3-7352-4b8b-9e54-4e06802ac7cc%20ScanAgent%2024%2F05%2F2019%202%3A24%3A02%20PM%2010796%20(0x2A2C)%3CBR%20%2F%3ECScanAgent%3A%3AScanByUpdates%20-%20Found%20UpdateClassification%20e6cf1350-c01b-414d-a61f-263d14d133b4%20for%20Update%3Ac2ea7fb3-7352-4b8b-9e54-4e06802ac7cc%20ScanAgent%2024%2F05%2F2019%202%3A24%3A02%20PM%2010796%20(0x2A2C)%3CBR%20%2F%3EFound%20CategoryID%20of%20%3Ae6cf1350-c01b-414d-a61f-263d14d133b4%20for%20Update%3Aa970acb7-1129-4e94-9d1a-2e6045b0afc4%20ScanAgent%2024%2F05%2F2019%202%3A24%3A02%20PM%2010796%20(0x2A2C)%3CBR%20%2F%3ECScanAgent%3A%3AScanByUpdates%20-%20Found%20UpdateClassification%20e6cf1350-c01b-414d-a61f-263d14d133b4%20for%20Update%3Aa970acb7-1129-4e94-9d1a-2e6045b0afc4%20ScanAgent%2024%2F05%2F2019%202%3A24%3A02%20PM%2010796%20(0x2A2C)%3CBR%20%2F%3ESources%20are%20current%20and%20valid.%20TTLs%20are%20also%20valid.%20ScanAgent%2024%2F05%2F2019%202%3A24%3A02%20PM%2010796%20(0x2A2C)%3CBR%20%2F%3ESources%20are%20Valid%2C%20so%20converting%20to%20Offline%20Scan.%20ScanAgent%2024%2F05%2F2019%202%3A24%3A02%20PM%2010796%20(0x2A2C)%3CBR%20%2F%3EScanJob(%7B8389E6DE-91A8-4D67-9045-083EC041548B%7D)%3A%20CScanJob%3A%3AScan-%20Requesting%20Offline%20Scan%20with%20last%20known%20location.%20ScanAgent%2024%2F05%2F2019%202%3A24%3A02%20PM%2010796%20(0x2A2C)%3CBR%20%2F%3ESources%20are%20current%20and%20valid.%20TTLs%20are%20also%20valid.%20ScanAgent%2024%2F05%2F2019%202%3A24%3A02%20PM%2010564%20(0x2944)%3CBR%20%2F%3EScanJob(%7B8389E6DE-91A8-4D67-9045-083EC041548B%7D)%3A%20CScanJob%3A%3AExecute-%20Requesting%20scan%20with%20CategoryIDs%3DE6CF1350-C01B-414D-A61F-263D14D133B4%2CE6CF1350-C01B-414D-A61F-263D14D133B4%20ScanAgent%2024%2F05%2F2019%202%3A24%3A02%20PM%2010564%20(0x2944)%3CBR%20%2F%3EScanJob(%7B8389E6DE-91A8-4D67-9045-083EC041548B%7D)%3A%20Scan%20Succeeded%2C%20setting%20flag%20that%20performed%20scan%20was%20catscan%20ScanAgent%2024%2F05%2F2019%202%3A24%3A11%20PM%209088%20(0x2380)%3CBR%20%2F%3EScanJob(%7B8389E6DE-91A8-4D67-9045-083EC041548B%7D)%3A%20CScanJob%3A%3AOnScanComplete%20-%20Scan%20completed%20successfully%2C%20ScanType%3D2%20ScanAgent%2024%2F05%2F2019%202%3A24%3A11%20PM%209088%20(0x2380)%3CBR%20%2F%3EScanJob(%7B8389E6DE-91A8-4D67-9045-083EC041548B%7D)%3A%20CScanJobManager%3A%3AOnScanComplete%20-ScanJob%20is%20completed.%20ScanAgent%2024%2F05%2F2019%202%3A24%3A11%20PM%209088%20(0x2380)%3CBR%20%2F%3EScanJob(%7B8389E6DE-91A8-4D67-9045-083EC041548B%7D)%3A%20CScanJobManager%3A%3AOnScanComplete%20-%20Reporting%20Scan%20request%20complete%20to%20clients...%20ScanAgent%2024%2F05%2F2019%202%3A24%3A11%20PM%209088%20(0x2380)%3CBR%20%2F%3E-%20-%20-Evaluating%20Update%20Status...%20ScanAgent%2024%2F05%2F2019%202%3A24%3A11%20PM%2010564%20(0x2944)%3CBR%20%2F%3E-%20-%20Calling%20back%20to%20client%20on%20Scan%20request%20complete...%20ScanAgent%2024%2F05%2F2019%202%3A24%3A11%20PM%2010564%20(0x2944)%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWUAHandler%20LOG%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EOnSearchComplete%20-%20Failed%20to%20end%20search%20job.%20Error%20%3D%200x80244010.%20WUAHandler%2024%2F05%2F2019%208%3A11%3A00%20AM%201364%20(0x0554)%3CBR%20%2F%3EScan%20failed%20with%20error%20%3D%200x80244010.%20WUAHandler%2024%2F05%2F2019%208%3A11%3A00%20AM%201364%20(0x0554)%3CBR%20%2F%3EIts%20a%20WSUS%20Update%20Source%20type%20(%7B123D2DFE-5D16-49B4-A734-B7298CF3DC91%7D)%2C%20adding%20it.%20WUAHandler%2024%2F05%2F2019%208%3A41%3A00%20AM%20984%20(0x03D8)%3CBR%20%2F%3EOS%20Version%20is%2010.0.17134%20WUAHandler%2024%2F05%2F2019%208%3A41%3A00%20AM%206588%20(0x19BC)%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-660601%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3ESystem%20Center%20Configuration%20Manager%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EWSUS%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-663001%22%20slang%3D%22en-US%22%3ERe%3A%20WSUS%20and%20Software%20updates%20deployment%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-663001%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F351010%22%20target%3D%22_blank%22%3E%40Shieldwolf_0007%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EFrom%20your%20wcm.log%3A%20%22Remote%20configuration%20failed%20on%20WSUS%20Server.%22%3C%2FP%3E%0A%3CP%3EYou've%20either%20misconfigured%20your%20SUP%2C%20something%20like%20using%20the%20incorrect%20port(s)%2C%20or%20connectivity%20between%20your%20site%20server%20and%20SUP%20is%20blocked%20or%20not%20allowed.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ECan%20you%20connect%20from%20the%20site%20server%20to%20the%20WSUS%20instance%20on%20the%20site%20system%20hosting%20the%20SUP%20using%20the%20WSUS%20Admin%20console%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-663718%22%20slang%3D%22en-US%22%3ERe%3A%20WSUS%20and%20Software%20updates%20deployment%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-663718%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F117994%22%20target%3D%22_blank%22%3E%40Jason%20Sandys%3C%2FA%3E%26nbsp%3BThank%20you%20very%20much%20for%20replying.%20I'll%20try%20your%20suggestions.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EJust%20to%20give%20additional%20information%2C%20last%203-4mons%2C%20I%20was%20able%20to%20download%20software%20updates%20from%20SCCM%20but%20couldn't%20deploy%20updates.%20Our%20client%20decided%20to%20disable%20SCCM%20Domain%20Admin%20account%20and%20replace%20it%20with%20Service%20Account.%20I'm%20not%20sure%20if%20this%20is%20related%20to%20the%20issue.%20For%20the%20ports%2C%20we%20are%20using%208530%20and%208531.%20I've%20disabled%20the%20firewall%20also%20from%20WSUS%20and%20SCCM%20Server.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-699230%22%20slang%3D%22en-US%22%3ERe%3A%20WSUS%20and%20Software%20updates%20deployment%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-699230%22%20slang%3D%22en-US%22%3EThe%20issue%20is%20now%20solved.%20It%20was%20related%20to%20a%20Service%20account.%20I've%20replaced%20only%20the%20accounts%20from%20SCCM%20and%20WSUS%20proxy%20settings.%3C%2FLINGO-BODY%3E
Highlighted
Shieldwolf_0007
New Contributor

Hello,

 

 

Do you guys have any idea why our SCCM could not sync with WSUS and Deploy Software Updates?

Here's the log I found from our SCCM and one of our PC. Your response will be greatly appreciated.

 

 

WCM LOG

 

System.Security.SecurityException: Request for principal permission failed.~~ at Microsoft.UpdateServices.Administration.AdminProxy.CreateUpdateServer(Object[] args)~~ at Microsoft.SystemsManagementServer.WSUS.WSUSServer.ConnectToWSUSServer(String ServerName, Boolean UseSSL, Int32 PortNumber)~~The Zone of the assembly that failed was:~~MyComputer SMS_WSUS_CONFIGURATION_MANAGER 24/05/2019 12:10:08 AM 7792 (0x1E70)

Remote configuration failed on WSUS Server. SMS_WSUS_CONFIGURATION_MANAGER 24/05/2019 12:10:08 AM 7792 (0x1E70)

 

WSYNCMGR LOG

 

Sync failed: WSUS server not configured. Please refer to WCM.log for configuration error details.. Source: CWSyncMgr::DoSync SMS_WSUS_SYNC_MANAGER 24/05/2019 11:50:05 AM 7832 (0x1E98)

STATMSG: ID=6703 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=SCCMSVR.Domain.com SITE=ATC PID=3668 TID=7832 GMTDATE=Fri May 24 03:50:05.331 2019 ISTR0="CWSyncMgr::DoSync" ISTR1="WSUS server not configured. Please refer to WCM.log for configuration error details." ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_WSUS_SYNC_MANAGER 24/05/2019 11:50:05 AM 7832 (0x1E98)

 

 

 

UPDATESHANDLER LOG

 

CUpdatesAgent::FinalConstruct entered UpdatesHandler 24/05/2019 2:23:36 PM 10564 (0x2944)
Initiating updates scan for checking applicability. UpdatesHandler 24/05/2019 2:23:36 PM 9088 (0x2380)
Successfully initiated scan. UpdatesHandler 24/05/2019 2:23:37 PM 9088 (0x2380)
Updates scan completion received, result = 0x0. UpdatesHandler 24/05/2019 2:24:01 PM 10564 (0x2944)
Method (Discover) called from SDM. UpdatesHandler 24/05/2019 2:24:01 PM 10796 (0x2A2C)
Starting job with id = {DCB79C1C-A1C5-4593-A175-044A5F35C3C0} UpdatesHandler 24/05/2019 2:24:01 PM 10796 (0x2A2C)
Initiating Scan. Forced = (2) UpdatesHandler 24/05/2019 2:24:02 PM 10796 (0x2A2C)
Successfully initiated scan for job ({DCB79C1C-A1C5-4593-A175-044A5F35C3C0}). UpdatesHandler 24/05/2019 2:24:02 PM 10796 (0x2A2C)
Scan completion received for job ({DCB79C1C-A1C5-4593-A175-044A5F35C3C0}). UpdatesHandler 24/05/2019 2:24:11 PM 10564 (0x2944)
Evaluating status of the updates for the job ({DCB79C1C-A1C5-4593-A175-044A5F35C3C0}). UpdatesHandler 24/05/2019 2:24:11 PM 10564 (0x2944)
Successfully sent job ({DCB79C1C-A1C5-4593-A175-044A5F35C3C0}) success completion to the SdmAgent UpdatesHandler 24/05/2019 2:24:11 PM 9088 (0x2380)
CompleteJob received from SDM. UpdatesHandler 24/05/2019 2:24:11 PM 10564 (0x2944)
Complete - Job ({DCB79C1C-A1C5-4593-A175-044A5F35C3C0}) Cleanup. UpdatesHandler 24/05/2019 2:24:11 PM 10564 (0x2944)
CompleteJob - Job ({DCB79C1C-A1C5-4593-A175-044A5F35C3C0}) removed from job manager list. UpdatesHandler 24/05/2019 2:24:11 PM 10564 (0x2944)

 

 

 

SCANAGENT LOG

*****ScanByUpdates request received with ForceReScan=2, ScanOptions=0x00000002, WSUSLocationTimeout = 604800 ScanAgent 24/05/2019 2:24:02 PM 10796 (0x2A2C)
- - -Evaluating Update Status... ScanAgent 24/05/2019 2:24:02 PM 10796 (0x2A2C)
Found CategoryID of :e6cf1350-c01b-414d-a61f-263d14d133b4 for Update:c2ea7fb3-7352-4b8b-9e54-4e06802ac7cc ScanAgent 24/05/2019 2:24:02 PM 10796 (0x2A2C)
CScanAgent::ScanByUpdates - Found UpdateClassification e6cf1350-c01b-414d-a61f-263d14d133b4 for Update:c2ea7fb3-7352-4b8b-9e54-4e06802ac7cc ScanAgent 24/05/2019 2:24:02 PM 10796 (0x2A2C)
Found CategoryID of :e6cf1350-c01b-414d-a61f-263d14d133b4 for Update:a970acb7-1129-4e94-9d1a-2e6045b0afc4 ScanAgent 24/05/2019 2:24:02 PM 10796 (0x2A2C)
CScanAgent::ScanByUpdates - Found UpdateClassification e6cf1350-c01b-414d-a61f-263d14d133b4 for Update:a970acb7-1129-4e94-9d1a-2e6045b0afc4 ScanAgent 24/05/2019 2:24:02 PM 10796 (0x2A2C)
Sources are current and valid. TTLs are also valid. ScanAgent 24/05/2019 2:24:02 PM 10796 (0x2A2C)
Sources are Valid, so converting to Offline Scan. ScanAgent 24/05/2019 2:24:02 PM 10796 (0x2A2C)
ScanJob({8389E6DE-91A8-4D67-9045-083EC041548B}): CScanJob::Scan- Requesting Offline Scan with last known location. ScanAgent 24/05/2019 2:24:02 PM 10796 (0x2A2C)
Sources are current and valid. TTLs are also valid. ScanAgent 24/05/2019 2:24:02 PM 10564 (0x2944)
ScanJob({8389E6DE-91A8-4D67-9045-083EC041548B}): CScanJob::Execute- Requesting scan with CategoryIDs=E6CF1350-C01B-414D-A61F-263D14D133B4,E6CF1350-C01B-414D-A61F-263D14D133B4 ScanAgent 24/05/2019 2:24:02 PM 10564 (0x2944)
ScanJob({8389E6DE-91A8-4D67-9045-083EC041548B}): Scan Succeeded, setting flag that performed scan was catscan ScanAgent 24/05/2019 2:24:11 PM 9088 (0x2380)
ScanJob({8389E6DE-91A8-4D67-9045-083EC041548B}): CScanJob::OnScanComplete - Scan completed successfully, ScanType=2 ScanAgent 24/05/2019 2:24:11 PM 9088 (0x2380)
ScanJob({8389E6DE-91A8-4D67-9045-083EC041548B}): CScanJobManager::OnScanComplete -ScanJob is completed. ScanAgent 24/05/2019 2:24:11 PM 9088 (0x2380)
ScanJob({8389E6DE-91A8-4D67-9045-083EC041548B}): CScanJobManager::OnScanComplete - Reporting Scan request complete to clients... ScanAgent 24/05/2019 2:24:11 PM 9088 (0x2380)
- - -Evaluating Update Status... ScanAgent 24/05/2019 2:24:11 PM 10564 (0x2944)
- - Calling back to client on Scan request complete... ScanAgent 24/05/2019 2:24:11 PM 10564 (0x2944)

 

 

WUAHandler LOG

 

OnSearchComplete - Failed to end search job. Error = 0x80244010. WUAHandler 24/05/2019 8:11:00 AM 1364 (0x0554)
Scan failed with error = 0x80244010. WUAHandler 24/05/2019 8:11:00 AM 1364 (0x0554)
Its a WSUS Update Source type ({123D2DFE-5D16-49B4-A734-B7298CF3DC91}), adding it. WUAHandler 24/05/2019 8:41:00 AM 984 (0x03D8)
OS Version is 10.0.17134 WUAHandler 24/05/2019 8:41:00 AM 6588 (0x19BC)

3 Replies

@Shieldwolf_0007 

From your wcm.log: "Remote configuration failed on WSUS Server."

You've either misconfigured your SUP, something like using the incorrect port(s), or connectivity between your site server and SUP is blocked or not allowed.

 

Can you connect from the site server to the WSUS instance on the site system hosting the SUP using the WSUS Admin console?

@Jason Sandys Thank you very much for replying. I'll try your suggestions.

 

Just to give additional information, last 3-4mons, I was able to download software updates from SCCM but couldn't deploy updates. Our client decided to disable SCCM Domain Admin account and replace it with Service Account. I'm not sure if this is related to the issue. For the ports, we are using 8530 and 8531. I've disabled the firewall also from WSUS and SCCM Server.

Solution
The issue is now solved. It was related to a Service account. I've replaced only the accounts from SCCM and WSUS proxy settings.