locked
WSUS - Clients not yet reported RRS feed

  • Question

  • New installation of WSUS on Windows 2008 R2 standard

    A handful of machine have appeared in the console and mostly showing not yet reported. It has been over a week now and there are at least 250 machines in our environment

    Update services version  3.2.7600.226 

    Windows client version WU client version 7.6.7601.19016

    Any help greatly appreciated


    Thursday, November 19, 2015 6:02 PM

Answers

  • I think you must upgrade WSUS version:

    WSUS 3.0 (SP2):     Build 3.2.7600.226
    WSUS 3.0 (SP2) + KB2720211:     Build 3.2.7600.251
    WSUS 3.0 (SP2) + KB2734608:     Build 3.2.7600.256
    WSUS 3.0 (SP2) + KB2828185:     Build 3.2.7600.262
    WSUS 3.0 (SP2) + KB2938066:     Build 3.2.7600.274

    I also install a WSUS 2008 R2 with some problems with this updates. KB2720211 have a long history of problems. Search by this update.

    In my case, to have my WSUS update to Build 3.2.7600.274, i have to install in this order:

    1 - Setup WSUS 3.0 SP2 > . version 226.

    2 - KB2828185 (that include KB2720211 and KB2734608) . version 262.

    3 - KB2938066. This update show an error at the end of the installation, but the WSUS version show . version 274.

    I wrote a post with this problem:

    https://social.technet.microsoft.com/Forums/windowsserver/en-US/edc904f8-78f4-441d-a67c-880fa5f42941/kb2720211-kb2734608-wsus-nightmare?forum=winserverwsus#9599f690-3b3e-4242-9afa-1db099aa1154

    I hope to have helped, be carefull and read about all this before install this updates.

    Regards,



    • Edited by Pedro_A Wednesday, November 25, 2015 11:27 AM
    • Proposed as answer by Hello_2018 Friday, December 4, 2015 2:55 AM
    • Marked as answer by Steven_Lee0510 Tuesday, December 8, 2015 9:59 AM
    Wednesday, November 25, 2015 11:26 AM

