locked
WSUS Clients not reporting to WSUS server for more than 80 days RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    We have WSUS clients that are not reporting to WSUS server for more than 80 days approximately. These systems are marked RED in WSUS console.

    - Some of these systems marked RED, have failed to install one or more updates.

    - And large number of systems showing as RED have not been reported to WSUS server.

    Please advice on how to troubleshoot this issue.

    Regards, Lorin Davis

    Tuesday, February 17, 2015 1:56 PM

Answers

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Am 17.02.2015 schrieb Lorin Jovita:

    We have WSUS clients that are not reporting to WSUS server for more than 80 days approximately. These systems are marked RED in WSUS console.

    - Some of these systems marked RED, have failed to install one or more updates.

    - And large number of systems showing as RED have not been reported to WSUS server.

    Pls look for errormessages in the %windir%\WindowsUpdate.log on this
    Systems. Scroll to the bottom of the file.

    Which is the OS your WSUS is installed? Which OS have the Clients who
    not reported long time?

    Servus
    Winfried

    Gruppenrichtlinien
    HowTos zum WSUS Package Publisher
    WSUS Package Publisher
    HowTos zum Local Update Publisher
    NNTP-Bridge für MS-Foren

    Tuesday, February 17, 2015 1:59 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    WSUS is installed on a Windows server 2008. Clients not reporting to WSUS server are Windows 7 machines.

    WindowsUpdate.log has continuous warnings like "Failed to evaluate installed rule" and found an error like "Failed to synchronize".

    Regards, Lorin Davis

    Tuesday, February 17, 2015 6:56 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Can you try the below to reset the authorization and force a connection back from one of the win 7 machines: it should help pinpoint exact issues. 

    1. Record the system time.

    2. Reboot the system (or restart the Windows Update service).

    3. After reboot run the command wuauclt /resetauthorization /detectnow.

    4. Wait 30 minutes.

    5. Post the entries from the WindowsUpdate.log starting at the time recorded in Step #1.

    Do you have any Windows 7 machines that are reporting? Are other machines with different operating systems reporting correctly?

    Tuesday, February 17, 2015 8:14 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Am 17.02.2015 schrieb Lorin Jovita:

    WSUS is installed on a Windows server 2008.

    Pls check your WSUS-Build. If it is not .274, install Updates they are
    needed. Where i can find the Build:
    http://www.wsus.de/images/wsus-version.png

    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

    Clients not reporting to WSUS server are Windows 7 machines.

    Are they cleints cloned? Try method 1:
    http://support.microsoft.com/kb/903262

    WindowsUpdate.log has continuous warnings like "Failed to evaluate installed rule" and found an error like "Failed to synchronize".

    No Errormessages like 0.x80....?

    Servus
    Winfried

    Gruppenrichtlinien
    HowTos zum WSUS Package Publisher
    WSUS Package Publisher
    HowTos zum Local Update Publisher
    NNTP-Bridge für MS-Foren

    • Proposed as answer by Vivian_Wang Monday, March 9, 2015 7:23 AM
    • Marked as answer by Vivian_Wang Tuesday, March 10, 2015 1:58 AM
    Wednesday, February 18, 2015 5:57 AM