none
Updates Needed - are not applicable

Answers

  • I generated the syncronization report of the day the update kb2813347 arrives (old wsus server) . that´s the result:

    No... the update did not arrive on June 28, the current revision to the original update arrived on June 28. The original update was released on April 9 (and presumably arrived on the 9th or 10th).

    Based in the above syncronization report I ask. The update kb2813347 is a new update so this is the original revision. Ok ?

    No, not the original revision. It is the current revision.

    If this isn´t the original revision where is the original revision ?

    Apparently no longer on your system. This is one of the functions of the Server Cleanup Wizard: To remove expired updates and old revisions that are no longer needed.

    The update kb2813347 replaced this update --> 2483614 inMS11-017. This is the original revision ?

    No, those are two completely separate updates.

    Supercession is a relationship betwen Update 'A' and Update 'B'

    Revision is a relationship between different "versions" of Update 'A and Update 'A'.

    You said:

    I believe that if you right click on that update and view the Revision History, you'll see both revisions.

    Yeah... that didn't happen. Looks like the Server Cleanup Wizard has removed the orginal (April 9) revision. What you have here is the current revision released on June 25.


    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2013)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

    • Marked as answer by LyraMachado Tuesday, August 06, 2013 10:10 AM
    Monday, August 05, 2013 8:21 PM

