Clients not registering in wsus console


i have brand new 2016 server setup wsus on hyper - v.  6 processors , 32 gb memory.  
corresponding gpo setup point clients @ server windows updates, appears working should.
got test machine register, hasn't communicated server on month , no other devices have been recognized.
on client in windows update log see this:

2017-02-06 14:48:12:053 1000 1a74 misc warning: send failed hr = 80072ee2.
2017-02-06 14:48:12:053 1000 1a74 misc warning: sendrequest failed hr = 80072ee2. proxy list used: <(null)> bypass list used : <(null)> auth schemes used : <>
2017-02-06 14:48:12:053 1000 1a74 misc fatal: soap/winhttp - sendrequest: sendrequestusingproxy failed. error 0x80072ee2
2017-02-06 14:48:12:053 1000 1a74 pt  + last proxy send request failed hr = 0x80072ee2, http status code = 0
2017-02-06 14:48:12:053 1000 1a74 pt  + caller provided credentials = no
2017-02-06 14:48:12:053 1000 1a74 pt  + impersonate flags = 0
2017-02-06 14:48:12:053 1000 1a74 pt  + possible authorization schemes used = 
2017-02-06 14:48:12:053 1000 1a74 pt warning: getconfig failure, error = 0x80072ee2, soap client error = 5, soap error code = 0, http status code = 200
2017-02-06 14:48:12:053 1000 1a74 pt warning: pterror: 0x80072ee2
2017-02-06 14:48:12:053 1000 1a74 pt warning: getconfig_withrecovery failed: 0x80072ee2
2017-02-06 14:48:12:053 1000 1a74 pt warning: refreshconfig failed: 0x80072ee2
2017-02-06 14:48:12:053 1000 1a74 pt warning: refreshptstate failed: 0x80072ee2
2017-02-06 14:48:12:053 1000 1a74 pt warning: pterror: 0x80072ee2
2017-02-06 14:48:12:053 1000 1a74 report warning: reporter failed upload events hr = 80072ee2.

using wid database , see 2gb in size (updates limited english , win 10, 8, 7, server 16, server 12, office 16 , office 265.  

why aren't devices communicating server?  its within same subnet.  glad answer other questions needed.
thank you!

hi franze,

please provide related screenshots of wsus server, example:

wsus overview:

2. wsus client status:

wsus site:

what's more, check following things:

1. check windows update settings on clients' registry: hklm\software\policies\microsoft\windows\windowsupdate, ensure append port number 8530 in wsus url. ensure clients resolve name of wsus server correct ip address:

also ensure automatic update enabled.

welcome feedback.

best regards,

anne


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






Windows Server  >  WSUS



Comments

Popular posts from this blog

Group Policy Event ID 1058 Error Code 1326 (The user name or password is incorrect)

Suspicious event log Event ID: 4905

DCOM received error "2147746132" from...