|
Posted by Roger Abell [MVP] on May 4, 2006, 9:55 am
If you were Registered and logged in, you could reply and use other advanced thread options There can be a variety of causes, including the updates not being
authoritzed
in SUS (or WSUS) for distribution to the clients, the update not having been
successfully downloaded to the SUS (or WSUS) although that is uncommon,
or the client being plugged up with a pending, deferred update or reboot, or
a failed update application where there is some dependencies of others upon
the failed.
There are newsgroups for SUS (or WSUS)
microsoft.public.softwareupdatesvcs
(or microsoft.public.windows.server.update_services)
which is(/are) where you probably should be posting with your issue.
> Windows 2003 Standard SUS (NOT WSUS) server is configured via Group Policy
> to
> automatically download and install updates to client PCs at 9AM daily (the
> settings are correctly grayed out and show 9AM); however, when you login
> as
> administrator to a Windows Pro client workstations configured to pull
> updates from the SUS (NOT WSUS) server shows a long list of updates that
> were
> not automatically installed (KB899589, KB913446, etc).
>
> Anyone know how to fix this?
>
|