I am trying to push windows updates to a group of servers and when I do, I get an error on the server that is "An error has occurred; Code 80244019 windows update encountered an unknown error"

I am trying to push windows updates to a group of servers using WSUS (using a WID Database).  When I do this, I approve for installation, do not set a deadline and it succeeds according to WSUS.  When I log on to one of the servers, the update is not there.  I run the command "wuauclt /resetauthorization /detectnow" and it still won't show.  I look at the windowsupdate.log in the %windir% and find that it is pointing to the error "Code 80244019 windows update encountered an unknown error".  I am curious if someone can help me on this.  I am seeing that it could be a number of things, but not sure which direction to go.  Thanks in advance for any help.Screenshot---10-14-2014---10-38-08-PM.pn
Jim WilliamsonAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

DonNetwork AdministratorCommented:
You most likely dont have the gpo correctly setup using :8530
0
DonNetwork AdministratorCommented:
Check your gpo "Specify Intranet Microsoft update service location."

and make sure it says http:\\servername:8530
0
Jim WilliamsonAuthor Commented:
It does, but I also put the domain name behind the servername to make sure that it wasn't a DNS issue:  http://servername.domainname.org:8530
0
Acronis True Image 2019 just released!

Create a reliable backup. Make sure you always have dependable copies of your data so you can restore your entire system or individual files.

DonNetwork AdministratorCommented:
This can also happen when the files the client is looking for are missing.

Try running on your wsus server the command WSUSutil.exe reset
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Jim WilliamsonAuthor Commented:
Also in addition to the command that was given to me, I ran psexec.exe from Sysinternals and connected to each server to run wuauclt /resetauthorization /detectnow  This started the communication once again immediately.  Thanks for all the answers and responses.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Server Apps

From novice to tech pro — start learning today.