This is similar to a lot of postings for WSUS 3. But I still haven't gotten it working.
1) Installed a Windows Server 2012 Standard (last night), Installed all Windows updates from on-line
2) Added WSUS Role, standard configuration, Set Automatic Approve all categories except Drivers and Approved all Computers. Synchronized in about 12 hours (20Mbps Internet).
3) Ran the console command "gpedit" as Administrator on the clients. Changed Group Policy on a client Windows Server 2012 and a client Windows 7 Pro/64 to point the Intranet URL: http://wsus-2013:8530 where "wsus-2013" is the new WSUS server.
4. Tested browsing http://wsus-2013:8530/Selfupdate/iuident.cab on the clients, no problem
5. Ran the following console commands as Administrator on the clients:
gpupdate /force
wuauclt.exe /resetauthorization /detectnow
net stop wuauserv
net start wuauserv
shutdown -r -t 1 (Client Rebooted)
6. When I run Windows Update on the Windows 7 PC, I get "Windows cannot search for updates, Error Code 80244019"
7. When I run Windows Update on the Windows Server 2012, it seemed to work.
8. When I look at the WSUS Server's Computers, I only see the Windows Server 2012 client, not the Windows 7 client.
9. I changed the GPO in Active Directory for workstations in our AD domain, but I haven't seen any of those in the WSUS Computers yet. Note: the W7 and WS2012 clients above were not AD domain members.
I don't think this is an Active Directory issue.
Since all clients can see the WSUS URL and one of them works, I think something else is wrong. Before posting my question here, I have tried searching for a solution, but mostly find WSUS 3 version information. I did not have this problem when setting up WSUS 3 servers in the past.
10. Tried following standard Mr Fixit Windows Update diagnostic on client and it returns "No Problems Found" on the Windows 7 PC. The same PC that returns 80244019 Error Code when running Windows Update.
Any suggestions or clues?
UPDATE to My Issue with Windows Updates:
The WindowsUpdate.log provides a clue with the line:
"Misc WARNING: DownloadFileInternal failed for http://wsus-2013/selfupdate/wuident.cab: error 0x80190194"
SO, HOW DO I GET WINDOWS UPDATE TO USE THE PORT IN THE URL http://wsus-2013:8530 ???
2013-03-20 16:58:27:362 524 f14 Agent *************
2013-03-20 16:58:27:362 524 f14 Agent ** START ** Agent: Finding updates [CallerId = AutomaticUpdates]
2013-03-20 16:58:27:362 524 f14 Agent *********
2013-03-20 16:58:27:362 524 f14 Agent * Online = Yes; Ignore download priority = No
2013-03-20 16:58:27:362 524 f14 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"
2013-03-20 16:58:27:362 524 f14 Agent * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
2013-03-20 16:58:27:362 524 f14 Agent * Search Scope = {Machine}
2013-03-20 16:58:27:362 524 f14 Setup Checking for agent SelfUpdate
2013-03-20 16:58:27:362 524 f14 Setup Client version: Core: 7.6.7600.256 Aux: 7.6.7600.256
2013-03-20 16:58:27:362 524 f14 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
2013-03-20 16:58:27:377 524 f14 Misc Microsoft signed: Yes
2013-03-20 16:58:28:940 524 f14 Misc WARNING: WinHttp: SendRequestToServerForFileInformation failed with 0x80190194
2013-03-20 16:58:28:940 524 f14 Misc WARNING: WinHttp: ShouldFileBeDownloaded failed with 0x80190194
2013-03-20 16:58:28:940 524 f14 Misc WARNING: DownloadFileInternal failed forhttp://wsus-2013/selfupdate/wuident.cab: error 0x80190194
2013-03-20 16:58:28:940 524 f14 Setup WARNING: SelfUpdate check failed to download package information, error = 0x80244019
2013-03-20 16:58:28:940 524 f14 Setup FATAL: SelfUpdate check failed, err = 0x80244019
2013-03-20 16:58:28:940 524 f14 Agent * WARNING: Skipping scan, self-update check returned 0x80244019
2013-03-20 16:58:28:955 524 f14 Agent * WARNING: Exit code = 0x80244019
2013-03-20 16:58:28:955 524 f14 Agent *********
2013-03-20 16:58:28:955 524 f14 Agent ** END ** Agent: Finding updates [CallerId = AutomaticUpdates]
2013-03-20 16:58:28:955 524 f14 Agent *************
****************
It looks like I'll have to use a work-around for now. I disabled the WSUS server's Default website's binding for port 80 and added port 80 binding to the WSUS Administration website and now things are working.
I think the requirement to maintain the legacy Port 80 instead of Only using the new ports 8530 and 8531 on the WSUS server for Windows 7 and earlier should be documented somewhere so that it doesn't frustrate admins trying to use WSUS 6.2.92 for the first time.
Attention Microsoft: Please let me know when this is fixed or if there are any security issues related to enabling port 80 on the WSUS Administration website.