locked
Windows Update Can't Connect to WSUS Server (Which Happens to be Itself) After Switch to SSL RRS feed

  • Question

  • I recently switched our WSUS server from using HTTP to SSL.  The certificate comes from an internal CA (Windows Server 2012 R2, AD CS).  Client computers received the updated WSUS url via group policy (https://wsus.contoso.com:8531) which applies to all computers (including servers).  It works. On all of them.  Except...the actual WSUS server itself.  It throws an Error Code 80072EFE pretty much instantaneously when I manually try to check for updates.  Checking for updates via Microsoft's external Windows Update source works fine.

    Any ideas what might be the issue?  

    Below is a cycle of a failed attempt taken from the windowsupdate.log [host has been changed to "wsus.contoso.com"].

    2014-03-27 16:13:20:319 864 568 Misc ===========  Logging initialized (build: 7.9.9600.16422, tz: -0400)  ===========
    2014-03-27 16:13:20:334 864 568 Misc  = Process: C:\Windows\system32\svchost.exe
    2014-03-27 16:13:20:334 864 568 Misc  = Module: c:\windows\system32\wuaueng.dll
    2014-03-27 16:13:20:319 864 568 Service *************
    2014-03-27 16:13:20:334 864 568 Service ** START **  Service: Service startup
    2014-03-27 16:13:20:334 864 568 Service *********
    2014-03-27 16:13:20:428 864 568 Agent  * WU client version 7.9.9600.16422
    2014-03-27 16:13:20:428 864 568 Agent  * Base directory: C:\Windows\SoftwareDistribution
    2014-03-27 16:13:20:428 864 568 Agent  * Access type: No proxy
    2014-03-27 16:13:20:428 864 568 Service UpdateNetworkState Ipv6, cNetworkInterfaces = 1.
    2014-03-27 16:13:20:428 864 568 Service UpdateNetworkState Ipv4, cNetworkInterfaces = 1.
    2014-03-27 16:13:20:428 864 568 Agent  * Network state: Connected
    2014-03-27 16:13:20:522 864 568 Service UpdateNetworkState Ipv6, cNetworkInterfaces = 1.
    2014-03-27 16:13:20:522 864 568 Service UpdateNetworkState Ipv4, cNetworkInterfaces = 1.
    2014-03-27 16:13:20:553 864 568 Agent ***********  Agent: Initializing global settings cache  ***********
    2014-03-27 16:13:20:553 864 568 Agent  * Endpoint Provider: 00000000-0000-0000-0000-000000000000
    2014-03-27 16:13:20:553 864 568 Agent  * WSUS server: https://wsus.contoso.com:8531
    2014-03-27 16:13:20:553 864 568 Agent  * WSUS status server: https://wsus.contoso.com:8531
    2014-03-27 16:13:20:553 864 568 Agent  * Target group: (Unassigned Computers)
    2014-03-27 16:13:20:553 864 568 Agent  * Windows Update access disabled: No
    2014-03-27 16:13:20:600 864 568 Misc WARNING: Network Cost is assumed to be not supported as something failed with trying to get handles to wcmapi.dll
    2014-03-27 16:13:20:709 864 568 WuTask WuTaskManager delay initialize completed successfully..
    2014-03-27 16:13:20:912 864 568 Report CWERReporter::Init succeeded
    2014-03-27 16:13:20:912 864 568 Agent ***********  Agent: Initializing Windows Update Agent  ***********
    2014-03-27 16:13:20:912 864 568 DnldMgr Download manager restoring 0 downloads
    2014-03-27 16:13:20:912 864 568 AU ###########  AU: Initializing Automatic Updates  ###########
    2014-03-27 16:13:20:912 864 568 AU AIR Mode is disabled
    2014-03-27 16:13:20:912 864 568 AU  # Policy Driven Provider: https://wsus.contoso.com:8531
    2014-03-27 16:13:20:912 864 568 AU  # Detection frequency: 22
    2014-03-27 16:13:20:912 864 568 AU  # Approval type: Scheduled (Policy)
    2014-03-27 16:13:20:912 864 568 AU  # Auto-install minor updates: No (Policy)
    2014-03-27 16:13:20:912 864 568 AU  # Will interact with non-admins (Non-admins are elevated (User preference))
    2014-03-27 16:13:20:912 864 568 AU WARNING: Failed to get Wu Exemption info from NLM, assuming not exempt, error = 0x80240037
    2014-03-27 16:13:20:912 864 568 AU WARNING: Failed to get Network Cost info from NLM, assuming network is NOT metered, error = 0x80240037
    2014-03-27 16:13:20:928 864 568 AU AU finished delayed initialization
    2014-03-27 16:13:20:928 864 568 AU WARNING: Failed to get Network Cost info from NLM, assuming network is NOT metered, error = 0x80240037
    2014-03-27 16:13:20:928 864 568 AU WARNING: Failed to get Network Cost info from NLM, assuming network is NOT metered, error = 0x80240037
    2014-03-27 16:13:20:944 864 68c DnldMgr Asking handlers to reconcile their sandboxes
    2014-03-27 16:14:37:997 864 568 AU #############
    2014-03-27 16:14:37:997 864 568 AU ## START ##  AU: Search for updates
    2014-03-27 16:14:37:997 864 568 AU #########
    2014-03-27 16:14:37:997 864 568 IdleTmr WU operation (CSearchCall::Init ID 1) started; operation # 7; does use network; is at background priority
    2014-03-27 16:14:37:997 864 568 IdleTmr Incremented PDC RefCount for Network to 1
    2014-03-27 16:14:38:325 864 568 Report ***********  Report: Initializing static reporting data  ***********
    2014-03-27 16:14:38:325 864 568 Report  * OS Version = 6.3.9600.0.0.131344
    2014-03-27 16:14:38:325 864 568 Report  * OS Product Type = 0x00000007
    2014-03-27 16:14:38:388 864 568 Report  * Computer Brand = Microsoft Corporation
    2014-03-27 16:14:38:388 864 568 Report  * Computer Model = Virtual Machine
    2014-03-27 16:14:38:388 864 568 Report  * Platform Role = 1
    2014-03-27 16:14:38:388 864 568 Report  * AlwaysOn/AlwaysConnected (AOAC) = 0
    2014-03-27 16:14:38:388 864 568 Report  * Bios Revision = Hyper-V UEFI Release v1.0
    2014-03-27 16:14:38:388 864 568 Report  * Bios Name = Hyper-V UEFI Release v1.0
    2014-03-27 16:14:38:388 864 568 Report  * Bios Release Date = 2012-11-26T00:00:00
    2014-03-27 16:14:38:388 864 568 Report  * Bios Sku Number = None
    2014-03-27 16:14:38:388 864 568 Report  * Bios Vendor = Microsoft Corporation
    2014-03-27 16:14:38:388 864 568 Report  * Bios Family = Virtual Machine
    2014-03-27 16:14:38:388 864 568 Report  * Bios Major Release = 1
    2014-03-27 16:14:38:388 864 568 Report  * Bios Minor Release = 0
    2014-03-27 16:14:38:388 864 568 Report  * Locale ID = 1033
    2014-03-27 16:14:38:497 864 568 Agent *** START ***  Queueing Finding updates [CallerId = AutomaticUpdates  Id = 1]
    2014-03-27 16:14:38:497 864 568 AU <<## SUBMITTED ## AU: Search for updates  [CallId = {59B96811-6D62-4592-AD08-CADF29EA742B} ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}]
    2014-03-27 16:14:38:497 864 71c Agent ***  END  ***  Queueing Finding updates [CallerId = AutomaticUpdates  Id = 1]
    2014-03-27 16:14:38:497 864 71c Agent *************
    2014-03-27 16:14:38:497 864 71c Agent ** START **  Agent: Finding updates [CallerId = AutomaticUpdates  Id = 1]
    2014-03-27 16:14:38:497 864 71c Agent *********
    2014-03-27 16:14:38:497 864 71c Agent  * Online = Yes; Ignore download priority = No
    2014-03-27 16:14:38:497 864 71c Agent  * Criteria = "IsInstalled=0 and DeploymentAction='Installation' or IsPresent=1 and DeploymentAction='Uninstallation' or IsInstalled=1 and DeploymentAction='Installation' and RebootRequired=1 or IsInstalled=0 and DeploymentAction='Uninstallation' and RebootRequired=1"
    2014-03-27 16:14:38:497 864 71c Agent  * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
    2014-03-27 16:14:38:497 864 71c Agent  * Search Scope = {Machine & All Users}
    2014-03-27 16:14:38:497 864 71c Agent  * Caller SID for Applicability: S-1-5-18
    2014-03-27 16:14:38:513 864 71c SLS Retrieving SLS response from server...
    2014-03-27 16:14:38:513 864 71c SLS Making request with URL HTTPS://sls.update.microsoft.com/SLS/{9482F4B4-E343-43B6-B170-9A65BC822C77}/x64/6.3.9600.0/0?CH=299&L=en-US&P=&PT=0x7&WUA=7.9.9600.16422
    2014-03-27 16:14:38:996 864 71c Misc Validating signature for C:\Windows\SoftwareDistribution\SLS\9482F4B4-E343-43B6-B170-9A65BC822C77\sls.cab:
    2014-03-27 16:14:38:996 864 71c Misc Microsoft signed: Yes
    2014-03-27 16:14:39:012 864 71c Misc Infrastructure signed: Yes
    2014-03-27 16:14:39:012 864 71c Misc Validating signature for C:\Windows\SoftwareDistribution\SLS\9482F4B4-E343-43B6-B170-9A65BC822C77\TMP1D57.tmp:
    2014-03-27 16:14:39:027 864 71c Misc Microsoft signed: Yes
    2014-03-27 16:14:39:027 864 71c Misc Infrastructure signed: Yes
    2014-03-27 16:14:39:027 864 71c EP Got WSUS Client/Server URL: "https://wsus.contoso.com:8531/ClientWebService/client.asmx"
    2014-03-27 16:14:39:152 864 71c Setup Checking for agent SelfUpdate
    2014-03-27 16:14:39:215 864 71c Setup Client version: Core: 7.9.9600.16422  Aux: 7.9.9600.16384
    2014-03-27 16:14:39:215 864 71c EP Got WSUS SelfUpdate URL: "https://wsus.contoso.com:8531/selfupdate"
    2014-03-27 16:14:39:215 864 71c Misc WARNING: Send failed with hr = 80072efe.
    2014-03-27 16:14:39:215 864 71c Misc WARNING: Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes used : <None>
    2014-03-27 16:14:39:215 864 71c Misc WARNING: Send request failed, hr:0x80072efe
    2014-03-27 16:14:39:215 864 71c Misc WARNING: WinHttp: SendRequestUsingProxy failed for <https://wsus.contoso.com:8531/selfupdate/wuident.cab>. error 0x80072efe
    2014-03-27 16:14:39:215 864 71c Misc WARNING: WinHttp: SendRequestToServerForFileInformation MakeRequest failed. error 0x80072efe
    2014-03-27 16:14:39:215 864 71c Misc WARNING: WinHttp: SendRequestToServerForFileInformation failed with 0x80072efe
    2014-03-27 16:14:39:215 864 71c Misc WARNING: WinHttp: ShouldFileBeDownloaded failed with 0x80072efe
    2014-03-27 16:14:39:230 864 71c Misc WARNING: Send failed with hr = 80072efe.
    2014-03-27 16:14:39:230 864 71c Misc WARNING: Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes used : <None>
    2014-03-27 16:14:39:230 864 71c Misc WARNING: Send request failed, hr:0x80072efe
    2014-03-27 16:14:39:230 864 71c Misc WARNING: WinHttp: SendRequestUsingProxy failed for <https://wsus.contoso.com:8531/selfupdate/wuident.cab>. error 0x80072efe
    2014-03-27 16:14:39:230 864 71c Misc WARNING: WinHttp: SendRequestToServerForFileInformation MakeRequest failed. error 0x80072efe
    2014-03-27 16:14:39:230 864 71c Misc WARNING: WinHttp: SendRequestToServerForFileInformation failed with 0x80072efe
    2014-03-27 16:14:39:230 864 71c Misc WARNING: WinHttp: ShouldFileBeDownloaded failed with 0x80072efe
    2014-03-27 16:14:39:230 864 71c Misc WARNING: Send failed with hr = 80072efe.
    2014-03-27 16:14:39:230 864 71c Misc WARNING: Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes used : <None>
    2014-03-27 16:14:39:230 864 71c Misc WARNING: Send request failed, hr:0x80072efe
    2014-03-27 16:14:39:230 864 71c Misc WARNING: WinHttp: SendRequestUsingProxy failed for <https://wsus.contoso.com:8531/selfupdate/wuident.cab>. error 0x80072efe
    2014-03-27 16:14:39:230 864 71c Misc WARNING: WinHttp: SendRequestToServerForFileInformation MakeRequest failed. error 0x80072efe
    2014-03-27 16:14:39:230 864 71c Misc WARNING: WinHttp: SendRequestToServerForFileInformation failed with 0x80072efe
    2014-03-27 16:14:39:230 864 71c Misc WARNING: WinHttp: ShouldFileBeDownloaded failed with 0x80072efe
    2014-03-27 16:14:39:246 864 71c Misc WARNING: Send failed with hr = 80072efe.
    2014-03-27 16:14:39:308 864 71c Misc WARNING: Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes used : <None>
    2014-03-27 16:14:39:308 864 71c Misc WARNING: Send request failed, hr:0x80072efe
    2014-03-27 16:14:39:308 864 71c Misc WARNING: WinHttp: SendRequestUsingProxy failed for <https://wsus.contoso.com:8531/selfupdate/wuident.cab>. error 0x80072efe
    2014-03-27 16:14:39:308 864 71c Misc WARNING: WinHttp: SendRequestToServerForFileInformation MakeRequest failed. error 0x80072efe
    2014-03-27 16:14:39:308 864 71c Misc WARNING: WinHttp: SendRequestToServerForFileInformation failed with 0x80072efe
    2014-03-27 16:14:39:308 864 71c Misc WARNING: WinHttp: ShouldFileBeDownloaded failed with 0x80072efe
    2014-03-27 16:14:39:308 864 71c Misc WARNING: DownloadFileInternal failed for https://wsus.contoso.com:8531/selfupdate/wuident.cab: error 0x80072efe
    2014-03-27 16:14:39:308 864 71c Setup WARNING: SelfUpdate check failed to download package information, error = 0x80072EFE
    2014-03-27 16:14:39:308 864 71c Setup FATAL: SelfUpdate check failed, err = 0x80072EFE
    2014-03-27 16:14:39:308 864 71c Agent  * WARNING: Skipping scan, self-update check returned 0x80072EFE
    2014-03-27 16:14:39:308 864 71c Agent  * WARNING: Exit code = 0x80072EFE
    2014-03-27 16:14:39:308 864 71c Agent *********
    2014-03-27 16:14:39:308 864 71c Agent **  END  **  Agent: Finding updates [CallerId = AutomaticUpdates  Id = 1]
    2014-03-27 16:14:39:308 864 71c Agent *************
    2014-03-27 16:14:39:308 864 71c Agent WARNING: WU client failed Searching for update with error 0x80072efe
    2014-03-27 16:14:39:308 864 71c IdleTmr WU operation (CSearchCall::Init ID 1, operation # 7) stopped; does use network; is at background priority
    2014-03-27 16:14:39:308 864 71c IdleTmr Decremented PDC RefCount for Network to 0
    2014-03-27 16:14:39:308 864 4b8 AU >>##  RESUMED  ## AU: Search for updates [CallId = {59B96811-6D62-4592-AD08-CADF29EA742B} ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}]
    2014-03-27 16:14:39:308 864 4b8 AU  # WARNING: Search callback failed, result = 0x80072EFE
    2014-03-27 16:14:39:308 864 4b8 AU #########
    2014-03-27 16:14:39:308 864 4b8 AU ##  END  ##  AU: Search for updates  [CallId = {59B96811-6D62-4592-AD08-CADF29EA742B} ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}]
    2014-03-27 16:14:39:308 864 4b8 AU #############
    2014-03-27 16:14:39:308 864 4b8 AU All AU searches complete.
    2014-03-27 16:14:39:308 864 4b8 AU  # WARNING: Failed to find updates with error code 80072efe
    2014-03-27 16:14:39:308 864 4b8 AU AU setting next detection timeout to 2014-03-28 01:14:39
    2014-03-27 16:14:39:308 864 4b8 AU WARNING: Failed to get Network Cost info from NLM, assuming network is NOT metered, error = 0x80240037
    2014-03-27 16:14:39:371 864 4b8 AU WARNING: Failed to get Network Cost info from NLM, assuming network is NOT metered, error = 0x80240037
    2014-03-27 16:14:44:382 864 68c Report REPORT EVENT: {02EB88AA-6AC8-40C1-AB44-9CFB08E5C829} 2014-03-27 16:14:39:308-0400 1 148 [AGENT_DETECTION_FAILED] 101 {D67661EB-2423-451D-BF5D-13199E37DF28} 1 80072efe SelfUpdate Failure Software Synchronization Windows Update Client failed to detect with error 0x80072efe.
    2014-03-27 16:14:44:585 864 68c Report CWERReporter::HandleEvents - WER report upload completed with status 0x8
    2014-03-27 16:14:44:585 864 68c Report WER Report sent: 7.9.9600.16422 0x80072efe(0) D67661EB-2423-451D-BF5D-13199E37DF28 Scan 101 Managed
    2014-03-27 16:14:44:585 864 68c Report CWERReporter finishing event handling. (00000000)


    Sunday, March 30, 2014 12:53 AM

Answers

  • I recently switched our WSUS server from using HTTP to SSL.  The certificate comes from an internal CA (Windows Server 2012 R2, AD CS).  Client computers received the updated WSUS url via group policy (https://wsus.contoso.com:8531) which applies to all computers (including servers).

    And how, exactly, did you distribute the SSL certificate to the clients, and have you visually confirmed, using the Certificates MMC snap-in, that the SSL certificate is physically present in the correct certificate store of the WSUS server?

    Also.. masking CRITICAL configuration information makes it impossible for us to perform any useful diagnostics on that masked information. I'm quite sure that this WSUS Server does not exist in the contoso.com domain (since, presumably, you're talking about a production WSUS server, not one in a training lab).

    It works. On all of them.  Except...the actual WSUS server itself.  It throws an Error Code 80072EFE pretty much instantaneously when I manually try to check for updates.  Checking for updates via Microsoft's external Windows Update source works fine.

    Which suggests two things:

    • There's nothing wrong with the Windows Update Agent or related functionality on this system.
    • This system cannot connect with the WSUS services, where SSL was recently enabled, but presumably worked perfectly before SSL was enabled, which strongly suggest that SSL was not properly implemented. What guidance did you use to configure SSL on this WSUS v6.3 server (since there's none actually published yet for enabling SSL on WSUS on IIS8).

    Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
    My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

    • Marked as answer by Daniel JiSun Saturday, April 5, 2014 12:57 PM
    Tuesday, April 1, 2014 1:20 PM
    • There's nothing wrong with the Windows Update Agent or related functionality on this system.
    • This system cannot connect with the WSUS services, where SSL was recently enabled, but presumably worked perfectly before SSL was enabled, which strongly suggest that SSL was not properly implemented. What guidance did you use to configure SSL on this WSUS v6.3 server (since there's none actually published yet for enabling SSL on WSUS on IIS8).

    Sorry for taking so long to return to this.  It wasn't an explicit SSL issue after all, rather it turned out to be a name resolution / IP address binding issue:

    The GPO that specifies the WSUS server for domain members to use specifies it by using FQDN (e.g., https://wsus.contoso.local:8531), rather than an explicit IP address (e.g., https://192.168.0.1:8531).  When I set up the SSL Binding on IIS, I only assigned a single IP address, rather than using the select-all-unassigned wildcard '*'.  All other workstations in our domain resolve the WSUS server to this single IP address.  The server itself, does NOT resolve to that IP address, but rather resolves to its IPV6 address.  Therein lies the problem, since IIS is not binding the site to that address.

    I found two possible ways to resolve the issue in this case:

    • use the wildcard selector when configuring the SSL binding settings for the WSUS site; or
    • use the explicit IP address in GPO that configures the WSUS url for clients.
    • Marked as answer by merv_f Tuesday, April 22, 2014 8:52 PM
    Tuesday, April 22, 2014 8:51 PM

All replies

  • Hi,

    Error 0x80072EFE is an INTERNET_CONNECTION_ABORTED condition

    Try the commend

    netsh winhttp reset proxy

    If it does help, you can download and run client diagnose tool.

    Windows Server Update Services Tools and Utilities

    http://technet.microsoft.com/en-us/windowsserver/bb466192.aspx

    Hope this helps.

    • Marked as answer by Daniel JiSun Saturday, April 5, 2014 12:57 PM
    • Unmarked as answer by merv_f Tuesday, April 22, 2014 8:51 PM
    Tuesday, April 1, 2014 7:23 AM
  • I recently switched our WSUS server from using HTTP to SSL.  The certificate comes from an internal CA (Windows Server 2012 R2, AD CS).  Client computers received the updated WSUS url via group policy (https://wsus.contoso.com:8531) which applies to all computers (including servers).

    And how, exactly, did you distribute the SSL certificate to the clients, and have you visually confirmed, using the Certificates MMC snap-in, that the SSL certificate is physically present in the correct certificate store of the WSUS server?

    Also.. masking CRITICAL configuration information makes it impossible for us to perform any useful diagnostics on that masked information. I'm quite sure that this WSUS Server does not exist in the contoso.com domain (since, presumably, you're talking about a production WSUS server, not one in a training lab).

    It works. On all of them.  Except...the actual WSUS server itself.  It throws an Error Code 80072EFE pretty much instantaneously when I manually try to check for updates.  Checking for updates via Microsoft's external Windows Update source works fine.

    Which suggests two things:

    • There's nothing wrong with the Windows Update Agent or related functionality on this system.
    • This system cannot connect with the WSUS services, where SSL was recently enabled, but presumably worked perfectly before SSL was enabled, which strongly suggest that SSL was not properly implemented. What guidance did you use to configure SSL on this WSUS v6.3 server (since there's none actually published yet for enabling SSL on WSUS on IIS8).

    Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
    My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

    • Marked as answer by Daniel JiSun Saturday, April 5, 2014 12:57 PM
    Tuesday, April 1, 2014 1:20 PM
    • There's nothing wrong with the Windows Update Agent or related functionality on this system.
    • This system cannot connect with the WSUS services, where SSL was recently enabled, but presumably worked perfectly before SSL was enabled, which strongly suggest that SSL was not properly implemented. What guidance did you use to configure SSL on this WSUS v6.3 server (since there's none actually published yet for enabling SSL on WSUS on IIS8).

    Sorry for taking so long to return to this.  It wasn't an explicit SSL issue after all, rather it turned out to be a name resolution / IP address binding issue:

    The GPO that specifies the WSUS server for domain members to use specifies it by using FQDN (e.g., https://wsus.contoso.local:8531), rather than an explicit IP address (e.g., https://192.168.0.1:8531).  When I set up the SSL Binding on IIS, I only assigned a single IP address, rather than using the select-all-unassigned wildcard '*'.  All other workstations in our domain resolve the WSUS server to this single IP address.  The server itself, does NOT resolve to that IP address, but rather resolves to its IPV6 address.  Therein lies the problem, since IIS is not binding the site to that address.

    I found two possible ways to resolve the issue in this case:

    • use the wildcard selector when configuring the SSL binding settings for the WSUS site; or
    • use the explicit IP address in GPO that configures the WSUS url for clients.
    • Marked as answer by merv_f Tuesday, April 22, 2014 8:52 PM
    Tuesday, April 22, 2014 8:51 PM