IE7 Updates

We have pushed out IE7 to users; without a reboot; but before the end user
could reboot other updates have tried to install and now are continuously
attempting to install.

Any ideas on how to get the updates to install and show up as registered in
WSUS?

We have tried to do it manually, but only with a 50% success rate.

"Scott Gallagher" <Scott > wrote in
message news:FE04BCE9-6927-455D-9505-...
> We have pushed out IE7 to users; without a reboot; but before the end user
> could reboot other updates have tried to install and now are continuously
> attempting to install.

Was this IE7 deployment done via WSUS, or some other methodology?

Let's look at the logs to see what's really happening.

If you did deploy IE7, without rebooting, then generally WUAgent will not
download (much less attempt to install) any other updates until that
required reboot is performed. Of course, if there were already updates
downloaded (and maybe even scheduled) and then you used GPO, SMS, SCCM or
some other method to force IE7 onto those machines, there's all sorts of
possibilites for things that might be messed up - and that scenariou would
definitely account for attempted/failed installations.


--
Lawrence Garvin, M.S., MCITP:EA, MCDBA
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2009)

MS WSUS Website: http://www.microsoft.com/wsus
My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin

WSUS was used to push IE7 to remote machines.

"Lawrence Garvin [MVP]" wrote:

> "Scott Gallagher" <Scott > wrote in
> message news:FE04BCE9-6927-455D-9505-...
> > We have pushed out IE7 to users; without a reboot; but before the end user
> > could reboot other updates have tried to install and now are continuously
> > attempting to install.
>
> Was this IE7 deployment done via WSUS, or some other methodology?
>
> Let's look at the logs to see what's really happening.
>
> If you did deploy IE7, without rebooting, then generally WUAgent will not
> download (much less attempt to install) any other updates until that
> required reboot is performed. Of course, if there were already updates
> downloaded (and maybe even scheduled) and then you used GPO, SMS, SCCM or
> some other method to force IE7 onto those machines, there's all sorts of
> possibilites for things that might be messed up - and that scenariou would
> definitely account for attempted/failed installations.
>
>
> --
> Lawrence Garvin, M.S., MCITP:EA, MCDBA
> Principal/CTO, Onsite Technology Solutions, Houston, Texas
> Microsoft MVP - Software Distribution (2005-2009)
>
> MS WSUS Website: http://www.microsoft.com/wsus
> My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin
>

"Scott Gallagher" <> wrote in
message news:433D3133-F9A1-44E3-BFE1-...

>> > We have pushed out IE7 to users; without a reboot; but before the end
>> > user
>> > could reboot other updates have tried to install and now are
>> > continuously
>> > attempting to install.

>> If you did deploy IE7, without rebooting, then generally WUAgent will not
>> download (much less attempt to install) any other updates until that
>> required reboot is performed.

> WSUS was used to push IE7 to remote machines.

Okay, so the first point of reference is to identify the WindowsUpdate.log
that shows IE7 being installed, the system not being rebooted, and
subsequent updates being detected/downloaded/installed by the WUAgent.

Fundamentally speaking, by design, this scenario is impossible -- so our
best effort may be first to determine what actually did happen.

--
Lawrence Garvin, M.S., MCITP:EA, MCDBA
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2009)

MS WSUS Website: http://www.microsoft.com/wsus
My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin