Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1119
  • Last Modified:

WSUS New Computers added show up as "not yet reported" status

I have Microsoft Windows Server Update Services 3.0 running Server 2003.  I just recently took over the administration of this from another IT tech.  We use a reg key as we do not have Active Directory at this company.  All the new clients I add the reg key to show up under the update service console as "not yet reported".  Once interesting is they do talk to WSUS because they are showing up on the WSUS server, so they make the connection but thats it, they never get the updates.  Below is the log from a sample client computer.

2008-11-05      12:02:54:062      1336      7f4      AU      Triggering AU detection through DetectNow API
2008-11-05      12:02:54:062      1336      7f4      AU      Triggering Online detection (non-interactive)
2008-11-05      12:02:54:062      1336      6e0      AU      #############
2008-11-05      12:02:54:062      1336      6e0      AU      ## START ##  AU: Search for updates
2008-11-05      12:02:54:062      1336      6e0      AU      #########
2008-11-05      12:02:54:062      1336      6e0      AU      <<## SUBMITTED ## AU: Search for updates [CallId = {393E0E67-B0A4-440F-84D9-D0CE90CDCB56}]
2008-11-05      12:02:54:062      1336      9e4      Agent      *************
2008-11-05      12:02:54:062      1336      9e4      Agent      ** START **  Agent: Finding updates [CallerId = AutomaticUpdates]
2008-11-05      12:02:54:062      1336      9e4      Agent      *********
2008-11-05      12:02:54:062      1336      9e4      Agent        * Online = Yes; Ignore download priority = No
2008-11-05      12:02:54:062      1336      9e4      Agent        * Criteria = "IsHidden=0 and IsInstalled=0 and DeploymentAction='Installation' and IsAssigned=1 or IsHidden=0 and IsPresent=1 and DeploymentAction='Uninstallation' and IsAssigned=1 or IsHidden=0 and IsInstalled=1 and DeploymentAction='Installation' and IsAssigned=1 and RebootRequired=1 or IsHidden=0 and IsInstalled=0 and DeploymentAction='Uninstallation' and IsAssigned=1 and RebootRequired=1"
2008-11-05      12:02:54:062      1336      9e4      Agent        * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}
2008-11-05      12:02:54:078      1336      9e4      Misc      Validating signature for C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default\wuident.cab:
2008-11-05      12:02:54:078      1336      9e4      Misc       Microsoft signed: Yes
2008-11-05      12:03:05:109      1336      9e4      Misc      WARNING: WinHttp: SendRequestToServerForFileInformation failed with 0x80190194
2008-11-05      12:03:05:109      1336      9e4      Misc      WARNING: WinHttp: ShouldFileBeDownloaded failed with 0x80190194
2008-11-05      12:03:05:109      1336      9e4      Misc      WARNING: DownloadFileInternal failed for http://NEMESIS.newsctr.ljworld.com:8530/selfupdate/wuident.cab: error 0x80190194
2008-11-05      12:03:05:109      1336      9e4      Setup      FATAL: IsUpdateRequired failed with error 0x80244019
2008-11-05      12:03:05:109      1336      9e4      Setup      WARNING: SelfUpdate: Default Service: IsUpdateRequired failed: 0x80244019
2008-11-05      12:03:05:109      1336      9e4      Setup      WARNING: SelfUpdate: Default Service: IsUpdateRequired failed, error = 0x80244019
2008-11-05      12:03:05:109      1336      9e4      Agent        * WARNING: Skipping scan, self-update check returned 0x80244019
2008-11-05      12:03:05:140      1336      9e4      Agent        * WARNING: Exit code = 0x80244019
2008-11-05      12:03:05:140      1336      9e4      Agent      *********
2008-11-05      12:03:05:140      1336      9e4      Agent      **  END  **  Agent: Finding updates [CallerId = AutomaticUpdates]
2008-11-05      12:03:05:140      1336      9e4      Agent      *************
2008-11-05      12:03:05:140      1336      9e4      Agent      WARNING: WU client failed Searching for update with error 0x80244019
2008-11-05      12:03:05:140      1336      9f4      AU      >>##  RESUMED  ## AU: Search for updates [CallId = {393E0E67-B0A4-440F-84D9-D0CE90CDCB56}]
2008-11-05      12:03:05:140      1336      9f4      AU        # WARNING: Search callback failed, result = 0x80244019
2008-11-05      12:03:05:140      1336      9f4      AU        # WARNING: Failed to find updates with error code 80244019
2008-11-05      12:03:05:140      1336      9f4      AU      #########
2008-11-05      12:03:05:140      1336      9f4      AU      ##  END  ##  AU: Search for updates [CallId = {393E0E67-B0A4-440F-84D9-D0CE90CDCB56}]
2008-11-05      12:03:05:140      1336      9f4      AU      #############
2008-11-05      12:03:05:140      1336      9f4      AU      AU setting next detection timeout to 2008-11-05 23:03:05
2008-11-05      12:03:05:140      1336      9f4      AU      Setting AU scheduled install time to 2008-11-06 12:00:00
2008-11-05      12:03:10:109      1336      9e4      Report      REPORT EVENT: {09C968E8-3C5E-45F5-9274-9A86CAA0F27C}      2008-11-05 12:03:05:109-0600      1      148      101      {D67661EB-2423-451D-BF5D-13199E37DF28}      0      80244019      SelfUpdate      Failure      Software Synchronization      Windows Update Client failed to detect with error 0x80244019.

