WSUS Client is not updating while it is connected to the WSUS Server

-

hi guys,

day. having issue in getting updates pushed wsus server  one of test client. environment 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, connected through local network server) (192.168.207.130)

client can found in admin console of server, , updates have been approved (critical , security updates only).

however, not updates downloaded , installed in client, despite there no error message in windowsupdate.log file. below can found in log file of 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 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 @ 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   # interact non-admins (non-admins elevated (user preference))
2017-03-07 16:17:25:902   872 55c au   # display featured software notifications (policy)
2017-03-07 16:17:25:902   872 55c au setting au scheduled install time 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 wrote event 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 wrote event au health state:0
2017-03-07 16:17:26:136   872 55c au wrote event 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 updates
2017-03-07 16:17:26:136   872 55c au #########
2017-03-07 16:17:26:152   872 55c au <<## submitted ## au: search 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 , deploymentaction='installation' or ispresent=1 , deploymentaction='uninstallation' or isinstalled=1 , deploymentaction='installation' , rebootrequired=1 or isinstalled=0 , deploymentaction='uninstallation' , 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 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 c:\windows\softwaredistribution\selfupdate\wuident.cab 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 c:\windows\softwaredistribution\selfupdate\tmp5427.tmp 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 c:\windows\softwaredistribution\selfupdate\wsus3setup.cab 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 new setup handler needs downloaded
2017-03-07 16:18:21:392   872 284 setup selfupdate handler not found. 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" 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" 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" installed.
2017-03-07 16:18:21:485   872 284 setup selfupdate check completed. selfupdate 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 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 au detection 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 au detection 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 policy.
2017-03-07 18:01:50:728   872 55c au wrote event 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 @ 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   # interact non-admins (non-admins elevated (user preference))
2017-03-07 18:01:50:728   872 55c au   # 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 2017-03-07 11:00:00
2017-03-07 18:01:50:728   872 55c au wrote event au health state:0
2017-03-07 18:01:50:728   872 55c au wrote event 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 au detection in progress
2017-03-07 18:29:40:009   872 55c au au setting next sqm report timeout 2017-03-08 10:29:40
2017-03-07 19:00:10:001   872 55c au forced install timer expired scheduled install
2017-03-07 19:00:10:001   872 55c au updatedownloadproperties: 0 download(s) still in progress.
2017-03-07 19:00:10:001   872 55c au setting au scheduled install time 2017-03-08 11:00:00
2017-03-07 19:00:10:001   872 55c au wrote event 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 policy.
2017-03-08 10:05:36:410   872 55c au wrote event 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 @ 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   # interact non-admins (non-admins elevated (user preference))
2017-03-08 10:05:36:410   872 55c au   # 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 2017-03-08 03:00:00
2017-03-08 10:05:36:410   872 55c au wrote event au health state:0
2017-03-08 10:05:36:410   872 55c au wrote event 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 au detection in progress
2017-03-08 11:00:10:013   872 55c au forced install timer expired scheduled install
2017-03-08 11:00:10:013   872 55c au updatedownloadproperties: 0 download(s) still in progress.
2017-03-08 11:00:10:013   872 55c au setting au scheduled install time 2017-03-09 03:00:00
2017-03-08 11:00:10:013   872 55c au wrote event 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 au detection in progress


note: 

1) have run  wuauclt /resetauthorization  and /detectnow commands few times without luck
2) solarwinds client diagnostic tool shows fine
3) tried set iis , without directory browsing (and monitored few days, still no changes)
4) cleared susid , susclientid
5) re-format client pc
6) deleted softwaredistribution folder

7) enabled anonymous access in iis setting
8) created "selfupdate" virtual directory in iis

have tried possible solutions found online, no luck. appreciate if can point out  what did wrong can work, first time set wsus.

in advance.

farid

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 out of support, suggest install wsus on server 2012, 2012r2 or 2016, may better support;

>wsus server: http://192.168.207.188:8530

wsus 2003 use http port 80 , https port 443 default, change port manually http 8530? if not, port not correct;

>the client can found in admin console of server, , updates have been approved (critical , security updates only).

could provide related screenshot of wsus server, wsus clients need show in wsus console , "report" wsus server, clients report wsus server there updates needed installed?

please try resetting windows update components on clients, check if help:

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

best regards,

anne

please remember mark replies answers if help.
if have feedback technet subscriber support, contact tnmff@microsoft.com.




Windows Server  >  WSUS



Comments

Post a Comment

Popular posts from this blog

Error: 0x80073701 when trying to add Print Services Role in Windows 2012 Standard

-
hello, i'm getting error when trying add print services role in windows 2012 standard. i'm getting same error whether use gui or powershell. this new server install. the powershell error follows: add-windowsfeature : request add or remove features on specified server failed. installation of 1 or more roles, role services, or features failed. the referenced assembly not found. error: 0x80073701 at line:1 char:1 + add-windowsfeature print-services + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     + categoryinfo          : invalidoperation: (@{vhd=; credent...name=localhost}:psobject) [install-windowsfeature],     exception     + fullyqualifiederrorid : dismapi_error__failed_to_enable_updates,microsoft.windows.servermanager.commands.addwind    owsfeaturecommand success restart needed exit code      feature result ------- ------...
Read more

Windows 2016 RDS event 1306 Connection Broker Client failed to redirect the user... Error: NULL

-
Image
i'm attempting setup windows 2016 rds standard deployment session hosting.  layout follows: rds01 - rds connection broker , web access ts02 - rds session host ts03 - rds session host domain these servers part of has (1) windows 2008 server , (2) windows 2016 servers acting dcs.  domain running @ windows 2003 functional level. servers on single routed network no firewall between them.  dns , ptr records servers exist , resolve on hosts.  servers can pinged each other. in other words, there no network connectivity issues. i've setup rds deployment several times w/ same results. the issue can login via rdweb interface on rds01 win10 desktop , connect published rdp desktop without issue (i.e. no error messages user) , no errors in logs.  when try directly rdp rds01, authenticate user (per event log) error stating user doesn't have access system.  in event log event id 1306 message of "remote desktop connection broker client faile...
Read more

Como saber quien entro a mi PC por la Red

-
quisiera saber si es posible, o existe forma de auditar quien accedió a mi pc vía red, es decir se que hay software que perminten auditar el file server para saber quien entro y modifico y/o borro un archivo... pero si alguien entro mi pc \\pcname\c$ hay forma de determinar que usuario entro al disco c de una pc en especifica y copio, modifico o borro un archivo...   y la otra pregunta cuales son las mejores herramientas para auditar la red y el file server   gracias una forma de detectar quien esta conectado tu pc es través del comando net user entra en cmd y escribes net user eso muestra los usuarios que están conectados en tu equipo en un momento determinado, se que no es lo que pides pero puede servir para descubir alguien en determinado momento. para que no este compartido le dan clic derecho sobre mi pc>propiedades>remoto y le desmarcan donde dice ''permitir que este equipo envíe invitaciones ...
Read more