Clients not reporting, not detecting, working properly at all

All replies

• 

  

  0

  Sign in to vote

  Many things concern me about this, especially the "Found 0 updates in 0 categories in search".

  Which simply means that at this moment there are no updates available for this client to download from the WSUS server. For all the things you've mentioned in this post, and they're all good things, I don't see where there's any discussion about whether the WSUS server is successfully downloading content after you've approved the updates.

  I have told WSUS to approve every single package in the repo

  And that probably didn't help your process. My guess is the server is so busy downloading content for updates that are not needed, that the content for the updates that ARE needed is stuck a couple dozen gigabytes down the queue, and maybe might get downloaded next week.

  ---

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

  Wednesday, November 19, 2014 11:30 AM
• 

  

  0

  Sign in to vote

  How long should it take to download the updates?  And/or how can I check on the packages that are being downloaded so I can see if that is indeed the problem?  Also I've had this same problem for months now and I've had these patches approved for quite sometime, I didn't just recently approve everything, so I would assume it should have downloaded everything by this point in time...
  

  • Edited by Dean Berman Wednesday, November 19, 2014 1:23 PM Meant to add something else to this

  Wednesday, November 19, 2014 1:13 PM
• 

  

  0

  Sign in to vote

  How long should it take to download the updates?

  Well.. that really depends. If the downloads are currently failing, then it'll take forever. If you've got 100GB of downloads, it could take a couple of weeks, depending on how much bandwidth is actually available to the WSUS server to do those downloads.

  And/or how can I check on the packages that are being downloaded so I can see if that is indeed the problem?

  Look at the "Download Status" in the main screen of the root node of the console. Inspect the ApplicationEventLog for EventID 364s.

  Also I've had this same problem for months now and I've had these patches approved for quite sometime

  Then I'd bet a lot of money on the fact that the downloads are failing.

  ---

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

  Wednesday, November 19, 2014 10:21 PM
• 

  

  0

  Sign in to vote

  I'm going to rebuild my WSUS box then and not approve anything and see if the systems can report in without any issues and stay reported in...

  Thanks for your help Lawrence.

  Wednesday, November 19, 2014 11:56 PM
• 

  

  0

  Sign in to vote

  I'm going to rebuild my WSUS box then and not approve anything and see if the systems can report in without any issues and stay reported in...

  The client is working PERFECTLY!

  There are no updates available at the SERVER.

  Reinstalling the SERVER is not going to fix this problem. The problem is almost certainly external to the server. Furthermore, rebuilding the server will DESTROY any forensic information you currently have that would help identify the problem so you can FIX the problem.

  ---

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

  • Proposed as answer by Ben Herila [MSFT] Sunday, November 30, 2014 7:44 AM
  • Marked as answer by Steven_Lee0510 Sunday, November 30, 2014 2:58 PM

  Thursday, November 20, 2014 1:54 PM
• 

  

  0

  Sign in to vote

  I know you mentioned not reinstalling the server, but unfortunately I had to, I wasn't able to see what  updates were being downloaded and what wasn't because WSUS continued to crash constantly without any hope of recovery.  With that being said, I've reinstalled it, I've kept an eye on the Download Status and everything is working much better now.  I've gotten numerous packages approved and downloaded as necessary (by doing them in chunks at a time instead of all at once) except for the drivers, since all of my clients are VMs.

  My WSUS currently has:
  Server version: 3.2.7600.251
  Unapproved updates: 23684
  Approved updates: 12728
  Declined updates: 4406
  Updates needing files: 0

  I have a win7 32bit client connecting without any issues, but I'm still getting 0 files needed to be installed.  I installed updates prior to approving 95% of the packages on WSUS, but I'm still getting 0 even after.  Also, my clients are still reporting as:
  Updates with errors: 0
  Updates needed: 0
  Updates installed/not applicable: 36412
  Updates with no status: 0

  Why isn't it showing me what updates were installed originally?  At first it showed the updates as 167 files needed, 25 installed, but now everything is at 0.  The client isn't reporting into the server, even after running wuauclt /reportnow /detectnow

  Again, any help would be greatly appreciated!  Thanks Lawrence (and/or anyone else who hops on this thread).

  Thursday, December 11, 2014 5:34 AM
• 

  

  0

  Sign in to vote

  Unapproved updates: 23684
  Approved updates: 12728
  

  If this is not already a core cause of your issues, it soon will be again.

  One, that you have over 40,000 synchronized updates.

  Two, that over 12,000 of them are approved.

  I would highly recommend reviewing this blog series:

  WSUS Timeout Errors - When? and Why?, Eliminating and Avoiding

  The client isn't reporting into the server, even after running wuauclt /reportnow /detectnow

  That's an invalid command, so no great surprise there.

  So what *IS* the client actually doing? is the relevant question.

  Please do the following on this client:

  1. Record System Time
  2. Reboot
  3. Run this command: wuauclt /resetauthorization /detectnow
  4. Wait -30- minutes.
  5. Post the entries from the WindowsUpdate.log starting at the time recorded in Step #1.

  ---

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

  Thursday, December 11, 2014 7:23 PM
• 

  

  0

  Sign in to vote

  Thanks for the info, I'm going through the clean-up now.  I'll get back to you on the client log information in a few.

  My WSUS server now states the following after deleting the superseded updates and running the cleanup wizard.

  Unapproved updates: 23492
  Approved updates: 4477
  Declined updates: 12857

  I've run the client commands and after 30min, the following output is below:

  2014-12-13 20:27:32:808 876 c8c AU Triggering AU detection through DetectNow API
  2014-12-13 20:27:32:808 876 c8c AU Triggering Online detection (non-interactive)
  2014-12-13 20:27:32:808 876 25c AU #############
  2014-12-13 20:27:32:808 876 25c AU ## START ##  AU: Search for updates
  2014-12-13 20:27:32:808 876 25c AU #########
  2014-12-13 20:27:32:808 876 25c AU <<## SUBMITTED ## AU: Search for updates [CallId = {65B8B60D-BA42-42B6-9D78-5AAE689D2A2A}]
  2014-12-13 20:27:32:808 876 b80 Agent *************
  2014-12-13 20:27:32:808 876 b80 Agent ** START **  Agent: Finding updates [CallerId = AutomaticUpdates]
  2014-12-13 20:27:32:808 876 b80 Agent *********
  2014-12-13 20:27:32:808 876 b80 Agent  * Online = Yes; Ignore download priority = No
  2014-12-13 20:27:32:808 876 b80 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"
  2014-12-13 20:27:32:808 876 b80 Agent  * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
  2014-12-13 20:27:32:808 876 b80 Agent  * Search Scope = {Machine}
  2014-12-13 20:27:32:808 876 b80 Setup Checking for agent SelfUpdate
  2014-12-13 20:27:32:808 876 b80 Setup Client version: Core: 7.6.7600.256  Aux: 7.6.7600.256
  2014-12-13 20:27:32:808 876 b80 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
  2014-12-13 20:27:32:824 876 b80 Misc Microsoft signed: Yes
  2014-12-13 20:27:32:824 876 b80 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
  2014-12-13 20:27:32:824 876 b80 Misc Microsoft signed: Yes
  2014-12-13 20:27:32:839 876 b80 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
  2014-12-13 20:27:32:839 876 b80 Misc Microsoft signed: Yes
  2014-12-13 20:27:32:839 876 b80 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
  2014-12-13 20:27:32:855 876 b80 Misc Microsoft signed: Yes
  2014-12-13 20:27:32:871 876 b80 Setup Determining whether a new setup handler needs to be downloaded
  2014-12-13 20:27:32:871 876 b80 Setup SelfUpdate handler is not found.  It will be downloaded
  2014-12-13 20:27:32:871 876 b80 Setup Evaluating applicability of setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~x86~~7.6.7600.256"
  2014-12-13 20:27:32:871 876 b80 Setup Setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~x86~~7.6.7600.256" is already installed.
  2014-12-13 20:27:32:871 876 b80 Setup Evaluating applicability of setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~x86~~7.6.7600.256"
  2014-12-13 20:27:32:902 876 b80 Setup Setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~x86~~7.6.7600.256" is already installed.
  2014-12-13 20:27:32:902 876 b80 Setup Evaluating applicability of setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~x86~~7.6.7600.256"
  2014-12-13 20:27:32:933 876 b80 Setup Setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~x86~~7.6.7600.256" is already installed.
  2014-12-13 20:27:32:933 876 b80 Setup SelfUpdate check completed.  SelfUpdate is NOT required.
  2014-12-13 20:27:32:996 876 b80 PT +++++++++++  PT: Synchronizing server updates  +++++++++++
  2014-12-13 20:27:32:996 876 b80 PT  + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://WSUSSERVER/ClientWebService/client.asmx
  2014-12-13 20:27:33:074 876 b80 PT Initializing simple targeting cookie, clientId = 1cc4458c-92f7-49cd-a1d4-7415e09d8f84, target group = ccop_test, DNS name = cwc-3
  2014-12-13 20:27:33:074 876 b80 PT  Server URL = http://WSUSSERVER/SimpleAuthWebService/SimpleAuth.asmx
  2014-12-13 20:27:33:105 876 b80 Agent  * Found 0 updates and 0 categories in search; evaluated appl. rules of 0 out of 0 deployed entities
  2014-12-13 20:27:33:105 876 b80 Agent *********
  2014-12-13 20:27:33:105 876 b80 Agent **  END  **  Agent: Finding updates [CallerId = AutomaticUpdates]
  2014-12-13 20:27:33:105 876 b80 Agent *************
  2014-12-13 20:27:33:105 876 bdc AU >>##  RESUMED  ## AU: Search for updates [CallId = {65B8B60D-BA42-42B6-9D78-5AAE689D2A2A}]
  2014-12-13 20:27:33:105 876 bdc AU  # 0 updates detected
  2014-12-13 20:27:33:105 876 bdc AU #########
  2014-12-13 20:27:33:105 876 bdc AU ##  END  ##  AU: Search for updates [CallId = {65B8B60D-BA42-42B6-9D78-5AAE689D2A2A}]
  2014-12-13 20:27:33:105 876 bdc AU #############
  2014-12-13 20:27:33:105 876 bdc AU Successfully wrote event for AU health state:0
  2014-12-13 20:27:33:105 876 bdc AU Featured notifications is disabled.
  2014-12-13 20:27:33:105 876 bdc AU AU setting next detection timeout to 2014-12-14 02:26:18
  2014-12-13 20:27:33:105 876 bdc AU Successfully wrote event for AU health state:0
  2014-12-13 20:27:33:105 876 bdc AU Successfully wrote event for AU health state:0
  2014-12-13 20:27:38:105 876 b80 Report REPORT EVENT: {A546E216-FB1E-4FA3-BB2A-B5B5B6DDDDC8} 2014-12-13 20:27:33:105-0500 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software Synchronization Windows Update Client successfully detected 0 updates.
  2014-12-13 20:27:38:105 876 b80 Report REPORT EVENT: {2E7B8482-9C5F-4123-9A71-F029F0311F3A} 2014-12-13 20:27:33:105-0500 1 156 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Pre-Deployment Check Reporting client status.
  2014-12-13 20:27:38:105 876 b80 Report CWERReporter finishing event handling. (00000000)
  2014-12-13 20:37:05:099 876 b80 Report Uploading 4 events using cached cookie, reporting URL = http://WSUSSERVER/ReportingWebService/ReportingWebService.asmx
  2014-12-13 20:37:07:693 876 b80 Report Reporter successfully uploaded 4 events.
  

  The client reported in to WSUS (Last Status Report), but it still says:
  Updates with errors: 0
  Updates needed: 0
  Updates installed/not applicable: 27969
  Updates with no status: 0

  I wonder if I need to delete/decline more updates that didn't get effected from the cleanup or the superseded statuses...?

  • Edited by Dean Berman Sunday, December 14, 2014 6:00 AM Additional updates

  Sunday, December 14, 2014 5:07 AM
