Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Queries for Office 2000 installations

Status
Not open for further replies.

bardfor

IS-IT--Management
May 23, 2002
1
US
all:

Has anyone out there developed a set of queries to determine which variation of Office 2000 (or 97 or XP) is installed on a network?

We have installed multiple configurations (Standard, Professional, Premium) from one installation point varying the components installed for each installation. We have made some modifications to our network and would like to be able to see how many of each variety of Office are installed.

I have tried multiple approaches to differentiate the installations with no luck. FrontPage will show the installation of Premium on machine X, for instance, but then Machine X will also show up when you query for Access (Professional) or Word (Standard). I have not been able to exclude Machine X from the Standard / Professional queries.

Any advice / solutions would be greatly appreciated.

Thanks in Advance.

BDC
bardfor@hotmail.com
 
I have a solution that will work for you, though it usually takes a bit of fine tuning.

Create a query for each version of Office that you use, it does not matter if there are duplicates across the queries.

You can then creata a second query using the same selection criteria. This time however you can use the previous queries to filter out the duplicates.

As an example for Office 97 create a query that picks out OSA.exe (q1) and for 2000 OSA9.exe(q2). There will be a few duplicates here, depending on the upgrade method used. Now them again (q3 for 97 and q4 for 2000). In the criteria for q3 you can add an additional rule, which ammounts to is not in q2. In the criteria tab add a new criteria and select "subselected value" for Criterion Type, you can then pick field to select on and use browse to pick a query to compare against.

I have found that it is best for q1 and q2 you only use it to extract the system.resource NAME variable, anymore than that seems to confuse SMS.

Anyway once you get the hang of the "Subselected Values" bit I'm sure you'll sort it out.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top