none
Clients not registering in wsus console RRS feed

  • Question

  • I have a brand new 2016 server setup with WSUS on hyper - V.  6 processors and 32 GB memory.  
    Corresponding GPO setup to point clients at the server for windows updates, it appears to be working as it should.
    I initially got my test machine to register, but it hasn't communicated with the server for over a month and no other devices have been recognized.
    On the client in the windows update log I see this:

    2017-02-06 14:48:12:053 1000 1a74 Misc WARNING: Send failed with hr = 80072ee2.
    2017-02-06 14:48:12:053 1000 1a74 Misc WARNING: SendRequest failed with 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 with 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 to upload events with hr = 80072ee2.

    using WID for my database and I see its almost 2GB in size (updates are limited to english and Win 10, 8, 7, server 16, server 12, office 16 and office 265.  

    So why aren't my devices communicating with the server?  Its within the same subnet.  Glad to answer other questions as needed.
    Thank you!

    Monday, February 6, 2017 9:03 PM

Answers

  • Hi franze,

    Please provide the related screenshots of the WSUS server, example:

    WSUS overview:

    2. WSUS Client status:

    WSUS site:

    What's more, check the following things:

    1. Check Windows Update settings on clients' registry: HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate, ensure you append the port number 8530 in the WSUS URL. Also ensure the clients could resolve the name of the WSUS server to correct IP address:

    Also ensure automatic update is enabled.

    Welcome to feedback.

    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.




    Thursday, February 9, 2017 9:04 AM
    Moderator

All replies

  • Hi franze98,

    >I initially got my test machine to register, but it hasn't communicated with the server for over a month and no other devices have been recognized.

    Check if my understanding is correct, the test machine do not report to the WSUS server for a long time, and other machines do not show up in the WSUS console.

    If my understanding is correct, then for the clients that do not show up in the WSUS console, please reset SUSClientID:

    Reset SusClientId:
    1). In cmd, net stop wuauserv

    2). Delete the value in registry key " SusClientId " and "SusClientIDValidation" locates in:

    HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate

    3). In cmd, net start wuauserv
         wuauclt.exe /resetauthorization /detectnow

    On the clients that do not report to the WSUS server, please reset windows update components:

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

    On the WSUS server, please run Server Cleanup Wizard.

    Check what is the result after then, welcome to feedback.

    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.

    Tuesday, February 7, 2017 5:13 AM
    Moderator
  • (updates are limited to english and Win 10, 8, 7, server 16, server 12, office 16 and office 265.  

    If you are using WSUS only, and you are not integrating with System Center Configuration Manager, there is no point synchronising O365 updates, they will never deploy from WSUS.

    Don [doesn't work for MSFT, and they're probably glad about that ;]

    Tuesday, February 7, 2017 5:57 AM
  • why aren't my devices communicating with the server?  

    The windowsupdate.log file, including the STARTUP section of the logfile, will help us to assist diagnosis (post a link to a onedrive share of the file :)

    You can also examine the server-side logs, at c:\Program Files\Update Services\Logfiles


    Don [doesn't work for MSFT, and they're probably glad about that ;]


    • Edited by DonPick Tuesday, February 7, 2017 6:01 AM
    Tuesday, February 7, 2017 6:00 AM
  • I tried the steps above as directed by Anne, but I see no change at least in my test machine.  Anne you did understand me correctly as well.

    Here is the windowsupdate log from it

    Don - thanks for the tip on the O365 updates as i didn't know that and am not using SCCM.

    If it matters this is the first installation of a WSUS for this network.  

    the changelog file on the server has lots of lines like this:

    2017-02-06 19:01:43.341 UTC Successfully deployed deployment(Decline) of Cumulative Update for Windows 10 (KB3205383) by MJMEC\(adminaccount) UpdateID:0B86866E-3D6D-47C1-BF17-71928781D802 Revision Number:202 
    2017-02-06 19:01:43.372 UTC Successfully deployed deployment(Decline) of Windows Malicious Software Removal Tool x64 - December 2016 (KB890830) by MJMEC\(adminaccount) UpdateID:10BDEEAB-AA25-4573-B478-180BB492971A Revision Number:200 
    2017-02-06 19:01:43.403 UTC Successfully deployed deployment(Decline) of Windows Malicious Software Removal Tool for Windows 8, 8.1 and 10 - December 2016 (KB890830) by MJMEC\(adminaccount) UpdateID:B6880D4E-55AA-492B-BCA2-1943F5173AC9 Revision Number:200 
    2017-02-06 19:01:43.450 UTC Successfully deployed deployment(Decline) of Windows Malicious Software Removal Tool - December 2016 (KB890830) by MJMEC\(adminaccount) UpdateID:755947CC-7FCA-489A-AC56-E67B036D3895 Revision Number:200 
    2017-02-06 19:01:43.482 UTC Successfully deployed deployment(Decline) of Windows Malicious Software Removal Tool for Windows 8, 8.1, 10 and Windows Server 2012, 2012 R2, 2016 x64 Edition - December 2016 (KB890830) by MJMEC\(adminaccount) UpdateID:202FBC3A-18B2-42EC-97D5-EAD9BD7C80DA Revision Number:200 
    2017-02-06 19:01:43.513 UTC Successfully deployed deployment(Decline) of Update for Windows 7 for x64-based Systems (KB3203884) by MJMEC\(adminaccount) UpdateID:AFFF7632-7488-43C1-8E02-31E235A53D09 Revision Number:201 
    2017-02-06 19:01:43.544 UTC Successfully deployed deployment(Decline) of Update for Windows 7 (KB3203884) by MJMEC\(adminaccount) UpdateID:9242AC40-865F-4D87-9F3C-66F0101C7462 Revision Number:201 
    2017-02-06 19:01:43.575 UTC Successfully deployed deployment(Decline) of Update for Windows Server 2008 R2 for Itanium-based Systems (KB3203884) by MJMEC\(adminaccount) UpdateID:FE9E4E94-8294-4C4D-8E26-A3A35ABC8098 Revision Number:201 
    2017-02-06 19:01:43.622 UTC Successfully deployed deployment(Decline) of Update for Windows 8.1 for x64-based Systems (KB3203884) by MJMEC\(adminaccount) UpdateID:ABA8138C-22D0-4F60-BF3D-FDB5857B800D Revision Number:201 
    2017-02-06 19:01:43.653 UTC Successfully deployed deployment(Decline) of Update for Windows Server 2012 R2 (KB3203884) by MJMEC\(adminaccount) UpdateID:F4301ECC-3118-497F-9DEA-CBA18F8BDA6B Revision Number:201 
    2017-02-06 19:01:43.685 UTC Successfully deployed deployment(Decline) of Update for Windows 8.1 (KB3203884) by MJMEC\(adminaccount) UpdateID:3703C979-70FD-4E3A-A04E-0DB8B9646831 Revision Number:202 
    2017-02-06 19:01:43.732 UTC Successfully deployed deployment(Decline) of Update for Windows Server 2008 R2 x64 Edition (KB3203884) by MJMEC\(adminaccount) UpdateID:AF9E8216-3D96-40B6-AE0E-266700718759 Revision Number:201 
    2017-02-06 19:01:43.763 UTC Successfully deployed deployment(Decline) of November, 2016 Security Monthly Quality Rollup for Windows 7 (KB3197868) by MJMEC\(adminaccount) UpdateID:2501EA5A-6FED-4767-8A3F-1702B0956B4B Revision Number:218 
    2017-02-06 19:01:43.810 UTC Successfully deployed deployment(Decline) of November, 2016 Security Monthly Quality Rollup for Windows Server 2008 R2 for x64-based Systems (KB3197868) by MJMEC\(adminaccount) UpdateID:FF5CB055-65FA-47CA-98CD-7E6EFC5563F5 Revision Number:222 
    2017-02-06 19:01:43.841 UTC Successfully deployed deployment(Decline) of November, 2016 Security Monthly Quality Rollup for Windows Server 2008 R2 for Itanium-based Systems (KB3197868) by MJMEC\(adminaccount) UpdateID:00328BC9-60AE-496D-9755-B7B07B5FCCE8 Revision Number:218 
    2017-02-06 19:01:43.888 UTC Successfully deployed deployment(Decline) of November, 2016 Security Monthly Quality Rollup for Windows 7 for x64-based Systems (KB3197868) by MJMEC\(adminaccount) UpdateID:7B6B1929-1F54-47A9-B3AD-EAEC4B2B377D Revision Number:224 
    2017-02-06 19:01:43.919 UTC Successfully deployed deployment(Decline) of November, 2016 Security Monthly Quality Rollup for Windows 8.1 (KB3197874) by MJMEC\(adminaccount) UpdateID:71ADE0E0-189C-4D16-B9AB-5A5D9D9D7908 Revision Number:222 
    2017-02-06 19:01:43.950 UTC Successfully deployed deployment(Decline) of November, 2016 Security Monthly Quality Rollup for Windows 8.1 for x64-based Systems (KB3197874) by MJMEC\(adminaccount) UpdateID:99248B4D-E3E9-41FD-AF39-8D960997AD08 Revision Number:218 
    2017-02-06 19:01:43.997 UTC Successfully deployed deployment(Decline) of November, 2016 Security Monthly Quality Rollup for Windows Server 2012 R2 (KB3197874) by MJMEC\(adminaccount) UpdateID:71AFF791-0CA9-4D16-BCFD-BA844162EE15 Revision Number:228 
    2017-02-06 19:01:44.044 UTC Deleted deployment(Install) of December, 2016 Security Monthly Quality Rollup for Windows 7 for x64-based Systems (KB3207752) by MJMEC\(adminaccount) UpdateID:3BECFA4F-0A7A-482E-9057-0C15DDB3364B Revision Number:204 TargetGroup:regular machines
    2017-02-06 19:01:44.060 UTC Deleted deployment(Install) of December, 2016 Security Monthly Quality Rollup for Windows 7 for x64-based Systems (KB3207752) by MJMEC\(adminaccount) UpdateID:3BECFA4F-0A7A-482E-9057-0C15DDB3364B Revision Number:204 TargetGroup:test group
    2017-02-06 19:01:44.091 UTC Deleted deployment(Install) of December, 2016 Security Monthly Quality Rollup for Windows 7 for x64-based Systems (KB3207752) by MJMEC\(adminaccount) UpdateID:3BECFA4F-0A7A-482E-9057-0C15DDB3364B Revision Number:204 TargetGroup:servers
    2017-02-06 19:01:44.122 UTC Successfully deployed deployment(Decline) of December, 2016 Security Monthly Quality Rollup for Windows 7 for x64-based Systems (KB3207752) by MJMEC\(adminaccount) UpdateID:3BECFA4F-0A7A-482E-9057-0C15DDB3364B Revision Number:204 
    2017-02-06 19:01:44.153 UTC Deleted deployment(Install) of December, 2016 Security Monthly Quality Rollup for Windows Server 2008 R2 for Itanium-based Systems (KB3207752) by MJMEC\(adminaccount) UpdateID:0221C6C4-F67B-4C01-8763-22E03C765774 Revision Number:203 TargetGroup:regular machines
    2017-02-06 19:01:44.185 UTC Deleted deployment(Install) of December, 2016 Security Monthly Quality Rollup for Windows Server 2008 R2 for Itanium-based Systems (KB3207752) by MJMEC\(adminaccount) UpdateID:0221C6C4-F67B-4C01-8763-22E03C765774 Revision Number:203 TargetGroup:test group
    2017-02-06 19:01:44.200 UTC Deleted deployment(Install) of December, 2016 Security Monthly Quality Rollup for Windows Server 2008 R2 for Itanium-based Systems (KB3207752) by MJMEC\(adminaccount) UpdateID:0221C6C4-F67B-4C01-8763-22E03C765774 Revision Number:203 TargetGroup:servers
    2017-02-06 19:01:44.232 UTC Successfully deployed deployment(Decline) of December, 2016 Security Monthly Quality Rollup for Windows Server 2008 R2 for Itanium-based Systems (KB3207752) by MJMEC\(adminaccount) UpdateID:0221C6C4-F67B-4C01-8763-22E03C765774 Revision Number:203 
    2017-02-06 19:01:44.263 UTC Deleted deployment(Install) of December, 2016 Security Monthly Quality Rollup for Windows 7 (KB3207752) by MJMEC\(adminaccount) UpdateID:10CC5874-6DA0-40C8-940A-D85FB71F115E Revision Number:202 TargetGroup:regular machines
    2017-02-06 19:01:44.294 UTC Deleted deployment(Install) of December, 2016 Security Monthly Quality Rollup for Windows 7 (KB3207752) by MJMEC\(adminaccount) UpdateID:10CC5874-6DA0-40C8-940A-D85FB71F115E Revision Number:202 TargetGroup:test group
    2017-02-06 19:01:44.310 UTC Deleted deployment(Install) of December, 2016 Security Monthly Quality Rollup for Windows 7 (KB3207752) by MJMEC\(adminaccount) UpdateID:10CC5874-6DA0-40C8-940A-D85FB71F115E Revision Number:202 TargetGroup:servers
    2017-02-06 19:01:44.341 UTC Successfully deployed deployment(Decline) of December, 2016 Security Monthly Quality Rollup for Windows 7 (KB3207752) by MJMEC\(adminaccount) UpdateID:10CC5874-6DA0-40C8-940A-D85FB71F115E Revision Number:202 
    2017-02-06 19:01:44.372 UTC Deleted deployment(Install) of December, 2016 Security Monthly Quality Rollup for Windows Server 2008 R2 for x64-based Systems (KB3207752) by MJMEC\(adminaccount) UpdateID:C26A0CB1-0736-413F-8392-5EA283C86292 Revision Number:204 TargetGroup:regular machines
    2017-02-06 19:01:44.403 UTC Deleted deployment(Install) of December, 2016 Security Monthly Quality Rollup for Windows Server 2008 R2 for x64-based Systems (KB3207752) by MJMEC\(adminaccount) UpdateID:C26A0CB1-0736-413F-8392-5EA283C86292 Revision Number:204 TargetGroup:test group
    2017-02-06 19:01:44.435 UTC Deleted deployment(Install) of December, 2016 Security Monthly Quality Rollup for Windows Server 2008 R2 for x64-based Systems (KB3207752) by MJMEC\(adminaccount) UpdateID:C26A0CB1-0736-413F-8392-5EA283C86292 Revision Number:204 TargetGroup:servers
    2017-02-06 19:01:44.450 UTC Successfully deployed deployment(Decline) of December, 2016 Security Monthly Quality Rollup for Windows Server 2008 R2 for x64-based Systems (KB3207752) by MJMEC\(adminaccount) UpdateID:C26A0CB1-0736-413F-8392-5EA283C86292 Revision Number:204 

    Thanks for your time!

    Tuesday, February 7, 2017 3:59 PM
  • ok, the changelog looks fine (no warnings nor errors noted)

    The windowsupdate.log from the client Win7 PC, shows for that entire logfile, this client has *never* successfully contacted your WSUS.
    This client has *once* successfully updated WindowsDefender data from Microsoft.com

    2017-02-06 14:47:08:263 1000 13a0 Agent   * WSUS server: http://c3po:8350
    2017-02-06 14:47:08:263 1000 13a0 Agent   * WSUS status server: http://c3po:8350
    2017-02-06 14:47:08:263 1000 13a0 Agent   * Target group: (Unassigned Computers)

    This client continually logs 0x80072EE2 (time out) when attempting to contact the host WSUS "c3po".

    Either, a networking error is preventing proper communication between client and host, or, the host has some issue, perhaps at IIS level.

    Check the IIS logfiles on the WSUS host.

    Also, check the softwaredistribution.log on the WSUS host.

    Also, check the Windows event log on the WSUS host.

    The WSUS service on the host will log events if there are certain types of issues (eg no clients contacted WSUS recently), this is part of the automatic WSUS health check routine (which runs daily, from my memory)


    Don [doesn't work for MSFT, and they're probably glad about that ;]

    Tuesday, February 7, 2017 8:08 PM

  • softwaredistribution.log file on WSUS host

    I see this in the windows application log:

    The description for Event ID 0 from source WSusCertServer cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

    If the event originated on another computer, the display information had to be saved with the event.

    The following information was included with the event: 

    Service started

    IIS has 0 events over past day.  Does show this as running

    C3PO IIS Admin Service IISADMIN Running Automatic
    C3PO World Wide Web Publishing Service W3SVC Running Automatic
    C3PO Application Host Helper Service AppHostSvc Running Automatic
    C3PO Windows Process Activation Service WAS Running Manual

    Anything look odd there?

    Thanks!

    Tuesday, February 7, 2017 9:27 PM
  • I can't see *any* client AGENT traffic al all, not in either log.

    you may need to examine the IIS logs, to see if requests are hitting your WSUS from clients, and, what response is being issued. Guessing from the clients logs, that client is getting a timeout because <something> has gone wrong in your WSUS. Your WSUS *seems* to be doing sync-to-MSFT, download-contentfiles-from-MSFT and cleanupWizard ok...

    %SystemDrive%\inetpub\logs\LogFiles

    Edit: can you browse to the default website of your WSUS, from a client browser ?
    Could it be a local firewall enabled on your WSUS, blocking client inbound attempts?


    Don [doesn't work for MSFT, and they're probably glad about that ;]



    • Edited by DonPick Wednesday, February 8, 2017 8:53 AM
    Wednesday, February 8, 2017 8:50 AM
  • I can browse directly to http://c3po and see the default IIS page.  

    I turned off the firewall on the server and still no change.

    %SystemDrive%\inetpub\logs\LogFiles log file is empty

    So I would guess IIS isn't configured correctly for WSUS?  


    Thanks! 
    Wednesday, February 8, 2017 5:05 PM
  • I just recently put up a new Windows Server 2016 VM to replace my old WSUS server. All I did from a fresh install was install WSUS on this new server and I am having the exact same problem. My clients are not showing up in my console although the GPO is configured correctly.
    Wednesday, February 8, 2017 7:35 PM
  • I can browse directly to http://c3po and see the default IIS page.  

    I turned off the firewall on the server and still no change.

    %SystemDrive%\inetpub\logs\LogFiles log file is empty

    So I would guess IIS isn't configured correctly for WSUS?  


    Thanks! 

    after you browsed to http://c3po  there should be logs by IIS of that traffic. Did that occur?

    I'm assuming that you configured WSUS using default port (8530) and not SSL (8531) ?

    Possibly unrelated, but this discussion link, might offer some thoughts/suggestions?

    http://serverfault.com/questions/740833/wsus-clients-failing-to-get-updates-with-error-80072ee2

    Also, check https://support.microsoft.com/en-us/kb/3194798 or a later/superseding equivalent, e.g.

    Cumulative Update for Windows Server 2016 for x64-based Systems (KB3197954)


    Don [doesn't work for MSFT, and they're probably glad about that ;]



    • Edited by DonPick Wednesday, February 8, 2017 8:06 PM
    Wednesday, February 8, 2017 8:01 PM
  • Yes, I got traffic to appear in the log.  Some of that traffic:

    #Software: Microsoft Internet Information Services 10.0
    #Version: 1.0
    #Date: 2017-02-08 19:27:03
    #Fields: date time s-ip cs-method cs-uri-stem cs-uri-query s-port cs-username c-ip cs(User-Agent) cs(Referer) sc-status sc-substatus sc-win32-status time-taken
    2017-02-08 19:27:03 fe80::502e:8102:95d4:97e5%3 GET /selfupdate/iuident.cab - 8530 - fe80::502e:8102:95d4:97e5%3 - - 200 0 0 1785
    2017-02-08 19:27:10 fe80::502e:8102:95d4:97e5%3 POST /reportingwebservice/reportingwebservice.asmx - 8530 - fe80::502e:8102:95d4:97e5%3 Mozilla/4.0+(compatible;+MSIE+6.0;+MS+Web+Services+Client+Protocol+4.0.30319.42000) - 200 0 0 5691
    2017-02-08 19:27:12 fe80::502e:8102:95d4:97e5%3 POST /ApiRemoting30/WebService.asmx - 8530 - fe80::502e:8102:95d4:97e5%3 Mozilla/4.0+(compatible;+MSIE+6.0;+MS+Web+Services+Client+Protocol+4.0.30319.42000) - 401 2 5 328
    2017-02-08 19:27:14 fe80::502e:8102:95d4:97e5%3 POST /ApiRemoting30/WebService.asmx - 8530 MJMEC\C3PO$ fe80::502e:8102:95d4:97e5%3 Mozilla/4.0+(compatible;+MSIE+6.0;+MS+Web+Services+Client+Protocol+4.0.30319.42000) - 200 0 0 1500
    2017-02-08 19:27:18 fe80::502e:8102:95d4:97e5%3 POST /ServerSyncWebService/serversyncwebservice.asmx - 8530 - fe80::502e:8102:95d4:97e5%3 Mozilla/4.0+(compatible;+MSIE+6.0;+MS+Web+Services+Client+Protocol+4.0.30319.42000) - 200 0 0 3433
    2017-02-08 19:27:21 fe80::502e:8102:95d4:97e5%3 POST /ClientWebService/Client.asmx - 8530 - fe80::502e:8102:95d4:97e5%3 Mozilla/4.0+(compatible;+MSIE+6.0;+MS+Web+Services+Client+Protocol+4.0.30319.42000) - 200 0 0 3282
    2017-02-08 19:27:21 fe80::502e:8102:95d4:97e5%3 POST /SimpleAuthWebService/SimpleAuth.asmx - 8530 - fe80::502e:8102:95d4:97e5%3 Mozilla/4.0+(compatible;+MSIE+6.0;+MS+Web+Services+Client+Protocol+4.0.30319.42000) - 200 0 0 449
    2017-02-08 19:27:22 fe80::502e:8102:95d4:97e5%3 POST /DssAuthWebService/DssAuthWebService.asmx - 8530 - fe80::502e:8102:95d4:97e5%3 Mozilla/4.0+(compatible;+MSIE+6.0;+MS+Web+Services+Client+Protocol+4.0.30319.42000) - 200 0 0 525
    2017-02-08 19:27:22 fe80::502e:8102:95d4:97e5%3 GET /Content/anonymousCheckFile.txt - 8530 - fe80::502e:8102:95d4:97e5%3 - - 200 0 0 6
    2017-02-08 19:37:22 fe80::502e:8102:95d4:97e5%3 GET /selfupdate/iuident.cab - 8530 - fe80::502e:8102:95d4:97e5%3 - - 200 0 0 15
    2017-02-08 19:37:22 fe80::502e:8102:95d4:97e5%3 POST /reportingwebservice/reportingwebservice.asmx - 8530 - fe80::502e:8102:95d4:97e5%3 Mozilla/4.0+(compatible;+MSIE+6.0;+MS+Web+Services+Client+Protocol+4.0.30319.42000) - 200 0 0 0
    2017-02-08 19:37:22 fe80::502e:8102:95d4:97e5%3 POST /ApiRemoting30/WebService.asmx - 8530 MJMEC\C3PO$ fe80::502e:8102:95d4:97e5%3 Mozilla/4.0+(compatible;+MSIE+6.0;+MS+Web+Services+Client+Protocol+4.0.30319.42000) - 200 0 0 15
    2017-02-08 19:37:22 fe80::502e:8102:95d4:97e5%3 POST /ServerSyncWebService/serversyncwebservice.asmx - 8530 - fe80::502e:8102:95d4:97e5%3 Mozilla/4.0+(compatible;+MSIE+6.0;+MS+Web+Services+Client+Protocol+4.0.30319.42000) - 200 0 0 0
    2017-02-08 19:37:22 fe80::502e:8102:95d4:97e5%3 POST /ClientWebService/Client.asmx - 8530 - fe80::502e:8102:95d4:97e5%3 Mozilla/4.0+(compatible;+MSIE+6.0;+MS+Web+Services+Client+Protocol+4.0.30319.42000) - 200 0 0 15
    2017-02-08 19:37:22 fe80::502e:8102:95d4:97e5%3 POST /SimpleAuthWebService/SimpleAuth.asmx - 8530 - fe80::502e:8102:95d4:97e5%3 Mozilla/4.0+(compatible;+MSIE+6.0;+MS+Web+Services+Client+Protocol+4.0.30319.42000) - 200 0 0 0
    2017-02-08 19:37:22 fe80::502e:8102:95d4:97e5%3 POST /DssAuthWebService/DssAuthWebService.asmx - 8530 - fe80::502e:8102:95d4:97e5%3 Mozilla/4.0+(compatible;+MSIE+6.0;+MS+Web+Services+Client+Protocol+4.0.30319.42000) - 200 0 0 0
    2017-02-08 19:37:22 fe80::502e:8102:95d4:97e5%3 GET /Content/anonymousCheckFile.txt - 8530 - fe80::502e:8102:95d4:97e5%3 - - 200 0 0 0
    2017-02-08 19:47:22 fe80::502e:8102:95d4:97e5%3 GET /selfupdate/iuident.cab - 8530 - fe80::502e:8102:95d4:97e5%3 - - 200 0 0 0
    2017-02-08 19:47:22 fe80::502e:8102:95d4:97e5%3 POST /reportingwebservice/reportingwebservice.asmx - 8530 - fe80::502e:8102:95d4:97e5%3 Mozilla/4.0+(compatible;+MSIE+6.0;+MS+Web+Services+Client+Protocol+4.0.30319.42000) - 200 0 0 0
    2017-02-08 19:47:22 fe80::502e:8102:95d4:97e5%3 POST /ApiRemoting30/WebService.asmx - 8530 MJMEC\C3PO$ fe80::502e:8102:95d4:97e5%3 Mozilla/4.0+(compatible;+MSIE+6.0;+MS+Web+Services+Client+Protocol+4.0.30319.42000) - 200 0 0 0
    2017-02-08 19:47:22 fe80::502e:8102:95d4:97e5%3 POST /ServerSyncWebService/serversyncwebservice.asmx - 8530 - fe80::502e:8102:95d4:97e5%3 Mozilla/4.0+(compatible;+MSIE+6.0;+MS+Web+Services+Client+Protocol+4.0.30319.42000) - 200 0 0 0
    2017-02-08 19:47:22 fe80::502e:8102:95d4:97e5%3 POST /ClientWebService/Client.asmx - 8530 - fe80::502e:8102:95d4:97e5%3 Mozilla/4.0+(compatible;+MSIE+6.0;+MS+Web+Services+Client+Protocol+4.0.30319.42000) - 200 0 0 0
    2017-02-08 19:47:22 fe80::502e:8102:95d4:97e5%3 POST /SimpleAuthWebService/SimpleAuth.asmx - 8530 - fe80::502e:8102:95d4:97e5%3 Mozilla/4.0+(compatible;+MSIE+6.0;+MS+Web+Services+Client+Protocol+4.0.30319.42000) - 200 0 0 15
    2017-02-08 19:47:22 fe80::502e:8102:95d4:97e5%3 POST /DssAuthWebService/DssAuthWebService.asmx - 8530 - fe80::502e:8102:95d4:97e5%3 Mozilla/4.0+(compatible;+MSIE+6.0;+MS+Web+Services+Client+Protocol+4.0.30319.42000) - 200 0 0 0
    2017-02-08 19:47:22 fe80::502e:8102:95d4:97e5%3 GET /Content/anonymousCheckFile.txt - 8530 - fe80::502e:8102:95d4:97e5%3 - - 200 0 0 0
    2017-02-08 19:57:23 fe80::502e:8102:95d4:97e5%3 GET /selfupdate/iuident.cab - 8530 - fe80::502e:8102:95d4:97e5%3 - - 200 0 0 0
    2017-02-08 19:57:23 fe80::502e:8102:95d4:97e5%3 POST /reportingwebservice/reportingwebservice.asmx - 8530 - fe80::502e:8102:95d4:97e5%3 Mozilla/4.0+(compatible;+MSIE+6.0;+MS+Web+Services+Client+Protocol+4.0.30319.42000) - 200 0 0 15
    2017-02-08 19:57:23 fe80::502e:8102:95d4:97e5%3 POST /ApiRemoting30/WebService.asmx - 8530 MJMEC\C3PO$ fe80::502e:8102:95d4:97e5%3 Mozilla/4.0+(compatible;+MSIE+6.0;+MS+Web+Services+Client+Protocol+4.0.30319.42000) - 200 0 0 0
    2017-02-08 19:57:23 fe80::502e:8102:95d4:97e5%3 POST /ServerSyncWebService/serversyncwebservice.asmx - 8530 - fe80::502e:8102:95d4:97e5%3 Mozilla/4.0+(compatible;+MSIE+6.0;+MS+Web+Services+Client+Protocol+4.0.30319.42000) - 200 0 0 0
    2017-02-08 19:57:23 fe80::502e:8102:95d4:97e5%3 POST /ClientWebService/Client.asmx - 8530 - fe80::502e:8102:95d4:97e5%3 Mozilla/4.0+(compatible;+MSIE+6.0;+MS+Web+Services+Client+Protocol+4.0.30319.42000) - 200 0 0 0
    2017-02-08 19:57:23 fe80::502e:8102:95d4:97e5%3 POST /SimpleAuthWebService/SimpleAuth.asmx - 8530 - fe80::502e:8102:95d4:97e5%3 Mozilla/4.0+(compatible;+MSIE+6.0;+MS+Web+Services+Client+Protocol+4.0.30319.42000) - 200 0 0 0
    2017-02-08 19:57:23 fe80::502e:8102:95d4:97e5%3 POST /DssAuthWebService/DssAuthWebService.asmx - 8530 - fe80::502e:8102:95d4:97e5%3 Mozilla/4.0+(compatible;+MSIE+6.0;+MS+Web+Services+Client+Protocol+4.0.30319.42000) - 200 0 0 15
    2017-02-08 19:57:23 fe80::502e:8102:95d4:97e5%3 GET /Content/anonymousCheckFile.txt - 8530 - fe80::502e:8102:95d4:97e5%3 - - 200 0 0 0
    2017-02-08 20:00:01 fe80::502e:8102:95d4:97e5%3 POST /ApiRemoting30/WebService.asmx - 8530 - fe80::502e:8102:95d4:97e5%3 Mozilla/4.0+(compatible;+MSIE+6.0;+MS+Web+Services+Client+Protocol+4.0.30319.42000) - 401 2 5 15
    2017-02-08 20:00:01 fe80::502e:8102:95d4:97e5%3 POST /ApiRemoting30/WebService.asmx - 8530 MJMEC\(adminaccount) fe80::502e:8102:95d4:97e5%3 Mozilla/4.0+(compatible;+MSIE+6.0;+MS+Web+Services+Client+Protocol+4.0.30319.42000) - 200 0 0 0
    2017-02-08 20:00:01 fe80::502e:8102:95d4:97e5%3 POST /ApiRemoting30/WebService.asmx - 8530 MJMEC\(adminaccount) fe80::502e:8102:95d4:97e5%3 Mozilla/4.0+(compatible;+MSIE+6.0;+MS+Web+Services+Client+Protocol+4.0.30319.42000) - 200 0 0 0
    2017-02-08 20:00:01 fe80::502e:8102:95d4:97e5%3 POST /ApiRemoting30/WebService.asmx - 8530 MJMEC\(adminaccount) fe80::502e:8102:95d4:97e5%3 Mozilla/4.0+(compatible;+MSIE+6.0;+MS+Web+Services+Client+Protocol+4.0.30319.42000) - 200 0 0 46
    2017-02-08 20:00:01 fe80::502e:8102:95d4:97e5%3 POST /ApiRemoting30/WebService.asmx - 8530 MJMEC\(adminaccount) fe80::502e:8102:95d4:97e5%3 Mozilla/4.0+(compatible;+MSIE+6.0;+MS+Web+Services+Client+Protocol+4.0.30319.42000) - 200 0 0 0
    2017-02-08 20:00:01 fe80::502e:8102:95d4:97e5%3 POST /ApiRemoting30/WebService.asmx - 8530 MJMEC\(adminaccount) fe80::502e:8102:95d4:97e5%3 Mozilla/4.0+(compatible;+MSIE+6.0;+MS+Web+Services+Client+Protocol+4.0.30319.42000) - 200 0 0 0
    2017-02-08 20:00:01 fe80::502e:8102:95d4:97e5%3 POST /ApiRemoting30/WebService.asmx - 8530 MJMEC\(adminaccount) fe80::502e:8102:95d4:97e5%3 Mozilla/4.0+(compatible;+MSIE+6.0;+MS+Web+Services+Client+Protocol+4.0.30319.42000) - 200 0 0 15

    I had reviewed the first link already and resetting the port didn't help. 
    The update wasn't applicable to the server.  So it must be good on updates itself at least.   
    Seems like we are running out of ideas, reloading with 2012 instead of might have be necessary.


    Thanks,


    • Edited by franze98 Wednesday, February 8, 2017 8:21 PM
    Wednesday, February 8, 2017 8:21 PM
  • Hi franze,

    Please provide the related screenshots of the WSUS server, example:

    WSUS overview:

    2. WSUS Client status:

    WSUS site:

    What's more, check the following things:

    1. Check Windows Update settings on clients' registry: HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate, ensure you append the port number 8530 in the WSUS URL. Also ensure the clients could resolve the name of the WSUS server to correct IP address:

    Also ensure automatic update is enabled.

    Welcome to feedback.

    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.




    Thursday, February 9, 2017 9:04 AM
    Moderator
  • Anne - ok we finally cleared a hurdle your screenshot request made me realize i had a number switchup on the port in my GPO.  Thus WSUS is now seeing machines.  
    My problem now is I can't change membership, the option to do so is greyed out.  Is that normal?
    I'm attaching screenshot of what I see.




    thanks for all your help and I hope you don't feel like it was time wasted due to my typo!
    Thursday, February 9, 2017 8:43 PM
  • And I found my own answer in the options settings. :)
    Thanks again everyone!

    If I didn't apply credit correctly please let me know since its my first time using this forum.
    • Edited by franze98 Thursday, February 9, 2017 10:16 PM
    Thursday, February 9, 2017 8:45 PM
  • If I didn't apply credit correctly please let me know since its my first time using this forum.

    Hi franze,

    You are welcome and we are glad to provide help. Feel free to post in WSUS forum if you have questions about WSUS.

    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.

    Friday, February 10, 2017 1:56 AM
    Moderator
  • This also fixed my issue. I didn't have the port in my GPO since in 2008 R2 it worked without it. After changing it to http://wsus:8530 in the GPO settings everything started working properly, thanks!
    Friday, February 10, 2017 1:36 PM
  • The windowsupdate.log from the client Win7 PC, shows........

    2017-02-06 14:47:08:263 1000 13a0 Agent   * WSUS server: http://c3po:8350
    2017-02-06 14:47:08:263 1000 13a0 Agent   * WSUS status server: http://c3po:8350
    2017-02-06 14:47:08:263 1000 13a0 Agent   * Target group: (Unassigned Computers)

    Apologies, I also missed the detail from your client windowsupdate logfile, which shows that you had an incorrect port (should be 8530)

    Don [doesn't work for MSFT, and they're probably glad about that ;]

    Saturday, February 11, 2017 12:12 AM
  • I got the same issue not urls are in Rededit and WSUS does not see the computer

    I would like some help on this 

    from oliver 

     
    Tuesday, December 10, 2019 12:40 AM