Software Deployment

yeah, chances are the setup.exe is a wrapper which contains the serial number for the application. You could try capturing the EXE/MSI, i know its against BP, but if you can't get the serial number you may not have a choice. Either that or contact the vendor or the customer to get the serial.

You might also want to search your registry for the Serial Nos.

ya cheers ..it looks as if i will have to recapture the MSI/exe..its crap because it is a driver application which means i will have to do a bit of work[:@]..ah well.there must be logic contained in the exe wrapper?

Good to see you're working hard anyways Davey...

They'll appreciate your work ethic in the UK next week!

It sounds like you're facing the classic $@#% InstallShield bootstrapped MSI problem. The Setup.exe installs InstallShield Script if it is not present or backlevel then uses InstallShield Script to pass data to an incomplete MSI.

If you extract everything in the install files you will find several MSIs. One is for the application you are installing. Another is an MSI for InstallShield Script. The InstallShield Script MSI is actually a complete MSI and you should extract that and install it as a prerequisite application. Once that is installed, see http://itninja.com/blog/view/7.8-gigabyte-size-limit-in-nt''s-ntfs4 for instructions on how to change the MSI to work without the Setup.exe.

You will also need to determine what data is being passed to the MSI and insert that, it is usually a property that is added to the property table.

1. Introduction
This document gives a detailed description of the Vendor MSI and ways of trouble-shooting.

All the concerned people in repackaging can use this document as reference.

2. Types of Vendor MSI’S

1.source as a vendor MSI.
2.Setup.exe pulling a vendor MSI.
3.Setup.exe pulling a vendor MSI (dependent on Setup.exe to install fine).

2.1 Do’s And Don’ts on getting a vendor MSI as a source.

If we get a Vendor MSI mentioned in the first case as a source, then using the Vendor MSI can directly create the Transforms.

Never Repackage an MSI. It will cause lots of problem in the functionality and even the product code and component information will be changed.

One more reason to retain Vendor MSI without making any changes is Vendor wants to retain the original source and logic in creating the source. Vendor should be able to look back to the changes. Therefore only Transforms should be created.

Transforms are used to make the changes to the Vendor MSI without actually disturbing the original source.

It is similar to giving information in the explanatory log for future references. The changes can be tracked using the tool as a part of wise package studio Visual MSIDiff.

2.2 Setup.exe pulling a vendor MSI

Packaging tools like Install Shield and Wise Package Studio can be used to create MSI embedded inside the set-up file.

How to identify?

There are various methods to identify the above-mentioned condition.

Method 1
1.Double-Click on the Setup.exe
2.Browse to C:\Documents and Settings\Administrator\Local Settings\Temp
3.Copy of MSI will be placed in the above-mentioned location.

Method 2
1.Double-click on the Setup.exe
2.Go to control Panel/Administrator Tools/Services and Disable the Windows Installer Service and Restart.
3.If the Setup.exe were pulling an MSI then it would throw an error while installing.





Therefore it can be confirmed that the setup.exe has an MSI embedded in it.



2.3 Setup.exe pulling a vendor MSI (dependent on Setup.exe to install Fine)

Install Shield gives option of creating the vendor MSI that is dependent on the setup.exe.

In such a scenario, Extracting MSI form the above mentioned methods will not work, as the MSI will have Install shield scripts for the installation through INI file.

1.How to identify?

1.Identify the MSI from the source by following one of the above-mentioned steps.

2. Steps to be followed.

1. Double click on the setup.exe
2. Browse to C:\Documents and Settings\Administrator\Local Settings\Temp.
3. Copy the MSI to different location
4. Double click on the MSI and follow the Installation Manual
5. If the MSI Throws an Error







Then the MSI is dependent on the Setup.exe configurations



Steps to Trouble Shoot
1. Delete the contents of C:\Documents and Settings\Administrator\Local Settings\Temp

2.Double click the setup.exe.

3. Browse to C:\Documents and Settings\Administrator\Local Settings\Temp

4.Copy the temporary files to a different location

5.Setup.exe is created using Install Shield will have some install scripts which will determine the installation procedure.


In such a case it will copy some MSI’S

1. ISScript.MSI
2. RoboDemo 5.0.msi

There are two ways to solve this
1.Delete all the Install Shield related custom actions in the MST.
2.Delete the launch condition in the MSI (If it is provided) in the MST.
Excellent way of solving
1.Create transforms for RoboDemo 5.0.msi and Add a property "ISSETUPDRIVEN" and set the value to "1".

2. Remove or comment out the "OnCheckSilentInstall" custom actin in the "InstallExecuteSequence".


Mention the ISScript.MSI as the dependency for this software to install fine in the Explanation Log.

By doing this we ensure no custom script of the original source is deleted.

Further these two MSI can be converted to one MSI by calling embedded MSI logic.

Lot of INI files will be copied to C:\Documents and Settings\Administrator\Local Settings\Temp.

For Example

1. _ISMSIDEL.INI-The function of this INI file is to delete the temporary files copied to C:\Documents and Settings\Administrator\Local Settings\Temp.
2. Setup.INI- The function this INI file is to provide information for the installation.
3. 0x0409.ini-The function this INI file is to detect the conditions for the proper installation like (detects OS)
And pops an error if the condition is not met.



send me your e-mail id.I would send you this document


End of the Document

setup.exe /a will usually expand the source files (including MSI) to a location of your choice.

From there, you can modify the MSI or (even better) use a transform.