• 

  

  0

  Sign in to vote

  I ran some more cleanup on the WSUS server and here are the results now:

  WSUS Server:
  Upapproved updates: 0
  Approved updates: 4552
  Declined updates: 36303

  I have run the client commands again and here's the following output/results from the log file:

  2014-12-14 16:56:57:663 876 150 AU Triggering AU detection through DetectNow API
  2014-12-14 16:56:57:663 876 150 AU Triggering Online detection (non-interactive)
  2014-12-14 16:56:57:663 876 bc0 AU #############
  2014-12-14 16:56:57:663 876 bc0 AU ## START ##  AU: Search for updates
  2014-12-14 16:56:57:663 876 bc0 AU #########
  2014-12-14 16:56:57:663 876 bc0 AU <<## SUBMITTED ## AU: Search for updates [CallId = {CF5777B0-92F4-42D3-8480-F1A570AA266C}]
  2014-12-14 16:56:57:678 876 7e4 Agent *************
  2014-12-14 16:56:57:678 876 7e4 Agent ** START **  Agent: Finding updates [CallerId = AutomaticUpdates]
  2014-12-14 16:56:57:678 876 7e4 Agent *********
  2014-12-14 16:56:57:678 876 7e4 Agent  * Online = Yes; Ignore download priority = No
  2014-12-14 16:56:57:678 876 7e4 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"
  2014-12-14 16:56:57:678 876 7e4 Agent  * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
  2014-12-14 16:56:57:678 876 7e4 Agent  * Search Scope = {Machine}
  2014-12-14 16:56:57:819 876 7e4 Setup Checking for agent SelfUpdate
  2014-12-14 16:56:57:819 876 7e4 Setup Client version: Core: 7.6.7600.256  Aux: 7.6.7600.256
  2014-12-14 16:56:57:819 876 7e4 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
  2014-12-14 16:56:57:819 876 7e4 Misc Microsoft signed: Yes
  2014-12-14 16:56:57:834 876 7e4 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
  2014-12-14 16:56:57:834 876 7e4 Misc Microsoft signed: Yes
  2014-12-14 16:56:57:850 876 7e4 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
  2014-12-14 16:56:57:850 876 7e4 Misc Microsoft signed: Yes
  2014-12-14 16:56:57:850 876 7e4 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
  2014-12-14 16:56:57:866 876 7e4 Misc Microsoft signed: Yes
  2014-12-14 16:56:57:881 876 7e4 Setup Determining whether a new setup handler needs to be downloaded
  2014-12-14 16:56:57:881 876 7e4 Setup SelfUpdate handler is not found.  It will be downloaded
  2014-12-14 16:56:57:881 876 7e4 Setup Evaluating applicability of setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~x86~~7.6.7600.256"
  2014-12-14 16:56:58:584 876 7e4 Setup Setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~x86~~7.6.7600.256" is already installed.
  2014-12-14 16:56:58:584 876 7e4 Setup Evaluating applicability of setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~x86~~7.6.7600.256"
  2014-12-14 16:56:58:616 876 7e4 Setup Setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~x86~~7.6.7600.256" is already installed.
  2014-12-14 16:56:58:616 876 7e4 Setup Evaluating applicability of setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~x86~~7.6.7600.256"
  2014-12-14 16:56:58:647 876 7e4 Setup Setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~x86~~7.6.7600.256" is already installed.
  2014-12-14 16:56:58:647 876 7e4 Setup SelfUpdate check completed.  SelfUpdate is NOT required.
  2014-12-14 16:56:58:725 876 7e4 PT +++++++++++  PT: Synchronizing server updates  +++++++++++
  2014-12-14 16:56:58:725 876 7e4 PT  + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://WSUSSERVER/ClientWebService/client.asmx
  2014-12-14 16:56:58:819 876 7e4 PT Initializing simple targeting cookie, clientId = 1cc4458c-92f7-49cd-a1d4-7415e09d8f84, target group = ccop_test, DNS name = cwc-3
  2014-12-14 16:56:58:819 876 7e4 PT  Server URL = http://WSUSSERVER/SimpleAuthWebService/SimpleAuth.asmx
  2014-12-14 16:56:58:850 876 7e4 Agent  * Found 0 updates and 0 categories in search; evaluated appl. rules of 0 out of 0 deployed entities
  2014-12-14 16:56:58:881 876 7e4 Agent *********
  2014-12-14 16:56:58:881 876 7e4 Agent **  END  **  Agent: Finding updates [CallerId = AutomaticUpdates]
  2014-12-14 16:56:58:881 876 7e4 Agent *************
  2014-12-14 16:56:58:881 876 dd0 AU >>##  RESUMED  ## AU: Search for updates [CallId = {CF5777B0-92F4-42D3-8480-F1A570AA266C}]
  2014-12-14 16:56:58:881 876 dd0 AU  # 0 updates detected
  2014-12-14 16:56:58:881 876 dd0 AU #########
  2014-12-14 16:56:58:881 876 dd0 AU ##  END  ##  AU: Search for updates [CallId = {CF5777B0-92F4-42D3-8480-F1A570AA266C}]
  2014-12-14 16:56:58:881 876 dd0 AU #############
  2014-12-14 16:56:58:881 876 dd0 AU Successfully wrote event for AU health state:0
  2014-12-14 16:56:58:881 876 dd0 AU Featured notifications is disabled.
  2014-12-14 16:56:58:881 876 dd0 AU AU setting next detection timeout to 2014-12-14 22:49:14
  2014-12-14 16:56:58:881 876 dd0 AU Successfully wrote event for AU health state:0
  2014-12-14 16:56:58:881 876 dd0 AU Successfully wrote event for AU health state:0
  2014-12-14 16:57:03:881 876 7e4 Report REPORT EVENT: {7DCA3700-ADF2-4C99-A8E6-79B72FC997D0} 2014-12-14 16:56:58:881-0500 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software Synchronization Windows Update Client successfully detected 0 updates.
  2014-12-14 16:57:03:881 876 7e4 Report REPORT EVENT: {6AEEF3F7-D167-4F00-9AE4-293124E7147A} 2014-12-14 16:56:58:881-0500 1 156 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Pre-Deployment Check Reporting client status.
  2014-12-14 16:57:03:881 876 7e4 Report CWERReporter finishing event handling. (00000000)
  2014-12-14 17:07:08:022 876 7e4 Report Uploading 2 events using cached cookie, reporting URL = http://WSUSSERVER/ReportingWebService/ReportingWebService.asmx
  2014-12-14 17:07:08:038 876 7e4 Report Reporter successfully uploaded 2 events.

  My WSUS server is stating the following about this computer:
  Installed/Not Applicable Percentage=100%
  Updates with errors: 0
  Updates needed: 0
  Updates installed/not applicable: 4552
  Updates with no status: 0

  So it's still saying 0 across the board...?

  Monday, December 15, 2014 3:34 AM
