none
WSUS - Update Status Showing as Not Applicable but update is installed

    Question

  • I am trying to remove an update that have been installed by WSUS.  The update is KB2592687 - RDP 8.0 client.

    I have set the update to "Approved for removal" and a date in the past - to force the removal ASAP.

    When I run a report based on the update, most clients that have the update installed (by WSUS) now show a status of Not Applicable.  Why would this happen?  Is there a way that the removal can be forced?

    mardi 2 avril 2013 16:59

Réponses

  • I am trying to remove an update that have been installed by WSUS

    One final note.. with regard to the subject line, which I only really noticed just now.... If the update is displayed as Not Applicable, then the update is not installed in the eyes of the WUAgent, and thus any attempt to remove the update using Approve for Removal will achieve absolutely nothing. You can only remove an update via Approve for Removed if it's actually reported as Installed by the WUAgent.

    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.

    dimanche 26 mai 2013 16:15
    Modérateur

Toutes les réponses

  • I am trying to remove an update that have been installed by WSUS.  The update is KB2592687 - RDP 8.0 client.

    I have set the update to "Approved for removal" and a date in the past - to force the removal ASAP.

    When I run a report based on the update, most clients that have the update installed (by WSUS) now show a status of Not Applicable.  Why would this happen?  Is there a way that the removal can be forced?

    You've configured the methodology to force the removal.... set the approval, and optionally add a deadline to make it occur sooner than it could.

    There are still the same requirements though:

    1. The client must communicate with the WSUS server to get the approval status.
    2. The client must be powered on during the scheduled 'installation' event to remove the update.
    3. If a deadline is applied, the client will perform the uninstallation when the deadline is reached. If the deadline is passed, the removal will occur immediately upon discovery.

    The question is not so much what the client has reported to WSUS, but rather what did the client do on its next detection after setting the approval to remove the update? For this we'll need to see the log entries in the WindowsUpdate.log.


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

    mardi 2 avril 2013 22:04
    Modérateur
  • Hi Lawrence,

    Thanks for the information....  Log file extract for 03-04-2013 - I ran WUAUCLT /detectnow /reportnow yesterday to try and force the WSUS server communication.  Will this help? 

    2013-04-03          09:33:07:490       1096       117c       Misc       ===========  Logging initialized (build: 7.6.7600.256, tz: +0100)  ===========

    2013-04-03          09:33:07:708       1096       117c       Misc         = Process: C:\Windows\system32\svchost.exe

    2013-04-03          09:33:07:708       1096       117c       Misc         = Module: c:\windows\system32\wuaueng.dll

    2013-04-03          09:33:07:490       1096       117c       Service *************

    2013-04-03          09:33:07:708       1096       117c       Service ** START **  Service: Service startup

    2013-04-03          09:33:07:879       1096       117c       Service *********

    2013-04-03          09:33:13:283       1096       117c       Agent      * WU client version 7.6.7600.256

    2013-04-03          09:33:13:283       1096       117c       Agent      * Base directory: C:\Windows\SoftwareDistribution

    2013-04-03          09:33:13:314       1096       117c       Agent      * Access type: No proxy

    2013-04-03          09:33:13:470       1096       117c       Agent      * Network state: Connected

    2013-04-03          09:34:02:192       1096       117c       Report  CWERReporter::Init succeeded

    2013-04-03          09:34:02:192       1096       117c       Agent    ***********  Agent: Initializing Windows Update Agent  ***********

    2013-04-03          09:34:02:239       1096       117c       Agent    ***********  Agent: Initializing global settings cache  ***********

    2013-04-03          09:34:02:239       1096       117c       Agent      * WSUS server: https://wsus.MY-Server.co.uk

    2013-04-03          09:34:02:239       1096       117c       Agent      * WSUS status server: https://wsus.MY-Server.co.uk

    2013-04-03          09:34:02:239       1096       117c       Agent      * Target group: clients.MY-Group.co.uk

    2013-04-03          09:34:02:239       1096       117c       Agent      * Windows Update access disabled: No

    2013-04-03          09:34:02:410       1096       117c       DnldMgr              Download manager restoring 0 downloads

    2013-04-03          09:34:02:659       1096       117c       Agent    Attempt 0 to obtain post-reboot results.

    2013-04-03          09:34:03:002       1096       117c       Handler                Post-reboot status for package Package_for_KB2729094~31bf3856ad364e35~amd64~~6.1.2.0: 0x00000000.

    2013-04-03          09:34:03:594       1096       117c       Handler                Post-reboot status for package Package_for_KB2732500~31bf3856ad364e35~amd64~~6.1.2.0: 0x00000000.

    2013-04-03          09:34:03:983       1096       117c       Handler                Post-reboot status for package Package_for_KB982018~31bf3856ad364e35~amd64~~6.1.3.2: 0x00000000.

    2013-04-03          09:34:04:357       1096       117c       Handler                Post-reboot status for package Package_for_KB2773072~31bf3856ad364e35~amd64~~6.1.1.5: 0x00000000.

    2013-04-03          09:34:04:746       1096       117c       Handler                Post-reboot status for package Package_for_KB2709630~31bf3856ad364e35~amd64~~6.1.1.0: 0x00000000.

    2013-04-03          09:34:05:711       1096       117c       Handler                Post-reboot status for package Package_for_KB2660075~31bf3856ad364e35~amd64~~6.1.1.0: 0x00000000.

    2013-04-03          09:34:06:069       1096       117c       Handler                Post-reboot status for package Package_for_KB2709981~31bf3856ad364e35~amd64~~6.1.2.0: 0x00000000.

    2013-04-03          09:34:06:490       1096       117c       Handler                Post-reboot status for package Package_for_KB2515325~31bf3856ad364e35~amd64~~6.1.1.0: 0x00000000.

    2013-04-03          09:34:06:848       1096       117c       Handler                Post-reboot status for package Package_for_KB2739159~31bf3856ad364e35~amd64~~6.1.1.1: 0x00000000.

    2013-04-03          09:34:08:623       1096       117c       Report  ***********  Report: Initializing static reporting data  ***********

    2013-04-03          09:34:08:623       1096       117c       Report    * OS Version = 6.1.7601.1.0.65792

    2013-04-03          09:34:08:623       1096       117c       Report    * OS Product Type = 0x00000004

    2013-04-03          09:34:08:701       1096       117c       Report    * Computer Brand = Sony Corporation

    2013-04-03          09:34:08:701       1096       117c       Report    * Computer Model = VPCF22M0E

    2013-04-03          09:34:08:701       1096       117c       Report    * Bios Revision = R1180V3

    2013-04-03          09:34:08:701       1096       117c       Report    * Bios Name = BIOS Date: 05/04/11 08:36:21 Ver: 04.06.03

    2013-04-03          09:34:08:701       1096       117c       Report    * Bios Release Date = 2011-05-04T00:00:00

    2013-04-03          09:34:08:701       1096       117c       Report    * Locale ID = 2057

    2013-04-03          09:34:09:807       1096       117c       AU          ###########  AU: Initializing Automatic Updates  ###########

    2013-04-03          09:34:09:853       1096       117c       AU          AU setting next detection timeout to 2013-04-03 08:34:09

    2013-04-03          09:34:09:853       1096       117c       AU          AU setting next sqm report timeout to 2013-04-03 08:34:09

    2013-04-03          09:34:09:853       1096       117c       AU            # WSUS server: https://wsus.MY-Server.co.uk

    2013-04-03          09:34:09:853       1096       117c       AU            # Detection frequency: 3

    2013-04-03          09:34:09:853       1096       117c       AU            # Target group: clients.MY-Group.co.uk

    2013-04-03          09:34:09:853       1096       117c       AU            # Approval type: Scheduled (Policy)

    2013-04-03          09:34:09:853       1096       117c       AU            # Scheduled install day/time: Wednesday at 12:00

    2013-04-03          09:34:09:853       1096       117c       AU            # Auto-install minor updates: Yes (User preference)

    2013-04-03          09:34:09:853       1096       117c       AU            # Will interact with non-admins (Non-admins are elevated (User preference))

    2013-04-03          09:34:10:211       1096       117c       AU          Setting AU scheduled install time to 2013-04-03 11:00:00

    2013-04-03          09:34:10:211       1096       117c       AU          Successfully wrote event for AU health state:0

    2013-04-03          09:34:10:274       1096       117c       AU          Initializing featured updates

    2013-04-03          09:34:10:274       1096       117c       AU          Found 0 cached featured updates

    2013-04-03          09:34:10:274       1096       117c       AU          Successfully wrote event for AU health state:0

    2013-04-03          09:34:10:383       1096       117c       AU          Successfully wrote event for AU health state:0

    2013-04-03          09:34:10:383       1096       117c       AU          AU finished delayed initialization

    2013-04-03          09:34:10:383       1096       117c       AU          AU setting next sqm report timeout to 2013-04-04 08:34:10

    2013-04-03          09:34:10:383       1096       117c       AU          #############

    2013-04-03          09:34:10:383       1096       117c       AU          ## START ##  AU: Search for updates

    2013-04-03          09:34:10:383       1096       117c       AU          #########

    2013-04-03          09:34:10:585       1096       117c       AU          <<## SUBMITTED ## AU: Search for updates [CallId = {2CE93230-A6D2-41DF-8BD8-906064995C4F}]

    2013-04-03          09:34:31:918       1096       1dcc       Report  REPORT EVENT: {B6165703-0130-4ABD-8B87-5E5A0FD3A5A0}                2013-04-03 09:34:08:981+0100    1              197         101         {D86DCBFE-F105-4AB3-B863-08891A52FF55}       200         0                AutomaticUpdates          Success                Content Install  Installation Successful: Windows successfully installed the following update: Update for Windows 7 for x64-based Systems (KB2739159)

    2013-04-03          09:34:31:918       1096       1dcc       Report  REPORT EVENT: {7A8A55F7-0952-41A8-8123-F8E6430FE163}                2013-04-03 09:34:09:075+0100    1              197         101         {361475E2-3578-411C-83DF-77C450DEAC5A}        100         0                AutomaticUpdates          Success                Content Install  Installation Successful: Windows successfully installed the following update: Update for Windows 7 for x64-based Systems (KB2515325)

    mercredi 3 avril 2013 09:46
  • 2013-04-03          09:34:31:918       1096       1dcc       Report  REPORT EVENT: {02C50D7E-6F5A-4EA4-9BFC-6A6CEA08B90A}                2013-04-03 09:34:09:153+0100    1              197         101         {3F08EED3-8FC3-4253-8FA9-F301430C4B24}         102         0                AutomaticUpdates          Success                Content Install  Installation Successful: Windows successfully installed the following update: Update for Windows 7 for x64-based Systems (KB2709981)

    2013-04-03          09:34:31:918       1096       1dcc       Report  REPORT EVENT: {410668D2-401E-4B90-9C91-2FCFF805A6B9}                2013-04-03 09:34:09:386+0100    1              197         101         {149402B1-7EE8-4DDE-B1F5-5F1F0F1B8B2D}        100         0                AutomaticUpdates          Success                Content Install  Installation Successful: Windows successfully installed the following update: Update for Windows 7 for x64-based Systems (KB2660075)

    2013-04-03          09:34:31:918       1096       1dcc       Report  REPORT EVENT: {54FB73F3-ECB7-4153-A5E5-C74BD4F60812}                2013-04-03 09:34:09:417+0100    1              197         101         {9A6ADA7B-27FF-40D7-A77E-403F6B4DDEA7}     101         0                AutomaticUpdates          Success                Content Install  Installation Successful: Windows successfully installed the following update: Update for Windows 7 for x64-based Systems (KB2709630)

    2013-04-03          09:34:33:849       1096       1dcc       Report  CWERReporter finishing event handling. (00000000)

    2013-04-03          09:34:33:849       1096       1dcc       Report  REPORT EVENT: {B574D31F-C3E7-4578-9AD4-EFF3727D6F04}                2013-04-03 09:34:09:495+0100    1              197         101         {49DDEC56-93F2-48E7-98AF-ECD54526D34C}       200         0                AutomaticUpdates          Success                Content Install  Installation Successful: Windows successfully installed the following update: Update for Windows 7 for x64-based Systems (KB2773072)

    2013-04-03          09:34:33:849       1096       1dcc       Report  REPORT EVENT: {28186512-B4CD-4CFC-BDA6-2FBA8F2D6C8F}                2013-04-03 09:34:09:573+0100    1              197         101         {E71EF51D-C577-4E59-9B87-31967547F41C}          101         0                AutomaticUpdates          Success                Content Install  Installation Successful: Windows successfully installed the following update: Update for Windows 7 for x64-based Systems (KB982018)

    2013-04-03          09:34:33:849       1096       1dcc       Report  REPORT EVENT: {D50AFEA2-B414-4338-B56A-BEC6B959EC9D}                2013-04-03 09:34:09:682+0100    1              197         101         {FC7E731B-F4C9-44AF-AAA8-952A614B4A64}      201         0                AutomaticUpdates          Success                Content Install  Installation Successful: Windows successfully installed the following update: Update for Windows 7 for x64-based Systems (KB2732500)

    2013-04-03          09:34:33:849       1096       1dcc       Report  REPORT EVENT: {C425E9A7-F849-47E1-A2E6-621299601198}                2013-04-03 09:34:09:791+0100    1              197         101         {083F5713-854C-4CB9-88BC-9D944F89947F}         201         0                AutomaticUpdates          Success                Content Install  Installation Successful: Windows successfully installed the following update: Update for Windows 7 for x64-based Systems (KB2729094)

    2013-04-03          09:34:33:849       1096       1dcc       Report  CWERReporter finishing event handling. (00000000)

    2013-04-03          09:34:33:849       1096       1dcc       Report  REPORT EVENT: {60B3C512-2595-40BB-94E9-DA1DFCEC8C30}                2013-04-03 09:34:10:274+0100    1              202         102         {00000000-0000-0000-0000-000000000000}           0              0                AutomaticUpdates          Success                Content Install  Reboot completed.

    2013-04-03          09:34:33:849       1096       1dcc       Report  CWERReporter finishing event handling. (00000000)

    2013-04-03          09:34:34:144       1096       1dcc       PT           WARNING: Cached cookie has expired or new PID is available

    2013-04-03          09:34:34:144       1096       1dcc       PT           Initializing simple targeting cookie, clientId = d9a5f756-0119-4e66-aec6-25907c3e1307, target group = clients.MY-Group.co.uk, DNS name = karl-pc.MY-Group.co.uk

    2013-04-03          09:34:34:144       1096       1dcc       PT             Server URL = https://wsus.MY-Server.co.uk/SimpleAuthWebService/SimpleAuth.asmx

    2013-04-03          09:34:36:589       1096       1dcc       Report  Uploading 1 events using cached cookie, reporting URL = https://wsus.MY-Server.co.uk/ReportingWebService/ReportingWebService.asmx

    2013-04-03          09:34:36:605       1096       1dcc       Report  Reporter successfully uploaded 1 events.

    2013-04-03          09:34:36:605       1096       1dcc       Agent    *************

    2013-04-03          09:34:36:605       1096       1dcc       Agent    ** START **  Agent: Finding updates [CallerId = AutomaticUpdates]

    2013-04-03          09:34:36:605       1096       1dcc       Agent    *********

    2013-04-03          09:34:36:605       1096       1dcc       Agent      * Online = No; Ignore download priority = No

    2013-04-03          09:34:36:605       1096       1dcc       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"

    2013-04-03          09:34:36:605       1096       1dcc       Agent      * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed

    2013-04-03          09:34:36:605       1096       1dcc       Agent      * Search Scope = {Machine}

    2013-04-03          09:35:13:439       1096       1dcc       Agent    WARNING: Failed to evaluate Installed rule, updateId = {189A8F50-0C3A-4FDF-8BC2-BC23A3EB11FB}.101, hr = 80242013

    2013-04-03          09:35:32:833       1096       1dcc       Agent      * Found 0 updates and 69 categories in search; evaluated appl. rules of 921 out of 1952 deployed entities

    2013-04-03          09:35:32:849       1096       1dcc       Agent    *********

    2013-04-03          09:35:32:849       1096       1dcc       Agent    **  END  **  Agent: Finding updates [CallerId = AutomaticUpdates]

    2013-04-03          09:35:32:849       1096       1dcc       Agent    *************

    2013-04-03          09:35:32:880       1096       1e40      AU          >>##  RESUMED  ## AU: Search for updates [CallId = {2CE93230-A6D2-41DF-8BD8-906064995C4F}]

    2013-04-03          09:35:32:880       1096       1e40      AU            # 0 updates detected

    2013-04-03          09:35:32:880       1096       1e40      AU          #########

    2013-04-03          09:35:32:880       1096       1e40      AU          ##  END  ##  AU: Search for updates [CallId = {2CE93230-A6D2-41DF-8BD8-906064995C4F}]

    2013-04-03          09:35:32:880       1096       1e40      AU          #############

    2013-04-03          09:35:32:880       1096       1e40      AU          Featured notifications is disabled.

    2013-04-03          09:35:32:880       1096       1e40      AU          Setting AU scheduled install time to 2013-04-03 11:00:00

    2013-04-03          09:35:32:880       1096       1e40      AU          Successfully wrote event for AU health state:0

    2013-04-03          09:35:32:896       1096       1e40      AU          Successfully wrote event for AU health state:0

    2013-04-03          09:35:32:896       1096       117c       AU          #############

    2013-04-03          09:35:32:896       1096       117c       AU          ## START ##  AU: Search for updates

    2013-04-03          09:35:32:896       1096       117c       AU          #########

    2013-04-03          09:35:32:896       1096       117c       AU          <<## SUBMITTED ## AU: Search for updates [CallId = {97F61ED5-9421-4F60-A491-BEF251156079}]

    2013-04-03          09:35:32:896       1096       1dcc       Agent    *************

    2013-04-03          09:35:32:896       1096       1dcc       Agent    ** START **  Agent: Finding updates [CallerId = AutomaticUpdates]

    2013-04-03          09:35:32:896       1096       1dcc       Agent    *********

    2013-04-03          09:35:32:896       1096       1dcc       Agent      * Online = Yes; Ignore download priority = No

    2013-04-03          09:35:32:896       1096       1dcc       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"

    2013-04-03          09:35:32:896       1096       1dcc       Agent      * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed

    2013-04-03          09:35:32:896       1096       1dcc       Agent      * Search Scope = {Machine}

    2013-04-03          09:35:32:896       1096       1dcc       Setup    Checking for agent SelfUpdate

    2013-04-03          09:35:32:896       1096       1dcc       Setup    Client version: Core: 7.6.7600.256  Aux: 7.6.7600.256

    2013-04-03          09:35:32:911       1096       1dcc       Misc       Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:

    2013-04-03          09:35:32:942       1096       1dcc       Misc       Microsoft signed: Yes

    2013-04-03          09:35:32:942       1096       1dcc       Misc       Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:

    2013-04-03          09:35:32:958       1096       1dcc       Misc       Microsoft signed: Yes

    2013-04-03          09:35:32:973       1096       1dcc       Misc       Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:

    2013-04-03          09:35:32:973       1096       1dcc       Misc       Microsoft signed: Yes

    2013-04-03          09:35:32:989       1096       1dcc       Misc       Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:

    2013-04-03          09:35:32:989       1096       1dcc       Misc       Microsoft signed: Yes

    2013-04-03          09:35:33:161       1096       1dcc       Setup    Determining whether a new setup handler needs to be downloaded

    2013-04-03          09:35:33:161       1096       1dcc       Setup    SelfUpdate handler is not found.  It will be downloaded

    2013-04-03          09:35:33:161       1096       1dcc       Setup    Evaluating applicability of setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.256"

    2013-04-03          09:35:33:207       1096       1dcc       Setup    Setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.256" is already installed.

    2013-04-03          09:35:33:207       1096       1dcc       Setup    Evaluating applicability of setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256"

    2013-04-03          09:35:33:426       1096       1dcc       Setup    Setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256" is already installed.

    2013-04-03          09:35:33:426       1096       1dcc       Setup    Evaluating applicability of setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256"

    2013-04-03          09:35:33:909       1096       1dcc       Setup    Setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256" is already installed.

    2013-04-03          09:35:33:909       1096       1dcc       Setup    SelfUpdate check completed.  SelfUpdate is NOT required.

    2013-04-03          09:35:34:252       1096       1dcc       PT           +++++++++++  PT: Synchronizing server updates  +++++++++++

    2013-04-03          09:35:34:252       1096       1dcc       PT             + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = https://wsus.MY-Server.co.uk/ClientWebService/client.asmx

    2013-04-03          09:35:36:949       1096       1dcc       Agent    WARNING: Failed to evaluate Installed rule, updateId = {189A8F50-0C3A-4FDF-8BC2-BC23A3EB11FB}.101, hr = 80242013

    2013-04-03          09:35:39:287       1096       1dcc       PT           +++++++++++  PT: Synchronizing extended update info  +++++++++++

    2013-04-03          09:35:39:287       1096       1dcc       PT             + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = https://wsus.MY-Server.co.uk/ClientWebService/client.asmx

    2013-04-03          09:35:40:192       1096       1dcc       Agent      * Found 0 updates and 69 categories in search; evaluated appl. rules of 1142 out of 1952 deployed entities

    2013-04-03          09:35:40:207       1096       1dcc       Agent    *********

    2013-04-03          09:35:40:207       1096       1dcc       Agent    **  END  **  Agent: Finding updates [CallerId = AutomaticUpdates]

    2013-04-03          09:35:40:207       1096       1dcc       Agent    *************

    2013-04-03          09:35:40:238       1096       1dcc       Report  CWERReporter finishing event handling. (00000000)

    2013-04-03          09:35:40:238       1096       1e40      AU          >>##  RESUMED  ## AU: Search for updates [CallId = {97F61ED5-9421-4F60-A491-BEF251156079}]

    2013-04-03          09:35:40:238       1096       1e40      AU            # 0 updates detected

    2013-04-03          09:35:40:238       1096       1e40      AU          #########

    2013-04-03          09:35:40:238       1096       1e40      AU          ##  END  ##  AU: Search for updates [CallId = {97F61ED5-9421-4F60-A491-BEF251156079}]

    2013-04-03          09:35:40:238       1096       1e40      AU          #############

    2013-04-03          09:35:40:238       1096       1e40      AU          Successfully wrote event for AU health state:0

    2013-04-03          09:35:40:238       1096       1e40      AU          Featured notifications is disabled.

    2013-04-03          09:35:40:238       1096       1e40      AU          AU setting next detection timeout to 2013-04-03 11:11:26

    2013-04-03          09:35:40:238       1096       1e40      AU          Setting AU scheduled install time to 2013-04-03 11:00:00

    2013-04-03          09:35:40:238       1096       1e40      AU          Successfully wrote event for AU health state:0

    2013-04-03          09:35:40:238       1096       1e40      AU          Successfully wrote event for AU health state:0

    2013-04-03          09:35:45:211       1096       1dcc       Report  REPORT EVENT: {370D460D-2E0D-4790-A9CC-539549F32A47}                2013-04-03 09:35:40:192+0100    1              147         101         {00000000-0000-0000-0000-000000000000}           0              0                AutomaticUpdates          Success                Software Synchronization            Windows Update Client successfully detected 0 updates.

    2013-04-03          09:35:45:211       1096       1dcc       Report  REPORT EVENT: {A40E1B31-D924-4DCA-A2CE-4E677C38C836}                2013-04-03 09:35:40:207+0100    1              156         101         {00000000-0000-0000-0000-000000000000}           0              0                AutomaticUpdates          Success                Pre-Deployment Check Reporting client status.

    2013-04-03          09:35:45:211       1096       1dcc       Report  CWERReporter finishing event handling. (00000000)

    2013-04-03          09:47:40:627       1096       1dcc       Report  Uploading 12 events using cached cookie, reporting URL = https://wsus.MY-Server.co.uk/ReportingWebService/ReportingWebService.asmx

    2013-04-03          09:47:40:643       1096       1dcc       Report  Reporter successfully uploaded 12 events.

    mercredi 3 avril 2013 09:47
  • I ran WUAUCLT /detectnow /reportnow yesterday to try and force the WSUS server communication.  Will this help?

    Hard to say, but probably made very little difference. First, the use of the /reportnow parameter in this syntax is insignificant. This syntax does not work in the way you think it works. wuauclt /detectnow /reportnow is exactly the same thing as wuauclt /detectnow because the /reportnow parameter does absolutely nothing in this command.

    Second, without the logfiles for that invocation I have no way of knowing what it did or did not do.

    2013-04-03          09:33:07:490       1096       117c       Service *************
    2013-04-03          09:33:07:708       1096       117c       Service ** START **  Service: Service startup
    2013-04-03          09:33:07:879       1096       117c       Service *********

    2013-04-03          09:34:02:659       1096       117c       Agent    Attempt 0 to obtain post-reboot results.

    In the logfile presented here, we see the system was rebooted following a set of update installations ... which did not include the original installation of KB2592687, nor did it include the removal.

    Most likely in this case the machine had been pending reboot since whenever the previous installation had been done, and my guess would be that as a result of that pending reboot state, your invocation of a detection did absolutely nothing.


    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.

    dimanche 26 mai 2013 16:06
    Modérateur
  • 2013-04-03          09:35:13:439       1096       1dcc       Agent    WARNING: Failed to evaluate Installed rule, updateId = {189A8F50-0C3A-4FDF-8BC2-BC23A3EB11FB}.101, hr = 80242013

    Also, it would seem you have at least one defective, expired update that needs to be declined.

    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.

    dimanche 26 mai 2013 16:12
    Modérateur
  • I am trying to remove an update that have been installed by WSUS

    One final note.. with regard to the subject line, which I only really noticed just now.... If the update is displayed as Not Applicable, then the update is not installed in the eyes of the WUAgent, and thus any attempt to remove the update using Approve for Removal will achieve absolutely nothing. You can only remove an update via Approve for Removed if it's actually reported as Installed by the WUAgent.

    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.

    dimanche 26 mai 2013 16:15
    Modérateur