3 Replies Latest reply on Nov 26, 2015 4:37 AM by ibrahem

    How to lookup MSOffice Installations?  MSACCESS specifically?


      I've got a question about the inventory in LDMS 9.0 SP2+


      I am currently trying to build a query to give me a list of computers which don't have Microsoft Access 2010 installed and I am having trouble because it seems that all of my computers have it when in fact almost none of them really do.


      I am currently mining the computer.software.add or remove programs.program.name part of my inventory and I am looking for instances of Access 2010.  There are two options available in my inventory and they read as follows:


      Microsoft Office Access MUI (English) 2010

      Microosft Office Access Setup Metadata MUI (English) 2010


      again, a few computers have this software installed, but most don't.  My problem is that every one of my machines has office 2010 and according to landesk they all have access.   I know this to be false because I can go to the computers and verify that MSACCESS.EXE is not present, yet somehow the inventory scanner is picking up the installation.



      Any thoughts on this?  I'd really like to see the scanner be able to look for specific files or registry entries because it would be very easy for me to take care of this problem on my own.



        • 1. Re: How to lookup MSOffice Installations?  MSACCESS specifically?
          Catalysttgj Expert

          You've got quite a few options to try and tackle this. You could create a query that looks for MSACCESS.EXE instead of looking in "Add or Remove Programs".


          You could create a compound query that combines both, if that were a better result.



          To make a query look for the executable use this: "Computer"."Software"."Package"."Path" LIKE "MSACCESS.EXE"


          in the output columns be sure to include some useful items from the same area:



          "Computer"."Software"."Package"."Times Run"



          The result should be EVERY machine that has MSACCESS.EXE only, and you'll be able to tell by the version information which product you're dealing with.

          So for instance version 14 is Access 2010. By having "Times run" you'll be able to tell who actually uses the program vs. just some copy of the file showing up in inventory. Remember, that inventory captures the file regardless if its ACTUALLY installed, so having the path included in the output will help out on isolating cases where its just a copy of the software on a server share or different partition for instance.


          If you try to compound this query by doing say:


          "Computer"."Software"."Add or Remove Programs"."Program"."Name" = "Microsoft Office Access MUI (English) 2010"


          "Computer"."Software"."Package"."Path" LIKE "MSACCESS.EXE"


          The only issue with this will be that you will have to "qualify" the output columns if you try to use any under "Package", because if you don't you'll end up with a very long list of redundant devices, and more likely the query won't even run as it will overload memory and just give up on ya. The biggest problem with qualifying a column is that it will only return data for the very specific file path. You can't just pick "MSACCESS.EXE", you'll have to pick the specific case of file in a path, and that could be a lot of trouble, so this kind of query is really problematic and not a very good choice.


          A better query might be something like this:

          "Computer"."Software"."Package"."Path" LIKE "MSACCESS.EXE"


          "Computer"."Software"."Package"."Version" LIKE "14."


          Use like for the version as well, because otherwise you will have to put specifically the file version.There might be several of them, so then you'd have to do a group of OR statements where you specify each iteration that you want, where just going with LIKE is probably going to be good enough to get it done. Also, dont forget the dot (period) behind the 14 so that you wont get just any matching characters of 14. I tested the above query and it worked fine and isolated machines running only Access 2010, except without the dot (period), it did return about 3 devices where the file version was actually: 11.0.5614, since it matched on the last two characters. With the dot that goes away.


          On the last comments in your post. You can expand the inventory to look for registry values. There's a lot of articles in the forum on how to do that.

          As the above information shows, i think that covers the other comment pretty well i think.


          Be aware that until SP3 is in the mix, SLM is busted, so don't waste your time with it.


          Anyways, hope this was helpful.

          • 2. Re: How to lookup MSOffice Installations?  MSACCESS specifically?

            Thank you very much.  I didn't know about the PATH part of inventory.  This did exactly what i needed it to.  Very cool!

            • 3. Re: How to lookup MSOffice Installations?  MSACCESS specifically?


              how to create query to provide list with all users in who have got MS-Access installed


              we used LANDesk 9.5