• 

  

  0

  Sign in to vote

  2014-12-13 20:27:33:105 876 b80 Agent * Found 0 updates and 0 categories in search; evaluated appl. rules of 0 out of 0 deployed entities

  There are still NO updates available for this system. More significantly is the second half of this statement... there are NO updates *applicable* to this system.

  I've run the client commands and after 30min, the following output is below

  Unfortunately you did not run them as written, since I seen no evidence of a restart or service start at the head of this logfile.

  The client reported in to WSUS (Last Status Report), but it still says:
  Updates with errors: 0
  Updates needed: 0
  Updates installed/not applicable: 27969
  Updates with no status: 0

  There's only a very few scenarios I know of that can cause this result, and they are:

  • When the machine really is =100%= fully patched. (Note: I've never actually seen a machine in this state, but I've heard that it does happen from time to time.)
  • When updates for this client's operating system are not being synchronized to the WSUS server.
  • When the machine does not have the latest service pack installed, in which case, it's entirely possible that there are ZERO applicable updates.

  Had the logfile been completed, as requested, I could have verified/excluded the third option, but given the logfile entry "evaluated appl. rules of 0 out of 0 deployed entities" almost certainly it's one of the latter two reasons.

  ---

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

  Monday, December 15, 2014 9:17 PM
• 

  

  0

  Sign in to vote

  My apologies, I forgot to do the reboot prior.

  WSUS Data:
  Unapproved updates: 0
  Approved updates: 6510 (I accidentally removed some latest packages that weren't superseded, so I added and downloaded them back again)
  Declined updates: 34354

  My client is running Win7 Pro 32bit (no SP installed) and it now states the following (after recording the time and rebooting):

  2014-12-15 15:55:04:082 876 bc0 Shutdwn user declined update at shutdown
  2014-12-15 15:55:04:082 876 bc0 AU Successfully wrote event for AU health state:0
  2014-12-15 15:55:04:082 876 bc0 AU AU initiates service shutdown
  2014-12-15 15:55:04:082 876 bc0 AU ###########  AU: Uninitializing Automatic Updates  ###########
  2014-12-15 15:55:04:691 876 bc0 Report CWERReporter finishing event handling. (00000000)
  2014-12-15 15:55:04:707 876 bc0 Service *********
  2014-12-15 15:55:04:707 876 bc0 Service **  END  **  Service: Service exit [Exit code = 0x240001]
  2014-12-15 15:55:04:707 876 bc0 Service *************
  2014-12-15 15:56:48:565 872 be0 Misc ===========  Logging initialized (build: 7.6.7600.256, tz: -0500)  ===========
  2014-12-15 15:56:48:565 872 be0 Misc  = Process: C:\Windows\system32\svchost.exe
  2014-12-15 15:56:48:565 872 be0 Misc  = Module: c:\windows\system32\wuaueng.dll
  2014-12-15 15:56:48:565 872 be0 Service *************
  2014-12-15 15:56:48:565 872 be0 Service ** START **  Service: Service startup
  2014-12-15 15:56:48:565 872 be0 Service *********
  2014-12-15 15:56:48:581 872 be0 Agent  * WU client version 7.6.7600.256
  2014-12-15 15:56:48:581 872 be0 Agent  * Base directory: C:\Windows\SoftwareDistribution
  2014-12-15 15:56:48:596 872 be0 Agent  * Access type: No proxy
  2014-12-15 15:56:48:596 872 be0 Agent  * Network state: Connected
  2014-12-15 15:56:48:815 872 7e4 Report CWERReporter::Init succeeded
  2014-12-15 15:56:48:815 872 7e4 Agent ***********  Agent: Initializing Windows Update Agent  ***********
  2014-12-15 15:56:48:815 872 7e4 Agent ***********  Agent: Initializing global settings cache  ***********
  2014-12-15 15:56:48:815 872 7e4 Agent  * WSUS server: http://WSUSSERVER
  2014-12-15 15:56:48:815 872 7e4 Agent  * WSUS status server: http://WSUSSERVER
  2014-12-15 15:56:48:815 872 7e4 Agent  * Target group: ccop_test
  2014-12-15 15:56:48:815 872 7e4 Agent  * Windows Update access disabled: No
  2014-12-15 15:56:48:815 872 7e4 DnldMgr Download manager restoring 0 downloads
  2014-12-15 15:56:48:815 872 7e4 AU ###########  AU: Initializing Automatic Updates  ###########
  2014-12-15 15:56:48:815 872 7e4 AU  # WSUS server: http://WSUSSERVER
  2014-12-15 15:56:48:815 872 7e4 AU  # Detection frequency: 1
  2014-12-15 15:56:48:815 872 7e4 AU  # Target group: ccop_test
  2014-12-15 15:56:48:815 872 7e4 AU  # Approval type: Pre-download notify (Policy)
  2014-12-15 15:56:49:315 872 be0 Report ***********  Report: Initializing static reporting data  ***********
  2014-12-15 15:56:49:315 872 be0 Report  * OS Version = 6.1.7600.0.0.65792
  2014-12-15 15:56:49:315 872 be0 Report  * OS Product Type = 0x00000030
  2014-12-15 15:56:49:346 872 be0 Report  * Computer Brand = Red Hat
  2014-12-15 15:56:49:346 872 be0 Report  * Computer Model = KVM
  2014-12-15 15:56:49:362 872 be0 Report  * Bios Revision = 0.5.1
  2014-12-15 15:56:49:362 872 be0 Report  * Bios Name = Default System BIOS
  2014-12-15 15:56:49:362 872 be0 Report  * Bios Release Date = 2007-01-01T00:00:00
  2014-12-15 15:56:49:362 872 be0 Report  * Locale ID = 1033
  2014-12-15 15:56:49:377 872 7e4 AU Successfully wrote event for AU health state:0
  2014-12-15 15:56:49:377 872 7e4 AU Initializing featured updates
  2014-12-15 15:56:49:393 872 7e4 AU Found 0 cached featured updates
  2014-12-15 15:56:49:393 872 7e4 AU Successfully wrote event for AU health state:0
  2014-12-15 15:56:49:393 872 7e4 AU Successfully wrote event for AU health state:0
  2014-12-15 15:56:49:393 872 7e4 AU AU finished delayed initialization
  2014-12-15 15:56:49:393 872 7e4 AU Triggering AU detection through DetectNow API
  2014-12-15 15:56:49:393 872 7e4 AU Triggering Online detection (non-interactive)
  2014-12-15 15:56:49:409 872 be0 AU #############
  2014-12-15 15:56:49:409 872 be0 AU ## START ##  AU: Search for updates
  2014-12-15 15:56:49:409 872 be0 AU #########
  2014-12-15 15:56:49:471 872 be0 AU <<## SUBMITTED ## AU: Search for updates [CallId = {D686311E-4F1B-4B9B-BC27-3762E7383E3B}]
  2014-12-15 15:56:49:471 872 c20 Agent *************
  2014-12-15 15:56:49:471 872 c20 Agent ** START **  Agent: Finding updates [CallerId = AutomaticUpdates]
  2014-12-15 15:56:49:471 872 c20 Agent *********
  2014-12-15 15:56:49:471 872 c20 Agent  * Online = Yes; Ignore download priority = No
  2014-12-15 15:56:49:471 872 c20 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"
  2014-12-15 15:56:49:471 872 c20 Agent  * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
  2014-12-15 15:56:49:471 872 c20 Agent  * Search Scope = {Machine}
  2014-12-15 15:56:49:471 872 c20 Setup Checking for agent SelfUpdate
  2014-12-15 15:56:49:487 872 c20 Setup Client version: Core: 7.6.7600.256  Aux: 7.6.7600.256
  2014-12-15 15:56:49:487 872 c20 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
  2014-12-15 15:56:49:518 872 c20 Misc Microsoft signed: Yes
  2014-12-15 15:56:52:112 872 c20 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
  2014-12-15 15:56:52:112 872 c20 Misc Microsoft signed: Yes
  2014-12-15 15:56:52:159 872 c20 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
  2014-12-15 15:56:52:190 872 c20 Misc Microsoft signed: Yes
  2014-12-15 15:56:52:190 872 c20 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
  2014-12-15 15:56:52:206 872 c20 Misc Microsoft signed: Yes
  2014-12-15 15:56:52:518 872 c20 Setup Determining whether a new setup handler needs to be downloaded
  2014-12-15 15:56:52:518 872 c20 Setup SelfUpdate handler is not found.  It will be downloaded
  2014-12-15 15:56:52:534 872 c20 Setup Evaluating applicability of setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~x86~~7.6.7600.256"
  2014-12-15 15:56:53:549 872 c20 Setup Setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~x86~~7.6.7600.256" is already installed.
  2014-12-15 15:56:53:549 872 c20 Setup Evaluating applicability of setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~x86~~7.6.7600.256"
  2014-12-15 15:56:53:581 872 c20 Setup Setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~x86~~7.6.7600.256" is already installed.
  2014-12-15 15:56:53:581 872 c20 Setup Evaluating applicability of setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~x86~~7.6.7600.256"
  2014-12-15 15:56:53:612 872 c20 Setup Setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~x86~~7.6.7600.256" is already installed.
  2014-12-15 15:56:53:612 872 c20 Setup SelfUpdate check completed.  SelfUpdate is NOT required.
  2014-12-15 15:56:53:737 872 c20 PT +++++++++++  PT: Synchronizing server updates  +++++++++++
  2014-12-15 15:56:53:737 872 c20 PT  + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://WSUSSERVER/ClientWebService/client.asmx
  2014-12-15 15:56:53:768 872 c20 PT Initializing simple targeting cookie, clientId = 1cc4458c-92f7-49cd-a1d4-7415e09d8f84, target group = ccop_test, DNS name = cwc-3
  2014-12-15 15:56:53:768 872 c20 PT  Server URL = http://WSUSSERVER/SimpleAuthWebService/SimpleAuth.asmx
  2014-12-15 15:56:53:846 872 c20 Agent  * Found 0 updates and 0 categories in search; evaluated appl. rules of 0 out of 0 deployed entities
  2014-12-15 15:56:53:877 872 c20 Agent *********
  2014-12-15 15:56:53:877 872 c20 Agent **  END  **  Agent: Finding updates [CallerId = AutomaticUpdates]
  2014-12-15 15:56:53:877 872 c20 Agent *************
  2014-12-15 15:56:53:877 872 c9c AU >>##  RESUMED  ## AU: Search for updates [CallId = {D686311E-4F1B-4B9B-BC27-3762E7383E3B}]
  2014-12-15 15:56:53:877 872 c9c AU  # 0 updates detected
  2014-12-15 15:56:53:877 872 c9c AU #########
  2014-12-15 15:56:53:877 872 c9c AU ##  END  ##  AU: Search for updates [CallId = {D686311E-4F1B-4B9B-BC27-3762E7383E3B}]
  2014-12-15 15:56:53:877 872 c9c AU #############
  2014-12-15 15:56:53:877 872 c9c AU Successfully wrote event for AU health state:0
  2014-12-15 15:56:53:877 872 c9c AU Featured notifications is disabled.
  2014-12-15 15:56:53:877 872 c9c AU AU setting next detection timeout to 2014-12-15 21:56:01
  2014-12-15 15:56:53:877 872 c9c AU Successfully wrote event for AU health state:0
  2014-12-15 15:56:53:877 872 c9c AU Successfully wrote event for AU health state:0
  2014-12-15 15:56:53:893 872 c20 Report REPORT EVENT: {A6EDD2B2-FEEA-4A9A-BEB5-BED71570C771} 2014-12-15 15:56:53:877-0500 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software Synchronization Windows Update Client successfully detected 0 updates.
  2014-12-15 15:56:53:924 872 c20 Report CWERReporter finishing event handling. (00000000)
  2014-12-15 15:56:58:877 872 c20 Report REPORT EVENT: {850C3E6E-2F5D-4361-A0C1-C7C65E26B9F3} 2014-12-15 15:56:53:877-0500 1 156 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Pre-Deployment Check Reporting client status.
  2014-12-15 15:56:58:877 872 c20 Report CWERReporter finishing event handling. (00000000)
  2014-12-15 15:59:43:081 872 c20 Report Uploading 2 events using cached cookie, reporting URL = http://WSUSSERVER/ReportingWebService/ReportingWebService.asmx
  2014-12-15 15:59:43:096 872 c20 Report Reporter successfully uploaded 2 events.

  WSUS is still showing:
  Updates with errors: 0
  Updates needed: 0
  Updates installed/not applicable: 6510
  Updates with no status: 0

  It could still possibly be reason #3, but wouldn't SP1 come up as an available package to be installed?  I have the SP packages in my WSUS...

  • Edited by Dean Berman Tuesday, December 16, 2014 1:58 AM update

  Tuesday, December 16, 2014 1:57 AM
• 

  

  0

  Sign in to vote

  My client is running Win7 Pro 32bit (no SP installed)
  

  Well. THERE it is! There have been NO updates available for Windows 7 RTM since April, 2013 (IIRC). Install Service Pack 1 and miraculously about 300+ updates will suddenly be "Needed".

  2014-12-15 15:56:49:315 872 be0 Report * OS Version = 6.1.7600.0.0.65792

  This is the line from the logfile that would have told me you were missing Service Pack 1.

  It could still possibly be reason #3, but wouldn't SP1 come up as an available package to be installed?

  Only if you've synchronized the Service Packs update classification *AND* the necessary prerequisites for Service Pack 1 have been installed.

  ---

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

  Tuesday, December 16, 2014 6:07 PM
• 

  

  0

  Sign in to vote

  Ok, SP1 is installed on the Win7 32bit OS.  WSUS shows the following info:

  Unapproved updates: 9
  Approved updates: 6501
  Declined updates: 34363

  This client in particular:

  Updates with errors: 0
  Updates needed: 0
  Updates installed/not applicable: 6510
  Updates with no status: 0

  I ran the commands again on the client:

  2014-12-16 11:14:11:932 844 c74 Shutdwn user declined update at shutdown
  2014-12-16 11:14:11:932 844 c74 AU Successfully wrote event for AU health state:0
  2014-12-16 11:14:11:932 844 c74 AU AU initiates service shutdown
  2014-12-16 11:14:11:932 844 c74 AU ###########  AU: Uninitializing Automatic Updates  ###########
  2014-12-16 11:14:19:151 844 c74 Report CWERReporter finishing event handling. (00000000)
  2014-12-16 11:14:19:198 844 c74 Service *********
  2014-12-16 11:14:19:198 844 c74 Service **  END  **  Service: Service exit [Exit code = 0x240001]
  2014-12-16 11:14:19:198 844 c74 Service *************
  2014-12-16 11:16:52:686 824 a30 Misc ===========  Logging initialized (build: 7.6.7600.256, tz: -0500)  ===========
  2014-12-16 11:16:52:702 824 a30 Misc  = Process: C:\Windows\system32\svchost.exe
  2014-12-16 11:16:52:702 824 a30 Misc  = Module: c:\windows\system32\wuaueng.dll
  2014-12-16 11:16:52:686 824 a30 Service *************
  2014-12-16 11:16:52:702 824 a30 Service ** START **  Service: Service startup
  2014-12-16 11:16:52:702 824 a30 Service *********
  2014-12-16 11:16:52:717 824 a30 Agent  * WU client version 7.6.7600.256
  2014-12-16 11:16:52:733 824 a30 Agent  * Base directory: C:\Windows\SoftwareDistribution
  2014-12-16 11:16:52:733 824 a30 Agent  * Access type: No proxy
  2014-12-16 11:16:52:733 824 a30 Agent  * Network state: Connected
  2014-12-16 11:16:52:889 824 258 Report CWERReporter::Init succeeded
  2014-12-16 11:16:52:889 824 258 Agent ***********  Agent: Initializing Windows Update Agent  ***********
  2014-12-16 11:16:52:889 824 258 Agent ***********  Agent: Initializing global settings cache  ***********
  2014-12-16 11:16:52:889 824 258 Agent  * WSUS server: http://WSUSSERVER
  2014-12-16 11:16:52:889 824 258 Agent  * WSUS status server: http://WSUSSERVER
  2014-12-16 11:16:52:889 824 258 Agent  * Target group: ccop_test
  2014-12-16 11:16:52:889 824 258 Agent  * Windows Update access disabled: No
  2014-12-16 11:16:52:889 824 258 DnldMgr Download manager restoring 0 downloads
  2014-12-16 11:16:52:905 824 258 AU ###########  AU: Initializing Automatic Updates  ###########
  2014-12-16 11:16:52:905 824 258 AU  # WSUS server: http://WSUSSERVER
  2014-12-16 11:16:52:905 824 258 AU  # Detection frequency: 1
  2014-12-16 11:16:52:905 824 258 AU  # Target group: ccop_test
  2014-12-16 11:16:52:905 824 258 AU  # Approval type: Pre-download notify (Policy)
  2014-12-16 11:16:53:327 824 a30 Report ***********  Report: Initializing static reporting data  ***********
  2014-12-16 11:16:53:327 824 a30 Report  * OS Version = 6.1.7601.1.0.65792
  2014-12-16 11:16:53:327 824 a30 Report  * OS Product Type = 0x00000030
  2014-12-16 11:16:53:358 824 a30 Report  * Computer Brand = Red Hat
  2014-12-16 11:16:53:358 824 a30 Report  * Computer Model = KVM
  2014-12-16 11:16:53:358 824 a30 Report  * Bios Revision = 0.5.1
  2014-12-16 11:16:53:358 824 a30 Report  * Bios Name = Default System BIOS
  2014-12-16 11:16:53:358 824 a30 Report  * Bios Release Date = 2007-01-01T00:00:00
  2014-12-16 11:16:53:358 824 a30 Report  * Locale ID = 1033
  2014-12-16 11:16:53:389 824 258 AU Successfully wrote event for AU health state:0
  2014-12-16 11:16:53:389 824 258 AU Initializing featured updates
  2014-12-16 11:16:53:389 824 258 AU Found 0 cached featured updates
  2014-12-16 11:16:53:389 824 258 AU Successfully wrote event for AU health state:0
  2014-12-16 11:16:53:389 824 258 AU Successfully wrote event for AU health state:0
  2014-12-16 11:16:53:389 824 258 AU AU finished delayed initialization
  2014-12-16 11:16:53:405 824 258 AU Triggering AU detection through DetectNow API
  2014-12-16 11:16:53:405 824 258 AU Triggering Online detection (non-interactive)
  2014-12-16 11:16:53:405 824 a30 AU #############
  2014-12-16 11:16:53:405 824 a30 AU ## START ##  AU: Search for updates
  2014-12-16 11:16:53:405 824 a30 AU #########
  2014-12-16 11:16:53:483 824 a30 AU <<## SUBMITTED ## AU: Search for updates [CallId = {9DBA9FF6-5F6E-4EDC-9E2E-3CFA76A70C33}]
  2014-12-16 11:16:53:483 824 a70 Agent *************
  2014-12-16 11:16:53:483 824 a70 Agent ** START **  Agent: Finding updates [CallerId = AutomaticUpdates]
  2014-12-16 11:16:53:483 824 a70 Agent *********
  2014-12-16 11:16:53:483 824 a70 Agent  * Online = Yes; Ignore download priority = No
  2014-12-16 11:16:53:483 824 a70 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"
  2014-12-16 11:16:53:483 824 a70 Agent  * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
  2014-12-16 11:16:53:483 824 a70 Agent  * Search Scope = {Machine}
  2014-12-16 11:16:53:483 824 a70 Setup Checking for agent SelfUpdate
  2014-12-16 11:16:53:483 824 a70 Setup Client version: Core: 7.6.7600.256  Aux: 7.6.7600.256
  2014-12-16 11:16:53:483 824 a70 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
  2014-12-16 11:16:53:530 824 a70 Misc Microsoft signed: Yes
  2014-12-16 11:16:56:170 824 a70 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
  2014-12-16 11:16:56:170 824 a70 Misc Microsoft signed: Yes
  2014-12-16 11:16:56:217 824 a70 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
  2014-12-16 11:16:56:233 824 a70 Misc Microsoft signed: Yes
  2014-12-16 11:16:56:249 824 a70 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
  2014-12-16 11:16:56:249 824 a70 Misc Microsoft signed: Yes
  2014-12-16 11:16:56:374 824 a70 Setup Determining whether a new setup handler needs to be downloaded
  2014-12-16 11:16:56:374 824 a70 Setup SelfUpdate handler is not found.  It will be downloaded
  2014-12-16 11:16:56:374 824 a70 Setup Evaluating applicability of setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~x86~~7.6.7600.256"
  2014-12-16 11:16:57:952 824 a70 Setup Setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~x86~~7.6.7600.256" is already installed.
  2014-12-16 11:16:57:952 824 a70 Setup Evaluating applicability of setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~x86~~7.6.7600.256"
  2014-12-16 11:16:57:983 824 a70 Setup Setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~x86~~7.6.7600.256" is already installed.
  2014-12-16 11:16:57:983 824 a70 Setup Evaluating applicability of setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~x86~~7.6.7600.256"
  2014-12-16 11:16:58:030 824 a70 Setup Setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~x86~~7.6.7600.256" is already installed.
  2014-12-16 11:16:58:030 824 a70 Setup SelfUpdate check completed.  SelfUpdate is NOT required.
  2014-12-16 11:16:58:186 824 a70 PT +++++++++++  PT: Synchronizing server updates  +++++++++++
  2014-12-16 11:16:58:186 824 a70 PT  + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://WSUSSERVER/ClientWebService/client.asmx
  2014-12-16 11:16:58:202 824 a70 PT Initializing simple targeting cookie, clientId = 1cc4458c-92f7-49cd-a1d4-7415e09d8f84, target group = ccop_test, DNS name = cwc-3
  2014-12-16 11:16:58:202 824 a70 PT  Server URL = http://WSUSSERVER/SimpleAuthWebService/SimpleAuth.asmx
  2014-12-16 11:16:58:280 824 a70 Agent  * Found 0 updates and 0 categories in search; evaluated appl. rules of 0 out of 0 deployed entities
  2014-12-16 11:16:58:311 824 a70 Agent *********
  2014-12-16 11:16:58:311 824 a70 Agent **  END  **  Agent: Finding updates [CallerId = AutomaticUpdates]
  2014-12-16 11:16:58:311 824 a70 Agent *************
  2014-12-16 11:16:58:311 824 ab8 AU >>##  RESUMED  ## AU: Search for updates [CallId = {9DBA9FF6-5F6E-4EDC-9E2E-3CFA76A70C33}]
  2014-12-16 11:16:58:311 824 ab8 AU  # 0 updates detected
  2014-12-16 11:16:58:311 824 ab8 AU #########
  2014-12-16 11:16:58:311 824 ab8 AU ##  END  ##  AU: Search for updates [CallId = {9DBA9FF6-5F6E-4EDC-9E2E-3CFA76A70C33}]
  2014-12-16 11:16:58:311 824 ab8 AU #############
  2014-12-16 11:16:58:311 824 ab8 AU Successfully wrote event for AU health state:0
  2014-12-16 11:16:58:311 824 ab8 AU Featured notifications is disabled.
  2014-12-16 11:16:58:311 824 ab8 AU AU setting next detection timeout to 2014-12-16 17:10:12
  2014-12-16 11:16:58:311 824 ab8 AU Successfully wrote event for AU health state:0
  2014-12-16 11:16:58:311 824 ab8 AU Successfully wrote event for AU health state:0
  2014-12-16 11:16:58:311 824 a70 Report REPORT EVENT: {2463ADF8-5EDD-4C49-AF20-8DB5F8566223} 2014-12-16 11:16:58:311-0500 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software Synchronization Windows Update Client successfully detected 0 updates.
  2014-12-16 11:16:58:342 824 a70 Report CWERReporter finishing event handling. (00000000)
  2014-12-16 11:17:03:311 824 a70 Report REPORT EVENT: {7894B298-7793-44BA-A2D1-570149C6BCC5} 2014-12-16 11:16:58:311-0500 1 156 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Pre-Deployment Check Reporting client status.
  2014-12-16 11:17:03:311 824 a70 Report CWERReporter finishing event handling. (00000000)
  2014-12-16 11:19:43:249 824 a70 Report Uploading 6 events using cached cookie, reporting URL = http://WSUSSERVER/ReportingWebService/ReportingWebService.asmx
  2014-12-16 11:19:43:249 824 a70 Report Reporter successfully uploaded 6 events.

  ...more to come in the next post...

  Tuesday, December 16, 2014 8:36 PM
• 

  

  0

  Sign in to vote

  On the client, I then opened Windows Update and ran the "Check for updates" and it came back with 0 updates.  Here's the log output below:

  2014-12-16 11:36:18:259  824 fac AU Triggering AU detection through DetectNow API
  2014-12-16 11:36:18:259  824 fac AU Triggering Online detection (interactive)
  2014-12-16 11:36:18:259  824 a30 AU #############
  2014-12-16 11:36:18:259  824 a30 AU ## START ##  AU: Search for updates
  2014-12-16 11:36:18:259  824 a30 AU #########
  2014-12-16 11:36:18:275  824 a30 AU <<## SUBMITTED ## AU: Search for updates [CallId = {FEBE7563-F299-49B4-A857-BAB5BFB75778}]
  2014-12-16 11:36:18:275  824 b38 Agent *************
  2014-12-16 11:36:18:275  824 b38 Agent ** START **  Agent: Finding updates [CallerId = AutomaticUpdates]
  2014-12-16 11:36:18:275  824 b38 Agent *********
  2014-12-16 11:36:18:275  824 b38 Agent   * Online = Yes; Ignore download priority = No
  2014-12-16 11:36:18:275  824 b38 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"
  2014-12-16 11:36:18:275  824 b38 Agent   * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
  2014-12-16 11:36:18:275  824 b38 Agent   * Search Scope = {Machine}
  2014-12-16 11:36:18:275  824 b38 Setup Checking for agent SelfUpdate
  2014-12-16 11:36:18:275  824 b38 Setup Client version: Core: 7.6.7600.256  Aux: 7.6.7600.256
  2014-12-16 11:36:18:275  824 b38 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
  2014-12-16 11:36:18:291  824 b38 Misc  Microsoft signed: Yes
  2014-12-16 11:36:18:306  824 b38 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
  2014-12-16 11:36:18:306  824 b38 Misc  Microsoft signed: Yes
  2014-12-16 11:36:18:322  824 b38 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
  2014-12-16 11:36:18:322  824 b38 Misc  Microsoft signed: Yes
  2014-12-16 11:36:18:337  824 b38 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
  2014-12-16 11:36:18:337  824 b38 Misc  Microsoft signed: Yes
  2014-12-16 11:36:18:384  824 b38 Setup Determining whether a new setup handler needs to be downloaded
  2014-12-16 11:36:18:384  824 b38 Setup SelfUpdate handler is not found.  It will be downloaded
  2014-12-16 11:36:18:384  824 b38 Setup Evaluating applicability of setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~x86~~7.6.7600.256"
  2014-12-16 11:36:19:275  824 b38 Setup Setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~x86~~7.6.7600.256" is already installed.
  2014-12-16 11:36:19:275  824 b38 Setup Evaluating applicability of setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~x86~~7.6.7600.256"
  2014-12-16 11:36:19:291  824 b38 Setup Setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~x86~~7.6.7600.256" is already installed.
  2014-12-16 11:36:19:291  824 b38 Setup Evaluating applicability of setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~x86~~7.6.7600.256"
  2014-12-16 11:36:19:322  824 b38 Setup Setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~x86~~7.6.7600.256" is already installed.
  2014-12-16 11:36:19:322  824 b38 Setup SelfUpdate check completed.  SelfUpdate is NOT required.
  2014-12-16 11:36:19:384  824 b38 PT +++++++++++  PT: Synchronizing server updates  +++++++++++
  2014-12-16 11:36:19:384  824 b38 PT   + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://WSUSSERVER/ClientWebService/client.asmx
  2014-12-16 11:36:19:525  824 b38 Agent   * Found 0 updates and 0 categories in search; evaluated appl. rules of 0 out of 0 deployed entities
  2014-12-16 11:36:19:572  824 b38 Agent *********
  2014-12-16 11:36:19:572  824 b38 Agent **  END  **  Agent: Finding updates [CallerId = AutomaticUpdates]
  2014-12-16 11:36:19:572  824 b38 Agent *************
  2014-12-16 11:36:19:572  824 454 AU >>##  RESUMED  ## AU: Search for updates [CallId = {FEBE7563-F299-49B4-A857-BAB5BFB75778}]
  2014-12-16 11:36:19:572  824 454 AU   # 0 updates detected
  2014-12-16 11:36:19:572  824 454 AU #########
  2014-12-16 11:36:19:572  824 454 AU ##  END  ##  AU: Search for updates [CallId = {FEBE7563-F299-49B4-A857-BAB5BFB75778}]
  2014-12-16 11:36:19:572  824 454 AU #############
  2014-12-16 11:36:19:572  824 454 AU Successfully wrote event for AU health state:0
  2014-12-16 11:36:19:572  824 454 AU Featured notifications is disabled.
  2014-12-16 11:36:19:572  824 454 AU AU setting next detection timeout to 2014-12-16 17:26:50
  2014-12-16 11:36:19:572  824 454 AU Successfully wrote event for AU health state:0
  2014-12-16 11:36:19:572  824 454 AU Successfully wrote event for AU health state:0
  2014-12-16 11:36:24:572  824 b38 Report REPORT EVENT: {C3CD0348-E442-4990-BA0A-4C9B2FADBF86} 2014-12-16 11:36:19:572-0500 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software Synchronization Windows Update Client successfully detected 0 updates.
  2014-12-16 11:36:24:572  824 b38 Report REPORT EVENT: {4D23C8CC-1C13-4476-A465-96C77AA3B477} 2014-12-16 11:36:19:572-0500 1 156 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Pre-Deployment Check Reporting client status.
  2014-12-16 11:36:24:572  824 b38 Report CWERReporter finishing event handling. (00000000)

  
  

  Tuesday, December 16, 2014 8:36 PM
• 

  

  0

  Sign in to vote

  Ok, SP1 is installed on the Win7 32bit OS.

  How *exactly* did you obtain SP1 for installation? Quite likely you are still missing other requisite updates, such as KB2533552.

  And, forgive my impertinence, but you DO actually have =Windows 7= updates synchronized to the WSUS server?

  ---

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

  Wednesday, December 17, 2014 4:22 PM
• 

  

  0

  Sign in to vote

  Please forgive my lack of knowledge, we don't have anyone here on my team who's used WSUS before, we are trying to get some kinks worked out (obviously) before we move on to live testing.

  I downloaded SP1 from here: https://www.microsoft.com/en-us/download/details.aspx?id=5842
  windows6.1-KB976932-X86.exe

  My client is indeed checking in with my WSUS server.

  My WSUS server is synchronized daily with the Microsoft Windows Update server.

  My client does not have KB2533552 installed.  I've downloaded it from here: http://www.microsoft.com/en-us/download/details.aspx?id=18257

  I am installing it now...more to come as soon as I have an update for you after that...

  Wednesday, December 17, 2014 6:56 PM
• 

  

  0

  Sign in to vote

  Here's the output of the WindowsUpdate.log file after:
  1) Installed KB2533552
  2) Rebooted
  3) wuauclt /resetauthorization /detectnow
  4) Waited >30min

  ...sorry if it's more than what was run after the 30min, I forgot the time I ran it, so I copied and pasted below what I believe was within the 30min...

  2014-12-17 09:58:26:466 3832 f04 COMAPI -----------  COMAPI: IUpdateServiceManager::RemoveService  -----------
  2014-12-17 09:58:26:466 3832 f04 COMAPI  - ServiceId = {056616f4-7d5c-4160-9105-76c6606ed3bf}
  2014-12-17 09:58:26:607 3832 f04 COMAPI IUpdateService removing volatile scan package service, serviceID = {056616F4-7D5C-4160-9105-76C6606ED3BF}
  2014-12-17 09:58:26:607 820 ecc Agent WARNING: WU client fails CClientCallRecorder::RemoveService with error 0x80248014
  2014-12-17 09:58:26:607 3832 f04 COMAPI WARNING: ISusInternal::RemoveService failed, hr=80248014
  2014-12-17 09:58:35:268 820 7cc Shutdwn user declined update at shutdown
  2014-12-17 09:58:35:284 820 7cc AU Successfully wrote event for AU health state:0
  2014-12-17 09:58:35:284 820 7cc AU AU initiates service shutdown
  2014-12-17 09:58:35:284 820 7cc AU ###########  AU: Uninitializing Automatic Updates  ###########
  2014-12-17 09:58:43:831 820 7cc Report CWERReporter finishing event handling. (00000000)
  2014-12-17 09:58:44:081 820 7cc Service *********
  2014-12-17 09:58:44:081 820 7cc Service **  END  **  Service: Service exit [Exit code = 0x240001]
  2014-12-17 09:58:44:081 820 7cc Service *************
  2014-12-17 10:00:17:220 860 b70 Misc ===========  Logging initialized (build: 7.6.7600.256, tz: -0500)  ===========
  2014-12-17 10:00:17:220 860 b70 Misc  = Process: C:\Windows\system32\svchost.exe
  2014-12-17 10:00:17:220 860 b70 Misc  = Module: c:\windows\system32\wuaueng.dll
  2014-12-17 10:00:17:220 860 b70 Service *************
  2014-12-17 10:00:17:220 860 b70 Service ** START **  Service: Service startup
  2014-12-17 10:00:17:220 860 b70 Service *********
  2014-12-17 10:00:17:251 860 b70 Agent  * WU client version 7.6.7600.256
  2014-12-17 10:00:17:251 860 b70 Agent  * Base directory: C:\Windows\SoftwareDistribution
  2014-12-17 10:00:17:251 860 b70 Agent  * Access type: No proxy
  2014-12-17 10:00:17:251 860 b70 Agent  * Network state: Connected
  2014-12-17 10:00:17:517 860 550 Report CWERReporter::Init succeeded
  2014-12-17 10:00:17:517 860 550 Agent ***********  Agent: Initializing Windows Update Agent  ***********
  2014-12-17 10:00:17:517 860 550 Agent ***********  Agent: Initializing global settings cache  ***********
  2014-12-17 10:00:17:517 860 550 Agent  * WSUS server: http://WSUSSERVER
  2014-12-17 10:00:17:517 860 550 Agent  * WSUS status server: http://WSUSSERVER
  2014-12-17 10:00:17:517 860 550 Agent  * Target group: ccop_test
  2014-12-17 10:00:17:517 860 550 Agent  * Windows Update access disabled: No
  2014-12-17 10:00:17:533 860 550 DnldMgr Download manager restoring 0 downloads
  2014-12-17 10:00:17:533 860 550 AU ###########  AU: Initializing Automatic Updates  ###########
  2014-12-17 10:00:17:533 860 550 AU  # WSUS server: http://WSUSSERVER
  2014-12-17 10:00:17:533 860 550 AU  # Detection frequency: 1
  2014-12-17 10:00:17:533 860 550 AU  # Target group: ccop_test
  2014-12-17 10:00:17:533 860 550 AU  # Approval type: Pre-download notify (Policy)
  2014-12-17 10:00:17:970 860 b70 Report ***********  Report: Initializing static reporting data  ***********
  2014-12-17 10:00:17:970 860 b70 Report  * OS Version = 6.1.7601.1.0.65792
  2014-12-17 10:00:17:970 860 b70 Report  * OS Product Type = 0x00000030
  2014-12-17 10:00:18:001 860 b70 Report  * Computer Brand = Red Hat
  2014-12-17 10:00:18:001 860 b70 Report  * Computer Model = KVM
  2014-12-17 10:00:18:017 860 b70 Report  * Bios Revision = 0.5.1
  2014-12-17 10:00:18:017 860 b70 Report  * Bios Name = Default System BIOS
  2014-12-17 10:00:18:017 860 b70 Report  * Bios Release Date = 2007-01-01T00:00:00
  2014-12-17 10:00:18:017 860 b70 Report  * Locale ID = 1033
  2014-12-17 10:00:18:033 860 550 AU Successfully wrote event for AU health state:0
  2014-12-17 10:00:18:033 860 550 AU Initializing featured updates
  2014-12-17 10:00:18:033 860 550 AU Found 0 cached featured updates
  2014-12-17 10:00:18:033 860 550 AU Successfully wrote event for AU health state:0
  2014-12-17 10:00:18:033 860 550 AU Successfully wrote event for AU health state:0
  2014-12-17 10:00:18:033 860 550 AU AU finished delayed initialization
  2014-12-17 10:00:18:033 860 550 AU Triggering AU detection through DetectNow API
  2014-12-17 10:00:18:033 860 550 AU Triggering Online detection (non-interactive)
  2014-12-17 10:00:18:048 860 b70 AU #############
  2014-12-17 10:00:18:048 860 b70 AU ## START ##  AU: Search for updates
  2014-12-17 10:00:18:048 860 b70 AU #########
  2014-12-17 10:00:18:111 860 b70 AU <<## SUBMITTED ## AU: Search for updates [CallId = {99C72633-3952-4FC5-8026-686E3FD11445}]
  2014-12-17 10:00:18:111 860 bb0 Agent *************
  2014-12-17 10:00:18:111 860 bb0 Agent ** START **  Agent: Finding updates [CallerId = AutomaticUpdates]
  2014-12-17 10:00:18:111 860 bb0 Agent *********
  2014-12-17 10:00:18:111 860 bb0 Agent  * Online = Yes; Ignore download priority = No
  2014-12-17 10:00:18:111 860 bb0 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"
  2014-12-17 10:00:18:111 860 bb0 Agent  * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
  2014-12-17 10:00:18:111 860 bb0 Agent  * Search Scope = {Machine}
  2014-12-17 10:00:18:111 860 bb0 Setup Checking for agent SelfUpdate
  2014-12-17 10:00:18:126 860 bb0 Setup Client version: Core: 7.6.7600.256  Aux: 7.6.7600.256
  2014-12-17 10:00:18:126 860 bb0 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
  2014-12-17 10:00:18:158 860 bb0 Misc Microsoft signed: Yes
  2014-12-17 10:00:20:736 860 bb0 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
  2014-12-17 10:00:20:751 860 bb0 Misc Microsoft signed: Yes
  2014-12-17 10:00:20:783 860 bb0 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
  2014-12-17 10:00:20:798 860 bb0 Misc Microsoft signed: Yes
  2014-12-17 10:00:20:814 860 bb0 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
  2014-12-17 10:00:20:814 860 bb0 Misc Microsoft signed: Yes
  2014-12-17 10:00:20:970 860 bb0 Setup Determining whether a new setup handler needs to be downloaded
  2014-12-17 10:00:20:970 860 bb0 Setup SelfUpdate handler is not found.  It will be downloaded
  2014-12-17 10:00:20:970 860 bb0 Setup Evaluating applicability of setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~x86~~7.6.7600.256"
  2014-12-17 10:00:22:142 860 bb0 Setup Setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~x86~~7.6.7600.256" is already installed.
  2014-12-17 10:00:22:142 860 bb0 Setup Evaluating applicability of setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~x86~~7.6.7600.256"
  2014-12-17 10:00:22:330 860 bb0 Setup Setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~x86~~7.6.7600.256" is already installed.
  2014-12-17 10:00:22:330 860 bb0 Setup Evaluating applicability of setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~x86~~7.6.7600.256"
  2014-12-17 10:00:22:611 860 bb0 Setup Setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~x86~~7.6.7600.256" is already installed.
  2014-12-17 10:00:22:611 860 bb0 Setup SelfUpdate check completed.  SelfUpdate is NOT required.
  2014-12-17 10:00:22:783 860 bb0 PT +++++++++++  PT: Synchronizing server updates  +++++++++++
  2014-12-17 10:00:22:783 860 bb0 PT  + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://WSUSSERVER/ClientWebService/client.asmx
  2014-12-17 10:00:22:798 860 bb0 PT WARNING: Cached cookie has expired or new PID is available
  2014-12-17 10:00:22:798 860 bb0 PT Initializing simple targeting cookie, clientId = 1cc4458c-92f7-49cd-a1d4-7415e09d8f84, target group = ccop_test, DNS name = cwc-3
  2014-12-17 10:00:22:798 860 bb0 PT  Server URL = http://WSUSSERVER/SimpleAuthWebService/SimpleAuth.asmx
  2014-12-17 10:00:22:861 860 bb0 Agent  * Found 0 updates and 0 categories in search; evaluated appl. rules of 0 out of 0 deployed entities
  2014-12-17 10:00:22:892 860 bb0 Agent *********
  2014-12-17 10:00:22:892 860 bb0 Agent **  END  **  Agent: Finding updates [CallerId = AutomaticUpdates]
  2014-12-17 10:00:22:892 860 bb0 Agent *************
  2014-12-17 10:00:22:892 860 bec AU >>##  RESUMED  ## AU: Search for updates [CallId = {99C72633-3952-4FC5-8026-686E3FD11445}]
  2014-12-17 10:00:22:892 860 bec AU  # 0 updates detected
  2014-12-17 10:00:22:892 860 bec AU #########
  2014-12-17 10:00:22:892 860 bec AU ##  END  ##  AU: Search for updates [CallId = {99C72633-3952-4FC5-8026-686E3FD11445}]
  2014-12-17 10:00:22:892 860 bec AU #############
  2014-12-17 10:00:22:892 860 bec AU Successfully wrote event for AU health state:0
  2014-12-17 10:00:22:892 860 bec AU Featured notifications is disabled.
  2014-12-17 10:00:22:892 860 bec AU AU setting next detection timeout to 2014-12-17 15:55:05
  2014-12-17 10:00:22:892 860 bec AU Successfully wrote event for AU health state:0
  2014-12-17 10:00:22:892 860 bec AU Successfully wrote event for AU health state:0
  2014-12-17 10:00:22:908 860 bb0 Report REPORT EVENT: {A1E17DAA-2AD5-4630-A5EC-37723B7374AD} 2014-12-17 10:00:22:892-0500 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software Synchronization Windows Update Client successfully detected 0 updates.
  2014-12-17 10:00:22:939 860 bb0 Report CWERReporter finishing event handling. (00000000)
  2014-12-17 10:00:27:892 860 bb0 Report REPORT EVENT: {32FEE3AC-B414-4D3F-BE2B-EFFDDF9009F8} 2014-12-17 10:00:22:892-0500 1 156 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Pre-Deployment Check Reporting client status.
  2014-12-17 10:00:27:892 860 bb0 Report CWERReporter finishing event handling. (00000000)
  2014-12-17 10:11:09:064 860 bb0 Report Uploading 2 events using cached cookie, reporting URL = http://WSUSSERVER/ReportingWebService/ReportingWebService.asmx
  2014-12-17 10:11:09:080 860 bb0 Report Reporter successfully uploaded 2 events.

  Wednesday, December 17, 2014 7:30 PM
