everyday

I know that the title probably makes no sense to any one of the 2 people who read my weblog on a semi-annual basis, but I have decided to try to post more stuff related to my work as a Network Engineer. That being said…

Today I ran into a problem with our Microsoft WSUS server. Recently I upgraded the WSUS from 3.0 to 3.0 Service Pack 1 (SP1). This is the second time our WSUS has been broken by an update. Usually Microsoft’s updates are pretty solid, but WSUS updates seem to be a tad iffy. The upgrade from WSUS 2.0 to WSUS 3.0 broke completely and I had to completely rebuild the server, luckily I run the WSUS on a virtual server using VMWare’s ESX server, so rebuilding it was very simple.

The particulars of the problem are that the client machines would not download updates! Normally I don’t check on the update status of machines very often, but I was creating a new image for a laptop and the thing just would not download updates. I check the WSUS log on the client machine and noticed that there was a 0×80190194 error. A quick search on Google pointed me to a number of forum posts that state this is an HTTP 404 (Page not found) error. Unfortunately, none of these posts had any information about a solution. A bit more searching led me to a post on Microsoft’s TechNet Discussion Groups that had the solution, Re: WSUS 3 sp1 do not distribute patches to clients in Windows Server Update Services (URL is rather deep and may be broken, no warranty). The noteworthy part of the post:

1. Create a new virtual directory called ’selfupdate’
2. Set the pathname to
   %programfiles%\Update Services\selfupdate

Hopefully Microsoft will put some more resources into testing the updates for WSUS, it is a really nice product, but the updates always seem to break it!

This entry was posted on Thursday, May 22nd, 2008 at 4:05 pm and is filed under IT. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.