Clients not showing up, but still getting policy and updates. See

Discussion in 'Update Services' started by Jason, Jun 29, 2005.

  1. Jason

    Jason Guest

    Hi,
    This has been an ongoing issue since day1 of the installation. All my
    production servers, laptop reported right away but I only see 42 workstations
    out of a total of 70 in that specific OU. I use client side targeting to
    assign computers to their groups.

    Here is the log that I got from a machine that is missing in the console.
    From the log I believe it has been reporting successfully. Can anyone let me
    know why it is not showing up in the console? Thank you very much.

    2005-06-29 08:42:23 1088 110 Agent *********** Agent: Refreshing global
    settings cache ***********
    2005-06-29 08:42:23 1088 110 Agent * WSUS server: http://susserver (Changed)
    2005-06-29 08:42:23 1088 110 Agent * WSUS status server: http://susserver
    (Changed)
    2005-06-29 08:42:23 1088 110 Agent * Target group: Production Workstations
    (Changed)
    2005-06-29 08:42:23 1088 110 Agent * Windows Update access disabled: No
    (Unchanged)
    2005-06-29 08:42:23 1088 110 AU ########### AU: Policy change processed
    ###########
    2005-06-29 08:42:23 1088 110 AU # Policy changed, AU restart required = No
    2005-06-29 08:42:23 1088 110 AU # WSUS server: http://susserver
    2005-06-29 08:42:23 1088 110 AU # Detection frequency: 1
    2005-06-29 08:42:23 1088 110 AU # Target group: Production Workstations
    2005-06-29 08:42:23 1088 110 AU # Approval type: Scheduled (Policy)
    2005-06-29 08:42:23 1088 110 AU # Scheduled install day/time: Every day at
    3:00
    2005-06-29 08:42:23 1088 110 AU # Auto-install minor updates: Yes (Policy)
    2005-06-29 08:42:23 1088 110 AU # Will interact with non-admins
    (Non-admins are elevated)
    2005-06-29 08:42:23 1088 110 AU AU Restart required....
    2005-06-29 08:42:23 1088 110 AU ########### AU: Initializing Automatic
    Updates ###########
    2005-06-29 08:42:23 1088 110 AU AU setting next detection timeout to
    2005-06-29 12:42:23
    2005-06-29 08:42:23 1088 110 AU # WSUS server: http://susserver
    2005-06-29 08:42:23 1088 110 AU # Detection frequency: 1
    2005-06-29 08:42:23 1088 110 AU # Target group: Production Workstations
    2005-06-29 08:42:23 1088 110 AU # Approval type: Scheduled (Policy)
    2005-06-29 08:42:23 1088 110 AU # Scheduled install day/time: Every day at
    3:00
    2005-06-29 08:42:23 1088 110 AU # Auto-install minor updates: Yes (Policy)
    2005-06-29 08:42:23 1088 110 AU # Will interact with non-admins
    (Non-admins are elevated)
    2005-06-29 08:42:23 1088 110 AU #############
    2005-06-29 08:42:23 1088 110 AU ## START ## AU: Search for updates
    2005-06-29 08:42:23 1088 110 AU #########
    2005-06-29 08:42:23 1088 110 AU <<## SUBMITTED ## AU: Search for updates
    [CallId = {49DE859D-4C44-4EE8-96BB-A93E8FE16FEC}]
    2005-06-29 08:42:23 1088 544 Agent *************
    2005-06-29 08:42:23 1088 544 Agent ** START ** Agent: Finding updates
    [CallerId = AutomaticUpdates]
    2005-06-29 08:42:23 1088 544 Agent *********
    2005-06-29 08:42:24 1088 544 Setup *********** Setup: Checking whether
    self-update is required ***********
    2005-06-29 08:42:24 1088 544 Setup * Inf file:
    C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default\wusetup.inf
    2005-06-29 08:42:24 1088 544 Setup Update NOT required for
    C:\WINDOWS\system32\cdm.dll: target version = 5.8.0.2469, required version =
    5.8.0.2469
    2005-06-29 08:42:24 1088 544 Setup Update NOT required for
    C:\WINDOWS\system32\iuengine.dll: target version = 5.8.0.2469, required
    version = 5.8.0.2469
    2005-06-29 08:42:24 1088 544 Setup Update NOT required for
    C:\WINDOWS\system32\wuapi.dll: target version = 5.8.0.2469, required version
    = 5.8.0.2469
    2005-06-29 08:42:24 1088 544 Setup Update NOT required for
    C:\WINDOWS\system32\wuauclt.exe: target version = 5.8.0.2469, required
    version = 5.8.0.2469
    2005-06-29 08:42:24 1088 544 Setup Update NOT required for
    C:\WINDOWS\system32\wuauclt1.exe: target version = 5.8.0.2469, required
    version = 5.8.0.2469
    2005-06-29 08:42:24 1088 544 Setup Update NOT required for
    C:\WINDOWS\system32\wuaucpl.cpl: target version = 5.8.0.2469, required
    version = 5.8.0.2469
    2005-06-29 08:42:24 1088 544 Setup Update NOT required for
    C:\WINDOWS\system32\wuaueng.dll: target version = 5.8.0.2469, required
    version = 5.8.0.2469
    2005-06-29 08:42:24 1088 544 Setup Update NOT required for
    C:\WINDOWS\system32\wuaueng1.dll: target version = 5.8.0.2469, required
    version = 5.8.0.2469
    2005-06-29 08:42:24 1088 544 Setup Update NOT required for
    C:\WINDOWS\system32\wucltui.dll: target version = 5.8.0.2469, required
    version = 5.8.0.2469
    2005-06-29 08:42:24 1088 544 Setup Update NOT required for
    C:\WINDOWS\system32\wups.dll: target version = 5.8.0.2469, required version =
    5.8.0.2469
    2005-06-29 08:42:24 1088 544 Setup Update NOT required for
    C:\WINDOWS\system32\wups2.dll: target version = 5.8.0.2469, required version
    = 5.8.0.2469
    2005-06-29 08:42:24 1088 544 Setup Update NOT required for
    C:\WINDOWS\system32\wuweb.dll: target version = 5.8.0.2469, required version
    = 5.8.0.2469
    2005-06-29 08:42:24 1088 544 Setup * IsUpdateRequired = No
    2005-06-29 08:42:24 1088 544 PT +++++++++++ PT: Synchronizing server
    updates +++++++++++
    2005-06-29 08:42:24 1088 544 PT + ServiceId =
    {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL =
    http://susserver/ClientWebService/client.asmx
    2005-06-29 08:42:24 1088 544 PT Initializing simple targeting cookie,
    clientId = 8bf1ab49-59d3-48e2-b5ec-4bf35cc8b967, target group = Production
    Workstations, DNS name = det-apollo.urbanscience.net
    2005-06-29 08:42:24 1088 544 PT Server URL =
    http://susserver/SimpleAuthWebService/SimpleAuth.asmx
    2005-06-29 08:42:24 1088 544 Agent * Found 0 updates and 5 categories in
    search
    2005-06-29 08:42:24 1088 544 Agent *********
    2005-06-29 08:42:24 1088 544 Agent ** END ** Agent: Finding updates
    [CallerId = AutomaticUpdates]
    2005-06-29 08:42:24 1088 544 Agent *************
    2005-06-29 08:42:24 1088 544 AU >>## RESUMED ## AU: Search for updates
    [CallId = {49DE859D-4C44-4EE8-96BB-A93E8FE16FEC}]
    2005-06-29 08:42:24 1088 544 AU # 0 updates detected
    2005-06-29 08:42:24 1088 544 AU #########
    2005-06-29 08:42:24 1088 544 AU ## END ## AU: Search for updates [CallId
    = {49DE859D-4C44-4EE8-96BB-A93E8FE16FEC}]
    2005-06-29 08:42:24 1088 544 AU #############
    2005-06-29 08:42:24 1088 544 AU AU setting next detection timeout to
    2005-06-29 13:42:10
    2005-06-29 08:42:29 1088 544 Report REPORT EVENT:
    {945F91DD-7BEB-4F3D-803E-307CACF41B83} 2005-06-29
    08:42:24-0400 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software Synchronization Agent has finished detecting items.
    2005-06-29 08:42:29 1088 544 Report REPORT EVENT:
    {5580E585-5141-41C0-8AAF-8085DAD988E3} 2005-06-29 08:42:24-0400 1
     
    Jason, Jun 29, 2005
    #1
    1. Advertisements

  2. Jason

    Jason Guest

    Just to reply to my own post. I did a SQL query agaginst the SUSDB database.
    This is what I used:

    select * from tbcomputertarget
    order by fulldomainname

    I did not find the missing computer name so I guess that is why it's not
    showing up in the console. But how can this be fixed?? Thanks.

    Jason

     
    Jason, Jun 29, 2005
    #2
    1. Advertisements

  3. Jason... this particular client is not detecting any approved updates,and
    there are no error messages in this log snippet.

    Also, this log snippet shows no attempt to initiate a reporting contact to
    the ReportingWebService. Please scan the entire WindowsUpdate.log file for
    this client to see if there are any instances of ReportingWebService in the
    log.

    Also, inspect the %windir%\SoftwareDistribution\ReportingEvents.log to see
    if there are any reported events of successful detection, download,
    installation, or restarts.

     
    Lawrence Garvin, Jun 29, 2005
    #3
  4. That would be consistent with the client not executing the call to the
    ReportingWebService web service.


     
    Lawrence Garvin, Jun 29, 2005
    #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.