All replies

  • windowsupdate.log

    26/07/2013 07:05:01:310 1104 5c8 AU ###########  AU: Initializing Automatic Updates  ###########
    26/07/2013 07:05:01:311 1104 5c8 AU AU setting next detection timeout to 2013-07-26 10:05:01
    26/07/2013 07:05:01:312 1104 5c8 AU   # WSUS server: http://
    26/07/2013 07:05:01:312 1104 5c8 AU   # Detection frequency: 22
    26/07/2013 07:05:01:312 1104 5c8 AU   # Target group: 
    26/07/2013 07:05:01:312 1104 5c8 AU   # Approval type: Scheduled (Policy)
    26/07/2013 07:05:01:312 1104 5c8 AU   # Scheduled install day/time: Every day at 15:00
    26/07/2013 07:05:01:312 1104 5c8 AU   # Auto-install minor updates: Yes (User preference)
    26/07/2013 07:05:01:313 1104 5c8 AU Initializing featured updates
    26/07/2013 07:05:01:313 1104 5c8 AU Found 0 cached featured updates
    26/07/2013 07:05:01:313 1104 5c8 AU Successfully wrote event for AU health state:0
    26/07/2013 07:05:01:315 1104 5c8 AU Successfully wrote event for AU health state:0
    26/07/2013 07:05:01:315 1104 5c8 AU AU finished delayed initialization
    26/07/2013 07:05:01:315 1104 5c8 AU #############
    26/07/2013 07:05:01:315 1104 5c8 AU ## START ##  AU: Search for updates
    26/07/2013 07:05:01:315 1104 5c8 AU #########
    26/07/2013 07:05:01:319 1104 5c8 AU <<## SUBMITTED ## AU: Search for updates [CallId = {E0A8C0D2-E376-4607-9C5D-AF012B9FC551}]
    26/07/2013 07:05:01:875 1104 12c0 PT +++++++++++  PT: Synchronizing extended update info  +++++++++++
    26/07/2013 07:05:01:875 1104 12c0 PT   + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http:///ClientWebService/client.asmx
    26/07/2013 07:05:02:795 1104 12c0 Agent   * Added update {4AE85C00-0EAA-4BE0-B81B-DBD7053D5FAE}.104 to search result
    26/07/2013 07:05:02:795 1104 12c0 Agent   * Added update {AD388E06-2CD4-4131-8AE5-A19DA4F3FC8F}.201 to search result



    26/07/2013 07:05:02:797 1104 12c0 Agent   * Added update {0CFB8DEF-9B7E-478C-A746-8F9F91311DB5}.103 to search result
    26/07/2013 07:05:02:797 1104 12c0 Agent   * Added update {2EE7B9F1-22B7-4618-84B1-8F0804A2ED02}.101 to search result
    26/07/2013 07:05:02:797 1104 12c0 Agent   * Added update {99EB2EF3-7266-4488-9A80-A49418A4D1D4}.201 to search result
    26/07/2013 07:05:02:797 1104 12c0 Agent   * Added update {ACCDC8FE-BC27-4473-9F35-BD9D0880B4D2}.101 to search result
    26/07/2013 07:05:02:824 1104 12c0 Agent   * Found 74 updates and 71 categories in search; evaluated appl. rules of 1052 out of 1742 deployed entities
    26/07/2013 07:05:02:861 1104 12c0 Agent *********
    26/07/2013 07:05:02:861 1104 12c0 Agent **  END  **  Agent: Finding updates [CallerId = Kaspersky Network Agent]
    26/07/2013 07:05:02:861 1104 12c0 Agent *************
    26/07/2013 07:05:02:881 1104 12c0 Agent *************
    26/07/2013 07:05:02:881 1104 12c0 Agent ** START **  Agent: Finding updates [CallerId = AutomaticUpdates]
    26/07/2013 07:05:02:881 1104 12c0 Agent *********
    26/07/2013 07:05:02:881 1104 12c0 Agent   * Online = No; Ignore download priority = No
    26/07/2013 07:05:02:881 1104 12c0 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"
    26/07/2013 07:05:02:881 1104 12c0 Agent   * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
    26/07/2013 07:05:02:881 1104 12c0 Agent   * Search Scope = {Machine}
    26/07/2013 07:05:02:883 2360 1308 COMAPI >>--  RESUMED  -- COMAPI: Search [ClientId = Kaspersky Network Agent]
    26/07/2013 07:05:02:948 2360 1308 COMAPI   - Updates found = 74
    26/07/2013 07:05:02:948 2360 1308 COMAPI ---------
    26/07/2013 07:05:02:948 2360 1308 COMAPI --  END  --  COMAPI: Search [ClientId = Kaspersky Network Agent]
    26/07/2013 07:05:02:948 2360 1308 COMAPI -------------
    26/07/2013 07:05:05:460 1104 12c0 Agent   * Found 0 updates and 71 categories in search; evaluated appl. rules of 337 out of 1742 deployed entities
    26/07/2013 07:05:05:460 1104 12c0 Agent *********
    26/07/2013 07:05:05:460 1104 12c0 Agent **  END  **  Agent: Finding updates [CallerId = AutomaticUpdates]
    26/07/2013 07:05:05:460 1104 12c0 Agent *************
    26/07/2013 07:05:05:488 1104 14f0 AU >>##  RESUMED  ## AU: Search for updates [CallId = {E0A8C0D2-E376-4607-9C5D-AF012B9FC551}]
    26/07/2013 07:05:05:488 1104 14f0 AU   # 0 updates detected
    26/07/2013 07:05:05:488 1104 14f0 AU #########
    26/07/2013 07:05:05:488 1104 14f0 AU ##  END  ##  AU: Search for updates [CallId = {E0A8C0D2-E376-4607-9C5D-AF012B9FC551}]
    26/07/2013 07:05:05:489 1104 14f0 AU #############
    26/07/2013 07:05:05:489 1104 14f0 AU Featured notifications is disabled.
    26/07/2013 07:05:05:489 1104 14f0 AU Successfully wrote event for AU health state:0
    26/07/2013 07:05:05:489 1104 5c8 AU #############
    26/07/2013 07:05:05:490 1104 5c8 AU ## START ##  AU: Search for updates
    26/07/2013 07:05:05:490 1104 5c8 AU #########
    26/07/2013 07:05:05:492 1104 5c8 AU <<## SUBMITTED ## AU: Search for updates [CallId = {A965AF2C-4388-43FF-95D6-F10369168315}]
    26/07/2013 07:05:05:575 1104 12c0 Report CWERReporter finishing event handling. (00000000)
    26/07/2013 07:05:05:588 1104 12c0 Report REPORT EVENT: {04611E30-256F-4068-8C9A-2DB7C6ACA710}
    26/07/2013 07:05:05:588 1104 12c0 Report REPORT EVENT: {B56B706C-D6D0-4366-9C58-9D127E8E5EE0}
    26/07/2013 07:05:05:588 1104 12c0 Report REPORT EVENT: {F86B5538-F3CF-4190-BD46-1AC6B322AF0F}
    26/07/2013 07:05:05:606 1104 12c0 Report CWERReporter finishing event handling. (00000000)
    26/07/2013 07:05:05:607 1104 12c0 Report CWERReporter finishing event handling. (00000000)
    26/07/2013 07:05:05:607 1104 12c0 Report CWERReporter finishing event handling. (00000000)
    26/07/2013 07:05:05:607 1104 12c0 Report CWERReporter finishing event handling. (00000000)
    26/07/2013 07:05:05:608 1104 12c0 Report CWERReporter finishing event handling. (00000000)
    26/07/2013 07:05:05:608 1104 12c0 Report CWERReporter finishing event handling. (00000000)
    26/07/2013 07:05:05:608 1104 12c0 Report CWERReporter finishing event handling. (00000000)
    26/07/2013 07:05:05:608 1104 12c0 Report CWERReporter finishing event handling. (00000000)
    26/07/2013 07:05:05:608 1104 12c0 Agent *************
    26/07/2013 07:05:05:608 1104 12c0 Agent ** START **  Agent: Finding updates [CallerId = AutomaticUpdates]
    26/07/2013 07:05:05:608 1104 12c0 Agent *********
    26/07/2013 07:05:05:608 1104 12c0 Agent   * Online = Yes; Ignore download priority = No
    26/07/2013 07:05:05:608 1104 12c0 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"
    26/07/2013 07:05:05:609 1104 12c0 Agent   * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
    26/07/2013 07:05:05:609 1104 12c0 Agent   * Search Scope = {Machine}
    26/07/2013 07:05:05:609 1104 12c0 Setup Checking for agent SelfUpdate
    26/07/2013 07:05:05:610 1104 12c0 Setup Client version: Core: 7.4.7600.226  Aux: 7.4.7600.226
    26/07/2013 07:05:05:628 1104 12c0 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
    26/07/2013 07:05:05:687 1104 12c0 Misc  Microsoft signed: Yes
    26/07/2013 07:05:05:708 1104 12c0 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
    26/07/2013 07:05:05:713 1104 12c0 Misc  Microsoft signed: Yes
    26/07/2013 07:05:05:733 1104 12c0 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
    26/07/2013 07:05:05:747 1104 12c0 Misc  Microsoft signed: Yes
    26/07/2013 07:05:05:750 1104 12c0 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
    26/07/2013 07:05:05:755 1104 12c0 Misc  Microsoft signed: Yes
    26/07/2013 07:05:05:902 1104 12c0 Setup Determining whether a new setup handler needs to be downloaded
    26/07/2013 07:05:05:912 1104 12c0 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\Handler\WuSetupV.exe:
    26/07/2013 07:05:05:920 1104 12c0 Misc  Microsoft signed: Yes
    26/07/2013 07:05:05:920 1104 12c0 Setup SelfUpdate handler update NOT required: Current version: 7.4.7600.226, required version: 7.4.7600.226
    26/07/2013 07:05:05:920 1104 12c0 Setup Evaluating applicability of setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.4.7600.226"
    26/07/2013 07:05:05:931 1104 12c0 Setup Setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.4.7600.226" is already installed.
    26/07/2013 07:05:05:932 1104 12c0 Setup Evaluating applicability of setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.4.7600.226"
    26/07/2013 07:05:05:950 1104 12c0 Setup Setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.4.7600.226" is already installed.
    26/07/2013 07:05:05:951 1104 12c0 Setup Evaluating applicability of setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.4.7600.226"
    26/07/2013 07:05:05:977 1104 12c0 Setup Setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.4.7600.226" is already installed.
    26/07/2013 07:05:05:977 1104 12c0 Setup SelfUpdate check completed.  SelfUpdate is NOT required.
    26/07/2013 07:05:06:282 1104 12c0 PT +++++++++++  PT: Synchronizing server updates  +++++++++++
    26/07/2013 07:05:06:282 1104 12c0 PT   + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http:///ClientWebService/client.asmx
    26/07/2013 07:05:13:621 1104 12c0 Agent WARNING: Failed to evaluate Installed rule, updateId = {189A8F50-0C3A-4FDF-8BC2-BC23A3EB11FB}.101, hr = 80242013
    26/07/2013 07:05:18:264 1104 12c0 Agent   * Found 0 updates and 71 categories in search; evaluated appl. rules of 1052 out of 1742 deployed entities
    26/07/2013 07:05:18:265 1104 12c0 Agent *********
    26/07/2013 07:05:18:265 1104 12c0 Agent **  END  **  Agent: Finding updates [CallerId = AutomaticUpdates]
    26/07/2013 07:05:18:265 1104 12c0 Agent *************
    26/07/2013 07:05:18:285 1104 14f0 AU >>##  RESUMED  ## AU: Search for updates [CallId = {A965AF2C-4388-43FF-95D6-F10369168315}]
    26/07/2013 07:05:18:285 1104 14f0 AU   # 0 updates detected
    26/07/2013 07:05:18:285 1104 14f0 AU #########
    26/07/2013 07:05:18:285 1104 14f0 AU ##  END  ##  AU: Search for updates [CallId = {A965AF2C-4388-43FF-95D6-F10369168315}]

    Lyra


    • Edited by LyraMachado Monday, July 29, 2013 8:08 PM correction
    Monday, July 29, 2013 7:52 PM
  • 26/07/2013 07:05:13:621 1104 12c0 Agent WARNING: Failed to evaluate Installed rule, updateId = {189A8F50-0C3A-4FDF-8BC2-BC23A3EB11FB}.101, hr = 80242013
    26/07/2013 07:05:18:264 1104 12c0 Agent * Found 0 updates and 71 categories in search; evaluated appl. rules of 1052 out of 1742 deployed entities
    Find and decline the above update (it's likely already expired, but has an approval that needs to be removed), and then the client will be able to successfully complete the detection event and report the correct status for the relevant updates.

    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2013)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

    Monday, July 29, 2013 11:52 PM
  • Lawrence,

    I did this:

    I looked for the updateid = (189A8F50-0C3A-4FDF-8BC2-BC23A3EB11FB)  in C:\Program Files\Update Services\LogFiles\Change.log and I didn´t find.

    I used Microsoft Server management studio to connected do WID. We are using WID.---> \\.\pipe\mssql$microsoft##ssee\sql\query.

    I used this public view --> [SUSDB].[PUBLIC_VIEWS].[vUpdate] to find the update.

    And I didn´t find the update.

    Why  ?

    ------------------------------------------------------------------------

    SELECT [UpdateId]

     ,[RevisionNumber]

          ,[DefaultTitle]

          ,[DefaultDescription]
          ,[ClassificationId]
          ,[ArrivalDate]
          ,[CreationDate]
          ,[IsDeclined]
          ,[IsWsusInfrastructureUpdate]
          ,[MsrcSeverity]
          ,[PublicationState]
          ,[UpdateType]
          ,[UpdateSource]
          ,[KnowledgebaseArticle]
          ,[SecurityBulletin]
          ,[InstallationCanRequestUserInput]
          ,[InstallationRequiresNetworkConnectivity]
          ,[InstallationImpact]
          ,[InstallationRebootBehavior]
      FROM [SUSDB].[PUBLIC_VIEWS].[vUpdate] where [updateid] = '189A8F50-0C3A-4FDF-8BC2-BC23A3EB11FB'

    Lyra


    • Edited by LyraMachado Tuesday, July 30, 2013 10:34 AM Correction
    Tuesday, July 30, 2013 2:16 AM
  • Lawrence,

    another machine in the same test group ( windows 7 x64 Service pack 1 ) installed all the approved updates and has the same msg (windowsupdate.log):

    WARNING: Failed to evaluate Installed rule, updateId = {189A8F50-0C3A-4FDF-8BC2-BC23A3EB11FB}.101, hr = 80242013



    • Edited by LyraMachado Tuesday, July 30, 2013 12:55 PM add comments
    Tuesday, July 30, 2013 12:00 PM
  • reportingevents.log

    The machine where all new approved updates are installed. (same group)

    win 7 x64 - sp 1

    {E8EE0E01-A4DE-41DC-9718-FA8BD019D936} 2013-07-29 07:25:22:568-0300 1 190 101 {AE1E5CE2-3070-4FEE-B702-86C6A5B65708} 201 0 AutomaticUpdates Success Content Install Installation Successful: Windows successfully installed the following update: Atualização de segurança do Windows 7 para sistemas com base em x64 (KB2845690)
    {814353D4-CD81-4D57-8A3F-ED1614E36886} 2013-07-29 07:25:22:577-0300 1 190 101 {9842D9DB-8AE8-4F0B-B974-66787AEC8FBC} 201 0 AutomaticUpdates Success Content Install Installation Successful: Windows successfully installed the following update: Atualização de segurança do Microsoft .NET Framework 3.5.1 no Windows 7 e Windows Server 2008 R2 SP1 para sistemas com base em x64 (KB2840631)
    {141F5DC8-D51A-49AB-A3ED-165A4B1BB3EA} 2013-07-29 07:25:22:586-0300 1 190 101 {98FBCFA2-190C-4D27-AA94-A3618FAF95A4} 202 0 AutomaticUpdates Success Content Install Installation Successful: Windows successfully installed the following update: Atualização de segurança do Windows 7 para sistemas com base em x64 (KB2847927)
    {8103655F-85B2-400A-AAA6-30B9E675F4FA} 2013-07-29 07:25:22:594-0300 1 190 101 {DEFBDE73-65C3-4271-A949-9B77A1A65EF1} 201 0 AutomaticUpdates Success Content Install Installation Successful: Windows successfully installed the following update: Atualização de segurança do Windows 7 para sistemas com base em x64 (KB2845187)
    {CA486677-7035-4EB3-A861-241A0D0AE3AA} 2013-07-29 07:25:22:602-0300 1 190 101 {85820567-5339-431A-A5DE-0E271FA32E79} 201 0 AutomaticUpdates Success Content Install Installation Successful: Windows successfully installed the following update: Atualização de segurança do Windows 7 para sistemas com base em x64 (KB2803821)
    {2A1D6488-0416-4CE9-9DB8-C924A0D38DE8} 2013-07-29 07:25:22:611-0300 1 190 101 {0EEBE242-F0AD-4A1A-8796-4BFB54642198} 202 0 AutomaticUpdates Success Content Install Installation Successful: Windows successfully installed the following update: Atualização de segurança do Microsoft .NET Framework 3.5.1 no Windows 7 e Windows Server 2008 R2 SP1 para sistemas com base em x64 (KB2833946)
    {B5A24809-62F0-45C3-9895-B5C7134DDC7D} 2013-07-29 07:25:22:620-0300 1 190 101 {27A79441-F50A-441C-91D6-139F747D11CE} 201 0 AutomaticUpdates Success Content Install Installation Successful: Windows successfully installed the following update: Atualização de segurança cumulativa do Internet Explorer 9 para Windows 7 para sistemas baseados em x64 (KB2846071)
    {8F23F6A5-F900-49FB-800A-8DE353899841} 2013-07-29 07:25:22:628-0300 1 190 101 {E0840035-6B21-4554-A6E9-2FFEBC99D9AA} 201 0 AutomaticUpdates Success Content Install Installation Successful: Windows successfully installed the following update: Atualização de segurança do Windows 7 para sistemas com base em x64 (KB2839894)
    {4B1AC164-A161-40F4-B1A5-9CCB0BF43BDF} 2013-07-29 07:25:22:637-0300 1 190 101 {7725B934-3206-441D-90A6-824BAFC0F4EF} 201 0 AutomaticUpdates Success Content Install Installation Successful: Windows successfully installed the following update: Atualização de segurança do Windows 7 para sistemas com base em x64 (KB2850851)
    {BD8AEB36-E454-4F17-ADC9-0971B28922F1} 2013-07-29 07:25:22:646-0300 1 190 101 {FE133824-41AF-4F69-B146-B8EB6A6505C0} 201 0 AutomaticUpdates Success Content Install Installation Successful: Windows successfully installed the following update: Atualização de segurança do Windows 7 para sistemas com base em x64 (KB2835364)
    {7E1EDD04-38B1-4AB8-99FD-792CDB7DDFDE} 2013-07-29 07:25:22:653-0300 1 190 101 {53F2CC17-4951-4D4C-920F-4E44445F1EE2} 201 0 AutomaticUpdates Success Content Install Installation Successful: Windows successfully installed the following update: Atualização de segurança do Windows 7 para sistemas com base em x64 (KB2813430)
    {F0336136-AF15-4A9C-A18B-D11230B70C58} 2013-07-29 07:25:22:663-0300 1 190 101 {B841BD12-2184-4FE5-9F83-7CDDEBCB2030} 202 0 AutomaticUpdates Success Content Install Installation Successful: Windows successfully installed the following update: Atualização de segurança do Microsoft .NET Framework 3.5.1 no Windows 7 e Windows Server 2008 R2 SP1 para sistemas com base em x64 (KB2844286)
    {A22A58B1-87EF-4512-8E17-0C45F4C453E0} 2013-07-29 07:25:22:670-0300 1 190 101 {AEF6280F-8C4D-4804-9913-407582227E75} 202 0 AutomaticUpdates Success Content Install Installation Successful: Windows successfully installed the following update: Atualização de segurança do Microsoft .NET Framework 3.5.1 no Windows 7 e Windows Server 2008 R2 para sistemas baseados em x64 (KB2832414)
    {1F8750AD-1F53-4545-A62B-9DBDC0D90CAC} 2013-07-29 07:25:22:678-0300 1 190 101 {22091E0F-3395-4CF9-9F3D-4AC28BD868AD} 201 0 AutomaticUpdates Success Content Install Installation Successful: Windows successfully installed the following update: Atualização de segurança do Windows 7 para sistemas com base em x64 (KB2834886)
    {8982E19C-6C14-466B-8CC6-D17BD148CABD} 2013-07-29 07:25:24:187-0300 1 202 102 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Content Install Reboot completed.
    {594775C7-6E0B-40F1-BC13-D6028A71930A} 2013-07-29 07:26:07:760-0300 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 Kaspersky Network Agent Success Software Synchronization Windows Update Client successfully detected 58 updates.
    {1BF17E23-108A-4F53-912F-90B9EB3664DD} 2013-07-29 07:26:07:760-0300 1 156 101 {00000000-0000-0000-0000-000000000000} 0 0 Kaspersky Network Agent Success Pre-Deployment Check Reporting client status.
    {C27D1DD0-D893-41C2-8CC7-297E8AE442CC} 2013-07-29 07:26:28:713-0300 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software Synchronization Windows Update Client successfully detected 0 updates.
    {5F128A27-30F2-49DA-A8A1-2C3B0244E386} 2013-07-29 07:26:28:714-0300 1 156 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Pre-Deployment Check Reporting client status.
    {442BF16C-C29A-4504-9181-0E65867CAAA4} 2013-07-30 07:17:21:514-0300 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software Synchronization Windows Update Client successfully detected 0 updates.
    {F48C53B2-1701-42EB-A565-1937E2859CEB} 2013-07-30 07:17:21:514-0300 1 156 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Pre-Deployment Check Reporting client status.












    Tuesday, July 30, 2013 12:05 PM
  • Searching for the update via PUBLIC_VIEWS by UpdateID is not always successful because some packages have other updates associated with them that have unique UpdateIDs but are not exposed in the vUpdate view. Another variation on this is older revisions, which is the most common place for an expired update to get overlooked.

    Let's try a more simplistic approach. Note, I' may have misled you by suggesting that the update has an approval; it may not actually be approved, it's just not declined, making it visible to the client for analysis. Typically, however, it is approved, because an unapproved/expired update would be properly deleted by the Server Cleanup Wizard. An approved/expired update would be left untouched.

    In the WSUS Console, All Updates view, filter on Approval="Approved" and Status="Any", and sort by Release Date with the oldest update at the top of the list. You may have to enable the "Release Date" column for display.

    This particular update has been around for a while causing this issue for a lot of WSUS admins -- at least back to June, 2011. Unfortunately, as far as I can remember (and search results are no help), the actual update has never been identified by name, but there is a very strong indication from the empirical evidence, that this update is applicable to Windows 7 systems, possibly even only Windows 7 SP1 systems.

    My guess is that we've never identified the update because those who were affected likely got frustrated and re-built the WSUS server. Building a new WSUS server would not synchronize this 'expired' update, and would have seemingly solved the problem.

    Starting with the oldest update will likely get you to the objective much quicker, and you might also focus only on updates in the Win7 product category. (Which would also functionally eliminate anything prior to Oct 2009.)

    The only way to identify an expired update is by the yellow banner at the top of the details pane in the bottom half of the screen. You'll need to start at the top of the list, and scan through the updates, one-at-a-time, to display each update and check for the "expired" banner.

    Finally... it's also possible that this is an older revision of an update, and it's the revision that is expired, not the current update. If you're unable to find a current update dated Oct 2009 to June 2011 (the date range the update would have been active), it might be a revision to one of those updates.


    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2013)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

    Tuesday, July 30, 2013 4:36 PM
  • Lawrence,

    about expired updates. Excuse me about my basic question. Could you send me a print screen of the  yellow banner at the top of the details pane in the bottom half of the screen of the expired update ?

    I did what you said:

    In the WSUS Console, All Updates view, filter on Approval="Approved" and Status="Any", and sort by Release Date with the oldest update at the top of the list. You may have to enable the "Release Date" column for display.

    But I didn´t find the update ---> updateId = {189A8F50-0C3A-4FDF-8BC2-BC23A3EB11FB}

    You said:

    Finally... it's also possible that this is an older revision of an update, and it's the revision that is expired, not the current update. If you're unable to find a current update dated Oct 2009 to June 2011 (the date range the update would have been active), it might be a revision to one of those updates.

    How can I look for the revision  to one of those updates and look for the updateid= (189A8F50-0C3A-4FDF-8BC2-BC23A3EB11FB) ?

    Thanks for your time and efforts

    Lyra

    Wednesday, July 31, 2013 12:10 PM
  • Lawrence,

    at the same time I am looking for the problematic update I am preparing another computer (VM) and I am installing a new WSUS.

    Is there any problem to let two wsus server in my network with the correct Active Dicrectory (AD) configuration - GPO´s.

    Some Organizational Units (AD) it will have a GPO pointing to the old wsus server and others will pont to new wsus server. Only  during the time I am configuring the new wsus server.  Do you agree with that ?

    Lyra


    • Edited by LyraMachado Wednesday, July 31, 2013 4:41 PM Correction
    Wednesday, July 31, 2013 1:59 PM
  • Okay, first, forget about the UpdateID.

    You're looking for ANY expired update. You need to decline ALL expired updates. This will be part of your regular monthly patch administration activities.

    The yellow banner on the Update Details pane is the same yellow banner that's displayed for superseded updates (which should be very easy to find an example of). The only difference is the text. An expired update displays:

    "The selected update has expired and cannot be approved for installation. It is recommended you decline this update."

    Special note: While you cannot approve (or add approvals) to an expired updates, the act of expiring an update does not remove approvals that existed prior to the expiration.

    To check for revisions, right click on the update, select "File Information" and if there is more than one revision listed, inspect the state of the older revisions. (If you've used the Server Cleanup Wizard with the "Delete expired updates and old revisions..." option, then the only older revisions present will be ones with approvals still active. Old revisions should not have approvals.)


    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2013)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

    Wednesday, July 31, 2013 9:26 PM
  • Lawrence Like I said:
    at the same time I am looking for the problematic update I am preparing another computer (VM) and I am installing a new WSUS.server.

    I already installed the new WSUS Server and I saw something that intrigued me.

    I performed the first synchronization of the new wsus server and generated the synchronization report. The result showed some expired updates. One of the expired updates is the

    Security Update for Windows XP (KB2813347).

    Why When I saw that update (Security Update for Windows XP - KB2813347) in the wsus adminstration console (old an new wsus server)

    I don´t see the msg ""The selected update has expired and cannot be approved for installation. It is recommended you decline this update."


    What I missed ?

    Result synchronization report:

    New wsus server

    Lyra


    • Edited by LyraMachado Saturday, August 03, 2013 5:16 PM Correction
    Saturday, August 03, 2013 5:07 PM
  • continuing:

    Old WSUS server:


    • Edited by LyraMachado Saturday, August 03, 2013 5:09 PM Correction
    Saturday, August 03, 2013 5:08 PM
  • I performed the first synchronization of the new wsus server and generated the synchronization report. The result showed some expired updates. One of the expired updates is the

    Security Update for Windows XP (KB2813347).

    Why When I saw that update (Security Update for Windows XP - KB2813347) in the wsus adminstration console (old an new wsus server)

    I don´t see the msg ""The selected update has expired and cannot be approved for installation. It is recommended you decline this update."

    What I missed ?

    Result synchronization report:

    New wsus server


    This is a great question and providentially gives us a great example of understanding the distinction between an update that has been expired and a revision that has been expired.

    What you are reading in the synchronization report is that the original revision of KB2813347 has been expired; the current revision is Rev #200 released on June  25, 2013.

    Notice that all of the other instances of KB2813347, not for WinXP, have an original Release Date of April 9, 2013. You can also confirm this by researching the original release date for MS13-029, which was originally published on April 9, 2013.The new server actually synchronized multiple revisions -- the original (expired) and the current (Jun 25).

    I believe that if you right click on that update and view the Revision History, you'll see both revisions.

    Also, if you look at the Synchronization node on the old server, in the sync event for June 25 (or 26, perhaps), you'll see the arrival of the current Revision of that update on your original server.

    The update is not expired, which is why the update does not display the expired banner, only the original revision.


    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2013)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

    Saturday, August 03, 2013 7:07 PM
  • Lawrence,

    excuse me continuing asking but maybe I am not understanding the conecpt of original revision /  new update / current revision:

    I generated the syncronization report of the day the update kb2813347 arrives (old wsus server) . that´s the result:

    Based in the above syncronization report I ask. The update  kb2813347 is a new update so this is the original revision. Ok ?

    If this isn´t the original revision where is the original revision ?

    The  update  kb2813347  replaced  this update --> 2483614 in MS11-017. This is the original revision ?

     You said:

    I believe that if you right click on that update and view the Revision History, you'll see both revisions.

    Old WSUS Server:





    • Edited by LyraMachado Sunday, August 04, 2013 8:23 PM correction
    Sunday, August 04, 2013 6:11 PM
  • New wsus server:

    Sunday, August 04, 2013 6:15 PM
  • I generated the syncronization report of the day the update kb2813347 arrives (old wsus server) . that´s the result:

    No... the update did not arrive on June 28, the current revision to the original update arrived on June 28. The original update was released on April 9 (and presumably arrived on the 9th or 10th).

    Based in the above syncronization report I ask. The update kb2813347 is a new update so this is the original revision. Ok ?

    No, not the original revision. It is the current revision.

    If this isn´t the original revision where is the original revision ?

    Apparently no longer on your system. This is one of the functions of the Server Cleanup Wizard: To remove expired updates and old revisions that are no longer needed.

    The update kb2813347 replaced this update --> 2483614 inMS11-017. This is the original revision ?

    No, those are two completely separate updates.

    Supercession is a relationship betwen Update 'A' and Update 'B'

    Revision is a relationship between different "versions" of Update 'A and Update 'A'.

    You said:

    I believe that if you right click on that update and view the Revision History, you'll see both revisions.

    Yeah... that didn't happen. Looks like the Server Cleanup Wizard has removed the orginal (April 9) revision. What you have here is the current revision released on June 25.


    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2013)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

    • Marked as answer by LyraMachado Tuesday, August 06, 2013 10:10 AM
    Monday, August 05, 2013 8:21 PM
  • Lawrence.

    I made a big confusing with the date of the original revision.

    Your patience and attention are impressive.

    THANK YOU SO MUCH.

    Lyra

    Tuesday, August 06, 2013 1:51 PM