Update History
in [Windows Update]
|
From: Rob Meade on 27 Apr 2007 06:24 Hi all, I would very much like to access the update history from Windows Update on our servers but using my own application, ie, I can access it whenever I wanted rather than through the browser - does anyone know where/how this information is stored on each machine? Any help would be really appreciated, Google isn't offering me much at the moment... Cheers Rob
From: Robert Aldwinckle on 27 Apr 2007 11:34 (cross-post added to MBSA) "Rob Meade" <ku.shn.tsews.thbu(a)edaem.bor> wrote in message news:Ohg4PZLiHHA.1624(a)TK2MSFTNGP06.phx.gbl... > Hi all, > > I would very much like to access the update history from Windows Update on > our servers but using my own application, ie, I can access it whenever I > wanted rather than through the browser - does anyone know where/how this > information is stored on each machine? Try the MBSA NG? > > Any help would be really appreciated, Google isn't offering me much at the > moment... > > Cheers > > Rob > >
From: riggs on 27 Apr 2007 13:19 On Apr 27, 5:24 am, "Rob Meade" <ku.shn.tsews.t...(a)edaem.bor> wrote: > Hi all, > > I would very much like to access the update history from Windows Update on > our servers but using my own application, ie, I can access it whenever I > wanted rather than through the browser - does anyone know where/how this > information is stored on each machine? > > Any help would be really appreciated, Google isn't offering me much at the > moment... > > Cheers > > Rob Go to the ms dos prompt first, Then when you get there type in C: \>systeminfo no spaces. You should then see all of the updates to windows that have been made on your computer.
From: Gerry Hickman on 27 Apr 2007 18:04 Hi, His question is more on-topic for WindowsUpdate than it is for MBSA. There's a COM Collection of History Entries on each local machine that you access over DCOM, even on Vista. From what I can tell, pre-Vista updates will only show up in the history list if they were applied via Windows Update, they don't show up if you apply them manually, but with Vista, MSU files will be recorded, even if the MSU is applied manually. Does anyone know what the MSU file mapping runs when double-clicking such a file? Does anyone know why MSU updates are pre-extracted when using WU? Does anyone know how to turn them back into a single binary, like wot you could do with the old updates based on update.exe? If you try to use CopyFromCache() with MSU files it's _very_ messy, and how are you supposed to use CopyToCache() when you have to supply INDIVIDUAL files names, as opposed to just the path to the folder?? Does anyone know when WSUS will dump the useless .NET Framework dependency, and start using standards based COM instead? Robert Aldwinckle wrote: > (cross-post added to MBSA) > "Rob Meade" <ku.shn.tsews.thbu(a)edaem.bor> wrote in message > news:Ohg4PZLiHHA.1624(a)TK2MSFTNGP06.phx.gbl... >> Hi all, >> >> I would very much like to access the update history from Windows Update on >> our servers but using my own application, ie, I can access it whenever I >> wanted rather than through the browser - does anyone know where/how this >> information is stored on each machine? > > > Try the MBSA NG? > > >> Any help would be really appreciated, Google isn't offering me much at the >> moment... >> >> Cheers >> >> Rob >> >> > > -- Gerry Hickman (London UK)
From: Robert Aldwinckle on 27 Apr 2007 20:09
"Gerry Hickman" <gerry666uk(a)newsgroup.nospam> wrote in message news:udKxZgRiHHA.4064(a)TK2MSFTNGP02.phx.gbl... > Hi, > > His question is more on-topic for WindowsUpdate than it is for MBSA. Well, perhaps WSUS instead then. My idea was that MBSA posters seemed to be more aware of implementation issues than WU posters. ; ) > > There's a COM Collection of History Entries on each local machine that > you access over DCOM, even on Vista. From what I can tell, pre-Vista > updates will only show up in the history list if they were applied via > Windows Update, they don't show up if you apply them manually, but with > Vista, MSU files will be recorded, even if the MSU is applied manually. That's good news. ; ) > > Does anyone know what the MSU file mapping runs when double-clicking > such a file? I was only aware of a script being run. You think there's a file? Oh yes. I think you're right. If the SoftwareDistribution directory is cleared the WU generated History is lost somehow. So that part of it must be in there somewhere? As I said I have never seen implementation details discussed in the WU NG. Ohh... You've just given me an idea (synchronicity). This may be a good application for PowerShell scripting! E.g. port and adapt the script that WU runs to PowerShell... (foreach over "COM collection", registry branch, etc.) > > Does anyone know why MSU updates are pre-extracted when using WU? Does > anyone know how to turn them back into a single binary, like wot you > could do with the old updates based on update.exe? If you try to use > CopyFromCache() with MSU files it's _very_ messy, and how are you > supposed to use CopyToCache() when you have to supply INDIVIDUAL files > names, as opposed to just the path to the folder?? These questions sound like something a BITS expert might know more about. E.g. what you want to do is tap BITS and capture the files as they are delivered by it for WU MU or AU? But sometimes they are still there in the Download directory perhaps unchanged anyway? I'd run ProcMon to try to see if that's not the case for any particular example. Thanks! Robert --- |