• 

  

  0

  Sign in to vote

  Please forgive my lack of knowledge, we don't have anyone here on my team who's used WSUS before

  Understood, but this issue really has very little to do with WSUS and everything to do with understanding Microsoft's lifecycle polices with respect to service packs and end-of-life dates ... a practice which really hasn't changed much at all in the past five years.

  I downloaded SP1 from here: https://www.microsoft.com/en-us/download/details.aspx?id=5842
  windows6.1-KB976932-X86.exe

  Good information, which tells me that you are absolutely missing KB2533522 which is a required baseline Servicing Stack Update.

  ---

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

  Thursday, December 18, 2014 4:09 PM
• 

  

  0

  Sign in to vote

  Okay..so next step...

  2014-12-17 10:00:17:533 860 550 AU # Detection frequency: 1

  Please change this to at least 2 hours. When using Server-Side Targeting (you are not), the group membership changes made at the console are obtained by the client system when the targeting cookie is expired and refreshed. The targeting cookie has an expiration time of 60 minutes. Unfortunately, with a 1 hour detection frequency, the detection actually occurs every (60-20%)=48-60 minutes, and as a result the targeting cookie never expires, and the client never gets group change information from the WSUS server.

  This is also one of the reasons why the /resetauthorization parameter is specified in the CheckForUpdates that is launched in my instructions after the system restart -- to ensure the targeting cookie is re-initialized.

  2014-12-17 10:00:17:533 860 550 AU # Approval type: Pre-download notify (Policy)

  Also, you've configured this client as Notify-For-Download... so the client is NEVER going to download anything on its own. It will require a user to launch the Control Panel WUApp and initiate the download of updates that need to be installed. More importantly.. to REMEMBER to do that!

  2014-12-17 10:00:18:001 860 b70 Report * Computer Brand = Red Hat
  2014-12-17 10:00:18:001 860 b70 Report * Computer Model = KVM

  Just to confirm, in case it becomes relevant... this machine is a VM running on KVM?

  2014-12-17 10:00:17:517 860 550 Agent * Target group: ccop_test

  2014-12-17 10:00:22:798 860 bb0 PT Initializing simple targeting cookie, clientId = 1cc4458c-92f7-49cd-a1d4-7415e09d8f84, target group = ccop_test, DNS name = cwc-3

  You appear to be using Client-Side Targeting in this instance.

  • Does the group ccop_test actually exist on the WSUS server?
  • Does this client cwc-3 appear as a member of the ccop_test group in the WSUS console?

  2014-12-17 10:00:22:861 860 bb0 Agent * Found 0 updates and 0 categories in search; evaluated appl. rules of 0 out of 0 deployed entities

  And still this client finds **ZERO** updates available on this WSUS server to scan!

  My understanding is that *ALL* of your clients are exhibiting this same behavior. Notwithstanding the question of whether all of your other Windows 7 clients were (are) also missing Service Pack 1, but having ensured that *this* client is actually capable of being patched, we're now faced with the more fundamental question of whether your WSUS server is actually working or not.

  • Have you confirmed that the WSUS server is operational by configuring the WSUS server to be a client of itself?
  • Are there ANY client systems that can successfully execute a scan against this WSUS server and get results?

  If not, then here's my next question: When this problem first appeared "months ago" (August? June? March?)... what CHANGED on the WSUS server? To wit: When *exactly* did you install any of the patches to this WSUS server, to include KB2720211, KB2734608, KB2828185, or KB2938066. After installing those patches, did you confirm the WSUS server was fully operational?

  ---

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

  Thursday, December 18, 2014 4:33 PM
