TABLE OF CONTENTS Are all of your clients configured for WSUS to appear automatically in your WSUS console? Doyou use any type of disk-cloning software? Have all of your deployments and installations goneflawlessly? The following sections discuss some of the problematic client scenarios, and some ofthe valuable client investigation tools. These sections also discuss WSUS client logs, and detailsany Event log entries that you may find. They take you through some useful Group Policy utilitiesand finishes with pertinent online resources that you should have when investigating your AU clientenvironment.
Like most clients, the AU client generates its own log files, using them to track currentcomputer settings, updated changes, scheduled downloads and deployments, client communicationfailures, installation failures, service restarts, and so on. The log files are the best place tostart when troubleshooting AU client problems. The following sections discuss two log files andshows how to enable verbose logging when you want a lot more detail regarding troublesome issues.
As it receives and executes requests from a WSUS server, the AUclient continuously appends its working state to a log filecalled WindowsUpdate.log,which is located under the Windows installation folder at %windir%\WindowsUpdate.log. Do not confuse this with the other file called Windows Update.log (notice the space between Windows andUpdate). This is a legacy log file that is used by older AU clients to connect to older version ofMicrosoft s online Windows Update site, and WSUS predecessor, SUS. WindowsUpdate.log can be deleted.
The WindowsUpdate.log file can be...
