Who installed the IE7?

Does anyone know how to tell how an update or rollup got installed on a
computer?
Our WSUS server has IE7 set to Declined but one of the workstations got
it installed anyway.
Does the manually run Windows Update create a log? If it uses the
Windowsupdate.log how can you search to find manually downloaded items?
Thanks

Forwarded to microsoft.public.windows.server.update_services newsgroup via
crosspost.

> Does the manually run Windows Update create a log?

Yes: %windir%\windows update.log (note the space; not
%windir%\windowsupdate.log [no space]).

> how can you search to find manually downloaded items?

How to read the Windowsupdate.log file
(applies to 'windows update.log', too)
http://support.microsoft.com/?kbid=902093
--
~Robear Dyer (PA Bear)
MS MVP-Windows (IE, OE, Security, Shell/User)

Davez2 wrote:
> Does anyone know how to tell how an update or rollup got installed on a
> computer?
> Our WSUS server has IE7 set to Declined but one of the workstations got
> it installed anyway.
> Does the manually run Windows Update create a log? If it uses the
> Windowsupdate.log how can you search to find manually downloaded items?
> Thanks

"PA Bear" <> wrote in message
news:...
> Forwarded to microsoft.public.windows.server.update_services newsgroup via
> crosspost.
>
>> Does the manually run Windows Update create a log?
>
> Yes: %windir%\windows update.log (note the space; not
> %windir%\windowsupdate.log [no space]).

This is somewhat inaccurate...

The /legacy/ AU client created the file [Windows Update.log] (the one with
the space).

The /current/ WUA client (in use since WindowsUpdate v5 was launched in the
summer of 2005) uses the [WindowsUpdate.log] file (the one without the
space).

Today, there are only two scenarios that would result in the continued use
of the [Windows Update.log] file:

[a] The system still has a legacy AU client installed (which means it's
never connected to Windows Update).
[b] The system is still using a /SUS/ server for updates, which causes the
WUA to revert to 'legacy AU' mode in order to communicate with the /SUS/
server, and that activity is logged to [Windows Update.log] and not
[WindowsUpdate.log].

Any access to Window Update or Microsoft Update or Office Update /today/
will make entries to [WindowsUpdate.log] not [Windows Update.log].



--
Lawrence Garvin, M.S., MCTS, MVP-Software Distribution
Everything you need for WSUS is at
http://technet2.microsoft.com/window...s/default.mspx
And, everything else is at
http://wsusinfo.onsitechsolutions.com
.....

You are correct, of course. 'Windows update.log' gets written to when
searching and using the Windows Update Catalogue (which use the V4 Engine),
not Windows/Microsoft Update website. I apologize for any confusion.
--
~PA Bear

Lawrence Garvin (MVP) wrote:
> "PA Bear" <> wrote in message
> news:...
>> Forwarded to microsoft.public.windows.server.update_services newsgroup
>> via
>> crosspost.
>>
>>> Does the manually run Windows Update create a log?
>>
>> Yes: %windir%\windows update.log (note the space; not
>> %windir%\windowsupdate.log [no space]).
>
> This is somewhat inaccurate...
>
> The /legacy/ AU client created the file [Windows Update.log] (the one with
> the space).
>
> The /current/ WUA client (in use since WindowsUpdate v5 was launched in
> the
> summer of 2005) uses the [WindowsUpdate.log] file (the one without the
> space).
>
> Today, there are only two scenarios that would result in the continued use
> of the [Windows Update.log] file:
>
> [a] The system still has a legacy AU client installed (which means it's
> never connected to Windows Update).
> [b] The system is still using a /SUS/ server for updates, which causes the
> WUA to revert to 'legacy AU' mode in order to communicate with the /SUS/
> server, and that activity is logged to [Windows Update.log] and not
> [WindowsUpdate.log].
>
> Any access to Window Update or Microsoft Update or Office Update /today/
> will make entries to [WindowsUpdate.log] not [Windows Update.log].

Hi Davez2,
I have been fighting with the exact same problem. A newer release of IE7
keeps getting release every 2 weeks or earlier, and it is automatically
approved for INSTALL to ALL COMPUTERS, which is driving us nuts!!!! I have
turned off all options to automatically approve anything for install, yet it
continuously does this, and sends us scrambling as we are experiencing
side-effects from IE7 and some of out other software. PLEASE IS THERE A PATCH
TO FIX THIS PROBLEM IN WSUS!!!! We can't have IE7 being automatically
approved for INSTALL to ALL COMPUTERS everytime there is a new version of it.

Janet

> Davez2 wrote:
> > Does anyone know how to tell how an update or rollup got installed on a
> > computer?
> > Our WSUS server has IE7 set to Declined but one of the workstations got
> > it installed anyway.
> > Does the manually run Windows Update create a log? If it uses the
> > Windowsupdate.log how can you search to find manually downloaded items?
> > Thanks
>
>

"Genie75" <> wrote in message
news:54978914-ED50-417D-96C0-...
> Hi Davez2,
> I have been fighting with the exact same problem. A newer release of
> IE7
> keeps getting release every 2 weeks or earlier, and it is automatically
> approved for INSTALL to ALL COMPUTERS, which is driving us nuts!!!! I have
> turned off all options to automatically approve anything for install,

Turning off auto-approval rules won't help.

You need to find the specific update(s) and mark them as NOT APPROVED.

--
Lawrence Garvin, M.S., MCTS, MVP-Software Distribution
Everything you need for WSUS is at
http://technet2.microsoft.com/window...s/default.mspx
And, everything else is at
http://wsusinfo.onsitechsolutions.com
.....