• 

  

  0

  Sign in to vote

  Detection Freq on my client wasn't configured originally, so it was defaulted to 1, so I've changed it to 2 hours.  I've also set my client to auto download and notify for install and restarted the client.

  That is correct, my client is running as a VM on a linux KVM system.

  Regarding the group name, this might be the problem...I have the group name "ccop_test" on the client, but inside WSUS, I have the computer assigned to a different group "ccop_test_win7_32bit".  WSUS shows me the computer assigned to that group...but you're telling me that it's checking for a "ccop_test" group.  I'm going to change it in the registry to be the one that's in WSUS (so WSUS, the client registry, and the logs are all matching), restart the client, then run through the commands again.  I will re-post once I have an update, hopefully shortly...

  Thursday, December 18, 2014 7:28 PM
• 

  

  0

  Sign in to vote

  I have the group name "ccop_test" on the client, but inside WSUS, I have the computer assigned to a different group "ccop_test_win7_32bit".

  The fact that you were able to assign group membership on the console also means that you have not properly set Options->Computers to "Use Group Policy...."

  I'm going to change it in the registry to be the one that's in WSUS (so WSUS, the client registry, and the logs are all matching), restart the client, then run through the commands again.

  That won't do you a darn bit of good if the GROUP POLICY being assigned to that client is assigning a DIFFERENT group name! In fact, the mere act of restarting the computer will cause the GPO to be reapplied and completely overwrite any changes you made.

  ---

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

  Thursday, December 18, 2014 7:53 PM
