Wsus last status report not updating sccm

Our setup executed the check at 9am one morning each week, but people who shutdown their pc and were late that day to turn it back on did not have their pcs checked for updates.Is it possible that these workstations were not turned on? One of them is our DC, so that thing is on 99% of the time and it hasn't reported in 18 days.The timeout period elapsed prior to completion of the operation or the server is not responding.look here: ==== also, on a client try restarting the Windows Update Service and execute: wuauclt /resetauthorization /detectnow wait 15-20min and check the report then..Also, post back both key contents (one from a working box and another from a nonworking box) to try to diagnose the issue.Watch Guard DNSWatch reduces malware infections by detecting and blocking malicious DNS requests, improving your ability to protect employees from phishing attacks. is what I'm getting in the log 2007-03-01 1364 b50 AU ############# 2007-03-01 1364 b50 AU ## START ## AU: Search for updates 2007-03-01 1364 b50 AU ######### 2007-03-01 1364 b50 AU dll: target version = 5.8.0.2469, required version = 5.8.0.2469 2007-03-01 1364 1c64 Setup * Is Update Required = No 2007-03-01 1364 1c64 Dta Stor FATAL: Failed to initialize datastore, error = 0x C80003F3 2007-03-01 1364 1c64 Dta Stor FATAL: Failed to initialize datastore, error = 0x C80003F3 2007-03-01 1364 1c64 Agent * WARNING: Exit code = 0x C80003F3 2007-03-01 1364 1c64 Agent ********* 2007-03-01 1364 1c64 Agent ** END ** Agent: Finding updates [Caller Id = Automatic Updates] 2007-03-01 1364 1c64 Agent ************* 2007-03-01 1364 1c64 Agent WARNING: WU client failed Searching for update with error 0xc80003f3 2007-03-01 1364 1c64 AU ## RESUMED ## AU: Search for updates [Call Id = ] 2007-03-01 1364 1c64 AU # WARNING: Search callback failed, result = 0x C80003F3 2007-03-01 1364 1c64 AU ######### 2007-03-01 1364 1c64 AU ## END ## AU: Search for updates [Call Id = ] 2007-03-01 1364 1c64 AU ############# 2007-03-01 1364 1c64 AU AU setting next detection timeout to 2007-03-01 2007-03-01 1364 1c64 Dta Stor FATAL: Failed to initialize datastore, error = 0x C80003F3 2007-03-01 1364 1c64 AU FATAL: Failed to get session from datastore, error = 0x C80003F3 2007-03-01 1364 1c64 Report REPORT EVENT: 2007-03-01 -0500 1 148 101 0 c80003f3 Automatic Updates Failure Software Synchronization Error: Agent failed detecting with reason: 0xc80003f3 2007-03-01 1364 1c64 Dta Stor FATAL: Failed to initialize datastore, error = 0x C80003F3 2007-03-01 1364 1c64 Report WARNING: Reporter failed to upload events with hr = c80003f3.

==== if this is your problem: The following error message is logged in the log file on client computers: WARNING: Failed to upload events to the server with hr = 80244008 • Microsoft SQL Server time-out error messages are displayed in the administrative console on the WSUS server.

p=208 suggests that clients might need an update manually applied. Digital Signatures on file C:\Windows\Software are not trusted: Error 0x800b0001 It links to If that is the solution , it's unclear to me if the patch should be installed on the WSUS client or the WSUS server. Windows Update-24-10Hi There, I wrote the article on the blog that you linked.

Or even better, that there's a totally different explanation for the behaviour?

Learn more about our newest service included in Total Security Suite today!

That is wierd, I remember there was a similar problem where i work, it could possibly be because the computers are not on when it is scheduled to check.

Leave a Reply