Video Screencast Help
Search Video Help Close Back
to help
Not able to make it to Vision this year? Get a sampling in the Best of Vision on Demand group.

Which msi / mst files have a certain file in them?

Updated: 21 Dec 2011 | 4 comments
Darren Collins's picture
0 0 Votes
Login to vote
This issue has been solved. See solution.

We use Wise Package Studio Professional 7 SP3.

A Sophos scan has picked up that we have pskill.exe as a Potentially Unwanted Application on our Wise Share Point.  It is showing as in E:\Wise Share Point\000\046\pskill.exe

Therefore the file looks like it was extracted from an msi or mst during the import of the package into the database for conflict checks etc.

My question is, how can I tell which msi / mst the pskill.exe file came in with, or is within?

 

By the way it looks like it is the genuine SysInternals version of the file, but I just want to know how I can track any file from the imported folder structure on the Wise Share Point back to the original msi or mst.

 

Many thanks in advance,

Darren.

Comments

EdT's picture
14
Dec
2011
0 Votes 0
Login to vote

Hi Darren

If the application has been imported into Software Manager, you should be able to track the file in the Software database. Might be worth having a look with the SQL tools to see if you can track it that way.

If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.

Darren Collins's picture
14
Dec
2011
0 Votes 0
Login to vote

Urrggh! SQL Server!

Hi Ed, cheers for that, I was hoping there was a way via the application without digging into the SQL server.  As you know, I'm not the SQL guru in this office!

Darren.

Darren Collins
Applications Packaging and Deployment for the ICT Support Team,
Oxford University, UK.

Darren Collins's picture
14
Dec
2011
0 Votes 0
Login to vote

By the way ...

... I realise that mst files themselves do not have files in them, I should have said msi or cab files (that may have been generated as a result of creating an mst via WPS).

Darren.

Darren Collins
Applications Packaging and Deployment for the ICT Support Team,
Oxford University, UK.

EdT's picture
14
Dec
2011
0 Votes 0
Login to vote

Maybe a quick and dirty

Maybe a quick and dirty solution - make an MSI with pskill.exe in it, import into software manager and look for conflicts.  It might be worth sticking the file into several folders, eg TEMP.

From what I recall, it should not be too diffficult to view the database tables directly rather than using SQL calls.  I'm in tomorrow so we can have a peek if necessary.

If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.