"Intel" <Intel[ at ]discussions.microsoft.com> wrote in message
news:E20C6FFD-1733-495B-AFB9-6A6061D0BE18[ at ]microsoft.com...
[Quoted Text] >I am running Windows 2003 R2 (SP1). I have approved SP2 for Windows 2003
>R2
> and in the report it show Install and downloaded. This does not support
> deadlines and says user input required. Is there something I need to do
> manually to get WSUS to push out SP2 for my Windows 2003 machines?
[a] WSUS doesn't push anything.
[b] The client detects that the update is approved for installation. The
client downloads the update package (which is quite large, I imagine) from
the WSUS server. The client installs the update according to the policy
configured on the client system.
Now, having said that, here's a whole bunch of prerequisites that you'll
probably want to verify.
[1] The client needs to have a policy assigned and properly applied.
[2] The client needs to have successfully selfupdated to the latest WUA
client.
[3] The client needs to be able to successfully execute a detection.
[4] When executing that detection, the client needs to be looking in the
right target group. (Quite often, in these scenarios, the client has bad
target group information, and never sees the approval. Inspect the
WindowsUpdate.log to determine which target group the client *thinks* it
belongs to.)
[5] Before the client can see an approval for installation, the content has
to have been successfully downloaded on the WSUS Server. Verify with the
WSUS Server that the update content for Win2003SP2 has successfully
downloaded.
[6] After executing the detection, the client needs to download the service
pack. Verify with the client that the update package has successfully
downloaded (Is there a multimegabyte package in the
%windir%\SoftwareDistribution\Downloads folder? Does the
%windir%\SoftwareDistribution\ReportingEvents.log file report that the
service pack was successfully downloaded?)
[7] After downloading the package, the client will schedule the update for
installation (if you've configured the client to use AU Option #4 -- NOT
recommended for servers -- and since we're talking about Win2003SP2, I would
hope this is not the case.)
[8] If not scheduled for installation, log onto the console with an
Administrator account, and the Notification Area will inform you updates are
ready for installation. Click on the icon and install the update.
[9] If no notification or icon appears, ensure that you have not blocked
access to use Windows Update on this machine.
[10] If you get this far and none of the above identifies a cause, post back
with your observations and we'll go from there.
> BTW If you see me asking this question again it is because I am not seeing
> any of my other one appear.
It takes some time for your post to get from the web interface, distributed
throughout the gazillion news servers at microsoft.com, and replicated back
to the web interface. Don't expect immediate visibility of your posts from
the web interface.
--
Lawrence Garvin, M.S., MCTS, MCP
Independent WSUS Evangelist
MVP-Software Distribution (2005-2007)
https://mvp.support.microsoft.com/profile=30E00990-8F1D-4774-BD62-D095EB07B36E
Everything you need for WSUS is at
http://technet2.microsoft.com/windowsserver/en/technologies/featured/wsus/default.mspx
And, almost everything else is at
http://wsusinfo.onsitechsolutions.com
.....
|