How to determine if your SUS Server is Working

Date: 27 Jan 2003 ~ Author: Wayne Flynn
Microsoft’s SUS server is merely a web server that mimics much (but not all) of the functionality of the Microsoft Windows Update website. The architecture consists of a client (the AutoUpdate client or AU) and the server. For each of these two components, there are log files that describe the “conversation” that each has with the other.

Basic Troubleshooting

If your AU Client’s log file is not indicating that the system is communicating with your SUS server, but is instead visiting Microsoft’s Windows Update site, then you may simply need to confirm that your Group Policy has been implemented correctly, or in the case where you do not run Active Directory, that the proper registry entries have been applied. Consult the SUS Deployment Guide for more information about this type of problem.
If you find errors in your client’s AU log but note that the client is trying to connect to your SUS server, then you should also look at the SUS log file to identify the problem. Run the logs through the online log interpreter at to determine if it is a widespread problem or a problem with just a particular machine.
If, after reviewing the SUS Deployment Guide, you still cannot determine the source of your problem, read the microsoft.public.softwareupdatesvcs newsgroup. The vast majority of problems and solutions are located in this online resource.