locked
Clients not receiving updates from WSUS server RRS feed

  • Question

  • Configured WSUS serer with group policy.Synchronization also done. Created computer group in all computers.

    But computers not added in this group.

    Thanks,

    JNR

    Wednesday, September 21, 2016 10:09 PM

Answers

  • Hi Nagaraju J,

    >2) I deployed GPO correctly only, but in client machines wsus policy is not showing when given gpresult /r

    Registry keys in HKLM\SOFTWARE\Policies\Microsoft\Windows\Windows Update there is no windows update folder.

    This indicates the client do not apply the GPO correctly:

    1. Please check if the client in a domain member;

    2. If yes, please check the network connection between the client and DC;

    3. Please run gpupdate /force on the client to force the apply of the GPO;

    You need to ensure the GPO apply correctly and related registry keys are right first.

    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 Subscriber Support, contact tnmff@microsoft.com.

    Friday, September 23, 2016 3:17 AM

All replies

  • Hi Nagaraju J,

    1. What is the version of you WSUS server?

    2. If you use GPO to deploy WSUS clients, please check the clients apply the GPO correctly. Please check related registry keys in HKLM\SOFTWARE\Policies\Microsoft\Windows\Windows Update, check if the WSUS server address is correct;

    3. If you use the WSUS server's name in WUServer URL, please check your DNS settings, enable the client can resolve the name of the WSUS server;

    4. Have you enabled client side targeting, if yes, then you need to ensure the computer group name is totally the same with that in GPO, and in WSUS server, check "Use Group Policy or registry settings on computers":

    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 Subscriber Support, contact tnmff@microsoft.com.

    Thursday, September 22, 2016 5:15 AM
  • Hi Anne,

    1)WSUS Version is 6.3.9600.16384.

    2) I deployed GPO correctly only, but in client machines wsus policy is not showing when given gpresult /r

    Registry keys in HKLM\SOFTWARE\Policies\Microsoft\Windows\Windows Update there is no windows update folder.

    3)when can i enable the client to resolve the name of the WSUS server;

    4) I already enabled client side targeting. Computer name group and GPO name bothe are with same name.

    The Client computers are not showing in wsus server.


    Thursday, September 22, 2016 7:30 PM
  • Hi Anne,

    1)WSUS Version is 6.3.9600.16384.

    2) I deployed GPO correctly only, but in client machines wsus policy is not showing when given gpresult /r

    Then your issue is Group Policy related. Check your policy and OUs again. 

    Thursday, September 22, 2016 8:08 PM
  • Hi ,

    Please go through this link which may help you.

    https://technet.microsoft.com/en-us/magazine/gg153542.aspx

    Thursday, September 22, 2016 8:21 PM
  • Hi Nagaraju J,

    >2) I deployed GPO correctly only, but in client machines wsus policy is not showing when given gpresult /r

    Registry keys in HKLM\SOFTWARE\Policies\Microsoft\Windows\Windows Update there is no windows update folder.

    This indicates the client do not apply the GPO correctly:

    1. Please check if the client in a domain member;

    2. If yes, please check the network connection between the client and DC;

    3. Please run gpupdate /force on the client to force the apply of the GPO;

    You need to ensure the GPO apply correctly and related registry keys are right first.

    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 Subscriber Support, contact tnmff@microsoft.com.

    Friday, September 23, 2016 3:17 AM
  • Hi Anne,

    I am not able to  resolve this issue up to now.

    In Rsop there is no 'Administrative template" item in both computer and User configuration

    Thanks,

    Nagaraju

    Wednesday, September 28, 2016 8:32 PM
  • Hi Nagaraju J,

    >In Rsop there is no 'Administrative template" item in both computer and User configuration

    If you didn't modify the GPO, then in RSOP, it is normal that there's no "Administrative template".

    To check GPO apply result, please run  "gpupdate /force" to apply, then run "gpresult /h C:\report.html" on client.

    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 Subscriber Support, contact tnmff@microsoft.com.

    Thursday, September 29, 2016 8:38 AM
  • Hi Nagaraju J,

    Could the above replies be of help? If yes, you may mark it as answer, if not, feel free to feed back.

    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 Subscriber Support, contact tnmff@microsoft.com.

    Monday, October 3, 2016 6:22 AM
  • Hi Anne,

    No, the above replies didn't help for me. How can i share windows update log file.

    Thanks & regards,

    Nagaraju J

    

    Monday, October 3, 2016 7:41 PM
  • 2016-09-29 00:59:27:231 872 12a0 Service ** START **  Service: Service startup
    2016-09-29 00:59:27:231 872 12a0 Service *********
    2016-09-29 00:59:27:246 872 12a0 IdleTmr Non-AoAc machine.  Aoac operations will be ignored.
    2016-09-29 00:59:27:246 872 12a0 Agent  * WU client version 7.9.9600.18340
    2016-09-29 00:59:27:246 872 12a0 Agent WARNING: SleepStudyTracker: Machine is non-AOAC. Sleep study tracker disabled.
    2016-09-29 00:59:27:246 872 12a0 Agent  * Base directory: C:\Windows\SoftwareDistribution
    2016-09-29 00:59:27:246 872 12a0 Agent  * Access type: No proxy
    2016-09-29 00:59:27:246 872 12a0 Service UpdateNetworkState Ipv6, cNetworkInterfaces = 1.
    2016-09-29 00:59:27:246 872 12a0 Service UpdateNetworkState Ipv4, cNetworkInterfaces = 1.
    2016-09-29 00:59:27:246 872 12a0 Agent  * Network state: Connected
    2016-09-29 00:59:27:246 872 12a0 Service UpdateNetworkState Ipv6, cNetworkInterfaces = 1.
    2016-09-29 00:59:27:246 872 12a0 Service UpdateNetworkState Ipv4, cNetworkInterfaces = 1.
    2016-09-29 00:59:27:277 872 12a0 Agent ***********  Agent: Initializing global settings cache  ***********
    2016-09-29 00:59:27:277 872 12a0 Agent  * Endpoint Provider: 00000000-0000-0000-0000-000000000000
    2016-09-29 00:59:27:277 872 12a0 Agent  * WSUS server: <NULL>
    2016-09-29 00:59:27:277 872 12a0 Agent  * WSUS status server: <NULL>
    2016-09-29 00:59:27:277 872 12a0 Agent  * Target group: (Unassigned Computers)
    2016-09-29 00:59:27:277 872 12a0 Agent  * Windows Update access disabled: No
    2016-09-29 00:59:27:277 872 12a0 Misc WARNING: Network Cost is assumed to be not supported as something failed with trying to get handles to wcmapi.dll
    2016-09-29 00:59:27:293 872 12a0 WuTask WuTaskManager delay initialize completed successfully..
    2016-09-29 00:59:27:293 872 12a0 AU    Timer: 31DA7559-FE27-4810-8FF6-987195B1FD98, Expires 2016-09-29 05:54:04, not idle-only, not network-only
    2016-09-29 00:59:27:293 872 12a0 AU    Timer: CF1ABEC6-7887-4964-BB93-B2E21B31CEC1, Expires 2016-09-29 00:08:32, not idle-only, not network-only
    2016-09-29 00:59:27:293 872 12a0 AU    Timer: 29A863E7-8609-4D1E-B7CD-5668F857F1DB, Expires 2016-09-29 00:08:32, not idle-only, not network-only
    2016-09-29 00:59:27:293 872 12a0 Report CWERReporter::Init succeeded
    2016-09-29 00:59:27:293 872 12a0 Agent ***********  Agent: Initializing Windows Update Agent  ***********
    2016-09-29 00:59:27:293 872 12a0 DnldMgr Download manager restoring 0 downloads
    2016-09-29 00:59:27:293 872 12a0 AU ###########  AU: Initializing Automatic Updates  ###########
    2016-09-29 00:59:27:293 872 12a0 AU AIR Mode is disabled
    2016-09-29 00:59:27:293 872 12a0 AU  # Approval type: Scheduled (User preference)
    2016-09-29 00:59:27:293 872 12a0 AU  # Auto-install minor updates: Yes (User preference)
    2016-09-29 00:59:27:293 872 12a0 AU  # Will interact with non-admins (Non-admins are elevated (User preference))
    2016-09-29 00:59:27:324 872 12a0 AU WARNING: Failed to get Wu Exemption info from NLM, assuming not exempt, error = 0x80240037
    2016-09-29 00:59:27:324 872 12a0 AU WARNING: Failed to get Network Cost info from NLM, assuming network is NOT metered, error = 0x80240037
    2016-09-29 00:59:27:324 872 12a0 AU AU finished delayed initialization
    2016-09-29 00:59:27:340 872 12a0 AU Currently AUX is enabled - so not show any WU Upgrade notifications.
    2016-09-29 00:59:27:340 872 12a0 AU WARNING: Failed to get Network Cost info from NLM, assuming network is NOT metered, error = 0x80240037
    2016-09-29 00:59:27:340 872 12a0 AU WARNING: Failed to get Network Cost info from NLM, assuming network is NOT metered, error = 0x80240037
    2016-09-29 00:59:27:340 872 c20 DnldMgr Asking handlers to reconcile their sandboxes
    2016-09-29 01:04:27:303 872 12a0 AU AU received policy change subscription event
    2016-09-29 01:09:27:419 872 2e0 AU Earliest future timer found: 
    2016-09-29 01:09:27:419 872 2e0 AU    Timer: CF1ABEC6-7887-4964-BB93-B2E21B31CEC1, Expires 2016-09-29 00:08:32, not idle-only, not network-only
    2016-09-29 01:09:28:122 872 12a0 AU AU received policy change subscription event
    2016-09-29 01:09:28:420 872 12a0 AU ###########  AU: Uninitializing Automatic Updates  ###########
    2016-09-29 01:09:28:435 872 12a0 WuTask Uninit WU Task Manager
    2016-09-29 01:09:28:482 872 12a0 AU Earliest future timer found: 
    2016-09-29 01:09:28:482 872 12a0 AU    Timer: CF1ABEC6-7887-4964-BB93-B2E21B31CEC1, Expires 2016-09-29 00:08:32, not idle-only, not network-only
    2016-09-29 01:09:28:498 872 12a0 AU Earliest future timer found: 
    2016-09-29 01:09:28:498 872 12a0 AU    Timer: CF1ABEC6-7887-4964-BB93-B2E21B31CEC1, Expires 2016-09-29 00:08:32, not idle-only, not network-only
    2016-09-29 01:09:28:560 872 12a0 Service *********
    2016-09-29 01:09:28:560 872 12a0 Service **  END  **  Service: Service exit [Exit code = 0x240001]
    2016-09-29 01:09:28:560 872 12a0 Service *************
    2016-09-29 01:14:28:436 872 ba8 Misc ===========  Logging initialized (build: 7.9.9600.18340, tz: +0530)  ===========
    2016-09-29 01:14:28:436 872 ba8 Misc  = Process: C:\Windows\system32\svchost.exe
    2016-09-29 01:14:28:436 872 ba8 Misc  = Module: c:\windows\system32\wuaueng.dll
    • Edited by Nagaraju J Monday, October 3, 2016 7:49 PM
    Monday, October 3, 2016 7:47 PM
  • Hi Anne,

    We have two DC servers previously, one is Primary another secondary. That we installed WSUS on primary, Now we shutdown Primary DC server. We are using only secondary DC at present.

    Is any problem with this changes.

    Thanks,

    Nagaraju

    Monday, October 3, 2016 8:09 PM
  • Hi Nagaraju J,

    WSUS is not domain based, so, the key to solve the issue is to ensure your WSUS server works well, and WSUS clients could apply the GPO correctly.

    According to your above replies and your windows update log, seems your WSUS clients didn't apply the GPO, so, you need to figure out why the clients not apply the GPO.

    Since you have two DCs previously, then do you dismiss the primary DC using the correctly way, could the clients contact with the present DC correctly. These are all DS issues. After enabling the client could apply the GPO correctly, then troubleshoot later issue.

    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 Subscriber Support, contact tnmff@microsoft.com.

    Thursday, October 6, 2016 2:38 AM