locked
Windows client server showing WSUS as as NULL. RRS feed

  • Question

  • In Clients this path not available in regedit.

    HKLM\software\policies\windows\WindwosUpdate\WUServer

    HKLM\software\policies\windows\WindwosUpdate\Wuerverstatus

    I am getting below path:

    HKLM\software\policies\windows\ 

    Logs:

    2018-02-01 00:56:52:856 40492 5f0c Agent   * WSUS server: <NULL>
    2018-02-01 00:56:52:856 40492 5f0c Agent   * WSUS status server: <NULL>
    2018-02-01 00:56:52:856 40492 5f0c Agent   * Target group: (Unassigned Computers)
    2018-02-01 00:56:52:856 40492 5f0c Agent   * Windows Update access disabled: No


    Thursday, February 1, 2018 7:23 AM

All replies

  • Did you check that the policy which assigns update server to the client is actually applied? run GPresult or RSoP and check the applied gpos list.

    Gleb.

    Thursday, February 1, 2018 8:37 AM
  • 1. Try this tool,

    https://gallery.technet.microsoft.com/scriptcenter/Reset-Windows-Update-Agent-d824badc

    2. Follow up below guide lines also...

    1. Check Availability of Registry settings.

    HKLM->Software->Policies->Microsoft->Window->WindowsUpdate

    2. Make sure he WSUS client can see the WSUS website by navigating to :

    http://(Name Of WSUS Server):8530/Selfupdate/iuident.cab and make sure open/download the file

    3. View Proxy configuration on WSUS client
    Open cmd and run :
    i. netsh winhttp show proxy
    ii.    netsh winhttp import proxy source=ie

    4. Open cmd and Run ‘wuauclt / detectnow’ command 

    5. Check WSUS log file in below path for errors
    c:\windows\WindowsUpdate.log

    6. Sometimes image a machine (or a clone a VM) keeps it’s unique update ID.
    If this happens then the first machine with this ID to register gets listed, and all the rest do not. To find out if this is the problem, 
    i. locate and stop the WSUS service on the affected client. 
    ii.    Open Registry Editor and navigate to:
    HKLM->Software->Microsoft->Windows->Current Version->WinowsUpdate

    iii. Delete SusClientID entry.
    iv. Restart WSUS service and run below commands.
    Wuauclt /resetauthorization /detectnow
    Wuauclt /reportnow

    • Proposed as answer by Elton_Ji Friday, February 2, 2018 4:35 AM
    Thursday, February 1, 2018 11:54 AM
  • I am getting the below error when I try gpupdate in client machines.

    ===============

    C:\Windows\system32>gpupdate /force
    Updating policy...

    Computer policy could not be updated successfully. The following errors were enc
    ountered:

    The processing of Group Policy failed because of lack of network connectivity to
     a domain controller. This may be a transient condition. A success message would
     be generated once the machine gets connected to the domain controller and Group
     Policy has successfully processed. If you do not see a success message for seve
    ral hours, then contact your administrator.
    User Policy could not be updated successfully. The following errors were encount
    ered:

    The processing of Group Policy failed because of lack of network connectivity to
     a domain controller. This may be a transient condition. A success message would
     be generated once the machine gets connected to the domain controller and Group
     Policy has successfully processed. If you do not see a success message for seve
    ral hours, then contact your administrator.

    To diagnose the failure, review the event log or run GPRESULT /H GPReport.html f
    rom the command line to access information about Group Policy results.

    ===================

    Thursday, March 1, 2018 7:48 AM
  • I am not able to see  below regedit path in my client machine.

    "HKLM->Software->Policies->Microsoft->Window->WindowsUpdate"

    In My machine I am seeing this alone

    "HKLM->Software->Policies->Microsoft->Windows"

    Thanks,


    * One more thing I am using default 80 port not 8530 port.

    Thursday, March 1, 2018 7:51 AM
  • Your Group Policies were not applied. Please change them manually with Group Policies. Then check the status.
    Thursday, March 1, 2018 11:39 AM
  • I  have created separate Windows update group policy in Domain server. Even though it is not working. I have been trying to troubleshoot more than an 6months but not able to get it done. Previously we have used 2012 R2 after that moved to to 2016. I can get updates for Windows 7 and 2008, 2012 R2 OS verisons. Only issue with 8.1 and 10 OS. Can any one please give me fix for this? 

    I am even changed the gpo settings that pointing to WSUS in client servers. But still same issue in my case !!!!!

    Wednesday, April 18, 2018 12:33 PM
  • Can you please share the steps to create Group policies at client servers side?
    Thursday, September 6, 2018 5:59 AM