WSUS Server 2012 R2: Computers won't show up in console

SCENARIO

You used to use Server 2008 or Server 2008 R2 for your WSUS server.  You are upgrading to Server 2012 R2, but when you point your clients to the new server, they don't show up in the Update Services Console.


When we moved to Server 2012 R2 for our WSUS server, we setup a test GPO that points our client machines to the new WSUS server, but the clients were not showing up in the console.  I checked the normal settings.

1. The policy pointed the client to the right servername http://wsusserver
2. A DNS entry existed for my WSUS server. I could use nslookup to see the entry.
3. I setup the clients to download and install every week.
4. I ran the cmdline wuauclt.exe /detectnow on the client machine.

Since it wasn't working, I decided to do a netmon and procmon capture on the client and server side.  I also took a look at the Windows Update log (C:\Windows\WindowsUpdate.log) and this is what I found.

WINDOWS UPDATE LOG

2016-09-09        08:52:32:238         384        184        AU        #############

2016-09-09        08:52:32:238         384        184        AU        ## START ##  AU: Search for updates

2016-09-09        08:52:32:238         384        184        AU        #########

2016-09-09        08:52:32:238         384        184        AU        <<## SUBMITTED ## AU: Search for updates [CallId = {C38B9768-1BF5-4733-A067-906EDCD3E9F3}]

2016-09-09        08:52:32:238         384        e74        Agent        *************

2016-09-09        08:52:32:238         384        e74        Agent        ** START **  Agent: Finding updates [CallerId = AutomaticUpdates]

2016-09-09        08:52:32:238         384        e74        Agent        *********

2016-09-09        08:52:32:238         384        e74        Agent          * Online = Yes; Ignore download priority = No

2016-09-09        08:52:32:238         384        e74        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"

2016-09-09        08:52:32:238         384        e74        Agent          * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed

2016-09-09        08:52:32:238         384        e74        Agent          * Search Scope = {Machine}

2016-09-09        08:52:32:301         384        e74        Setup        Checking for agent SelfUpdate

2016-09-09        08:52:32:301         384        e74        Setup        Client version: Core: 7.6.7601.19161  Aux: 7.6.7601.19161

2016-09-09        08:52:32:410         384        e74        Misc        WARNING: WinHttp: SendRequestToServerForFileInformation failed with 0x80190194

2016-09-09        08:52:32:410         384        e74        Misc        WARNING: WinHttp: ShouldFileBeDownloaded failed with 0x80190194

2016-09-09        08:52:32:410         384        e74        Misc        WARNING: DownloadFileInternal failed for http://WSUSSERVER/selfupdate/wuident.cab: error 0x80190194

2016-09-09        08:52:32:410         384        e74        Setup        FATAL: DownloadCab failed, err = 0x80190194

2016-09-09        08:52:32:410         384        e74        Setup        WARNING: SelfUpdate check failed to download package information, error = 0x80244019

2016-09-09        08:52:32:410         384        e74        Setup        FATAL: SelfUpdate check failed, err = 0x80244019

2016-09-09        08:52:32:410         384        e74        Agent          * WARNING: Skipping scan, self-update check returned 0x80244019

2016-09-09        08:52:32:410         384        e74        Agent          * WARNING: Exit code = 0x80244019

2016-09-09        08:52:32:410         384        e74        Agent        *********

2016-09-09        08:52:32:410         384        e74        Agent        **  END  **  Agent: Finding updates [CallerId = AutomaticUpdates]

2016-09-09        08:52:32:410         384        e74        Agent        *************

2016-09-09        08:52:32:410         384        e74        Agent        WARNING: WU client failed Searching for update with error 0x80244019

2016-09-09        08:52:32:410         384        e6c        AU        >>##  RESUMED  ## AU: Search for updates [CallId = {C38B9768-1BF5-4733-A067-906EDCD3E9F3}]

2016-09-09        08:52:32:410         384        e6c        AU          # WARNING: Search callback failed, result = 0x80244019

2016-09-09        08:52:32:410         384        e6c        AU          # WARNING: Failed to find updates with error code 80244019

2016-09-09        08:52:32:410         384        e6c        AU        #########

2016-09-09        08:52:32:410         384        e6c        AU        ##  END  ##  AU: Search for updates [CallId = {C38B9768-1BF5-4733-A067-906EDCD3E9F3}]

2016-09-09        08:52:32:410         384        e6c        AU        #############

NETMON TRACE (Filter for HTTP protocol)

0.0000966 23 8:52:32 AM 9/9/2016 2.7940332 svchost.exe 10.10.10.10 WSUSServer HTTP HTTP:Request, HEAD /selfupdate/wuident.cab, Query:1609091252 {HTTP:25, TCP:24, IPv4:23}
0.0218388 24 8:52:32 AM 9/9/2016 2.8158720 svchost.exe WSUSServer 10.10.10.10 HTTP HTTP:Response, HTTP/1.1, Status: Not found, URL: /selfupdate/wuident.cab {HTTP:25, TCP:24, IPv4:23}
0.0002662 25 8:52:32 AM 9/9/2016 2.8161382 svchost.exe 10.10.10.10 WSUSServer HTTP HTTP:Request, GET /selfupdate/wuident.cab, Query:1609091252 {HTTP:25, TCP:24, IPv4:23}
0.0216961 26 8:52:32 AM 9/9/2016 2.8378343 svchost.exe WSUSServer 10.10.10.10 HTTP HTTP:Response, HTTP/1.1, Status: Not found, URL: /selfupdate/wuident.cab {HTTP:25, TCP:24, IPv4:23}

It turns out that in Server 2008 R2, when you install the WSUS role IIS is installed and a "Default Site" is created.  However, when you install the WSUS role for 2012 R2 IIS is installed, but it creates two sites.  It creates a "Default Site" and a "WSUS Administration" site.

Server 2008

 Server 2012 R2

For me, I was able to change the http port to 80 and this resolved the issue.  You can right click on "WSUS Administration" and click on "Edit Bindings" to modify the port.

HOWEVER - If I would have gone to technet, I would have seen the following:

When you type the intranet address of your WSUS server make sure to specify which port is going to be used. By default WSUS will use port 8530 for HTTP and 8531 for HTTPS. For example, if you are using HTTP, you should type http://servername:8530.

You can see more about this here: https://technet.microsoft.com/en-us/library/hh852346(v=ws.11).aspx

I guess the moral of the story - read the documentation!

At least I got to learn more about how the windows update client works in the process.