none
Server tries to download updates from MS instead of configured WSUS server

    Question

  • Hey all,

    I got some strange behaviour of a server that I try to update with our WSUS server. Both the client and the WSUS server are Win2k12, not R2. A policy is applied on all servers in which the WSUS server is set. Actually, the update procedure and the policy works on all servers but this one.
    I am able to find and select updates for the target server on my WSUS server and the server is able to find the server. When I try "Install now" on the target server, nothing happens. According to the log the server is communicating with the WSUS server, but is not downloading the updates from it, instead it tries to download them from MS itself what is not possible. I inserted my proxy user and then it worked so I nailed it down.
    How can I reset all the configuration or where is the registry key that leads to the download source?

    Thanks in advance and kind regards,

    Azreth

    Thursday, June 26, 2014 9:27 AM

Answers

  • The registry keys for the update source are controlled by the group policy, so configuring the policy and making sure it is applying correctly will automatically configure the appropriate registry keys.  However, the keys specific to windows updates are located here:

    HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\WindowsUpdate

    WUServer

    Reg_SZ

    HTTP(S) URL of the WSUS server that is used by Automatic Updates and API callers (by default). This policy is paired with WUStatusServer, and both keys must be set to the same value to be valid.

    WUStatusServer

    Reg_SZ

    The HTTP(S) URL of the server to which reporting information is sent for client computers that use the WSUS server that is configured by the WUServer key. This policy is paired with WUServer, and both keys must be set to the same value to be valid.

    The full list of related keys can be found here: http://technet.microsoft.com/en-us/library/dd939844(v=ws.10).aspx

    Thursday, June 26, 2014 11:38 AM
  • actually the problem seems to be that the policy is not linked correctly. Though I do not understand why. When I use "gpresult /r" it is shown under: "The following GPOs were not applied because they were filtered out" and the paramter is "Filtering: Disabled (GPO)" on my WSUS policy.

    This suggests that you have linked the GPO to the OU, but, the GPO itself contains a ComputerSettings=disabled flag.
    Check the "GPO Status" in GPMC.

    e.g. 1/2/3 here:
    http://technet.microsoft.com/en-us/library/cc753067(v=ws.10).aspx


    Don
    (Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
    This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

    Saturday, June 28, 2014 11:15 PM

All replies

  • The registry keys for the update source are controlled by the group policy, so configuring the policy and making sure it is applying correctly will automatically configure the appropriate registry keys.  However, the keys specific to windows updates are located here:

    HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\WindowsUpdate

    WUServer

    Reg_SZ

    HTTP(S) URL of the WSUS server that is used by Automatic Updates and API callers (by default). This policy is paired with WUStatusServer, and both keys must be set to the same value to be valid.

    WUStatusServer

    Reg_SZ

    The HTTP(S) URL of the server to which reporting information is sent for client computers that use the WSUS server that is configured by the WUServer key. This policy is paired with WUServer, and both keys must be set to the same value to be valid.

    The full list of related keys can be found here: http://technet.microsoft.com/en-us/library/dd939844(v=ws.10).aspx

    Thursday, June 26, 2014 11:38 AM
  • Hi,

    What is the version of your WSUS? For WSUS 3.2 with windows server 2012 clients we have seen such issues.

    And the solution is to patch WSUS server with KB 2734608.

    http://support.microsoft.com/kb/2734608

    Hope this helps.

    Friday, June 27, 2014 5:45 AM
  • Hey all,

    actually the problem seems to be that the policy is not linked correctly. Though I do not understand why. When I use "gpresult /r" it is shown under: "The following GPOs were not applied because they were filtered out" and the paramter is "Filtering: Disabled (GPO)" on my WSUS policy.
    Also the entries in the registry and in the local policy is correct.

    The policy actually works on all servers (also 2012) within the same OU. What might be the problem? How can I resolve it?

    @Daniel JiSun: WSUS server is 4.0 and there are no issues with any other 2012 servers.

    Thanks in advance and kind regards,

    Azreth

    Friday, June 27, 2014 11:31 AM
  • actually the problem seems to be that the policy is not linked correctly. Though I do not understand why. When I use "gpresult /r" it is shown under: "The following GPOs were not applied because they were filtered out" and the paramter is "Filtering: Disabled (GPO)" on my WSUS policy.

    This suggests that you have linked the GPO to the OU, but, the GPO itself contains a ComputerSettings=disabled flag.
    Check the "GPO Status" in GPMC.

    e.g. 1/2/3 here:
    http://technet.microsoft.com/en-us/library/cc753067(v=ws.10).aspx


    Don
    (Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
    This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

    Saturday, June 28, 2014 11:15 PM