Sign in
Microsoft.com
 
Windows Server TechCenter
 
 
 
Windows Server TechCenter > Windows Server Forums > WSUS > WSUS Updates do not appear on workstations
Ask a questionAsk a question
Search Forums:
 

AnswerWSUS Updates do not appear on workstations

  • Saturday, November 07, 2009 2:10 AMCarolynCAPMPT Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote

    Hello,

    I created a group of computers and approved updates for them. I set the deadline to the day before today, but the updates are not installing. I went through the WSUS Server configuration wizard, and everything seems to be set up properly. Is there a setting which determines when the updates will be deployed on workstations? I am using WSUS 3.0 SP2.

    Thanks,
    Carolyn

     

Answers

  • Monday, November 09, 2009 8:48 AMEric Zhang - MSFTMSFT, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer
    Sign In to Vote
    1
    Sign In to Vote
    Hi,

    Like Lawrence said, 0x80244019 indicated that you have misconfigured URL for your WSUS Server.

    Please add the port to the address in group policy, refresh group policy setting on your client.
    • Marked As Answer byCarolynCAPMPT Thursday, November 12, 2009 5:02 AM
    •  
     
  • Wednesday, November 11, 2009 5:00 PMLawrence GarvinMVP, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer
    Sign In to Vote
    1
    Sign In to Vote
    Hi,

    I checked our SCCM server, which is able to obtain updates from WSUS, and it is configured with port 8530. I set the port suffix as 8530 in the WSUS group policy.

    Here are the entries from the WindowsUpdate.log that I collected after following the instructions from Lawrence:

    2009-11-10 20:49:13:371 1436 b24 Agent   * WSUS server: http://capinfo.cap-mpt.com:80
    2009-11-10 20:49:13:371 1436 b24 Agent   * WSUS status server: http://capinfo.cap-mpt.com:80

    Here we see the client is still using the (incorrect) port 80 suffix -- which suggests to me that the policy you modified is not being applied to this client.
    Lawrence Garvin, M.S., MCITP:EA, MCDBA
    Principal/CTO, Onsite Technology Solutions, Houston, Texas
    Microsoft MVP - Software Distribution (2005-2009)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    My Blog: http://onsitechsolutions.spaces.live.com
    • Marked As Answer byCarolynCAPMPT Thursday, November 12, 2009 5:01 AM
    •  
     

