locked
WSUS Client is not updating while it is connected to the WSUS Server RRS feed

  • Question

  • HI Guys,

    Good day. I am having an issue in getting the updates to be pushed from WSUS Server into  one of my Test Client. The environment is as below:

    WSUS Server : Win Server 2003 R2 SP2 (with internet connection) (IP: 192.168.207.188)
    (Version: 3.2.7600.226)

    WSUS Client : Win Server 2008 R2  Standard (without internet connection, but connected through local network to the server) (192.168.207.130)

    The Client can be found in Admin Console of the server, and all updates have been approved (Critical and Security updates only).

    However, I could not get the updates to be downloaded and installed in the Client, despite there is no error message in the WindowsUpdate.log file. Below is what can be found in the log file of the Client:

    2017-03-07 16:16:40:147   872 55c Service ** START ** Service: Service startup
    2017-03-07 16:16:40:147   872 55c Service *********
    2017-03-07 16:16:40:303   872 55c Agent   * WU client version 7.6.7600.320
    2017-03-07 16:16:40:303   872 55c Agent   * Base directory: C:\Windows\SoftwareDistribution
    2017-03-07 16:16:40:303   872 55c Agent   * Access type: No proxy
    2017-03-07 16:16:40:319   872 55c Agent   * Network state: Connected
    2017-03-07 16:17:25:887   872 55c Report CWERReporter::Init succeeded
    2017-03-07 16:17:25:887   872 55c Agent *********** Agent: Initializing Windows Update Agent ***********
    2017-03-07 16:17:25:902   872 55c Agent   * Prerequisite roots succeeded.
    2017-03-07 16:17:25:902   872 55c Agent *********** Agent: Initializing global settings cache ***********
    2017-03-07 16:17:25:902   872 55c Agent   * WSUS server: http://192.168.207.188:8530
    2017-03-07 16:17:25:902   872 55c Agent   * WSUS status server: http://192.168.207.188:8530
    2017-03-07 16:17:25:902   872 55c Agent   * Target group: (Unassigned Computers)
    2017-03-07 16:17:25:902   872 55c Agent   * Windows Update access disabled: No
    2017-03-07 16:17:25:902   872 55c DnldMgr Download manager restoring 0 downloads
    2017-03-07 16:17:25:902   872 55c AU ########### AU: Initializing Automatic Updates ###########
    2017-03-07 16:17:25:902   872 55c AU AU setting next detection timeout to 2017-03-07 08:17:25
    2017-03-07 16:17:25:902   872 55c AU   # WSUS server: http://192.168.207.188:8530
    2017-03-07 16:17:25:902   872 55c AU   # Detection frequency: 1
    2017-03-07 16:17:25:902   872 55c AU   # Approval type: Scheduled (Policy)
    2017-03-07 16:17:25:902   872 55c AU   # Scheduled install day/time: Every day at 16:00
    2017-03-07 16:17:25:902   872 55c AU   # Auto-install minor updates: Yes (User preference)
    2017-03-07 16:17:25:902   872 55c AU   # Will interact with non-admins (Non-admins are elevated (User preference))
    2017-03-07 16:17:25:902   872 55c AU   # Will display featured software notifications (Policy)
    2017-03-07 16:17:25:902   872 55c AU Setting AU scheduled install time to 2017-03-08 08:00:00
    2017-03-07 16:17:26:089   872 55c Report *********** Report: Initializing static reporting data ***********
    2017-03-07 16:17:26:089   872 55c Report   * OS Version = 6.1.7601.1.0.196880
    2017-03-07 16:17:26:089   872 55c Report   * OS Product Type = 0x00000007
    2017-03-07 16:17:26:121   872 55c Report   * Computer Brand = HP
    2017-03-07 16:17:26:121   872 55c Report   * Computer Model = ProLiant DL380p Gen8
    2017-03-07 16:17:26:121   872 55c Report   * Bios Revision = P70
    2017-03-07 16:17:26:121   872 55c Report   * Bios Name = Default System BIOS
    2017-03-07 16:17:26:121   872 55c Report   * Bios Release Date = 2014-02-10T00:00:00
    2017-03-07 16:17:26:121   872 55c Report   * Locale ID = 1033
    2017-03-07 16:17:26:136   872 55c AU Successfully wrote event for AU health state:0
    2017-03-07 16:17:26:136   872 55c AU Initializing featured updates
    2017-03-07 16:17:26:136   872 55c AU Found 0 cached featured updates
    2017-03-07 16:17:26:136   872 55c AU Successfully wrote event for AU health state:0
    2017-03-07 16:17:26:136   872 55c AU Successfully wrote event for AU health state:0
    2017-03-07 16:17:26:136   872 55c AU AU finished delayed initialization
    2017-03-07 16:17:26:136   872 55c AU #############
    2017-03-07 16:17:26:136   872 55c AU ## START ## AU: Search for updates
    2017-03-07 16:17:26:136   872 55c AU #########
    2017-03-07 16:17:26:152   872 55c AU <<## SUBMITTED ## AU: Search for updates [CallId = {89669659-231A-41EE-828E-0B20399757F0}]
    2017-03-07 16:17:26:152   872 284 Agent *************
    2017-03-07 16:17:26:152   872 284 Agent ** START ** Agent: Finding updates [CallerId = AutomaticUpdates]
    2017-03-07 16:17:26:152   872 284 Agent *********
    2017-03-07 16:17:26:152   872 284 Agent   * Online = Yes; Ignore download priority = No
    2017-03-07 16:17:26:152   872 284 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"
    2017-03-07 16:17:26:152   872 284 Agent   * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
    2017-03-07 16:17:26:152   872 284 Agent   * Search Scope = {Machine}
    2017-03-07 16:17:26:152   872 284 Setup Checking for agent SelfUpdate
    2017-03-07 16:17:26:152   872 284 Setup Client version: Core: 7.6.7600.320 Aux: 7.6.7600.320
    2017-03-07 16:17:28:788   872 284 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab with dwProvFlags 0x00000080:
    2017-03-07 16:17:44:560   872 284 Misc   Microsoft signed: NA
    2017-03-07 16:17:44:607   872 284 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\TMP5427.tmp with dwProvFlags 0x00000080:
    2017-03-07 16:18:05:495   872 284 Misc   Microsoft signed: NA
    2017-03-07 16:18:05:511   872 284 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab with dwProvFlags 0x00000080:
    2017-03-07 16:18:21:173   872 284 Misc   Microsoft signed: NA
    2017-03-07 16:18:21:392   872 284 Setup Determining whether a new setup handler needs to be downloaded
    2017-03-07 16:18:21:392   872 284 Setup SelfUpdate handler is not found. It will be downloaded
    2017-03-07 16:18:21:392   872 284 Setup Evaluating applicability of setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.320"
    2017-03-07 16:18:21:392   872 284 Setup Setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.320" is already installed.
    2017-03-07 16:18:21:392   872 284 Setup Evaluating applicability of setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.320"
    2017-03-07 16:18:21:438   872 284 Setup Setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.320" is already installed.
    2017-03-07 16:18:21:438   872 284 Setup Evaluating applicability of setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.320"
    2017-03-07 16:18:21:485   872 284 Setup Setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.320" is already installed.
    2017-03-07 16:18:21:485   872 284 Setup SelfUpdate check completed. SelfUpdate is NOT required.
    2017-03-07 16:18:21:672   872 284 PT +++++++++++ PT: Synchronizing server updates +++++++++++
    2017-03-07 16:18:21:672   872 284 PT   + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://192.168.207.188:8530/ClientWebService/client.asmx
    2017-03-07 16:18:21:735   872 284 PT WARNING: Cached cookie has expired or new PID is available
    2017-03-07 16:18:21:735   872 284 PT Initializing simple targeting cookie, clientId = c83a9b7d-2618-4544-9a0b-df66a7015304, target group = , DNS name = wsus-clienttest
    2017-03-07 16:18:21:735   872 284 PT   Server URL = http://192.168.207.188:8530/SimpleAuthWebService/SimpleAuth.asmx
    2017-03-07 16:24:01:893   872 284 PT +++++++++++ PT: Synchronizing extended update info +++++++++++
    2017-03-07 16:24:01:893   872 284 PT   + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://192.168.207.188:8530/ClientWebService/client.asmx
    2017-03-07 17:30:15:018   872 f10 AU Triggering AU detection through DetectNow API
    2017-03-07 17:30:15:018   872 f10 AU Piggybacking on an AU detection already in progress
    2017-03-07 17:49:01:490   872 d74 AU Triggering AU detection through DetectNow API
    2017-03-07 17:49:01:490   872 d74 AU Piggybacking on an AU detection already in progress
    2017-03-07 18:01:50:728   872 55c AU AU received policy change subscription event
    2017-03-07 18:01:50:728   872 55c AU AU Options changed from policy.
    2017-03-07 18:01:50:728   872 55c AU Successfully wrote event for AU health state:0
    2017-03-07 18:01:50:728   872 55c AU ########### AU: Policy change processed ###########
    2017-03-07 18:01:50:728   872 55c AU   # Policy changed, AU refresh required = No
    2017-03-07 18:01:50:728   872 55c AU   # WSUS server: http://192.168.207.188:8530
    2017-03-07 18:01:50:728   872 55c AU   # Detection frequency: 1
    2017-03-07 18:01:50:728   872 55c AU   # Approval type: Scheduled (Policy)
    2017-03-07 18:01:50:728   872 55c AU   # Scheduled install day/time: Every day at 19:00
    2017-03-07 18:01:50:728   872 55c AU   # Auto-install minor updates: Yes (User preference)
    2017-03-07 18:01:50:728   872 55c AU   # Will interact with non-admins (Non-admins are elevated (User preference))
    2017-03-07 18:01:50:728   872 55c AU   # Will display featured software notifications (Policy)
    2017-03-07 18:01:50:728   872 55c AU AU settings changed through Policy.
    2017-03-07 18:01:50:728   872 55c AU Setting AU scheduled install time to 2017-03-07 11:00:00
    2017-03-07 18:01:50:728   872 55c AU Successfully wrote event for AU health state:0
    2017-03-07 18:01:50:728   872 55c AU Successfully wrote event for AU health state:0
    2017-03-07 18:01:59:745   872 55c AU AU received policy change subscription event
    2017-03-07 18:02:32:770   872 ec8 AU Triggering AU detection through DetectNow API
    2017-03-07 18:02:32:770   872 ec8 AU Piggybacking on an AU detection already in progress
    2017-03-07 18:29:40:009   872 55c AU AU setting next sqm report timeout to 2017-03-08 10:29:40
    2017-03-07 19:00:10:001   872 55c AU Forced install timer expired for scheduled install
    2017-03-07 19:00:10:001   872 55c AU UpdateDownloadProperties: 0 download(s) are still in progress.
    2017-03-07 19:00:10:001   872 55c AU Setting AU scheduled install time to 2017-03-08 11:00:00
    2017-03-07 19:00:10:001   872 55c AU Successfully wrote event for AU health state:0
    2017-03-08 10:05:36:410   872 55c AU AU received policy change subscription event
    2017-03-08 10:05:36:410   872 55c AU AU Options changed from policy.
    2017-03-08 10:05:36:410   872 55c AU Successfully wrote event for AU health state:0
    2017-03-08 10:05:36:410   872 55c AU ########### AU: Policy change processed ###########
    2017-03-08 10:05:36:410   872 55c AU   # Policy changed, AU refresh required = No
    2017-03-08 10:05:36:410   872 55c AU   # WSUS server: http://192.168.207.188:8530
    2017-03-08 10:05:36:410   872 55c AU   # Detection frequency: 1
    2017-03-08 10:05:36:410   872 55c AU   # Approval type: Scheduled (Policy)
    2017-03-08 10:05:36:410   872 55c AU   # Scheduled install day/time: Every day at 11:00
    2017-03-08 10:05:36:410   872 55c AU   # Auto-install minor updates: Yes (User preference)
    2017-03-08 10:05:36:410   872 55c AU   # Will interact with non-admins (Non-admins are elevated (User preference))
    2017-03-08 10:05:36:410   872 55c AU   # Will display featured software notifications (Policy)
    2017-03-08 10:05:36:410   872 55c AU AU settings changed through Policy.
    2017-03-08 10:05:36:410   872 55c AU Setting AU scheduled install time to 2017-03-08 03:00:00
    2017-03-08 10:05:36:410   872 55c AU Successfully wrote event for AU health state:0
    2017-03-08 10:05:36:410   872 55c AU Successfully wrote event for AU health state:0
    2017-03-08 10:06:01:230   872 c58 AU Triggering AU detection through DetectNow API
    2017-03-08 10:06:01:230   872 c58 AU Piggybacking on an AU detection already in progress
    2017-03-08 11:00:10:013   872 55c AU Forced install timer expired for scheduled install
    2017-03-08 11:00:10:013   872 55c AU UpdateDownloadProperties: 0 download(s) are still in progress.
    2017-03-08 11:00:10:013   872 55c AU Setting AU scheduled install time to 2017-03-09 03:00:00
    2017-03-08 11:00:10:013   872 55c AU Successfully wrote event for AU health state:0
    2017-03-08 11:26:25:179   872 11c AU Triggering AU detection through DetectNow API
    2017-03-08 11:26:25:179   872 11c AU Piggybacking on an AU detection already in progress


    Note: 

    1) I have run  wuauclt /resetauthorization  and /detectnow commands a few times without any luck
    2) SolarWinds Client Diagnostic Tool shows everything is fine
    3) Tried to set the IIS with and without Directory Browsing (and monitored for a few days, still no changes)
    4) Cleared the SUSID and SUSClientID
    5) Re-format the client PC
    6) Deleted SoftwareDistribution folder

    7) Enabled Anonymous Access in IIS setting
    8) Created "selfupdate" virtual directory in IIS

    I have tried all the possible solutions that I found online, but with no luck. Appreciate if anyone can point out  what did I do wrong so that I can get this to work, as this is my first time to set up WSUS.

    Thanks in advance.

    Farid

    Wednesday, March 8, 2017 6:14 AM

