Clients not connecting to WSUS

Discussion in 'Update Services' started by BDempsey, Apr 14, 2008.

  1. BDempsey

    BDempsey Guest

    I am a newbie per say, so bear with me. I original had WSUS installed on a
    windows server 2003 running on the default website; everything was happy and
    I then installed Symantec enterprise endpoint protection console on the same
    machine. I used its default website, not realizing that it would overwrite
    the virtual director called “content†because each uses one. I uninstalled
    both software and now I am trying to install Symantec on its default website
    (port 80) and WSUS on the custom one (port 8530). But I can not get any of
    the WSUS clients to show up in the MMC for WSUS. How do I check to see if
    the group policy is being received by my clients (I set it to
    http://servername:8530)? Also here is a sample log of the windowsupdate.log
    from one of the clients. I have been working on this for over a week,
    uninstalling and reinstalling software and reading blogs and posts. Any help
    or direction would be great because I am at a lost right now.

    2008-04-14 10:02:20:660 1528 72c AU #############
    2008-04-14 10:02:20:660 1528 72c AU ## START ## AU: Search for updates
    2008-04-14 10:02:20:660 1528 72c AU #########
    2008-04-14 10:02:20:660 1528 72c AU <<## SUBMITTED ## AU: Search for updates
    [CallId = {2F5CA57B-A682-46CF-91FA-831F20331B05}]
    2008-04-14 10:02:20:660 1528 2668 Agent *************
    2008-04-14 10:02:20:660 1528 2668 Agent ** START ** Agent: Finding updates
    [CallerId = AutomaticUpdates]
    2008-04-14 10:02:20:660 1528 2668 Agent *********
    2008-04-14 10:02:20:660 1528 2668 Agent * Online = Yes; Ignore download
    priority = No
    2008-04-14 10:02:20:660 1528 2668 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-04-14 10:02:20:660 1528 2668 Agent * ServiceID =
    {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}
    2008-04-14 10:02:20:676 1528 2668 Misc Validating signature for
    C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default\wuident.cab:
    2008-04-14 10:02:20:707 1528 2668 Misc Microsoft signed: Yes
    2008-04-14 10:02:20:707 1528 2668 Misc Validating signature for
    C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default\wuident.cab:
    2008-04-14 10:02:20:722 1528 2668 Misc Microsoft signed: Yes
    2008-04-14 10:02:20:754 1528 2668 Misc Validating signature for
    C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default\wsus3setup.cab:
    2008-04-14 10:02:20:769 1528 2668 Misc Microsoft signed: Yes
    2008-04-14 10:02:20:769 1528 2668 Setup *********** Setup: Checking whether
    self-update is required ***********
    2008-04-14 10:02:20:769 1528 2668 Setup * Inf file:
    C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default\wsus3setup.inf
    2008-04-14 10:02:20:800 1528 2668 Setup Update NOT required for
    C:\WINDOWS\system32\cdm.dll: target version = 7.0.6000.381, required version
    = 7.0.6000.374
    2008-04-14 10:02:20:816 1528 2668 Setup Update NOT required for
    C:\WINDOWS\system32\wuapi.dll: target version = 7.0.6000.381, required
    version = 7.0.6000.374
    2008-04-14 10:02:20:832 1528 2668 Setup Update NOT required for
    C:\WINDOWS\system32\wuapi.dll.mui: target version = 7.0.6000.381, required
    version = 7.0.6000.374
    2008-04-14 10:02:20:832 1528 2668 Setup Update NOT required for
    C:\WINDOWS\system32\wuauclt.exe: target version = 7.0.6000.381, required
    version = 7.0.6000.374
    2008-04-14 10:02:20:878 1528 2668 Setup Update NOT required for
    C:\WINDOWS\system32\wuaucpl.cpl: target version = 7.0.6000.381, required
    version = 7.0.6000.374
    2008-04-14 10:02:20:894 1528 2668 Setup Update NOT required for
    C:\WINDOWS\system32\wuaucpl.cpl.mui: target version = 7.0.6000.381, required
    version = 7.0.6000.374
    2008-04-14 10:02:20:909 1528 2668 Setup Update NOT required for
    C:\WINDOWS\system32\wuaueng.dll: target version = 7.0.6000.381, required
    version = 7.0.6000.374
    2008-04-14 10:02:20:941 1528 2668 Setup Update NOT required for
    C:\WINDOWS\system32\wuaueng.dll.mui: target version = 7.0.6000.381, required
    version = 7.0.6000.374
    2008-04-14 10:02:20:956 1528 2668 Setup Update NOT required for
    C:\WINDOWS\system32\wucltui.dll: target version = 7.0.6000.381, required
    version = 7.0.6000.374
    2008-04-14 10:02:20:972 1528 2668 Setup Update NOT required for
    C:\WINDOWS\system32\wucltui.dll.mui: target version = 7.0.6000.381, required
    version = 7.0.6000.374
    2008-04-14 10:02:20:987 1528 2668 Setup Update NOT required for
    C:\WINDOWS\system32\wups.dll: target version = 7.0.6000.381, required version
    = 7.0.6000.374
    2008-04-14 10:02:21:019 1528 2668 Setup Update NOT required for
    C:\WINDOWS\system32\wups2.dll: target version = 7.0.6000.381, required
    version = 7.0.6000.374
    2008-04-14 10:02:21:050 1528 2668 Setup Update NOT required for
    C:\WINDOWS\system32\wuweb.dll: target version = 7.0.6000.381, required
    version = 7.0.6000.374
    2008-04-14 10:02:21:050 1528 2668 Setup * IsUpdateRequired = No
    2008-04-14 10:02:22:250 1528 2668 PT +++++++++++ PT: Synchronizing server
    updates +++++++++++
    2008-04-14 10:02:22:250 1528 2668 PT + ServiceId =
    {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL =
    http://JSEC-Update.JSEC.MIL/ClientWebService/client.asmx
    2008-04-14 10:02:22:406 1528 2668 PT WARNING: Cached cookie has expired or
    new PID is available
    2008-04-14 10:02:22:406 1528 2668 PT Initializing simple targeting cookie,
    clientId = 22812d46-4ea8-4a81-ae79-b871009df34b, target group = JSEC LAB, DNS
    name = dell-brian.jsec.mil
    2008-04-14 10:02:22:406 1528 2668 PT Server URL =
    http://JSEC-Update.JSEC.MIL/SimpleAuthWebService/SimpleAuth.asmx
    2008-04-14 10:02:22:406 1528 2668 PT WARNING: GetAuthorizationCookie
    failure, error = 0x80244019, soap client error = 10, soap error code = 0,
    HTTP status code = 404
    2008-04-14 10:02:22:406 1528 2668 PT WARNING: Failed to initialize Simple
    Targeting Cookie: 0x80244019
    2008-04-14 10:02:22:406 1528 2668 PT WARNING: PopulateAuthCookies failed:
    0x80244019
    2008-04-14 10:02:22:406 1528 2668 PT WARNING: RefreshCookie failed: 0x80244019
    2008-04-14 10:02:22:406 1528 2668 PT WARNING: RefreshPTState failed:
    0x80244019
    2008-04-14 10:02:22:406 1528 2668 PT WARNING: Sync of Updates: 0x80244019
    2008-04-14 10:02:22:406 1528 2668 PT WARNING: SyncServerUpdatesInternal
    failed: 0x80244019
    2008-04-14 10:02:22:406 1528 2668 Agent * WARNING: Failed to synchronize,
    error = 0x80244019
    2008-04-14 10:02:22:624 1528 2668 Agent * WARNING: Exit code = 0x80244019
    2008-04-14 10:02:22:624 1528 2668 Agent *********
    2008-04-14 10:02:22:624 1528 2668 Agent ** END ** Agent: Finding updates
    [CallerId = AutomaticUpdates]
    2008-04-14 10:02:22:624 1528 2668 Agent *************
    2008-04-14 10:02:22:624 1528 2668 Agent WARNING: WU client failed Searching
    for update with error 0x80244019
    2008-04-14 10:02:22:624 1528 1ad0 AU >>## RESUMED ## AU: Search for
    updates [CallId = {2F5CA57B-A682-46CF-91FA-831F20331B05}]
    2008-04-14 10:02:22:624 1528 1ad0 AU # WARNING: Search callback failed,
    result = 0x80244019
    2008-04-14 10:02:22:624 1528 1ad0 AU # WARNING: Failed to find updates
    with error code 80244019
    2008-04-14 10:02:22:624 1528 1ad0 AU #########
    2008-04-14 10:02:22:624 1528 1ad0 AU ## END ## AU: Search for updates
    [CallId = {2F5CA57B-A682-46CF-91FA-831F20331B05}]
    2008-04-14 10:02:22:624 1528 1ad0 AU #############
    2008-04-14 10:02:22:624 1528 1ad0 AU AU setting next detection timeout to
    2008-04-14 15:01:36
    2008-04-14 10:02:27:611 1528 2668 Report REPORT EVENT:
    {93344D6E-ED68-4B4F-976E-5F7C3B39B721} 2008-04-14
    10:02:22:624-0400 1 148 101 {00000000-0000-0000-0000-000000000000} 0 80244019 AutomaticUpdates Failure Software
    Synchronization Windows Update Client failed to detect with error 0x80244019.
    2008-04-14 10:04:38:680 1528 2668 PT WARNING: Cached cookie has expired or
    new PID is available
    2008-04-14 10:04:38:680 1528 2668 PT Initializing simple targeting cookie,
    clientId = 22812d46-4ea8-4a81-ae79-b871009df34b, target group = JSEC LAB, DNS
    name = dell-brian.jsec.mil
    2008-04-14 10:04:38:680 1528 2668 PT Server URL =
    http://JSEC-Update.JSEC.MIL/SimpleAuthWebService/SimpleAuth.asmx
    2008-04-14 10:04:38:695 1528 2668 PT WARNING: GetAuthorizationCookie
    failure, error = 0x80244019, soap client error = 10, soap error code = 0,
    HTTP status code = 404
    2008-04-14 10:04:38:695 1528 2668 PT WARNING: Failed to initialize Simple
    Targeting Cookie: 0x80244019
    2008-04-14 10:04:38:695 1528 2668 PT WARNING: PopulateAuthCookies failed:
    0x80244019
    2008-04-14 10:04:38:695 1528 2668 PT WARNING: RefreshCookie failed: 0x80244019
    2008-04-14 10:04:38:695 1528 2668 PT WARNING: RefreshPTState failed:
    0x80244019
    2008-04-14 10:04:38:695 1528 2668 PT WARNING: PTError: 0x80244019
    2008-04-14 10:04:38:695 1528 2668 Report WARNING: Reporter failed to upload
    events with hr = 80244019.


    Brian
     
    BDempsey, Apr 14, 2008
    #1
    1. Advertisements

  2. The logfile seems pretty clear that the URL (policy) hasn't been updated.

    Of course, by the time you read this, I'm sure the policy has updated... (90
    mins +/- 30 mins)

    If not, then you may have updated the wrong policy, or there's some other
    issue with the functioning of your group policy environment.

    --
    Lawrence Garvin, M.S., MCBMSP, MCTS, MCP
    Senior Data Architect, APQC, Houston, Texas
    Microsoft MVP - Software Distribution (2005-2008)

    MS WSUS Website: http://www.microsoft.com/wsus
    My Websites: http://www.onsitechsolutions.com;
    http://wsusinfo.onsitechsolutions.com
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
     
    Lawrence Garvin [MVP], Apr 14, 2008
    #2
    1. Advertisements

  3. BDempsey

    BDempsey Guest

    How would i check to see if the group policy is being update corretly to the
    clients? It was never a problem on port 80, but it is now on port 8530.
    what could be causing that. I have never been able to connect on port 8530.
     
    BDempsey, Apr 14, 2008
    #3
  4. Well, we already know that it's not, based on two facts you've presented:
    [1] You've updated the policy to include port 8530 in the URL, and
    [2] The WindowsUpdate.log shows that the WUA doesn't know about the URL
    change.

    The *only* logical conclusion from these two facts is that the policy has
    not been updated.

    The question is not *IF* the policy is being updated, but *WHY* the policy
    is not being updated.
    Which has nothing to do with WSUS, or the fact that you switched ports,
    specifically. When WSUS was on port 80, the URL possessed by the client was
    correct. Now that you've moved the server, updated, the policy, but the
    policy did not replicate, the URL is now incorrect.
    Because... as previously noted (and repeated here), your policy is *NOT*
    updating correctly.


    But, given that you posted back the same day, ostensibly with the problem
    continuing, then the likely causes are:
    [a] You updated the incorrect policy, or
    Something in your GPO replication system is broken.

    --
    Lawrence Garvin, M.S., MCBMSP, MCTS, MCP
    Senior Data Architect, APQC, Houston, Texas
    Microsoft MVP - Software Distribution (2005-2008)

    MS WSUS Website: http://www.microsoft.com/wsus
    My Websites: http://www.onsitechsolutions.com;
    http://wsusinfo.onsitechsolutions.com
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
     
    Lawrence Garvin [MVP], Apr 15, 2008
    #4
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.