"PadawanTech" <> wrote in message
news:...
> I approved some (16) updates on Monday, they were installed Tuesday
> morning. Only 13 of them were installed.
Could well be. Several possibilities here:
- The three updates that did not install were superceded by three of the 13
updates that did install.
- The three updates that did not install weren't actually applicable to that
machine.
- The three updates that did not install were applicable, but became Not
Applicable because something else was updated. (A prime example of this is
updates for IE6 which become Not Applicable when IE7 is installed, or
updates for SQL2005SP2 that become NA when SQL2005SP3 is installed.)
> Now, next week I approve some more updates. I run a report on that
> group that shows installed/ not applicable updates. Using excel I
> filter out the not applicable updates. But if there is no time and date
> how can I tell when they were approved or even when were they
> installed.
*Approvals* are logged to the Change.Log.
*Installations* are logged to the Application Event log of the client
system, the ReportingEvents.log of the client system, and the
WindowsUpdate.log of the client system. If you want installation times
you'll have to get those some other way than from WSUS.
> Second page
> List of computers that have the update
> Under status click on Installed, This will tell you when it was
> download and when it was installed (Date and time).
Okay, so if it's in the database, then you can either get the information
this way, or you can build a custom application or report that uses the WSUS
API. NOTE: If you're using *scheduled* installations, the installation time
ought to be reasonably presumable -- i.e. if the client has a scheduled
installation event at 3am, and you don't allow user-interactive
installations, then it's pretty much a fact that the updates were installed
at 3am within 48 hours after the approval.
> Please understand that I have clients that will ask "What was installed
> last week?" or last month.
Okay... but unless you're approving updates on a *daily* basis -- even
though they're only released twice a month -- it should be pretty trivial to
document when updates were installed. I submit that the point here is not
when updates were installed, but *IF* updates were installed when they were
approved. The real question is this: Why would there be any uninstalled
updates 72 hours after you've approved them? The answer is: Because
something is broken, or the machines were powered off.
--
Lawrence Garvin, M.S., MCITP:EA, MCDBA
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2009)
My Blog:
http://onsitechsolutions.spaces.live.com
Microsoft WSUS Website:
http://www.microsoft.com/wsus
My MVP Profile:
http://mvp.support.microsoft.com/pro...awrence.Garvin