|
I've
gone through all of the steps to install and use SUS, but I can't figure out if
it is working. Some updates have been installed as evidenced by ADD/REMOVE
PROGRAMS but not all of them. Also, it didn't happen at a time that I had
selected.
- What IS supposed to happen
at the scheduled time? I thought it should download and install necessary
updates, so I should see something happening. I've set the time and then
waited for it to pass and nothing happens, even though a reboot should be
required. (Yes, WU is installed on my client (Win2k SP3), Updates have been
approved, the server name is resolvable and the policy is being applied.)
- How does WU handle missed
events? (i.e. If I set it to 2 AM and the computer isn't on, does it try again
when the computer is turned on?)
- If multiple events require a
reboot, does it chain them? or do them one at a time? or one each day? What
happens? (i.e. do I have to dribble them out to prevent users from being
locked out of their machines for 45 minutes.)
I have looked at the log files
and event log and seen some evidence that it has talked to my test client, but
nothing consistent has taken place.
Contributed By: Wayne
Flynn, MVP SUS
The Windows Event Log on the client
computer will post an event when updates are installed (or are ready for
installation). If you are using the "forced install" setting (option 4 in the
Group Policy) then the install will occur at the proper time and a message will
inform the client computer that the machine will restart. This is quite
reliable, once the policy is properly applied.
Also, you can determine some other things about timing from the 'C:\WINNT\WINDOWS
UPDATE.LOG' file. There's a good bit
of information about the interaction with the SUS server in there.
And finally, by looking at the IIS logs on the SUS server, you will find the
entire conversation between the client and SUS. The IIS logs are at 'C:\WINNT\SYSTEM32\LOGFILES\W3SVC1'. Contributed By: Wayne Flynn,
MVP SUS
[1/7/03]
In addition to the above, the following article also
offers some advice on what to check:
http://www.susserver.com/FAQs/FAQ-IsYourSUSServerWorking.asp
The key to troubleshooting is reviewing the
information in the logs, both on the client and on the server. Also, it is a bit
easier to import the 'WUAU.ADM' admin template than it is to create your own
registry entries which need to be perfect as far as capitalization goes and all
that - 'GPEDIT.MSC' is the tool for that.
|
