How to identify systems that have been recached after admin point updated

[Hugh Campbell]

The Subject pretty much says it, I guess. We updated our admin point.
Some workstations that had previously been installed from there, have
been "recached" and again recognize that admin point (for
Install-on-Demand items, for example). We would now like to recache
the remaining 250+ workstations. Because the recache process takes up
to 30 minutes, we don't want to repeat it on those which don't need
it.

QUESTION: Is there any way to identify systems that have been recached
within a specific period, say, within the past 3 months?

Many thanks,
Hugh

 

[Arie - ×ריה]

Hi Hugh,

There are 2 main options that i usually use:
1. Since every fix installed changes the version of a specific file/files -
mostlydll/exe files, you can use a script (via login script) that will give
you a clear undestanding who has the new version and who doesnt (requires
VBScript knowledge)
If you have SMS deployed in your organization, you can use its features to
gather that information.

2. MS has released a tool called: Office Update Inventory Tool
That you can use to make an inventory of who has what...say several fixes
were installed to the admin point, and different station did a recache after
each fix...

More info:
http://www.microsoft.com/office/ork/2003/journ/offutoolv2.htm

Hope this helps

Arie H.