• 

  

  0

  Sign in to vote

  You are correct, we are not using Group Policy settings to override anything, except for in:
  gpedit.msc...Computer Configuration...Administrative Templates...Windows Components...Windows Update:
  Configure Automatic Updates=3
  Specify intranet Microsoft update service location=http://wsusserver/
  automatic Updates detection frequency=2

  In the registry, someone set a few additional settings, which are:
  

  [HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\WindowsUpdate]
  "DisableWindowsUpdateAccess"=dword:0
  "ElevateNonAdmins"=dword:0
  "TargetGroup"="ccop_test" (which is now changed to ccop_test_win7_32bit)
  "TargetGroupEnabled"=dword:1 (which is now set to 0)
  "WUServer"="http://wsusserver"
  "WUStatusServer"="http://wsusserver"
  [HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer]
  "NoWindowsUpdate"=dword:0
  [HKEY_LOCAL_MACHINE\System\Internet Communication Management\Internet Communication]
  "DisableWindowsUpdateAccess"=dword:0
  [HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\WindowsUpdate\AU]
  "AUOptions"=dword:2
  "AutoInstallMinorUpdates"=dword:0
  "DetectionFrequency"=dword:1 (which is now set to 2)
  "DetectionFrequencyEnabled"=dword:1
  "NoAutoRebootWithLoggedOnUsers"=dword:1
  "NoAutoUpdate"=dword:0
  "RebootRelaunchTimeoutEnabled"=dword:0
  "RebootWarningTimeoutEnabled"=dword:0
  "RescheduleWaitTimeEnabled"=dword:0
  "UseWUServer"=dword:1

  Thursday, December 18, 2014 8:10 PM
