locked
WSUS is Not Working RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    I have configured a WSUS server on Server 2008 R2 and updated it with latest patches (KB2720211, KB2734608, KB2828185, and KB2938066). But there are computers that getting reported to WSUS server without no issues and there are computers that it only displaying in computers section with the exclamation mark and it displays “This computer has not reported status yet” message. This is really annoying issue and I have spent lot of time to figure this out but it doesn’t work very well.

    Below I have inserted a part of a “windowsupdate.log” file which I got from a successful and unsuccessful computer.


    Successful Computer

    2016-06-08          21:22:05:662       740        d84         Setup    Client version: Core: 7.6.7600.256  Aux: 7.6.7600.256

    2016-06-08          21:22:05:662       740        d84         Misc       Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:

    2016-06-08          21:22:05:678       740        d84         Misc       Microsoft signed: Yes

    2016-06-08          21:22:05:678       740        d84         Misc       Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:

    2016-06-08          21:22:05:678       740        d84         Misc       Microsoft signed: Yes

    2016-06-08          21:22:05:678       740        d84         Misc       Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:

    2016-06-08          21:22:05:694       740        d84         Misc       Microsoft signed: Yes

    2016-06-08          21:22:05:694       740        d84         Misc       Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:

    2016-06-08          21:22:05:694       740        d84         Misc       Microsoft signed: Yes

    2016-06-08          21:22:05:694       740        d84         Setup    Determining whether a new setup handler needs to be downloaded

    2016-06-08          21:22:05:694       740        d84         Setup    SelfUpdate handler is not found.  It will be downloaded

    Unsuccessful Computer

    2016-06-08          22:22:28:645       496        aa4         Setup    Client version: Core: 7.6.7600.320  Aux: 7.6.7600.320

    2016-06-08          22:22:28:645       496        aa4         Misc       Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab with dwProvFlags 0x00000080:

    2016-06-08          22:22:53:683       496        aa4         Misc       Microsoft signed: NA

    2016-06-08          22:22:53:683       496        aa4         Misc       Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\TMPB80F.tmp with dwProvFlags 0x00000080:

    2016-06-08          22:23:18:767       496        aa4         Misc       Microsoft signed: NA

    2016-06-08          22:23:18:783       496        aa4         Misc       Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab with dwProvFlags 0x00000080:

    2016-06-08          22:23:18:799       496        aa4         Misc       Microsoft signed: NA

    2016-06-08          22:23:18:799       496        aa4         Misc       Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab with dwProvFlags 0x00000080:

    2016-06-08          22:23:18:799       496        aa4         Misc       Microsoft signed: NA

    2016-06-08          22:23:18:830       496        aa4         Setup    Determining whether a new setup handler needs to be downloaded

    2016-06-08          22:23:18:845       496        aa4         Setup    SelfUpdate handler is not found.  It will be downloaded

    Could you please give me a solution to get rid of this issue?

    Regards,

    Thisaru Perera.

    Wednesday, June 8, 2016 8:01 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    Thank you very for your reply Anne.

    I was able to successfully resolve the issue. All the clients are automatically reported back to the WSUS console after 4 to 5 hours. Hope this duration is normal.

    Anyway thanks a lot for your valuable response.

    Regards,

    Thisaru Perera.

    Sunday, June 12, 2016 4:11 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Thisaru,

    According to your description, several WSUS clients do not report to WSUS server after upgrading WSUS server.

    Try if reset windows update components on problematic clients could work:

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

    After resetting, run wuauclt/detectnow, then wait for some time, check if clients could report.

    If it still doesn't work, please reindex WSUS database on WSUS server and run server cleanup wizard:

    Reindex WSUS database:

    https://gallery.technet.microsoft.com/scriptcenter/6f8cde49-5c52-4abd-9820-f1d270ddea61

    Best Regards,

    Anne

    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    Thursday, June 9, 2016 5:05 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Thisaru,

    The snippets you post are not showing any mis-behavior, please refer to the article below for more info:

    How to read the Windowsupdate.log file

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

    The latest Windows Update Agent should be installed:

    Windows Update Client for Windows 7 and Windows Server 2008 R2: March 2016

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

    The only difference in your post is the version of the Windows Update Agent: .256/.320 which are both very old.

    Best regards,

    Andrei


    We could change the world, if God would give us the source code.

    Friday, June 10, 2016 5:08 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Thank you very for your reply Anne.

    I was able to successfully resolve the issue. All the clients are automatically reported back to the WSUS console after 4 to 5 hours. Hope this duration is normal.

    Anyway thanks a lot for your valuable response.

    Regards,

    Thisaru Perera.

    Sunday, June 12, 2016 4:11 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Thank you very much for your reply Andrei.

    As I said to Anne, I was able to successfully resolve the issue. All the clients are automatically reported back to the WSUS console after 4 to 5 hours.

    I will let you know about the status after installing the update that you have mentioned.

    Anyway thanks a lot for your valuable response.

    Regards,

    Thisaru Perera.

    Sunday, June 12, 2016 4:18 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Thisaru,

    Glad to hear you have resolved the issue. Yeah, it will take a period of time for clients to report to the WSUS server. Now you may mark your reply as answers and we can close this case.

    Best Regards,

    Anne

    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.


    Monday, June 13, 2016 1:30 AM