During the analysis phase of a windows 7 x64 migration I have been using the MAP, ACT and OMPM tools.
After handing over all the lists on the application and current client side infrastructure, the first question that came is: “ok I see a lot of applications listed that are only installed on one machine, can you give us the machinenames?”.
ehm well, it should be possible…
in the ACT GUI you can find the computername if you click on the application, but I had to find a way to automate this
So I installed the SQL management studio express and dived into the ACT database.
Here is the SQL query to give you all applications installed on only 1 machine:
FROM Application_Computer_Count INNER JOIN
Application_Report_Complete_vw ON Application_Computer_Count.appID = Application_Report_Complete_vw.AppID INNER JOIN
Application_Computers_Query ON Application_Report_Complete_vw.AppID =Application_Computers_Query.appID
WHERE (Application_Computer_Count.computerCount= 1)
What is more interesting is the following query, which will give you all applications installed on 1 pc marked with 1 or more issues:
FROM App_Issue_Counts INNER JOIN
Application_Computer_Count ON App_Issue_Counts.appID =Application_Computer_Count.appID INNER JOIN
Application_Computers_Query ON App_Issue_Counts.appID =Application_Computers_Query.appID INNER JOIN
Application_Report_Complete_vw ON App_Issue_Counts.appID =Application_Report_Complete_vw.AppID
WHERE (App_Issue_Counts.activeIssuesCount >=’1′) AND (Application_Computer_Count.computerCount = 1)
another thing with ACT 5.6, was that it did not seem clear to me why none of the 16 bit applications were listed in the collected data
Luckily there is a way to find them with another SQL query, checkout (and credits to): http://www.theexperienceblog.com/2011/04/14/how-to-find-16-bit-applications-in-your-act-inventory
The last thing for now on ACT is that the collector is not capable yet to work with windows 7 sp1.
you need to import a sql script to make this possible
Here is the content of this script (the import can be done via osql.exe -E -i<thenameofthesqlscript> -S”<sqlserver\instance>” -d<dbname> :
,N’Windows 7 SP1′
,N’Service Pack 1′
,N’Service Pack 1′
Also remember, the infliction point to test applications during a migration is:
COST of failure X PROBABILITY of failure > COST of testing