All replies

  • Hi Farid,

    >WSUS Server : Win Server 2003 R2 SP2 (with internet connection) (IP: 192.168.207.188)
    (Version: 3.2.7600.226)

    Since server 2003 is out of support, I would suggest you install WSUS on server 2012, 2012R2 or 2016, so that you may get better support;

    >WSUS server: http://192.168.207.188:8530

    WSUS 2003 use http port 80 and https port 443 by default, do you change the port manually to http 8530? If not, then the port is not correct;

    >The Client can be found in Admin Console of the server, and all updates have been approved (Critical and Security updates only).

    Could you provide the related screenshot of the WSUS server, WSUS clients need to show up in the WSUS console and "report" to the WSUS server, do clients report to the WSUS server that there are updates needed to be installed?

    Please try resetting windows update components on the clients, check if it could help:

    https://support.microsoft.com/en-us/kb/971058

    Best Regards,

    Anne


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.


    Wednesday, March 8, 2017 8:36 AM
  • Hi Anne, 

    Thanks for your prompt response. Kindly refer below:

    1) Since server 2003 is out of support, I would suggest you install WSUS on server 2012, 2012R2 or 2006, so that you may get better support

    -The issue is, this WSUS server existed before i joined this company, and once worked fine. One day, the person in-charge left the company, and it stopped working (that's what i got to know from my colleagues). We are going to migrate to new OS but it's still need some authorization and takes time. So for the time being, we are just using what we already have here. 

    2) WSUS 2003 use http port 80 and https port 443 by default, do you change the port manually to http 8530? If not, then the port is not correct;

    - At first, I thought that was the issue. I have tested port 80, 443, 8530, and 8531. After checking through and testing all of it, only port 8530 works while other ports showed connection error. Thus I can say that the previous admin has customed the port to 8530.

    3) Could you provide the related screenshot of the WSUS server, WSUS clients need to show up in the WSUS console and "report" to the WSUS server, do clients report to the WSUS server that there are updates needed to be installed?

    -Sure, please refer to the link below:
    https://social.technet.microsoft.com/Forums/getfile/1012272

    4) I have also done the update reset, yet nothing seems to be working.

    Thanks.

    Wednesday, March 8, 2017 9:34 AM
  • Hi Farid Buhari,

    Please run Server Cleanup Wizard and reindex WSUS database on the WSUS server, check if it could help:

    https://technet.microsoft.com/en-us/library/dd939795(v=ws.10).aspx

    Best Regards,

    Anne


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.


    Monday, March 13, 2017 9:27 AM
  • I would suggest just building a WSUS from scratch at this point. It will take the same amount of time to clean up the previous WSUS server. Just a thought.
    Monday, March 13, 2017 1:52 PM