How do I completely stop WSUS on SBS 2003

We are trying to trouble shoot several SQL issues on a SBS 2003 server. However WSUS is one of the problems but it is filling up the event logs making it more dificult to find errors from the more important issues right now. How do I temporarily completelsy disable WSUS. I have disabled update services, stopped it in IIS. What else am I missing.
Who is Participating?
ChiefITConnect With a Mentor Commented:
WSUS is a pull technology. Client machines will continue to try to logon and update themeselves as long as they are able to open up the web portal to the WSUS web site. These will cause errors in event logs if the WSUS update and SQL services are disabled. So, block the port number (with a software firewall, or port filtering) for the specific port that is used for WSUS.
Have you stopped MSSQL$WSUS service?
prosysconAuthor Commented:
We have and disabled update services aswell.
Free Tool: ZipGrep

ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.

One of a set of tools we're offering as a way to say thank you for being a part of the community.

Jaroslav MrazCTOCommented:
davorin is right you need to disable MS SQL services for wsus.

SQL WSUS server and all its linked servers SQL WSUS functions. And WSUS is another servise as system and sql is support for it but after disabling your system will give you erors becouse local OS is using it as client. Soo maybe this wil dont reduce errors in Event LOG.
Jaroslav MrazCTOCommented:
@ChiefIT you right but thats only for testing becouse if you want to PCs change the update server you must wait some time or use comand to CMD. So they will be Lots of events in clients PCs and they will be transfered to SBS (if they have configurated monitoring)

so if you want to try it for few hours you can do it

if you wanted to test it some days change UPDATE server to microsoft you can do it in GPO domain policy
prosysconAuthor Commented:

Didn't even think about the other machines trying to pull from the server. Blocked the port and that stopped the errors. Fixed the SQL issue now to figure out the rest of the WSUS errors. Thanks!
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.