Member_2_4488436
asked on
WSUS 3 on SBS2008 not working
I'm having some issues with WSUS on my SBS 2008 box. This all started when an HD died. After installing a new replacement drive I noticed that a new PC that I was trying to deploy was constantly failing on installing certain updates (the same ones).
I figured it was due to corrupted updates in WSUS (due to the HD failing) so I read that in order to re-download updates for WSUS, I had to run the wsusutil reset command.
I ran that command 2 weeks ago, and i'm not sure if it did anything but all i know now is that wsus is not working.
When I start the Update Services MMC, i can't view anything under the Updates Node. It sits there and eventually crashes because it times out.
If i go to the Options node and try to change the email settings for example, I get a notice at the bottom of the popup window that says "Cannot save configuration because the server is still processing a previous configuration change"
How do I figure out what its trying to process?
BTW, I did re-boot the server and that didn't change anything.
I figured it was due to corrupted updates in WSUS (due to the HD failing) so I read that in order to re-download updates for WSUS, I had to run the wsusutil reset command.
I ran that command 2 weeks ago, and i'm not sure if it did anything but all i know now is that wsus is not working.
When I start the Update Services MMC, i can't view anything under the Updates Node. It sits there and eventually crashes because it times out.
If i go to the Options node and try to change the email settings for example, I get a notice at the bottom of the popup window that says "Cannot save configuration because the server is still processing a previous configuration change"
How do I figure out what its trying to process?
BTW, I did re-boot the server and that didn't change anything.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
In the end I was not able to figure out what WSUS was doing to the DB. I ended up uninstalling WSUS and not keeping the DB.
When installing WSUS, I decided to install the DB on a remote SQL instance which seems to have helped with performance.
I did run into a snag when telling the WSUS wizard about the remote SQL server. For anyone reading this in the future, I have to put the following for the remote instance name: SQL_SERVER_NAME\MSSQLSERVE
Once everything was installed and all the computer groups were created for SBS to work, I realized I had to install KB2720211 in order for my clients to talk to WSUS. Apparently WSUS 3.0 with SP2 does not come with that update.
When installing WSUS, I decided to install the DB on a remote SQL instance which seems to have helped with performance.
I did run into a snag when telling the WSUS wizard about the remote SQL server. For anyone reading this in the future, I have to put the following for the remote instance name: SQL_SERVER_NAME\MSSQLSERVE
Once everything was installed and all the computer groups were created for SBS to work, I realized I had to install KB2720211 in order for my clients to talk to WSUS. Apparently WSUS 3.0 with SP2 does not come with that update.
ASKER
What tools can I use to see what the server is doing with the SUSDB so that I can stop it.
The last resort here would be to uninstall and start from scratch which I would like to avoid if possible.