Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 8216
  • Last Modified:

Server 2012 WSUS 0x80244019

Having a nightmare of a time getting server 2012 to run WSUS. The Roles ext install fine but after configuring the server with my usual WSUS GPO no machines can connect. Here is a sample of the log and any ideas would be welcome:
log.txt
0
Dead_Eyes
Asked:
Dead_Eyes
  • 14
  • 10
  • 3
1 Solution
 
Donald StewartNetwork AdministratorCommented:
In your WSUS GPO are you specifying to use port 8530 ??? <<<Most likely you should be
0
 
Donald StewartNetwork AdministratorCommented:
0
 
Dead_EyesAuthor Commented:
Thanks for the quick reply. Yes I have specified port 8530 in the GPO and I have looked at the self update folder (rebuild the server 3 times with no luck suggesting that its something extra you have to do in 2012 as running the setup and config does not seem to be enough)
0
What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

 
McKnifeCommented:
Hi.

Please make sure that you can telnet into port 8530.
0
 
Donald StewartNetwork AdministratorCommented:
Next, temporarily disable firewalls
0
 
Dead_EyesAuthor Commented:
Looking into how you test with telnet and firewalls are already disabled
0
 
Dead_EyesAuthor Commented:
Here are the results of the client diagnostic tool
client.png
0
 
Donald StewartNetwork AdministratorCommented:
Clientdiag does not work on 64Bit systems
0
 
Donald StewartNetwork AdministratorCommented:
This may or may not help

http://support.microsoft.com/kb/959894
0
 
McKnifeCommented:
About telnet: procedure to install (at the client): see http://technet.microsoft.com/en-us/library/cc771275(v=ws.10).aspx
Command to execute at the client after installation:
telnet NameOfWsus 8530
The outcome will show you if that port can be "talked to" or not.
0
 
Dead_EyesAuthor Commented:
Telnet servername 8530 seems to execute ok put just hangs there with a flashing prompt. Don't know if this indicates its working or not?
0
 
McKnifeCommented:
If the command shell clears, it tells you it's working, so that's not the problem here.
Can the server itself receive updates to install?
0
 
Donald StewartNetwork AdministratorCommented:
0
 
Dead_EyesAuthor Commented:
yeah services are fine and machine is clean. :(
0
 
Donald StewartNetwork AdministratorCommented:
Double check your WSUS GPO and ensure that you have your "Specify intranet....." settings correct

a spelling mistake or even a "Space" can make a difference
0
 
Donald StewartNetwork AdministratorCommented:
At a client, what are the results of ???


reg query HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate /s

from a cmd prompt
0
 
Donald StewartNetwork AdministratorCommented:
From your log "http://WIN2K12WSUS/selfupdate/wuident.cab"


We can see that your GPO is incorrect

it should be reading "http://WIN2K12WSUS:8530/selfupdate/wuident.cab
0
 
Dead_EyesAuthor Commented:
In my experience group policy assumes a port of 8530 but just to be sure I amended the gpo and re-tested but still same error.

Please find the results of reg query HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate /s attached

The specify intranet settings are correct but I do not expect the GPO settings to be the issue I as use this same policy on many sites and it works 100% every time
Untitled.png
0
 
Donald StewartNetwork AdministratorCommented:
"In my experience group policy assumes a port of 8530"?????



Absolutely not!!!

Again, from your screenshot you can still see the 8530 is missing and this needs to be added in order for the client to communicate correctly with WSUS.

Error 0x80244019 is always the result of network disruption
0
 
Donald StewartNetwork AdministratorCommented:
From....

http://technet.microsoft.com/en-us/library/hh852346.aspx

WSUS 3.0 uses port 80, by default. However, in Windows Server 2012, by default WSUS 4.0 uses port 8530.

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.
0
 
Dead_EyesAuthor Commented:
Sorry for late reply but had to fit in some weekend and do some testing. I have addpreped the domain by adding a DC running 2012 and checked IIS (confirmed my 2012 WSUS server is on port 8530 as I thought). I have specified 8530 in the GPO and all servers have been run gpupdate /force and rebooted. Still the same error though. I have even tried editing the registry and specifying http://win2k2012wsus:8530 . I have attached the latest windowsupdate.log entry
log.txt
0
 
Donald StewartNetwork AdministratorCommented:
Again from your log

784      EP      Got WSUS Client/Server URL: "http://WIN2K12WSUS/ClientWebService/client.asmx"
2013-02-04      14:21:46:769       828      784      Setup      Checking for agent SelfUpdate
2013-02-04      14:21:46:769       828      784      Setup      Client version: Core: 7.8.9200.16465  Aux: 7.8.9200.16451
2013-02-04      14:21:46:769       828      784      EP      Got WSUS SelfUpdate URL: "http://WIN2K12WSUS/selfupdate"

You can see that "8530" is not there
0
 
Donald StewartNetwork AdministratorCommented:
have you tried using RSOP.msc to see if there is another GPO conflicting??
0
 
Dead_EyesAuthor Commented:
I have reviewed RSOP and policy is applied specifying 8530 with no conflicts
0
 
Dead_EyesAuthor Commented:
Looking through logs from other sites I cannot see the port mentioned are you sure it should be?
0
 
Donald StewartNetwork AdministratorCommented:
POSITIVE!

Server 2012 WSUS uses port 8530 by default.

From within the WSUS console you can see which port WSUS is using.8530
0
 
Dead_EyesAuthor Commented:
Got it, it may well be coincidence but ever since I created the 2012 DNS, DC the other 2008 Servers started seeing the wsus server and then when I Deleted the group policy (the 2 groups of servers used different GPO’s but same WSUS settings) and recreated it.
0

Featured Post

Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

  • 14
  • 10
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now