New computers are not reporting into WSUS

hi,

we have wsus 3.0 server running on windows server 2003.  for past few months have noticed new computers have joined on domain not reporting status wsus , therefore not receiving updates.  all existing pcs continue report , continue receive updates.

i have been working on issue time , feel have tried internet has suggested.

i have tried obvious things on client machines such re-registering windows update dlls, removed client id key in registry etc.  there have been no changes server , have reviewed settings on here , nothing seems amiss.

finally, updated server 2003 , applied hotfixes wsus 3.0 has not made difference either!

can please assist this?  what relevance of soap errors seeing?

here excerpt windowsupdate.log

2016-03-09 16:33:01:142 964 1408 au triggering au detection through detectnow api
2016-03-09 16:33:01:142 964 1408 au triggering online detection (non-interactive)
2016-03-09 16:33:01:142 964 16c8 au #############
2016-03-09 16:33:01:142 964 16c8 au ## start ##  au: search updates
2016-03-09 16:33:01:142 964 16c8 au #########
2016-03-09 16:33:01:142 964 16c8 au <<## submitted ## au: search updates [callid = {d67f2984-842b-4765-90fc-2e667e0feac2}]
2016-03-09 16:33:01:142 964 11fc agent *************
2016-03-09 16:33:01:142 964 11fc agent ** start **  agent: finding updates [callerid = automaticupdates]
2016-03-09 16:33:01:142 964 11fc agent *********
2016-03-09 16:33:01:142 964 11fc agent  * online = yes; ignore download priority = no
2016-03-09 16:33:01:142 964 11fc 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"
2016-03-09 16:33:01:142 964 11fc agent  * serviceid = {3da21691-e39d-4da6-8a4b-b43877bcb1b7} managed
2016-03-09 16:33:01:142 964 11fc agent  * search scope = {machine}
2016-03-09 16:33:01:142 964 11fc setup checking agent selfupdate
2016-03-09 16:33:01:142 964 11fc setup client version: core: 7.6.7601.18804  aux: 7.6.7601.18804
2016-03-09 16:33:01:189 964 11fc misc validating signature c:\windows\softwaredistribution\selfupdate\wuident.cab dwprovflags 0x00000080:
2016-03-09 16:33:01:205 964 11fc misc microsoft signed: na
2016-03-09 16:33:01:205 964 11fc misc validating signature c:\windows\softwaredistribution\selfupdate\tmp71d6.tmp dwprovflags 0x00000080:
2016-03-09 16:33:01:220 964 11fc misc microsoft signed: na
2016-03-09 16:33:01:220 964 11fc misc validating signature c:\windows\softwaredistribution\selfupdate\wsus3setup.cab dwprovflags 0x00000080:
2016-03-09 16:33:01:236 964 11fc misc microsoft signed: na
2016-03-09 16:33:01:251 964 11fc misc validating signature c:\windows\softwaredistribution\selfupdate\wsus3setup.cab dwprovflags 0x00000080:
2016-03-09 16:33:01:251 964 11fc misc microsoft signed: na
2016-03-09 16:33:01:251 964 11fc setup determining whether new setup handler needs downloaded
2016-03-09 16:33:01:251 964 11fc setup selfupdate handler not found.  it downloaded
2016-03-09 16:33:01:251 964 11fc setup evaluating applicability of setup package "wuclient-selfupdate-activex~31bf3856ad364e35~amd64~~7.6.7600.320"
2016-03-09 16:33:01:267 964 11fc setup setup package "wuclient-selfupdate-activex~31bf3856ad364e35~amd64~~7.6.7600.320" installed.
2016-03-09 16:33:01:267 964 11fc setup evaluating applicability of setup package "wuclient-selfupdate-aux-toplevel~31bf3856ad364e35~amd64~~7.6.7600.320"
2016-03-09 16:33:01:267 964 11fc setup setup package "wuclient-selfupdate-aux-toplevel~31bf3856ad364e35~amd64~~7.6.7600.320" installed.
2016-03-09 16:33:01:267 964 11fc setup evaluating applicability of setup package "wuclient-selfupdate-core-toplevel~31bf3856ad364e35~amd64~~7.6.7600.320"
2016-03-09 16:33:01:283 964 11fc setup setup package "wuclient-selfupdate-core-toplevel~31bf3856ad364e35~amd64~~7.6.7600.320" installed.
2016-03-09 16:33:01:283 964 11fc setup selfupdate check completed.  selfupdate not required.
2016-03-09 16:33:01:470 964 11fc pt +++++++++++  pt: synchronizing server updates  +++++++++++
2016-03-09 16:33:01:470 964 11fc pt  + serviceid = {3da21691-e39d-4da6-8a4b-b43877bcb1b7}, server url = http://hull-wsus01:8530/clientwebservice/client.asmx
2016-03-09 16:33:01:532 964 11fc pt initializing simple targeting cookie, clientid = 9492997c-67b7-4532-998d-4cf0a94dfaee, target group = , dns name = g-22jfz72.ad.xxxx.co.uk
2016-03-09 16:33:01:532 964 11fc pt  server url = http://xxx-wsus01:8530/simpleauthwebservice/simpleauth.asmx
2016-03-09 16:34:06:928 964 11fc misc warning: send failed hr = 80072ee2.
2016-03-09 16:34:06:928 964 11fc misc warning: sendrequest failed hr = 80072ee2. proxy list used: <(null)> bypass list used : <(null)> auth schemes used : <>
2016-03-09 16:34:06:928 964 11fc misc fatal: soap/winhttp - sendrequest: sendrequestusingproxy failed. error 0x80072ee2
2016-03-09 16:34:06:928 964 11fc pt  + last proxy send request failed hr = 0x80072ee2, http status code = 0
2016-03-09 16:34:06:928 964 11fc pt  + caller provided credentials = no
2016-03-09 16:34:06:928 964 11fc pt  + impersonate flags = 0
2016-03-09 16:34:06:928 964 11fc pt  + possible authorization schemes used = 
2016-03-09 16:34:06:928 964 11fc pt warning: syncupdates failure, error = 0x80072ee2, soap client error = 5, soap error code = 0, http status code = 200
2016-03-09 16:34:06:928 964 11fc pt warning: pterror: 0x80072ee2
2016-03-09 16:34:06:928 964 11fc pt warning: syncupdates_withrecovery failed.: 0x80072ee2
2016-03-09 16:34:06:928 964 11fc pt warning: sync of updates: 0x80072ee2
2016-03-09 16:34:06:928 964 11fc pt warning: syncserverupdatesinternal failed: 0x80072ee2
2016-03-09 16:34:06:928 964 11fc agent  * warning: failed synchronize, error = 0x80072ee2
2016-03-09 16:34:06:928 964 11fc agent  * warning: exit code = 0x80072ee2
2016-03-09 16:34:06:928 964 11fc agent *********
2016-03-09 16:34:06:928 964 11fc agent **  end  **  agent: finding updates [callerid = automaticupdates]
2016-03-09 16:34:06:928 964 11fc agent *************
2016-03-09 16:34:06:928 964 11fc agent warning: wu client failed searching update error 0x80072ee2
2016-03-09 16:34:06:959 964 1058 au >>##  resumed  ## au: search updates [callid = {d67f2984-842b-4765-90fc-2e667e0feac2}]
2016-03-09 16:34:06:959 964 1058 au  # warning: search callback failed, result = 0x80072ee2
2016-03-09 16:34:06:959 964 1058 au  # warning: failed find updates error code 80072ee2
2016-03-09 16:34:06:959 964 1058 au #########
2016-03-09 16:34:06:959 964 1058 au ##  end  ##  au: search updates [callid = {d67f2984-842b-4765-90fc-2e667e0feac2}]

any appreciated.

thanks

allan

hi smittyuk,

according description, new joined computers don't report wsus server, may following things and check result:

1. new joined computer's os version?

2. check if new joined computers have applied wsus gpo correctly, may run gpresult /h c:\report.html on client to check result, check if related registry keys have been changed correctly:

configure automatic updates using registry editor

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

3. try reset windows update component on client:

reset windows update component:

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

4. try reset susid on 1 of clients test if susid duplicated:

reset wsus authorization , new wsus sid:

https://gallery.technet.microsoft.com/scriptcenter/reset-wsus-authorization-2e26d1b0

5. rename softwaredistribution folder on client:

in cmd, enter net stop wuauserv;

find softwaredistribution folder located in c:\windows\softwaredistribution, rename it.

in cmd, enter net start wuauserv;

6. on wsus server, run server cleanup wizard; if above methods still doesn't work, reindex wsus database on wsus server:

reindex wsus database:

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

welcome feed result.

best regards,

anne

---

please remember mark replies answers if , unmark them if provide no help. if have feedback technet support, contact tnmff@microsoft.com.

Windows Server  >  WSUS