MSI Upgrade/Product Code Discrepancies

[tmiller11]

I am building an msi with InstallAware 15 so that it can be deployed via SCCM by our corporate IT department. The trouble is that the product and upgrade codes that are displayed in the IA project properties are different than what the IT department is seeing. This is causing problems as they are trying to deploy via active setup and it requires us to write a registry key containing that GUID.

I have created a vbscript that extracts those codes and displays them for my testing purposes. I have attached screenshots of what IA shows and what the script outputs.

Please advise.

[FrancescoT]

Dear User,

the Product Code and the Upgrade code used by your package are those visible under the IA IDE.
However, the Windows Installer Engine creates some additional registry entries when the setup package is distributed as MSI.
These entries are based on random values generated by the MSI engine directly ( ... not controlled by IA).

Honestly, I don't understand where is the problem with them ... you should always refer to those reported by IA.

Regards

[tmiller11]

We are presently trying to deploy our software via active setup and cannot use the codes provided by InstallAware. We would like to be able to write these values to the registry for the active setup. Below is an MSDN article:

http://blogs.msdn.com/b/aruns_blog/archive/2011/11/02/10176957.aspx

[FrancescoT]

Dear User,

with doing a quick google search (... I'm not an Active Setup expert and honestly I never used it), I found some useful links that you may find interesting.

The following link describes a sample that releases an Active setup with embedding an EXE setup (... the effective User installation requirements) within an MSI package. The sample describes the steps using a Wise project, but I believe it can easily adapted in order to do the same with IA.
http://wisepackager.com/KJ/Active_Setup_and_how_to_implement_it.txt

For what I understand Active Setup works with comparing not only the PRODUCT CODE but with the Application name as well.

Anyway, Active Setup seems to be a deprecated technology and not document as well;
http://helgeklein.com/blog/2012/03/get-rid-of-active-setup/

Hope this helps you.

Regards