KK20 Posted February 22, 2016 Posted February 22, 2016 This is about as random as it gets and I'm stumped. HDD died in a machine, not a major issue. Swapped the HDD and set it to reimage - same as I do for other machines. After imaging we log into the machine and check it over making sure it works; normally there are no issues. However, this one machine refuses to work in WSUS. reportingeventslog gives "Windows Update Client failed to detect with error 0x80244016." which is normally a "clients cannot see the WSUS server" or "Windows update is out of date and cannot update with WSUS version". The second one shouldn't apply as this is a fairly up to date golden image. Checking windowsupdatelog I get this nugget: 2016-02-22 08:10:22:417 968 ec8 Misc =========== Logging initialized (build: 7.6.7601.19116, tz: -0000) =========== 2016-02-22 08:10:22:417 968 ec8 Misc = Process: C:\Windows\system32\svchost.exe 2016-02-22 08:10:22:417 968 ec8 Misc = Module: c:\windows\system32\wuaueng.dll 2016-02-22 08:10:22:417 968 ec8 Service ************* 2016-02-22 08:10:22:417 968 ec8 Service ** START ** Service: Service startup 2016-02-22 08:10:22:417 968 ec8 Service ********* 2016-02-22 08:10:22:495 968 ec8 Agent * WU client version 7.6.7601.19116 2016-02-22 08:10:22:495 968 ec8 Agent * Base directory: C:\Windows\SoftwareDistribution 2016-02-22 08:10:22:495 968 ec8 Agent * Access type: No proxy 2016-02-22 08:10:22:495 968 ec8 Agent * Network state: Connected 2016-02-22 08:11:07:886 968 ec8 Report CWERReporter::Init succeeded 2016-02-22 08:11:07:886 968 ec8 Agent *********** Agent: Initializing Windows Update Agent *********** 2016-02-22 08:11:07:886 968 ec8 Agent * Prerequisite roots succeeded. 2016-02-22 08:11:07:886 968 ec8 Agent *********** Agent: Initializing global settings cache *********** 2016-02-22 08:11:07:886 968 ec8 Agent * WSUS server: http://NEP_UP03:8530 2016-02-22 08:11:07:886 968 ec8 Agent * WSUS status server: http://NEP_UP03:8530 2016-02-22 08:11:07:886 968 ec8 Agent * Target group: C5Updates 2016-02-22 08:11:07:886 968 ec8 Agent * Windows Update access disabled: No 2016-02-22 08:11:07:886 968 ec8 DnldMgr Download manager restoring 0 downloads 2016-02-22 08:11:07:901 968 ec8 AU ########### AU: Initializing Automatic Updates ########### 2016-02-22 08:11:07:901 968 ec8 AU AU setting next detection timeout to 2016-02-22 08:11:07 2016-02-22 08:11:07:901 968 ec8 AU # WSUS server: http://NEP_UP03:8530 2016-02-22 08:11:07:901 968 ec8 AU # Detection frequency: 21 2016-02-22 08:11:07:901 968 ec8 AU # Target group: C5Updates 2016-02-22 08:11:07:901 968 ec8 AU # Approval type: Scheduled (Policy) 2016-02-22 08:11:07:901 968 ec8 AU # Scheduled install day/time: Every day at 16:00 2016-02-22 08:11:07:901 968 ec8 AU # Auto-install minor updates: No (Policy) 2016-02-22 08:11:07:901 968 ec8 AU # Will interact with non-admins (Non-admins are elevated (User preference)) 2016-02-22 08:11:07:901 968 ec8 AU Setting AU scheduled install time to 2016-02-22 16:00:00 2016-02-22 08:11:07:995 968 ec8 Report *********** Report: Initializing static reporting data *********** 2016-02-22 08:11:07:995 968 ec8 Report * OS Version = 6.1.7601.1.0.65792 2016-02-22 08:11:07:995 968 ec8 Report * OS Product Type = 0x00000030 2016-02-22 08:11:08:011 968 ec8 Report * Computer Brand = Gigabyte Technology Co., Ltd. 2016-02-22 08:11:08:011 968 ec8 Report * Computer Model = G41MT-S2P 2016-02-22 08:11:08:011 968 ec8 Report * Bios Revision = F1 2016-02-22 08:11:08:011 968 ec8 Report * Bios Name = Award Modular BIOS v6.00PG 2016-02-22 08:11:08:011 968 ec8 Report * Bios Release Date = 2010-12-31T00:00:00 2016-02-22 08:11:08:011 968 ec8 Report * Locale ID = 2057 2016-02-22 08:11:08:105 968 ec8 AU Successfully wrote event for AU health state:0 2016-02-22 08:11:08:105 968 ec8 AU Initializing featured updates 2016-02-22 08:11:08:105 968 ec8 AU Found 0 cached featured updates 2016-02-22 08:11:08:105 968 ec8 AU Successfully wrote event for AU health state:0 2016-02-22 08:11:08:105 968 ec8 AU Successfully wrote event for AU health state:0 2016-02-22 08:11:08:105 968 ec8 AU AU finished delayed initialization 2016-02-22 08:11:08:105 968 ec8 AU ############# 2016-02-22 08:11:08:105 968 ec8 AU ## START ## AU: Search for updates 2016-02-22 08:11:08:105 968 ec8 AU ######### 2016-02-22 08:11:08:105 968 ec8 AU <<## SUBMITTED ## AU: Search for updates [CallId = {E6F2416D-8BE5-425B-B63D-2D387E8C3DD6}] 2016-02-22 08:11:08:168 968 ff8 Agent ************* 2016-02-22 08:11:08:168 968 ff8 Agent ** START ** Agent: Finding updates [CallerId = AutomaticUpdates] 2016-02-22 08:11:08:183 968 ff8 Agent ********* 2016-02-22 08:11:08:183 968 ff8 Agent * Online = Yes; Ignore download priority = No 2016-02-22 08:11:08:183 968 ff8 Agent * Criteria = "IsInstalled=0 and DeploymentAction='Installation' or IsPresent=1 and DeploymentAction='Uninstallation' or IsInstalled=1 and DeploymentAction='Installation' and RebootRequired=1 or IsInstalled=0 and DeploymentAction='Uninstallation' and RebootRequired=1" 2016-02-22 08:11:08:183 968 ff8 Agent * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed 2016-02-22 08:11:08:183 968 ff8 Agent * Search Scope = {Machine} 2016-02-22 08:11:08:183 968 ff8 Setup Checking for agent SelfUpdate 2016-02-22 08:11:08:183 968 ff8 Setup Client version: Core: 7.6.7601.19116 Aux: 7.6.7601.19116 2016-02-22 08:11:08:183 968 ff8 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab with dwProvFlags 0x00000080: 2016-02-22 08:11:08:215 968 ff8 Misc Microsoft signed: NA 2016-02-22 08:11:08:230 968 ff8 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\TMPE7EE.tmp with dwProvFlags 0x00000080: 2016-02-22 08:11:08:246 968 ff8 Misc Microsoft signed: NA 2016-02-22 08:11:08:246 968 ff8 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab with dwProvFlags 0x00000080: 2016-02-22 08:11:08:246 968 ff8 Misc Microsoft signed: NA 2016-02-22 08:11:08:261 968 ff8 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab with dwProvFlags 0x00000080: 2016-02-22 08:11:08:261 968 ff8 Misc Microsoft signed: NA 2016-02-22 08:11:08:293 968 ff8 Setup Determining whether a new setup handler needs to be downloaded 2016-02-22 08:11:08:293 968 ff8 Setup SelfUpdate handler is not found. It will be downloaded 2016-02-22 08:11:08:293 968 ff8 Setup Evaluating applicability of setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.320" 2016-02-22 08:11:09:107 968 ff8 Setup Setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.320" is already installed. 2016-02-22 08:11:09:107 968 ff8 Setup Evaluating applicability of setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.320" 2016-02-22 08:11:09:138 968 ff8 Setup Setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.320" is already installed. 2016-02-22 08:11:09:138 968 ff8 Setup Evaluating applicability of setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.320" 2016-02-22 08:11:09:170 968 ff8 Setup Setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.320" is already installed. 2016-02-22 08:11:09:170 968 ff8 Setup SelfUpdate check completed. SelfUpdate is NOT required. 2016-02-22 08:11:09:624 968 ff8 PT +++++++++++ PT: Synchronizing server updates +++++++++++ 2016-02-22 08:11:09:624 968 ff8 PT + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://NEP_UP03:8530/ClientWebService/client.asmx 2016-02-22 08:11:09:639 968 ff8 PT WARNING: Cached cookie has expired or new PID is available 2016-02-22 08:11:09:639 968 ff8 PT Initializing simple targeting cookie, clientId = 4ab3d235-f41a-41da-9ecd-c046763765aa, target group = C5Updates, DNS name = unit7110.austinfriars.cumbria.sch.uk.local 2016-02-22 08:11:09:639 968 ff8 PT Server URL = http://NEP_UP03:8530/SimpleAuthWebService/SimpleAuth.asmx 2016-02-22 08:11:32:186 968 ff8 PT WARNING: SyncUpdates failure, error = 0x80244016, soap client error = 10, soap error code = 0, HTTP status code = 400 2016-02-22 08:11:32:186 968 ff8 PT WARNING: PTError: 0x80244016 2016-02-22 08:11:32:186 968 ff8 PT WARNING: SyncUpdates_WithRecovery failed.: 0x80244016 2016-02-22 08:11:32:186 968 ff8 PT WARNING: Sync of Updates: 0x80244016 2016-02-22 08:11:32:186 968 ff8 PT WARNING: SyncServerUpdatesInternal failed: 0x80244016 2016-02-22 08:11:32:186 968 ff8 Agent * WARNING: Failed to synchronize, error = 0x80244016 2016-02-22 08:11:32:186 968 ff8 Agent * WARNING: Exit code = 0x80244016 2016-02-22 08:11:32:186 968 ff8 Agent ********* 2016-02-22 08:11:32:186 968 ff8 Agent ** END ** Agent: Finding updates [CallerId = AutomaticUpdates] 2016-02-22 08:11:32:186 968 ff8 Agent ************* 2016-02-22 08:11:32:186 968 ff8 Agent WARNING: WU client failed Searching for update with error 0x80244016 2016-02-22 08:11:32:201 968 c9c AU >>## RESUMED ## AU: Search for updates [CallId = {E6F2416D-8BE5-425B-B63D-2D387E8C3DD6}] 2016-02-22 08:11:32:201 968 c9c AU # WARNING: Search callback failed, result = 0x80244016 2016-02-22 08:11:32:201 968 c9c AU # WARNING: Failed to find updates with error code 80244016 2016-02-22 08:11:32:201 968 c9c AU ######### 2016-02-22 08:11:32:201 968 c9c AU ## END ## AU: Search for updates [CallId = {E6F2416D-8BE5-425B-B63D-2D387E8C3DD6}] 2016-02-22 08:11:32:201 968 c9c AU ############# 2016-02-22 08:11:32:217 968 c9c AU Successfully wrote event for AU health state:0 2016-02-22 08:11:32:217 968 c9c AU AU setting next detection timeout to 2016-02-22 13:11:32 2016-02-22 08:11:32:217 968 c9c AU Setting AU scheduled install time to 2016-02-22 16:00:00 2016-02-22 08:11:32:217 968 c9c AU Successfully wrote event for AU health state:0 2016-02-22 08:11:32:217 968 c9c AU Successfully wrote event for AU health state:0 2016-02-22 08:11:37:212 968 ff8 Report REPORT EVENT: {DAD15CF9-9BF2-4C94-B940-59AB089082F2} 2016-02-22 08:11:32:186-0000 1 148 101 {00000000-0000-0000-0000-000000000000} 0 80244016 AutomaticUpdates Failure Software Synchronization Windows Update Client failed to detect with error 0x80244016. 2016-02-22 08:11:37:243 968 ff8 Report CWERReporter::HandleEvents - WER report upload completed with status 0x8 2016-02-22 08:11:37:243 968 ff8 Report WER Report sent: 7.6.7601.19116 0x80244016(0) 0000000-0000-0000-0000-000000000000 Scan 0 1 AutomaticUpdates {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} 0 so error "WARNING: SyncUpdates failure, error = 0x80244016, soap client error = 10, soap error code = 0, HTTP status code = 400". Getting somewhere! Odd though as this also says it cannot connect. No problem I think, it might be a corrupt entry for this PC in the WSUS database, i'll delete the computer from WSUS, shutdown the update and BITS on the client, delete softwaredistribution and reset the client WSUS information; I use this command on the client: (deleting the softwaredistribution manually) net stop wuauserv REG DELETE "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate" /v AccountDomainSid /f REG DELETE "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate" /v PingID /f REG DELETE "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate" /v SusClientId /f net start wuauserv wuauclt /resetauthorization /detectnow (cutting post to 2 parts due to size)
KK20 Posted February 22, 2016 Author Posted February 22, 2016 now I *DO* expect 0x80244010 errors after deleting softwaredistribution so I usually manually run updates until they go away - there are about 7000 updates and I know there is a limit as to how much it can pull back in one go - usually 2 or 3 manual updates gets rid of the 0x80244010 errors whilst softwaredistribution fills up. Sounds good? WSUS picks up the computer name again, I move it to the correct updates group and run windows update manually. It churns away, software distribution fills up to about a gigabyte aaaaaand the same error as before appears "WARNING: SyncUpdates failure, error = 0x80244016, soap client error = 10, soap error code = 0, HTTP status code = 400" no updates actually install. Now I think. Stuff it, i'll reimage - something must have gone wrong. Remove PC from WSUS, remove from AD and set to reimaging. Cutting a long story short, SAME THING happens again. I begin to get worried, have I messed up my golden image doing an update? do I have backups before the last update? Don't panic, try reimaging the PC next to it (identical model, BIOS, bought at same time etc), so I do (after deleting the PC from AD and WSUS for a fair comparison). Guess what happens to that one when I look in the windowsupdate.log : 2016-02-22 08:27:01:989 112 af4 Misc =========== Logging initialized (build: 7.6.7600.320, tz: -0000) =========== 2016-02-22 08:27:01:989 112 af4 Misc = Process: C:\Windows\system32\svchost.exe 2016-02-22 08:27:01:989 112 af4 Misc = Module: c:\windows\system32\wuaueng.dll 2016-02-22 08:27:01:989 112 af4 Service ************* 2016-02-22 08:27:01:989 112 af4 Service ** START ** Service: Service startup 2016-02-22 08:27:01:989 112 af4 Service ********* 2016-02-22 08:27:02:067 112 af4 Agent * WU client version 7.6.7600.320 2016-02-22 08:27:02:067 112 af4 Agent * Base directory: C:\Windows\SoftwareDistribution 2016-02-22 08:27:02:067 112 af4 Agent * Access type: No proxy 2016-02-22 08:27:02:083 112 af4 Agent * Network state: Connected 2016-02-22 08:27:47:924 112 af4 Report CWERReporter::Init succeeded 2016-02-22 08:27:47:924 112 af4 Agent *********** Agent: Initializing Windows Update Agent *********** 2016-02-22 08:27:47:924 112 af4 Agent * Prerequisite roots succeeded. 2016-02-22 08:27:47:924 112 af4 Agent *********** Agent: Initializing global settings cache *********** 2016-02-22 08:27:47:924 112 af4 Agent * WSUS server: http://NEP_UP03:8530 2016-02-22 08:27:47:924 112 af4 Agent * WSUS status server: http://NEP_UP03:8530 2016-02-22 08:27:47:924 112 af4 Agent * Target group: C5Updates 2016-02-22 08:27:47:924 112 af4 Agent * Windows Update access disabled: No 2016-02-22 08:27:47:924 112 af4 DnldMgr Download manager restoring 0 downloads 2016-02-22 08:27:47:940 112 af4 AU ########### AU: Initializing Automatic Updates ########### 2016-02-22 08:27:47:940 112 af4 AU AU setting next detection timeout to 2016-02-22 08:27:47 2016-02-22 08:27:47:940 112 af4 AU # WSUS server: http://NEP_UP03:8530 2016-02-22 08:27:47:940 112 af4 AU # Detection frequency: 21 2016-02-22 08:27:47:940 112 af4 AU # Target group: C5Updates 2016-02-22 08:27:47:940 112 af4 AU # Approval type: Scheduled (Policy) 2016-02-22 08:27:47:940 112 af4 AU # Scheduled install day/time: Every day at 16:00 2016-02-22 08:27:47:940 112 af4 AU # Auto-install minor updates: No (Policy) 2016-02-22 08:27:47:940 112 af4 AU # Will interact with non-admins (Non-admins are elevated (User preference)) 2016-02-22 08:27:47:940 112 af4 AU Setting AU scheduled install time to 2016-02-22 16:00:00 2016-02-22 08:27:48:034 112 af4 Report *********** Report: Initializing static reporting data *********** 2016-02-22 08:27:48:034 112 af4 Report * OS Version = 6.1.7601.1.0.65792 2016-02-22 08:27:48:034 112 af4 Report * OS Product Type = 0x00000030 2016-02-22 08:27:48:049 112 af4 Report * Computer Brand = Gigabyte Technology Co., Ltd. 2016-02-22 08:27:48:049 112 af4 Report * Computer Model = G41MT-S2P 2016-02-22 08:27:48:049 112 af4 Report * Bios Revision = F1 2016-02-22 08:27:48:049 112 af4 Report * Bios Name = Award Modular BIOS v6.00PG 2016-02-22 08:27:48:049 112 af4 Report * Bios Release Date = 2010-12-31T00:00:00 2016-02-22 08:27:48:049 112 af4 Report * Locale ID = 2057 2016-02-22 08:27:48:049 112 af4 AU Successfully wrote event for AU health state:0 2016-02-22 08:27:48:049 112 af4 AU Initializing featured updates 2016-02-22 08:27:48:049 112 af4 AU Found 0 cached featured updates 2016-02-22 08:27:48:049 112 af4 AU Successfully wrote event for AU health state:0 2016-02-22 08:27:48:049 112 af4 AU Successfully wrote event for AU health state:0 2016-02-22 08:27:48:049 112 af4 AU AU finished delayed initialization 2016-02-22 08:27:48:049 112 af4 AU ############# 2016-02-22 08:27:48:049 112 af4 AU ## START ## AU: Search for updates 2016-02-22 08:27:48:049 112 af4 AU ######### 2016-02-22 08:27:48:065 112 af4 AU <<## SUBMITTED ## AU: Search for updates [CallId = {B1260DD0-7CBD-40FC-976E-31E3D5BE0EB2}] 2016-02-22 08:27:48:190 112 d08 Agent ************* 2016-02-22 08:27:48:190 112 d08 Agent ** START ** Agent: Finding updates [CallerId = AutomaticUpdates] 2016-02-22 08:27:48:190 112 d08 Agent ********* 2016-02-22 08:27:48:190 112 d08 Agent * Online = Yes; Ignore download priority = No 2016-02-22 08:27:48:190 112 d08 Agent * Criteria = "IsInstalled=0 and DeploymentAction='Installation' or IsPresent=1 and DeploymentAction='Uninstallation' or IsInstalled=1 and DeploymentAction='Installation' and RebootRequired=1 or IsInstalled=0 and DeploymentAction='Uninstallation' and RebootRequired=1" 2016-02-22 08:27:48:190 112 d08 Agent * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed 2016-02-22 08:27:48:190 112 d08 Agent * Search Scope = {Machine} - - - Updated - - - 2016-02-22 08:27:48:190 112 d08 Setup Checking for agent SelfUpdate 2016-02-22 08:27:48:190 112 d08 Setup Client version: Core: 7.6.7600.320 Aux: 7.6.7600.320 2016-02-22 08:27:48:190 112 d08 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab with dwProvFlags 0x00000080: 2016-02-22 08:28:28:344 112 d08 Misc Microsoft signed: NA 2016-02-22 08:28:28:344 112 d08 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\TMPBC5B.tmp with dwProvFlags 0x00000080: 2016-02-22 08:28:58:421 112 d08 Misc Microsoft signed: NA 2016-02-22 08:28:58:421 112 d08 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab with dwProvFlags 0x00000080: 2016-02-22 08:29:23:497 112 d08 Misc Microsoft signed: NA 2016-02-22 08:29:23:513 112 d08 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab with dwProvFlags 0x00000080: 2016-02-22 08:29:23:513 112 d08 Misc Microsoft signed: NA 2016-02-22 08:29:23:544 112 d08 Setup Determining whether a new setup handler needs to be downloaded 2016-02-22 08:29:23:560 112 d08 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\Handler\WuSetupV.exe with dwProvFlags 0x00000080: 2016-02-22 08:29:23:560 112 d08 Misc Microsoft signed: NA 2016-02-22 08:29:23:560 112 d08 Setup SelfUpdate handler update NOT required: Current version: 7.6.7600.320, required version: 7.6.7600.320 2016-02-22 08:29:23:560 112 d08 Setup Evaluating applicability of setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.320" 2016-02-22 08:29:24:294 112 d08 Setup Setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.320" is already installed. 2016-02-22 08:29:24:294 112 d08 Setup Evaluating applicability of setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.320" 2016-02-22 08:29:24:310 112 d08 Setup Setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.320" is already installed. 2016-02-22 08:29:24:310 112 d08 Setup Evaluating applicability of setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.320" 2016-02-22 08:29:24:341 112 d08 Setup Setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.320" is already installed. 2016-02-22 08:29:24:341 112 d08 Setup SelfUpdate check completed. SelfUpdate is NOT required. 2016-02-22 08:29:42:528 112 d08 PT +++++++++++ PT: Synchronizing server updates +++++++++++ 2016-02-22 08:29:42:528 112 d08 PT + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://NEP_UP03:8530/ClientWebService/client.asmx 2016-02-22 08:29:42:653 112 d08 PT WARNING: Cached cookie has expired or new PID is available 2016-02-22 08:29:42:653 112 d08 PT Initializing simple targeting cookie, clientId = b7a9ab59-8e5d-4f92-9a08-18ab350dbbb1, target group = C5Updates, DNS name = unit7114.austinfriars.cumbria.sch.uk.local 2016-02-22 08:29:42:653 112 d08 PT Server URL = http://NEP_UP03:8530/SimpleAuthWebService/SimpleAuth.asmx 2016-02-22 08:32:56:737 112 d08 PT +++++++++++ PT: Synchronizing extended update info +++++++++++ 2016-02-22 08:32:56:737 112 d08 PT + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://NEP_UP03:8530/ClientWebService/client.asmx 2016-02-22 08:33:37:991 112 d08 Agent * Found 0 updates and 75 categories in search; evaluated appl. rules of 4406 out of 7525 deployed entities 2016-02-22 08:33:38:022 112 d08 Agent ********* 2016-02-22 08:33:38:022 112 d08 Agent ** END ** Agent: Finding updates [CallerId = AutomaticUpdates] 2016-02-22 08:33:38:022 112 d08 Agent ************* 2016-02-22 08:33:38:381 112 fe0 AU >>## RESUMED ## AU: Search for updates [CallId = {B1260DD0-7CBD-40FC-976E-31E3D5BE0EB2}] 2016-02-22 08:33:38:381 112 fe0 AU # 0 updates detected 2016-02-22 08:33:38:381 112 fe0 AU ######### 2016-02-22 08:33:38:381 112 fe0 AU ## END ## AU: Search for updates [CallId = {B1260DD0-7CBD-40FC-976E-31E3D5BE0EB2}] 2016-02-22 08:33:38:381 112 fe0 AU ############# 2016-02-22 08:33:38:459 112 fe0 AU Successfully wrote event for AU health state:0 2016-02-22 08:33:38:459 112 fe0 AU Featured notifications is disabled. 2016-02-22 08:33:38:459 112 fe0 AU AU setting next detection timeout to 2016-02-23 04:54:11 2016-02-22 08:33:38:475 112 fe0 AU Setting AU scheduled install time to 2016-02-22 16:00:00 2016-02-22 08:33:38:475 112 fe0 AU Successfully wrote event for AU health state:0 2016-02-22 08:33:38:475 112 fe0 AU Successfully wrote event for AU health state:0 2016-02-22 08:33:38:522 112 d08 Report CWERReporter finishing event handling. (00000000) 2016-02-22 08:33:43:033 112 d08 Report REPORT EVENT: {660D9DA0-4799-4264-B810-475564E4406B} 2016-02-22 08:33:38:007-0000 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software Synchronization Windows Update Client successfully detected 0 updates. 2016-02-22 08:33:43:033 112 d08 Report REPORT EVENT: {FEF4B900-D293-4BF5-9C5A-0FD6B9A7F143} 2016-02-22 08:33:38:022-0000 1 156 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Pre-Deployment Check Reporting client status. 2016-02-22 08:33:43:048 112 d08 Report CWERReporter finishing event handling. (00000000) 2016-02-22 08:36:27:228 112 d08 Report Uploading 2 events using cached cookie, reporting URL = http://NEP_UP03:8530/ReportingWebService/ReportingWebService.asmx 2016-02-22 08:36:27:244 112 d08 Report Reporter successfully uploaded 2 events. "but that looks fine!" I hear you cry! Yes it does. And WSUS works with it, the PC reports back to WSUS and WSUS sees it, as do 10 other logs I randomly check throughout the building. It is just ONE machine that utterly refuses to work with WSUS. Yes, the golden image is generalised; I once remember screwing WSUS up in XP by them all having the same ID on cloning, I wont make that mistake again - but at least in XP you could fix that with a batch file rather than redoing your golden image (and THEN learning all about rearms before making your golden image again swearing not to make THAT mistake again). The client can ping the WSUS server (NetBIOS name), it can connect to \\NEP_UP03 and see a shared folder happily. I can even open up a browser and go to http://NEP_UP03:8530/SimpleAuthWebService/SimpleAuth.asmx and get the simpleauth screen. I have no more ideas, short of putting a different network card (so it has another mac address) and changing the PC name so that it appears to all and sundry as a new PC I have no ideas left. I must stress that as far as I know, this is the ONLY PC that doesn't work with WSUS (WSUS is reporting the correct amount of PCs and WSUS lists this PC as "not reported" although there IS 1gb of data in the software distribution folder and I did delete it). I'm thinking of scrapping the PC as i'm sure I can cannibalise the parts for a non working one somewhere....
Oaktech Posted February 22, 2016 Posted February 22, 2016 Last time I had a sticky issue like this I just updated once from windows update rather than WSUS and after that WSUS worked fine... Worth a try?
KK20 Posted February 22, 2016 Author Posted February 22, 2016 (edited) forgot to mention that I tried that. I couldn't get windows (online) update to work when I deleted softwareupdate though, I left it overnight and it was still "updating" (i.e. getting the initial list of what it needs), I left if for a good half day afterwards before giving up caring. However, if I ran "online" update after imaging then it would update but not do anything with WSUS; always the same 0x80244016 soap 400 error. Whilst we DO have a proxy on site this is irrelevant for local web traffic (and has been this way before these PCs were first built years ago) so im happy for WSUS traffic to go DIRECT. I am leaning towards some sort of corruption in the WSUS database as there is nothing on a client that should stop WSUS working (on a proven working fresh image). I think i'll put a different NIC in there (for the MAC and system ID hash), delete it from AD and rejoin under a different name - if only to help my sanity. The irony is, I don't actually know if this machine was working with WSUS *before* I changed the HDD, it could have always had an issue (I doubt it as you tend to notice 0% entries in WSUS). I put this in W2k12 as WSUS is installed on W2K12, no idea if it is the client or server though.... Edited February 22, 2016 by KK20
KK20 Posted March 9, 2016 Author Posted March 9, 2016 Scrapped the PC. Yup, I couldn't get this PC to work with WSUS, no idea why. A same-model-pc-from-spares was reinstated using the SAME image (I swapped MAC addresses in FOG and redeployed, so the same PC name, same image etc) and the replacement worked. Go figure. The PSU found a new home in another PC, the RAM & CPU has gone into the spare pile and i've stickered up the motherboard as a "only use in emergency"
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now