All replies

  • Hi,

    Here are some basic suggestion for you to reference.

    1. Firewall rules are allowed access on both the WSUS server and your client.
    2. Check the connectivity between the client computer and WSUS server. You could use the ping utility to check connectivity.
    3. Contact the WSUS HTTP server by providing the server name: port number :8530. open the Internet Explorer and type http://wsusservername:portnumber. You could see the IIS version on the page.
    4. Verify the existence of the self-update tree. In an Internet Explorer address bar, type: http://WSUSServerName/selfupdate/wuident.cab. If the WSUS server is functioning properly, you would see a File Download window that asks you whether to open or save the file.
    5. Open the command prompt on the client machine, type the command –

      wuauclt.exe /resetauthorization /detectnow.

      Wait for 10 minutes for detection cycle to complete.
    6. The group policy you put in place is pointing to your WSUS server address.

     

    Hope this will be helpful.

    Best regards,


    • Edited by Hello_2018 Friday, November 20, 2015 9:33 AM
    Friday, November 20, 2015 9:28 AM
  • Hi

    1. Access is allowed

    2. Ping is successful

    3. I can see the IIS version if I type just http://WSUSServername but not if I type the port number. 

    4. The file is available for download

    5. Have tried but still showing not yet reported in WSUS console

    Friday, November 20, 2015 5:48 PM
  • Hi Chance08,

    May be the following link could be help with your issue as you have tried the method I have given you before:

    http://blogs.technet.com/b/sus/archive/2009/11/17/tips-for-troubleshooting-wsus-agents-that-are-not-reporting-to-the-wsus-server.aspx

    Best regards,

    Monday, November 23, 2015 6:48 AM
  • Hi

    Went through guidelines in the link. I now have two clients that have are showing in the WSUS console but they have not yet reported as their status. I have run a the client diagnostic tool on one of them and it reports back with the following:

    WSUS Client Diagnostics Tool

    Checking Machine State
            Checking for admin rights to run tool . . . . . . . . . PASS
            Automatic Updates Service is running. . . . . . . . . . PASS
            Background Intelligent Transfer Service is running. . . PASS
            Wuaueng.dll version 7.6.7601.19016. . . . . . . . . . . PASS
                    This version is WSUS 2.0

    Checking AU Settings
            AU Option is 1 : Disabled . . . . . . . . . . . . . . . PASS
            AU Settings do not match. . . . . . . . . . . . . . . . FAIL

    Checking Proxy Configuration
            Checking for winhttp local machine Proxy settings . . . PASS
                    Winhttp local machine access type
                            <Direct Connection>
                    Winhttp local machine Proxy. . . . . . . . . .  NONE
                    Winhttp local machine ProxyBypass. . . . . . .  NONE
            Checking User IE Proxy settings . . . . . . . . . . . . PASS
                    User IE Proxy. . . . . . . . . . . . . . . . .  NONE
                    User IE ProxyByPass. . . . . . . . . . . . . .  NONE
                    User IE AutoConfig URL Proxy . . . . . . . . .  NONE
                    User IE AutoDetect
                    AutoDetect not in use

    Checking Connection to WSUS/SUS Server
                    WUServer = http://<correct server name>
                    WUStatusServer = http://<correct server name>
            UseWuServer is enabled. . . . . . . . . . . . . . . . . PASS
            Connection to server. . . . . . . . . . . . . . . . . . PASS
            SelfUpdate folder is present. . . . . . . . . . . . . . PASS

    Press Enter to Complete

    WSUS Group policy setting policy for Configure automatic updating is set to option 4

    This applies to all machines in that OU and other OUs. 

    Why are machines not being detected and when they are, it is showing this status?

    Hope you can help

    Tuesday, November 24, 2015 2:30 PM
  • I think you must upgrade WSUS version:

    WSUS 3.0 (SP2):     Build 3.2.7600.226
    WSUS 3.0 (SP2) + KB2720211:     Build 3.2.7600.251
    WSUS 3.0 (SP2) + KB2734608:     Build 3.2.7600.256
    WSUS 3.0 (SP2) + KB2828185:     Build 3.2.7600.262
    WSUS 3.0 (SP2) + KB2938066:     Build 3.2.7600.274

    I also install a WSUS 2008 R2 with some problems with this updates. KB2720211 have a long history of problems. Search by this update.

    In my case, to have my WSUS update to Build 3.2.7600.274, i have to install in this order:

    1 - Setup WSUS 3.0 SP2 > . version 226.

    2 - KB2828185 (that include KB2720211 and KB2734608) . version 262.

    3 - KB2938066. This update show an error at the end of the installation, but the WSUS version show . version 274.

    I wrote a post with this problem:

    https://social.technet.microsoft.com/Forums/windowsserver/en-US/edc904f8-78f4-441d-a67c-880fa5f42941/kb2720211-kb2734608-wsus-nightmare?forum=winserverwsus#9599f690-3b3e-4242-9afa-1db099aa1154

    I hope to have helped, be carefull and read about all this before install this updates.

    Regards,



    • Edited by Pedro_A Wednesday, November 25, 2015 11:27 AM
    • Proposed as answer by Hello_2018 Friday, December 4, 2015 2:55 AM
    • Marked as answer by Steven_Lee0510 Tuesday, December 8, 2015 9:59 AM
    Wednesday, November 25, 2015 11:26 AM
  • Hi Chance08,

    The detail report you have given seems that your client worked well.

    There is another way you could use, by resetting the client's windows automatic update ,using the following tool I give you blow:

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

    Best regards,

     


    • Edited by Hello_2018 Tuesday, December 1, 2015 4:18 AM
    Thursday, November 26, 2015 2:40 AM