Reports showing different results than the All Computers view in WSUS

Jawab Reports showing different results than the All Computers view in WSUS

  • 20 Juni 2012 16:12
     
     

    I am using WSUS 3.0 SP2 on a Windows 2008 R2 Server.

    I am in the process of deploying Windows 7 64-bit machines to our network.  I have noticed that on 1 particular Windows 7 machine, when I look in WSUS Computers, All Computers it shows the machine needs 34 updates (all of which are approved).  These updates never get downloaded to the machine.  I have tried to wuauclt /resetauthorization /detect as well as the download switch and nothing changes on the client.

    I went to Windows Update, and I get the same list of updates that need to be applied, so I believe they really need to be applied, I just can't get them to download.

    Then I went into WSUS Reports.  When I run a Tabular Status Report for Approved Updates, the machine in question shows no updates needed. Why??  XP Machines continue to report accurately in the Computers view as well as in the Reports.  Also consistent when I go to Windows Updates on the web.

    Any ideas?? I do not want to roll out additional machines until I know they are getting patched correctly.

    Melissa

Semua Balasan

  • 26 Juni 2012 4:52
    Moderator
     
     

    Hi,

    If you went to MU, and got the same list of updates that need to be applied.Then, it indicates that you didn't approve the correct updates(for 64-bit win7) in the WSUS console for the corresponding groups which include the win 7 machine.

    Also, you can check out the windowsupdate.log in the client-side to see whether the WUA has detected the approved updates.

    Clarence


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

  • 29 Juni 2012 17:36
     
     

    I have approved all of these updates, see sample below:

     
    Update Detailed Status Report
    Title Classification Approval Status
    Update for Windows 7 for   x64-based Systems (KB2552343) Critical Updates Install Not Installed
    Security Update for Windows   7 for x64-based Systems (KB2476490) Security Updates Install Not Installed
    Security Update for Windows   7 for x64-based Systems (KB2503665) Security Updates Install Not Installed
    Security Update for Windows   7 for x64-based Systems (KB2507938) Security Updates Install Not Installed
    Security Update for Windows   7 for x64-based Systems (KB2532531) Security Updates Install Not Installed
    Security Update for Windows   7 for x64-based Systems (KB2536275) Security Updates Install Not Installed
    Security Update for Windows   7 for x64-based Systems (KB2536276) Security Updates Install Not Installed
    Security Update for Windows   7 for x64-based Systems (KB2544893) Security Updates Install Not Installed
    Security Update for Windows   7 for x64-based Systems (KB2560656) Security Updates Install Not Installed
    Security Update for Windows   7 for x64-based Systems (KB2564958) Security Updates Install Not Installed
    Security Update for Windows   7 for x64-based Systems (KB2567680) Security Updates Install Not Installed
    Security Update for Windows   7 for x64-based Systems (KB2570947) Security Updates Install Not Installed
    Security Update for Windows   7 for x64-based Systems (KB2579686) Security Updates Install Not Installed
    Security Update for Windows   7 for x64-based Systems (KB2584146) Security Updates Install Not Installed

    <v:shapetype coordsize="21600,21600" filled="f" id="_x0000_t75" o:preferrelative="t" o:spt="75" path="m@4@5l@4@11@9@11@9@5xe" stroked="f"><v:stroke joinstyle="miter"><v:formulas><v:f eqn="if lineDrawn pixelLineWidth 0"><v:f eqn="sum @0 1 0"><v:f eqn="sum 0 0 @1"><v:f eqn="prod @2 1 2"><v:f eqn="prod @3 21600 pixelWidth"><v:f eqn="prod @3 21600 pixelHeight"> <v:f eqn="sum @0 0 1">
      <v:f eqn="prod @6 1 2"> <v:f eqn="prod @7 21600 pixelWidth">
    </v:f></v:f></v:f></v:f></v:f></v:f></v:f></v:f></v:f></v:formulas></v:stroke></v:shapetype>
    Any other suggestions?

  • 02 Juli 2012 0:08
    Moderator
     
     
    I have approved all of these updates, see sample below:
    • What GROUP(s) have you approved these updates for?
    • What GROUP(s) does this Windows7 x64 system actually appear in on the WSUS console.
    • How do you assign your machines to groups?
    • What is the setting of the Options | Computers dialog in the WSUS console?

    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    Product Manager, SolarWinds
    Microsoft MVP - Software Distribution (2005-2012)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin

  • 02 Juli 2012 13:53
     
     

    1) I have set up groups for Clients and Servers.  The updates have been approved for Clients.

    2) The system appears under clients

    3) Once a system joins the network, it appears in the Unassigned group.  I then change it to the appropriate group

    4) Use the Update Services Console is set in Options

    I do use a group policy to point to the WSUS server for all machines rather than using Microsoft Update.

    I also have another Win7 machine, in the client group in WSUS that does not show that these updates still need to be installed.  I have tried the /resetauthorization, forcing a download, etc.

  • 02 Juli 2012 23:41
    Moderator
     
     

    Okay.. on this system that is not installing updates, please do the following:

    1. Record the System Time.
    2. Restart the Windows Update service (or reboot the system).
    3. Run this command at a command prompt: wuauclt /resetauthorization detectnow.
    4. Wait 30 minutes.
    5. Post all of the entries from the WindowsUpdate.log starting at the time you recorded in Step #1.

    This will tell us what is really happening to this client system.


    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    Product Manager, SolarWinds
    Microsoft MVP - Software Distribution (2005-2012)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin

  • 03 Juli 2012 15:21
     
     

    Results below:

    2012-07-03 08:49:58:647  944 1b74 Misc ===========  Logging initialized (build: 7.5.7601.17514, tz: -0500)  ===========
    2012-07-03 08:49:58:648  944 1b74 Misc   = Process: C:\Windows\system32\svchost.exe
    2012-07-03 08:49:58:648  944 1b74 Misc   = Module: c:\windows\system32\wuaueng.dll
    2012-07-03 08:49:58:647  944 1b74 Service *************
    2012-07-03 08:49:58:648  944 1b74 Service ** START **  Service: Service startup
    2012-07-03 08:49:58:648  944 1b74 Service *********
    2012-07-03 08:49:58:732  944 1b74 Agent   * WU client version 7.5.7601.17514
    2012-07-03 08:49:58:732  944 1b74 Agent   * Base directory: C:\Windows\SoftwareDistribution
    2012-07-03 08:49:58:732  944 1b74 Agent   * Access type: No proxy
    2012-07-03 08:49:58:763  944 1b74 Agent   * Network state: Connected
    2012-07-03 08:50:21:877  944 1bac Report CWERReporter::Init succeeded
    2012-07-03 08:50:21:877  944 1bac Agent ***********  Agent: Initializing Windows Update Agent  ***********
    2012-07-03 08:50:21:877  944 1bac Agent ***********  Agent: Initializing global settings cache  ***********
    2012-07-03 08:50:21:877  944 1bac Agent   * WSUS server: http://Sneezy
    2012-07-03 08:50:21:877  944 1bac Agent   * WSUS status server: http://Sneezy
    2012-07-03 08:50:21:877  944 1bac Agent   * Target group: (Unassigned Computers)
    2012-07-03 08:50:21:877  944 1bac Agent   * Windows Update access disabled: No
    2012-07-03 08:50:21:908  944 1bac DnldMgr Download manager restoring 0 downloads
    2012-07-03 08:50:21:908  944 1bac AU ###########  AU: Initializing Automatic Updates  ###########
    2012-07-03 08:50:21:908  944 1bac AU   # WSUS server: http://Sneezy
    2012-07-03 08:50:21:908  944 1bac AU   # Detection frequency: 22
    2012-07-03 08:50:21:908  944 1bac AU   # Approval type: Scheduled (Policy)
    2012-07-03 08:50:21:908  944 1bac AU   # Scheduled install day/time: Every day at 5:00
    2012-07-03 08:50:21:908  944 1bac AU   # Auto-install minor updates: Yes (User preference)
    2012-07-03 08:50:21:908  944 1bac AU   # Will interact with non-admins (Non-admins are elevated (User preference))
    2012-07-03 08:50:21:908  944 1bac AU Setting AU scheduled install time to 2012-07-04 10:00:00
    2012-07-03 08:50:22:033  944 1b74 Report ***********  Report: Initializing static reporting data  ***********
    2012-07-03 08:50:22:033  944 1b74 Report   * OS Version = 6.1.7601.1.0.65792
    2012-07-03 08:50:22:033  944 1b74 Report   * OS Product Type = 0x00000001
    2012-07-03 08:50:22:033  944 1b74 Report   * Computer Brand = Dell Inc.               
    2012-07-03 08:50:22:033  944 1b74 Report   * Computer Model = OptiPlex 745                
    2012-07-03 08:50:22:033  944 1b74 Report   * Bios Revision = 2.6.4
    2012-07-03 08:50:22:033  944 1b74 Report   * Bios Name = Phoenix ROM BIOS PLUS Version 1.10 2.6.4
    2012-07-03 08:50:22:033  944 1b74 Report   * Bios Release Date = 2010-03-01T00:00:00
    2012-07-03 08:50:22:033  944 1b74 Report   * Locale ID = 1033
    2012-07-03 08:50:22:064  944 1bac AU Successfully wrote event for AU health state:0
    2012-07-03 08:50:22:064  944 1bac AU Initializing featured updates
    2012-07-03 08:50:22:064  944 1bac AU Found 0 cached featured updates
    2012-07-03 08:50:22:064  944 1bac AU Successfully wrote event for AU health state:0
    2012-07-03 08:50:22:064  944 1bac AU Successfully wrote event for AU health state:0
    2012-07-03 08:50:22:064  944 1bac AU AU finished delayed initialization
    2012-07-03 08:50:22:064  944 1bac AU Triggering AU detection through DetectNow API
    2012-07-03 08:50:22:064  944 1bac AU Triggering Online detection (non-interactive)
    2012-07-03 08:50:22:064  944 1b74 AU #############
    2012-07-03 08:50:22:064  944 1b74 AU ## START ##  AU: Search for updates
    2012-07-03 08:50:22:064  944 1b74 AU #########
    2012-07-03 08:50:22:173  944 1b74 AU <<## SUBMITTED ## AU: Search for updates [CallId = {DBDEF8E4-81F9-43E4-8AC5-A8420F78D1FD}]
    2012-07-03 08:50:22:267  944 1384 Agent *************
    2012-07-03 08:50:22:267  944 1384 Agent ** START **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2012-07-03 08:50:22:267  944 1384 Agent *********
    2012-07-03 08:50:22:267  944 1384 Agent   * Online = Yes; Ignore download priority = No
    2012-07-03 08:50:22:267  944 1384 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"
    2012-07-03 08:50:22:267  944 1384 Agent   * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
    2012-07-03 08:50:22:267  944 1384 Agent   * Search Scope = {Machine}
    2012-07-03 08:50:22:267  944 1384 Setup Checking for agent SelfUpdate
    2012-07-03 08:50:22:267  944 1384 Setup Client version: Core: 7.5.7601.17514  Aux: 7.5.7601.17514
    2012-07-03 08:50:22:267  944 1384 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
    2012-07-03 08:50:22:282  944 1384 Misc  Microsoft signed: Yes
    2012-07-03 08:50:27:867  944 1384 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
    2012-07-03 08:50:27:867  944 1384 Misc  Microsoft signed: Yes
    2012-07-03 08:50:27:883  944 1384 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
    2012-07-03 08:50:27:883  944 1384 Misc  Microsoft signed: Yes
    2012-07-03 08:50:27:898  944 1384 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
    2012-07-03 08:50:27:914  944 1384 Misc  Microsoft signed: Yes
    2012-07-03 08:50:27:930  944 1384 Setup Determining whether a new setup handler needs to be downloaded
    2012-07-03 08:50:27:930  944 1384 Setup SelfUpdate handler is not found.  It will be downloaded
    2012-07-03 08:50:27:930  944 1384 Setup Evaluating applicability of setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.4.7600.226"
    2012-07-03 08:50:30:075  944 1384 Setup Setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.4.7600.226" is not applicable
    2012-07-03 08:50:30:075  944 1384 Setup Evaluating applicability of setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.4.7600.226"
    2012-07-03 08:50:30:095  944 1384 Setup Setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.4.7600.226" is not applicable
    2012-07-03 08:50:30:095  944 1384 Setup Evaluating applicability of setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.4.7600.226"
    2012-07-03 08:50:30:135  944 1384 Setup Setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.4.7600.226" is not applicable
    2012-07-03 08:50:30:135  944 1384 Setup SelfUpdate check completed.  SelfUpdate is NOT required.
    2012-07-03 08:50:32:435  944 1384 PT +++++++++++  PT: Synchronizing server updates  +++++++++++
    2012-07-03 08:50:32:435  944 1384 PT   + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://Sneezy/ClientWebService/client.asmx
    2012-07-03 08:50:32:451  944 1384 PT WARNING: Cached cookie has expired or new PID is available
    2012-07-03 08:50:32:451  944 1384 PT Initializing simple targeting cookie, clientId = cbd3dfae-6eab-4da1-abcc-e8f925e92b04, target group = , DNS name = maf_win7.consultbai.local
    2012-07-03 08:50:32:451  944 1384 PT   Server URL = http://Sneezy/SimpleAuthWebService/SimpleAuth.asmx
    2012-07-03 08:50:35:440  944 1384 Agent WARNING: Failed to evaluate Installed rule, updateId = {189A8F50-0C3A-4FDF-8BC2-BC23A3EB11FB}.101, hr = 80242013
    2012-07-03 08:50:36:877  944 1384 PT +++++++++++  PT: Synchronizing extended update info  +++++++++++
    2012-07-03 08:50:36:877  944 1384 PT   + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://Sneezy/ClientWebService/client.asmx
    2012-07-03 08:50:37:777  944 1384 Agent   * Found 0 updates and 70 categories in search; evaluated appl. rules of 1231 out of 1733 deployed entities
    2012-07-03 08:50:37:807  944 1384 Agent *********
    2012-07-03 08:50:37:807  944 1384 Agent **  END  **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2012-07-03 08:50:37:807  944 1384 Agent *************
    2012-07-03 08:50:37:827  944 1384 Report REPORT EVENT: {8A5A0088-F991-4693-AC73-863BD574A295} 2012-07-03 08:50:22:064-0500 1 202 102 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Content Install Reboot completed.
    2012-07-03 08:50:37:827  944 13dc AU >>##  RESUMED  ## AU: Search for updates [CallId = {DBDEF8E4-81F9-43E4-8AC5-A8420F78D1FD}]
    2012-07-03 08:50:37:827  944 13dc AU   # 0 updates detected
    2012-07-03 08:50:37:827  944 13dc AU #########
    2012-07-03 08:50:37:827  944 13dc AU ##  END  ##  AU: Search for updates [CallId = {DBDEF8E4-81F9-43E4-8AC5-A8420F78D1FD}]
    2012-07-03 08:50:37:827  944 13dc AU #############
    2012-07-03 08:50:37:837  944 13dc AU Successfully wrote event for AU health state:0
    2012-07-03 08:50:37:837  944 13dc AU Featured notifications is disabled.
    2012-07-03 08:50:37:837  944 13dc AU AU setting next detection timeout to 2012-07-04 11:32:30
    2012-07-03 08:50:37:837  944 13dc AU Setting AU scheduled install time to 2012-07-04 10:00:00
    2012-07-03 08:50:37:837  944 13dc AU Successfully wrote event for AU health state:0
    2012-07-03 08:50:37:837  944 13dc AU Successfully wrote event for AU health state:0
    2012-07-03 08:50:37:937  944 1384 Report CWERReporter finishing event handling. (00000000)
    2012-07-03 08:50:42:809  944 1384 Report REPORT EVENT: {A50D1538-7DAA-40FD-8B35-327DFB62BF9C} 2012-07-03 08:50:37:797-0500 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software Synchronization Windows Update Client successfully detected 0 updates.
    2012-07-03 08:50:42:809  944 1384 Report REPORT EVENT: {7F5AD1E4-BB1D-4EAE-A708-7E88C59E7C9B} 2012-07-03 08:50:37:807-0500 1 156 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Pre-Deployment Check Reporting client status.
    2012-07-03 08:50:42:809  944 1384 Report CWERReporter finishing event handling. (00000000)
    2012-07-03 08:51:58:965  944 1384 Report Uploading 3 events using cached cookie, reporting URL = http://Sneezy/ReportingWebService/ReportingWebService.asmx
    2012-07-03 08:51:58:980  944 1384 Report Reporter successfully uploaded 3 events.

    I was trying to include an image showing that the computer is really in the clients group and not "unassigned" as the log shows, but I couldn't get it in.  Please let me know what other info would be helpful.

  • 04 Juli 2012 0:22
    Moderator
     
     

    2012-07-03 08:50:37:777  944 1384 Agent   * Found 0 updates and 70 categories in search; evaluated appl. rules of 1231 out of 1733 deployed entities

    The machine has no available updates to install.

    2012-07-03 08:50:35:440  944 1384 Agent WARNING: Failed to evaluate Installed rule, updateId = {189A8F50-0C3A-4FDF-8BC2-BC23A3EB11FB}.101, hr = 80242013

    However, you do have a defective update in your WSUS console; most often this is associatedd with an expired update that still has an active approval. You should find the update and decline it. This defective update may be preventing the client system from seeing other available updates.

    http://support.microsoft.com/kb/938205 -- see error code 0x80242013


    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    Product Manager, SolarWinds
    Microsoft MVP - Software Distribution (2005-2012)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin

  • 04 Juli 2012 0:25
    Moderator
     
     

    I was trying to include an image showing that the computer is really in the clients group and not "unassigned" as the log shows, but I couldn't get it in.

    The WindowsUpdate.log does not record target group information when server-side targeting is being used. This is why I asked you the questions before asking for the logfile -- so I would know how to interpret the logfile entries.

    As for the image.. that functionality seems to be hit or miss. I can't get 'em to upload either. I think it's because I'm using IE -- might try another day with another browser.


    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    Product Manager, SolarWinds
    Microsoft MVP - Software Distribution (2005-2012)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin

  • 05 Juli 2012 20:38
     
     

    I did a little more digging and ran the wsusutil.exe reset command on the WSUS server.  Then I did the wuauclt /resetauthorization detectnow command again.  At that point the workstation picked up the updates (there were 31) and updated the machine properly and reported back to WSUS correctly.

    Thanks for your help.

  • 05 Juli 2012 21:34
    Moderator
     
     Jawab

    I did a little more digging and ran the wsusutil.exe reset command on the WSUS server.  Then I did the wuauclt /resetauthorization /detectnow command again.  At that point the workstation picked up the updates (there were 31) and updated the machine properly and reported back to WSUS correctly.

    Good news. Happy to hear you were able to get it working.

    There are two known scenarios that would be resolved by these actions.

    • It's possible that the update files were not yet downloaded for the approved updates. The wsusutil reset would remediate this.
    • It's possible that the WUAgent had cached the wrong target group assignments. The wuauclt /resetauthorization /detectnow would remediate this.

    Given that we had already investigated group memberships, and the WUAgent was initializing the targeting cookie, my money is on the first one -- unless you had other Win7x64 systems that did install these updates, and then I haven't got a clue.


    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    Product Manager, SolarWinds
    Microsoft MVP - Software Distribution (2005-2012)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin

    • Ditandai sebagai Jawaban oleh Ferg1349 06 Juli 2012 13:50
    •  
  • 06 Juli 2012 13:50
     
     

    I did have another Windows 7 machine that had already installed the updates.  That is why it is such a mystery.  I don’t know if something got corrupt or what happened.  We are getting ready to deploy many Windows 7 machines and I will keep an eye on things to make sure it doesn’t happen again, but for now, I believe that doing the wsusutil.exe reset is what fixed it.