I am facing a problem implementing my SUS server into my organization.
I have configured the group policy in my 2000 domain to AutoUpdate from my SUS server. But clients are getting updated from the server. In fact, they are not attempting to do so. I have checked the registry settings of these clients. They are showing the proper configuration and are pointing to my SUS server. The windows update option in the control panel is grayed out ( but it is not showing the time set for the update ). And If I log in to the same client computer using administrator account, everything works fine. Can you help?
It is not possible to determine the exact problem from the information you provided. The most common cause in this case is incorrect group policy implementation. The best way to troubleshoot the problem is to examine the logs at both the ends – AU and SUS server. The log file for the AutoUpdate client is located at c:winntwindows update.log or, for Microsoft Windows XP installations, c:windowswindows update.log. SUS server utilizes Microsoft's web server, Internet Information Services (IIS), to perform most of its communication with client computers. The log files for IIS (SUS server) are located at c:winntsystem32logfilesw3svc1 or, on Microsoft Windows XP, c:windowssystem32logfilesw3svc1. One log file for each 24 hour period is created (the default configuration) based on the time zone GMT. These files are named as exYYMMDD.log where YYMMDD indicates the date. The log records every transaction as part of client-server conversation and reports an error or success. You will need to refer to the SUS deployment guide in detail in order to interpret the logs correctly. One easy way to interpret the logs is to run them through a parser. Here's an online log interpreter
. The only entries that have significance to the AU/SUS conversation are the entries that contain a "pingback" (Microsoft's term for status report) encoded in the query string.
On the other hand you can also log onto microsoft.public.softwareupdatesvcs newsgroup, as the vast majority of problems and solutions are located in this online resource.
This was first published in July 2004