Software Update Services, Part 2

Web Figure 1 (http://www.secadministrator.com, InstantDoc ID 27069) lists initialization (&A=n), self-update (&A=s), and detection (&A=d) that 10.0.0.41 reported to SUS server 10.0.0.68. The information in the wutrack.bin log is cryptic, but the deployment guide makes an effort to explain the log entries in Appendix C: "Client Status Logging." The log contains records other than wutrack.bin messages. Appendix C also shows how to configure IIS to log only wutrack.bin messages by turning off logging at the Web site level and enabling logging only on the wutrack.bin file.

You can monitor update activity by using the \%windir%\windows update.log file on each of your clients. This log file contains an easy-to-read record of update information. As Web Figure 2 (http://www.secadministrator.com, InstantDoc ID 27069) shows, the computer queried a Windows Update server for new updates, downloaded them, installed them, and rebooted. If the systems administrator configured the client to pull updates from an internal SUS server, that configuration would be reflected in the log. . . .