All Replies

  • Saturday, November 07, 2009 8:30 AMLawrence GarvinMVP, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    Is there a setting which determines when the updates will be deployed on workstations?

    Yes, and it's 3am local time; however, detections and downloads occur at random offsets from every 22 hours. Installation requires that the update content has been successfully downloaded.

    How have you determined that the updates are not installing (as opposed to the updates are not downloading, or the computer is not detecting). What are the values for the Last Contact Time and Last Reported Time for the computers in this group?
    Lawrence Garvin, M.S., MCITP:EA, MCDBA
    Principal/CTO, Onsite Technology Solutions, Houston, Texas
    Microsoft MVP - Software Distribution (2005-2009)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    My Blog: http://onsitechsolutions.spaces.live.com
     
  • Sunday, November 08, 2009 3:51 PMCarolynCAPMPT Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    Hello Lawrence,

    Thanks for your reply. I'm not sure where to check the last contact time and last reported time for the computers in my group, but I looked at the log files on one of the computers. In C:\Windows\WindowsUpdate.log I saw the following errors:

    2009-11-08 07:22:07:938 1436 e1c PT WARNING: PTError: 0x80244019
    2009-11-08 07:22:07:938 1436 e1c PT WARNING: GetCookie_WithRecovery failed : 0x80244019
    2009-11-08 07:22:07:938 1436 e1c PT WARNING: RefreshCookie failed: 0x80244019
    2009-11-08 07:22:07:938 1436 e1c PT WARNING: RefreshPTState failed: 0x80244019
    2009-11-08 07:22:07:938 1436 e1c PT WARNING: PTError: 0x80244019
    2009-11-08 07:22:07:938 1436 e1c Report WARNING: Reporter failed to upload events with hr = 80244019.


    and in the C:\Windows\SoftwareDistribution\ReportingEvents.log:

    Automatic Updates failure Software Synchronization Windows Update client failed to detect with error 0x80244019.


    Any suggestions would be appreciated.

    -Carolyn
     
  • Sunday, November 08, 2009 4:11 PMLawrence GarvinMVP, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    I'm not sure where to check the last contact time and last reported time for the computers in my group
    Then you'll probably want to start with the product documentation. The section Administering WSUS 3.0 SP2 in the Operations Guide is probably a good place to start.
    2009-11-08 07:22:07:938 1436 e1c Report WARNING: Reporter failed to upload events with hr = 80244019.
    The log entries are incomplete, and out of context, so it's difficult to determine exactly what is happening, but the error code presented is an HTTP 404 error code, and generally indicates that you've configured an incorrect URL for your WSUS Server.

    And to my specific question of determining whether they're installing -- the issue is not that the updates are not installing, it's that the clients apparently cannot even find the WSUS server.
    Lawrence Garvin, M.S., MCITP:EA, MCDBA
    Principal/CTO, Onsite Technology Solutions, Houston, Texas
    Microsoft MVP - Software Distribution (2005-2009)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    My Blog: http://onsitechsolutions.spaces.live.com
     
  • Monday, November 09, 2009 8:48 AMEric Zhang - MSFTMSFT, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer
    Sign In to Vote
    1
    Sign In to Vote
    Hi,

    Like Lawrence said, 0x80244019 indicated that you have misconfigured URL for your WSUS Server.

    Please add the port to the address in group policy, refresh group policy setting on your client.
    • Marked As Answer byCarolynCAPMPT Thursday, November 12, 2009 5:02 AM
    •  
     
  • Tuesday, November 10, 2009 1:59 AMCarolynCAPMPT Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    Hi,

    I checked the group policy, the Specify intranet Microsoft update service location has http://[server's fully qualified domain name]:80 set in detecting updates and for intranet statistics server. I think this is correct, but it doesn't work.

    -Carolyn
     
  • Tuesday, November 10, 2009 2:58 AMLawrence GarvinMVP, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    I checked the group policy, the Specify intranet Microsoft update service location has http://[server's fully qualified domain name]:80 set in detecting updates and for intranet statistics server. I think this is correct, but it doesn't work.

    The fact that it doesn't work, and results with an HTTP 404 (URL not found) error, is a pretty strong indication that it's not the correct URL.

    However, if you could give us some background on the environment, or the complete detection output (unedited, in context) of a WindowsUpdate.log, we might be able to provide a bit more than "it would appear the URL is incorrect".

    For example -- here's a key question: Look in IIS Manager on your WSUS Server. Do you have a "WSUS Administration" v-root, or can you confirm that all WSUS resources are installed in the "Default Web Site"? Do you have any other webapps installed on your WSUS Server?

    btw... if DNS and DHCP are properly configured to supply DNS suffixes and search the DNS suffixes correctly, the URL should only need to be http://servername. The port suffix ':80' is optional, and, in fact, has been shown to cause some unnecessary complications - although strictly speaking it shouldn't. Assuming your server really is installed on port 80, the suffix can be removed.
    Lawrence Garvin, M.S., MCITP:EA, MCDBA
    Principal/CTO, Onsite Technology Solutions, Houston, Texas
    Microsoft MVP - Software Distribution (2005-2009)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    My Blog: http://onsitechsolutions.spaces.live.com
     
  • Tuesday, November 10, 2009 9:30 PMCarolynCAPMPT Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    Hi,

    I checked the IIS Manager, and there is a WSUS Administration v-root. It looks to me that the Default Web Site is being used by SCCM 2007. Those are the only applications on this server.

    I'm not sure how to find the section in the WindowsUpdate log that shows detection output. I checked the log and I found: "AU setting next detection timeout to . . . ," but I don't think that's what you want.

    Thanks for the help.

    Carolyn
     
  • Wednesday, November 11, 2009 2:13 AMLawrence GarvinMVP, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    I checked the IIS Manager, and there is a WSUS Administration v-root.
    Then as Eric suggested yesterday; verify that you have correctly affixed the port suffix to the configured URL.
    I'm not sure how to find the section in the WindowsUpdate log that shows detection output.
    See KB902093 for assistance in reading the WindowsUpdate.log

    However as a starting point, using a procedure I've posted in this forum at least weekly for the past gazillion weeks . .

    1. Record the system time.
    2. Restart the Automatic Updates service. (net stop wuauserv; net start wuauserv)
    3. Run a detection. (wuauclt /resetauthorization /detectnow)
    4. Wait 30 minutes.
    5. Post all of the entries from the WindowsUpdate.log starting at the time recorded in Step #1.
    Lawrence Garvin, M.S., MCITP:EA, MCDBA
    Principal/CTO, Onsite Technology Solutions, Houston, Texas
    Microsoft MVP - Software Distribution (2005-2009)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    My Blog: http://onsitechsolutions.spaces.live.com
     
  • Wednesday, November 11, 2009 5:33 AMCarolynCAPMPT Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    Hi,

    I checked our SCCM server, which is able to obtain updates from WSUS, and it is configured with port 8530. I set the port suffix as 8530 in the WSUS group policy.

    Here are the entries from the WindowsUpdate.log that I collected after following the instructions from Lawrence:

    2009-11-10 20:48:36:386 1436 c30 Service ** START **  Service: Service startup
    2009-11-10 20:48:36:386 1436 c30 Service *********
    2009-11-10 20:48:36:402 1436 c30 Agent   * WU client version 7.4.7600.226
    2009-11-10 20:48:36:402 1436 c30 Agent   * Base directory: C:\WINDOWS\SoftwareDistribution
    2009-11-10 20:48:36:418 1436 c30 Agent   * Access type: No proxy
    2009-11-10 20:48:36:433 1436 c30 Agent   * Network state: Connected
    2009-11-10 20:49:13:371 1436 b24 Agent ***********  Agent: Initializing Windows Update Agent  ***********
    2009-11-10 20:49:13:371 1436 b24 Agent ***********  Agent: Initializing global settings cache  ***********
    2009-11-10 20:49:13:371 1436 b24 Agent   * WSUS server: http://capinfo.cap-mpt.com:80
    2009-11-10 20:49:13:371 1436 b24 Agent   * WSUS status server: http://capinfo.cap-mpt.com:80
    2009-11-10 20:49:13:371 1436 b24 Agent   * Target group: Computers to receive WSUS updates
    2009-11-10 20:49:13:371 1436 b24 Agent   * Windows Update access disabled: No
    2009-11-10 20:49:13:371 1436 b24 DnldMgr Download manager restoring 0 downloads
    2009-11-10 20:49:13:371 1436 b24 AU ###########  AU: Initializing Automatic Updates  ###########
    2009-11-10 20:49:13:371 1436 b24 AU AU setting next sqm report timeout to 2009-11-11 04:49:13
    2009-11-10 20:49:13:371 1436 b24 AU   # WSUS server: http://capinfo.cap-mpt.com:80
    2009-11-10 20:49:13:371 1436 b24 AU   # Detection frequency: 22
    2009-11-10 20:49:13:371 1436 b24 AU   # Target group: Computers to receive WSUS updates
    2009-11-10 20:49:13:371 1436 b24 AU   # Approval type: Scheduled (Policy)
    2009-11-10 20:49:13:371 1436 b24 AU   # Scheduled install day/time: Every day at 3:00
    2009-11-10 20:49:13:371 1436 b24 AU   # Auto-install minor updates: Yes (User preference)
    2009-11-10 20:49:13:371 1436 b24 AU   # Will interact with non-admins (Non-admins are elevated (Policy))
    2009-11-10 20:49:13:387 1436 b24 AU Setting AU scheduled install time to 2009-11-11 11:00:00
    2009-11-10 20:49:13:402 1436 b24 AU Initializing featured updates
    2009-11-10 20:49:13:402 1436 b24 AU Found 0 cached featured updates
    2009-11-10 20:49:13:730 1436 c30 Report ***********  Report: Initializing static reporting data  ***********
    2009-11-10 20:49:13:730 1436 c30 Report   * OS Version = 5.1.2600.2.0.65792
    2009-11-10 20:49:13:762 1436 c30 Report   * Computer Brand = Dell Inc.               
    2009-11-10 20:49:13:762 1436 c30 Report   * Computer Model = Dimension 4700              
    2009-11-10 20:49:13:777 1436 c30 Report   * Bios Revision = A09
    2009-11-10 20:49:13:777 1436 c30 Report   * Bios Name = Phoenix ROM BIOS PLUS Version 1.10 A09
    2009-11-10 20:49:13:777 1436 c30 Report   * Bios Release Date = 2005-06-22T00:00:00
    2009-11-10 20:49:13:777 1436 c30 Report   * Locale ID = 1033
    2009-11-10 20:49:15:715 1436 b24 AU AU finished delayed initialization
    2009-11-10 20:49:15:715 1436 b24 AU Triggering AU detection through DetectNow API
    2009-11-10 20:49:15:715 1436 b24 AU Triggering Online detection (non-interactive)
    2009-11-10 20:49:15:715 1436 c30 AU #############
    2009-11-10 20:49:15:715 1436 c30 AU ## START ##  AU: Search for updates
    2009-11-10 20:49:15:715 1436 c30 AU #########
    2009-11-10 20:49:15:715 1436 c30 AU <<## SUBMITTED ## AU: Search for updates [CallId = {306CF399-A4FE-4D7B-8AAE-518B02481640}]
    2009-11-10 20:49:15:715 1436 7f4 PT WARNING: GetCurrentComputerInfo failed, not fatal: 0x8024000b
    2009-11-10 20:49:15:715 1436 7f4 PT WARNING: Cached cookie has expired or new PID is available
    2009-11-10 20:49:15:715 1436 7f4 PT WARNING: PopulateAuthCookies failed: 0x8024000b
    2009-11-10 20:49:15:715 1436 7f4 PT WARNING: RefreshCookie failed: 0x8024000b
    2009-11-10 20:49:15:715 1436 7f4 PT WARNING: RefreshPTState failed: 0x8024000b
    2009-11-10 20:49:15:715 1436 7f4 PT WARNING: PTError: 0x8024000b
    2009-11-10 20:49:15:715 1436 7f4 Report WARNING: Reporter failed to upload events with hr = 8024000b.
    2009-11-10 20:49:15:715 1436 7f4 Agent *************
    2009-11-10 20:49:15:715 1436 7f4 Agent ** START **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2009-11-10 20:49:15:715 1436 7f4 Agent *********
    2009-11-10 20:49:15:715 1436 7f4 Agent   * Online = Yes; Ignore download priority = No
    2009-11-10 20:49:15:715 1436 7f4 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"
    2009-11-10 20:49:15:715 1436 7f4 Agent   * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
    2009-11-10 20:49:15:715 1436 7f4 Agent   * Search Scope = {Machine}
    2009-11-10 20:49:15:715 1436 7f4 Misc Validating signature for C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default\wuident.cab:
    2009-11-10 20:49:15:777 1436 7f4 Misc  Microsoft signed: Yes
    2009-11-10 20:49:28:824 1436 7f4 Misc Validating signature for C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default\wuident.cab:
    2009-11-10 20:49:28:824 1436 7f4 Misc  Microsoft signed: Yes
    2009-11-10 20:49:28:902 1436 7f4 Misc Validating signature for C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default\wsus3setup.cab:
    2009-11-10 20:49:28:918 1436 7f4 Misc  Microsoft signed: Yes
    2009-11-10 20:49:28:934 1436 7f4 Setup ***********  Setup: Checking whether self-update is required  ***********
    2009-11-10 20:49:28:934 1436 7f4 Setup   * Inf file: C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default\wsus3setup.inf
    2009-11-10 20:49:28:996 1436 7f4 Setup Update NOT required for C:\WINDOWS\system32\cdm.dll: target version = 7.4.7600.226, required version = 7.4.7600.226
    2009-11-10 20:49:28:996 1436 7f4 Setup Update NOT required for C:\WINDOWS\system32\wuapi.dll: target version = 7.4.7600.226, required version = 7.4.7600.226
    2009-11-10 20:49:29:027 1436 7f4 Setup Update NOT required for C:\WINDOWS\system32\wuapi.dll.mui: target version = 7.4.7600.226, required version = 7.4.7600.226
    2009-11-10 20:49:29:027 1436 7f4 Setup Update NOT required for C:\WINDOWS\system32\wuauclt.exe: target version = 7.4.7600.226, required version = 7.4.7600.226
    2009-11-10 20:49:29:027 1436 7f4 Setup Update NOT required for C:\WINDOWS\system32\wuaucpl.cpl: target version = 7.4.7600.226, required version = 7.4.7600.226
    2009-11-10 20:49:29:027 1436 7f4 Setup Update NOT required for C:\WINDOWS\system32\wuaucpl.cpl.mui: target version = 7.4.7600.226, required version = 7.4.7600.226
    2009-11-10 20:49:29:027 1436 7f4 Setup Update NOT required for C:\WINDOWS\system32\wuaueng.dll: target version = 7.4.7600.226, required version = 7.4.7600.226
    2009-11-10 20:49:29:043 1436 7f4 Setup Update NOT required for C:\WINDOWS\system32\wuaueng.dll.mui: target version = 7.4.7600.226, required version = 7.4.7600.226
    2009-11-10 20:49:29:043 1436 7f4 Setup Update NOT required for C:\WINDOWS\system32\wucltui.dll: target version = 7.4.7600.226, required version = 7.4.7600.226
    2009-11-10 20:49:29:043 1436 7f4 Setup Update NOT required for C:\WINDOWS\system32\wucltui.dll.mui: target version = 7.4.7600.226, required version = 7.4.7600.226
    2009-11-10 20:49:29:059 1436 7f4 Setup Update NOT required for C:\WINDOWS\system32\wups.dll: target version = 7.4.7600.226, required version = 7.4.7600.226
    2009-11-10 20:49:29:059 1436 7f4 Setup Update NOT required for C:\WINDOWS\system32\wups2.dll: target version = 7.4.7600.226, required version = 7.4.7600.226
    2009-11-10 20:49:29:074 1436 7f4 Setup Update NOT required for C:\WINDOWS\system32\wuweb.dll: target version = 7.4.7600.226, required version = 7.4.7600.226
    2009-11-10 20:49:29:090 1436 7f4 Setup   * IsUpdateRequired = No
    2009-11-10 20:49:38:512 1436 7f4 PT +++++++++++  PT: Synchronizing server updates  +++++++++++
    2009-11-10 20:49:38:512 1436 7f4 PT   + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://capinfo.cap-mpt.com:80/ClientWebService/client.asmx
    2009-11-10 20:49:38:543 1436 7f4 PT WARNING: Cached cookie has expired or new PID is available
    2009-11-10 20:49:38:543 1436 7f4 PT Initializing simple targeting cookie, clientId = ebfe8280-3f7d-4464-bc09-84390040f4d1, target group = Computers to receive WSUS updates, DNS name = la-828e.cap-mpt.com
    2009-11-10 20:49:38:543 1436 7f4 PT   Server URL = http://capinfo.cap-mpt.com:80/SimpleAuthWebService/SimpleAuth.asmx
    2009-11-10 20:49:38:559 1436 7f4 PT WARNING: GetCookie failure, error = 0x80244019, soap client error = 10, soap error code = 0, HTTP status code = 404
    2009-11-10 20:49:38:559 1436 7f4 PT WARNING: PTError: 0x80244019
    2009-11-10 20:49:38:559 1436 7f4 PT WARNING: GetCookie_WithRecovery failed : 0x80244019
    2009-11-10 20:49:38:559 1436 7f4 PT WARNING: RefreshCookie failed: 0x80244019
    2009-11-10 20:49:38:559 1436 7f4 PT WARNING: RefreshPTState failed: 0x80244019
    2009-11-10 20:49:38:559 1436 7f4 PT WARNING: Sync of Updates: 0x80244019
    2009-11-10 20:49:38:559 1436 7f4 PT WARNING: SyncServerUpdatesInternal failed: 0x80244019
    2009-11-10 20:49:38:559 1436 7f4 Agent   * WARNING: Failed to synchronize, error = 0x80244019
    2009-11-10 20:49:38:793 1436 7f4 Agent   * WARNING: Exit code = 0x80244019
    2009-11-10 20:49:38:793 1436 7f4 Agent *********
    2009-11-10 20:49:38:793 1436 7f4 Agent **  END  **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2009-11-10 20:49:38:793 1436 7f4 Agent *************
    2009-11-10 20:49:38:793 1436 7f4 Agent WARNING: WU client failed Searching for update with error 0x80244019
    2009-11-10 20:49:38:824 1436 1d0 AU >>##  RESUMED  ## AU: Search for updates [CallId = {306CF399-A4FE-4D7B-8AAE-518B02481640}]
    2009-11-10 20:49:38:824 1436 1d0 AU   # WARNING: Search callback failed, result = 0x80244019
    2009-11-10 20:49:38:824 1436 1d0 AU   # WARNING: Failed to find updates with error code 80244019
    2009-11-10 20:49:38:824 1436 1d0 AU #########
    2009-11-10 20:49:38:824 1436 1d0 AU ##  END  ##  AU: Search for updates [CallId = {306CF399-A4FE-4D7B-8AAE-518B02481640}]
    2009-11-10 20:49:38:824 1436 1d0 AU #############
    2009-11-10 20:49:38:824 1436 1d0 AU AU setting next detection timeout to 2009-11-11 09:49:38
    2009-11-10 20:49:38:824 1436 1d0 AU Setting AU scheduled install time to 2009-11-11 11:00:00
    2009-11-10 20:49:38:871 1436 7f4 PT WARNING: Cached cookie has expired or new PID is available
    2009-11-10 20:49:38:871 1436 7f4 PT Initializing simple targeting cookie, clientId = ebfe8280-3f7d-4464-bc09-84390040f4d1, target group = Computers to receive WSUS updates, DNS name = la-828e.cap-mpt.com
    2009-11-10 20:49:38:871 1436 7f4 PT   Server URL = http://capinfo.cap-mpt.com:80/SimpleAuthWebService/SimpleAuth.asmx
    2009-11-10 20:49:38:871 1436 7f4 PT WARNING: GetCookie failure, error = 0x80244019, soap client error = 10, soap error code = 0, HTTP status code = 404
    2009-11-10 20:49:38:871 1436 7f4 PT WARNING: PTError: 0x80244019
    2009-11-10 20:49:38:871 1436 7f4 PT WARNING: GetCookie_WithRecovery failed : 0x80244019
    2009-11-10 20:49:38:871 1436 7f4 PT WARNING: RefreshCookie failed: 0x80244019
    2009-11-10 20:49:38:871 1436 7f4 PT WARNING: RefreshPTState failed: 0x80244019
    2009-11-10 20:49:38:871 1436 7f4 PT WARNING: PTError: 0x80244019
    2009-11-10 20:49:38:871 1436 7f4 Report WARNING: Reporter failed to upload events with hr = 80244019.
    2009-11-10 20:49:38:871 1436 7f4 Report REPORT EVENT: {EEA739AC-1B39-4CA8-9BF4-1FB8EEF7EB94} 2009-11-10 20:49:13:402-0800 1 202 102 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Content Install Reboot completed.
    2009-11-10 20:49:43:793 1436 7f4 Report REPORT EVENT: {8EC20BB1-A22C-47A2-BB98-6FD3356AE528} 2009-11-10 20:49:38:793-0800 1 148 101 {00000000-0000-0000-0000-000000000000} 0 80244019 AutomaticUpdates Failure Software Synchronization Windows Update Client failed to detect with error 0x80244019.
    2009-11-10 21:10:08:674 1436 358 PT WARNING: Cached cookie has expired or new PID is available
    2009-11-10 21:10:08:674 1436 358 PT Initializing simple targeting cookie, clientId = ebfe8280-3f7d-4464-bc09-84390040f4d1, target group = Computers to receive WSUS updates, DNS name = la-828e.cap-mpt.com
    2009-11-10 21:10:08:674 1436 358 PT   Server URL = http://capinfo.cap-mpt.com:80/SimpleAuthWebService/SimpleAuth.asmx
    2009-11-10 21:10:08:706 1436 358 PT WARNING: GetCookie failure, error = 0x80244019, soap client error = 10, soap error code = 0, HTTP status code = 404
    2009-11-10 21:10:08:706 1436 358 PT WARNING: PTError: 0x80244019
    2009-11-10 21:10:08:706 1436 358 PT WARNING: GetCookie_WithRecovery failed : 0x80244019
    2009-11-10 21:10:08:706 1436 358 PT WARNING: RefreshCookie failed: 0x80244019
    2009-11-10 21:10:08:706 1436 358 PT WARNING: RefreshPTState failed: 0x80244019
    2009-11-10 21:10:08:706 1436 358 PT WARNING: PTError: 0x80244019
    2009-11-10 21:10:08:706 1436 358 Report WARNING: Reporter failed to upload events with hr = 80244019.
    2009-11-10 21:22:47:562 1436 358 PT WARNING: Cached cookie has expired or new PID is available
    2009-11-10 21:22:47:562 1436 358 PT Initializing simple targeting cookie, clientId = ebfe8280-3f7d-4464-bc09-84390040f4d1, target group = Computers to receive WSUS updates, DNS name = la-828e.cap-mpt.com
    2009-11-10 21:22:47:562 1436 358 PT   Server URL = http://capinfo.cap-mpt.com:80/SimpleAuthWebService/SimpleAuth.asmx
    2009-11-10 21:22:47:578 1436 358 PT WARNING: GetCookie failure, error = 0x80244019, soap client error = 10, soap error code = 0, HTTP status code = 404
    2009-11-10 21:22:47:578 1436 358 PT WARNING: PTError: 0x80244019
    2009-11-10 21:22:47:578 1436 358 PT WARNING: GetCookie_WithRecovery failed : 0x80244019
    2009-11-10 21:22:47:578 1436 358 PT WARNING: RefreshCookie failed: 0x80244019
    2009-11-10 21:22:47:578 1436 358 PT WARNING: RefreshPTState failed: 0x80244019
    2009-11-10 21:22:47:578 1436 358 PT WARNING: PTError: 0x80244019
    2009-11-10 21:22:47:578 1436 358 Report WARNING: Reporter failed to upload events with hr = 80244019.
     
  • Wednesday, November 11, 2009 5:00 PMLawrence GarvinMVP, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer
    Sign In to Vote
    1
    Sign In to Vote
    Hi,

    I checked our SCCM server, which is able to obtain updates from WSUS, and it is configured with port 8530. I set the port suffix as 8530 in the WSUS group policy.

    Here are the entries from the WindowsUpdate.log that I collected after following the instructions from Lawrence:

    2009-11-10 20:49:13:371 1436 b24 Agent   * WSUS server: http://capinfo.cap-mpt.com:80
    2009-11-10 20:49:13:371 1436 b24 Agent   * WSUS status server: http://capinfo.cap-mpt.com:80

    Here we see the client is still using the (incorrect) port 80 suffix -- which suggests to me that the policy you modified is not being applied to this client.
    Lawrence Garvin, M.S., MCITP:EA, MCDBA
    Principal/CTO, Onsite Technology Solutions, Houston, Texas
    Microsoft MVP - Software Distribution (2005-2009)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    My Blog: http://onsitechsolutions.spaces.live.com
    • Marked As Answer byCarolynCAPMPT Thursday, November 12, 2009 5:01 AM
    •  
     
  • Thursday, November 12, 2009 5:00 AMCarolynCAPMPT Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    Hi Lawrence and Eric,

    It turns out the domain controller I was using to edit the group policy was not saving the changes I made. When I used a different domain controller to edit the WSUS group policy to set the WSUS server port to 8530, the change was applied and the updates are working on the workstations now. Thank you very much for finding the cause of the problem.

    -Carolyn