• 

  

  0

  Sign in to vote

  You are correct, we are not using Group Policy settings to override anything

  Why would you put PART of the configuration in a GPO, and HACK the registry to implement the rest???

  Configure Automatic Updates=3

  "AUOptions"=dword:2

  In addition, you have CONFLICTING settings between the claimed settings in the GPO and the claimed settings in the registry.

  After you re-hacked the registry... did you restart the Windows Update service (or reboot the client)?

  ---

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

  Thursday, December 18, 2014 11:33 PM
• 

  

  0

  Sign in to vote

  I did the GPEDIT method, a script that the other developers runs directly into the registry.  I'd rather not use the registry values and just set the minimum necessary fields in GPEDIT and have the WSUS server handle the assignments/configurations/etc.  How can I reset the registry values so they are more of a "default" setting, then allow GPEDIT to do what it needs to do?

  The computer has been restarted numerous times since these settings were put in place.

  Friday, December 19, 2014 4:09 AM
• 

  

  0

  Sign in to vote

  I did the GPEDIT method, a script that the other developers runs directly into the registry.  I'd rather not use the registry values and just set the minimum necessary fields in GPEDIT and have the WSUS server handle the assignments/configurations/etc.  How can I reset the registry values so they are more of a "default" setting, then allow GPEDIT to do what it needs to do?

  It sounds to me like a review of this section of the Deployment Guide might be helpful:

  Update and Configure the Automatic Updates Client Computer

  Also, make sure you fully understand the relationship between Group Policy, Local Policy, and the registry entries created by policy.

  The WSUS server doesn't "handle" anything. The WUAgent is configured how its configured and that's how it behaves. The only thing the WSUS server does is provide information upon request.

  ---

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

  Friday, December 19, 2014 5:57 PM
