locked
WSUS doesn't synchronize with clients RRS feed

  • Question

  • Hello

    The clients are listed in the wsus server, the updates are approved but the clients didn't get the updates automatically. 

    The GPO is set to auto download and schedule the install.
    If I search manually for updates on a client, it finds it. 

    WSUS Server: Win Server 2012 R2 with WSUS Version: 6.3.9600.16384.

    Client Server: Win Server 2008 R2.

    Thanks in advance.


    Friday, November 13, 2015 9:54 AM

Answers

  • Hi Florian,

    Pls find the below link for your assist,

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


    • Marked as answer by Florian White Monday, November 23, 2015 9:27 AM
    Wednesday, November 18, 2015 6:54 AM

All replies

  • Here is my log File from a Client Server:


    2015-11-13 09:54:14:079 836 5d8 PT +++++++++++  PT: Synchronizing server updates  +++++++++++
    2015-11-13 09:54:14:079 836 5d8 PT  + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://chapp537.gitbe.zehndergroup.com:8530/ClientWebService/client.asmx
    2015-11-13 09:54:35:186 836 5d8 Agent  * Found 0 updates and 77 categories in search; evaluated appl. rules of 839 out of 1803 deployed entities
    2015-11-13 09:54:35:186 836 5d8 Agent *********
    2015-11-13 09:54:35:186 836 5d8 Agent **  END  **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2015-11-13 09:54:35:186 836 5d8 Agent *************
    2015-11-13 09:54:35:186 836 810 AU >>##  RESUMED  ## AU: Search for updates [CallId = {341F9D6A-E0B6-4F72-8237-8FF7E016110C}]
    2015-11-13 09:54:35:186 836 810 AU  # 0 updates detected
    2015-11-13 09:54:35:186 836 810 AU #########
    2015-11-13 09:54:35:186 836 810 AU ##  END  ##  AU: Search for updates [CallId = {341F9D6A-E0B6-4F72-8237-8FF7E016110C}]
    2015-11-13 09:54:35:186 836 810 AU #############
    2015-11-13 09:54:35:202 836 810 AU Successfully wrote event for AU health state:0
    2015-11-13 09:54:35:202 836 810 AU Featured notifications is disabled.
    2015-11-13 09:54:35:202 836 810 AU AU setting next detection timeout to 2015-11-13 09:44:18
    2015-11-13 09:54:35:202 836 810 AU Setting AU scheduled install time to 2015-11-13 21:00:00
    2015-11-13 09:54:35:202 836 810 AU Successfully wrote event for AU health state:0
    2015-11-13 09:54:35:202 836 810 AU Successfully wrote event for AU health state:0
    2015-11-13 09:54:40:194 836 5d8 Report REPORT EVENT: {43198D5E-535D-4932-8466-EBFFDC704D85} 2015-11-13 09:54:35:186+0100 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software Synchronization Windows Update Client successfully detected 0 updates.
    2015-11-13 09:54:40:194 836 5d8 Report REPORT EVENT: {A5E13F28-7622-4A3B-BF07-625C7AF18ED9} 2015-11-13 09:54:35:186+0100 1 156 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Pre-Deployment Check Reporting client status.
    2015-11-13 10:06:41:368 836 5d8 PT WARNING: Cached cookie has expired or new PID is available
    2015-11-13 10:06:41:368 836 5d8 PT Initializing simple targeting cookie, clientId = 022888e0-94a6-4e76-aa8e-12e0abde864f, target group = , DNS name = chapp120.gitbe.zehndergroup.com
    2015-11-13 10:06:41:368 836 5d8 PT  Server URL = http://chapp537.gitbe.zehndergroup.com:8530/SimpleAuthWebService/SimpleAuth.asmx
    2015-11-13 10:06:43:723 836 5d8 Report Uploading 2 events using cached cookie, reporting URL = http://chapp537.gitbe.zehndergroup.com:8530/ReportingWebService/ReportingWebService.asmx
    2015-11-13 10:06:43:723 836 5d8 Report Reporter successfully uploaded 2 events.
    2015-11-13 10:23:56:036 836 1328 AU AU received policy change subscription event
    2015-11-13 10:23:56:036 836 1328 AU AU Options changed from policy.
    2015-11-13 10:23:56:036 836 1328 AU Successfully wrote event for AU health state:0
    2015-11-13 10:23:56:036 836 1328 AU ###########  AU: Policy change processed  ###########
    2015-11-13 10:23:56:036 836 1328 AU  # Policy changed, AU refresh required = No
    2015-11-13 10:23:56:036 836 1328 AU  # WSUS server: http://chapp537.gitbe.zehndergroup.com:8530
    2015-11-13 10:23:56:036 836 1328 AU  # Detection frequency: 1
    2015-11-13 10:23:56:036 836 1328 AU  # Approval type: Scheduled (Policy)
    2015-11-13 10:23:56:036 836 1328 AU  # Scheduled install day/time: Every day at 12:00
    2015-11-13 10:23:56:036 836 1328 AU  # Auto-install minor updates: No (Policy)
    2015-11-13 10:23:56:036 836 1328 AU  # Power management is turned off through policy
    2015-11-13 10:23:56:036 836 1328 AU AU settings changed through Policy.
    2015-11-13 10:23:56:036 836 1328 AU Setting AU scheduled install time to 2015-11-13 11:00:00
    2015-11-13 10:23:56:036 836 1328 AU Successfully wrote event for AU health state:0
    2015-11-13 10:23:56:082 836 1328 AU Successfully wrote event for AU health state:0

    Friday, November 13, 2015 10:01 AM
  • Hi Florian,

    You mean that, client machines are listed in the WSUS admin console but client machines are not running windows update.

    First you have to check, whether the client machine and WSUS server machines are communicating each others, for that

    Open WSUS admin console> Updates> Computers> Unassigned computer, select one of the client machine in the list and check the Last status report and last contact in the tab window. if Last status report has shown as not yet reported mean, you have to do some steps in the client machines,

    Open cmd prompt in the client machine and followed those commands in the client machines

    gpupdate /force /boot /logoff 

    logon the machine once the system has logged off then, 

    open cmd prompt and type, wuauclt /detectnow> exit

    then wait for sometimes and then check in the WSUS admin console.

    Friday, November 13, 2015 1:02 PM
  • Hi Arun,

    The WSUS Server get a report of my Clients. 

    Last Status Reported: 11/13/2015 3:34 PM.


    Friday, November 13, 2015 3:37 PM
  • Hi Florian,

    Pls find the below link for your assist,

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


    • Marked as answer by Florian White Monday, November 23, 2015 9:27 AM
    Wednesday, November 18, 2015 6:54 AM
  • Hi Arun

    With step 6 I was able to solve the problem.

    Thanks for your help.

    Monday, November 23, 2015 9:30 AM