I imagine that something with IIS is not setup right.  I do know we use the custom port of 8350.  So basically my question how are the client talking to WSUS but never reporting their status and getting the approved updates?  Thanks!
0
sunflower_it
Asked:
sunflower_it
  • 3
1 Solution
 
biscuit3Commented:
try exporting the reg key from a known good workstation that is communicating with the WSUS server, import it into your new workstations to see if that fixes the problem.
0
 
sunflower_itAuthor Commented:
I checked the registry settings and they are the same.  I guess now I can not say all new computers added report a status of "not yet reported".  I just noticed a computer that I imported the reg key on yesterday is reporting.  But there are around 10 others that are not reporting that I have added recently.  So some are and some are not.  I tried to find difference between these computer but for the most part they are on the same network and similar setups.  Another idea?
0
 
sunflower_itAuthor Commented:
Here is the windows update log from a client that is connecting and pulling updates correctly.

2008-11-05      12:57:24:949       352      1ed4      Report      REPORT EVENT: {1D9B6510-A76C-4FB3-A4EE-A377B72ADEDE}      2008-11-05 12:57:19:748-0600      1      148      101      {D67661EB-2423-451D-BF5D-13199E37DF28}      0      80244019      SelfUpdate      Failure      Software Synchronization      Windows Update Client failed to detect with error 0x80244019.
2008-11-05      13:08:31:162       352      1ed4      PT      WARNING: Cached cookie has expired or new PID is available
2008-11-05      13:08:31:162       352      1ed4      PT      Initializing simple targeting cookie, clientId = 35c0ac92-808d-448b-95b6-562a32ca04e5, target group = , DNS name = rfpcsr1074p
2008-11-05      13:08:31:162       352      1ed4      PT        Server URL = http://NEMESIS.newsctr.ljworld.com:8530/SimpleAuthWebService/SimpleAuth.asmx
2008-11-05      13:08:31:396       352      1ed4      PT      WARNING: GetCookie failure, error = 0x8024400D, soap client error = 7, soap error code = 300, HTTP status code = 200
2008-11-05      13:08:31:396       352      1ed4      PT      WARNING: SOAP Fault: 0x00012c
2008-11-05      13:08:31:396       352      1ed4      PT      WARNING:     faultstring:Fault occurred
2008-11-05      13:08:31:396       352      1ed4      PT      WARNING:     ErrorCode:ConfigChanged(2)
2008-11-05      13:08:31:396       352      1ed4      PT      WARNING:     Message:(null)
2008-11-05      13:08:31:396       352      1ed4      PT      WARNING:     Method:"http://www.microsoft.com/SoftwareDistribution/Server/ClientWebService/GetCookie"
2008-11-05      13:08:31:396       352      1ed4      PT      WARNING:     ID:94ff360c-0ac9-4a15-9d5b-2c6e6d74f7af
2008-11-05      13:08:31:521       352      1ed4      PT      WARNING: Cached cookie has expired or new PID is available
2008-11-05      13:08:31:521       352      1ed4      PT      Initializing simple targeting cookie, clientId = 35c0ac92-808d-448b-95b6-562a32ca04e5, target group = , DNS name = rfpcsr1074p
2008-11-05      13:08:31:521       352      1ed4      PT        Server URL = http://NEMESIS.newsctr.ljworld.com:8530/SimpleAuthWebService/SimpleAuth.asmx
2008-11-05      13:08:31:693       352      1ed4      Report      Uploading 1 events using cached cookie, reporting URL = http://NEMESIS.newsctr.ljworld.com:8530/ReportingWebService/ReportingWebService.asmx
2008-11-05      13:08:31:693       352      1ed4      Report      Reporter successfully uploaded 1 events.
0
 
sunflower_itAuthor Commented:
Setup new WSUS server, ok now.
0

Featured Post

Free Tool: IP Lookup

Get more info about an IP address or domain name, such as organization, abuse contacts and geolocation.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now