• 

  

  1

  Sign in to vote

  Thank you for sending that over to me.  After some conflicting information (by using group policy and editing the registry directly), I believe my issue(s) have been found.  I'm now using the registry settings and my systems seem to be re-checking in correctly, as well as popping up with notifications regarding pending/approved packages.  I'm running some more tests, but should know for sure within a couple of days if this was indeed the fix.

  Monday, December 22, 2014 6:06 AM
• 

  

  0

  Sign in to vote

  You are my hero!  That was the problem.  GP and LP (registry) were having some issues talking together.  I've removed the GP settings and updated the LP settings and reset the connections to the WSUS server and they started showing up again.

  Another thing I'm noticing (which almost seems like a problem, but from you're telling me, this is the way it should work):  in the registry, I'm telling it which group to connect to and query, but when it connects to the WSUS server, it shows up as unassigned and not in the group I tell it to be in.  I still have to go into WSUS and assign it to the appropriate group for it to work...

  I'm going to setup another test VM client to confirm this, but it was weird that it happened this way...?

  Tuesday, December 30, 2014 7:32 PM
• 

  

  0

  Sign in to vote

  Another thing I'm noticing (which almost seems like a problem, but from you're telling me, this is the way it should work):  in the registry, I'm telling it which group to connect to and query, but when it connects to the WSUS server, it shows up as unassigned and not in the group I tell it to be in.  I still have to go into WSUS and assign it to the appropriate group for it to work...

  The fact that you *can* use the WSUS console to assign group memberships tells us exactly what is wrong.

  If you want to use Client-Side Targeting (e.g. assign group memberships via registry settings), then the Options->Computers setting in the WSUS console MUST be set to "Use Group Policy...".

  Essentially what is happening is that the client is trying to tell the WSUS server what group(s) the client belongs to because the client knows that it is authoritative, but the WSUS server thinks that *IT* is authoritative because it's not been told otherwise. Setting Options->Computers to "Use Group Policy.." tells the WSUS server to consider the client authoritative for group membership assignments.

  ---

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

  Wednesday, December 31, 2014 5:20 PM