Hi this is my first post here at appdeploy!

I'm trying to find a easier way to edit my installation files MSI & MST. To edit my MSI & MST files I use WPS 7. Until now I have created a MSI file, and then created a MST file where I run search and replace in the Registry Table to change some registry settings.

What I would like to do is create a MSI file with some properties in the registry so that I can change these in an MST file.

I have tried to search the forum here, but I cant seem to find a solution. Any help would be most appreciated:-)

Regards
Sabelotodo
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
hi,

Easiest way I can think off is to create the properties you require in the property table, make sure you use all uppercase with no spaces when creating them for the name of the property. Eg. PROPERTY1.

The value of the property can be whatever you want.

Then add the required properties in the registry. To do this create your registry key in the usual way but when entering the value enter the name of the property you wish to use by putting the property name in the value field and surround them in these brackets [ ] eg., [PROPERTY1].

Depending on the type of property you are using will determine the type of registry key you create.

You can make these changes either in direct editor mode or through the WPS gui.

I hope this is easy to understand.

Cheers,
Answered 08/28/2009 by: joban2000
Senior Yellow Belt

Please log in to comment
0
I don't understand what it is you want at all. You would typically use an MST to change property values from those which are in its "parent" MSI, not the other way around.

The practical alternatives to editing with WPS are:

- InstallShield/Admin Studio
Out of the frying pan...

- Orca or InstEdit
These are MSI table editors, meaning that you really need to know what you're doing. Fine for quick-and-dirty edits.

- Script

- WIX
Answered 08/28/2009 by: VBScab
Red Belt

Please log in to comment
0
make sure you use all uppercase with no spaces when creating them for the name of the propertyUpper case for property names merely indicates that the property is public, meaning that they can be specified from a command line call to MSIExec, for example. They don't necessarily need to be upper case at all.
Answered 08/28/2009 by: VBScab
Red Belt

Please log in to comment
0
Fair point there, I just tend to make them Uppercase when I create them as I often call properties from the command line as opposed to creating a transform, it depends on how many Properties I have to set. Bad habits are hard to shake I suppose. [:)]
Answered 08/28/2009 by: joban2000
Senior Yellow Belt

Please log in to comment
0

What I would like to do is create a MSI file with some properties in the registry so that I can change these in an MST file.

I have tried to search the forum here, but I cant seem to find a solution. Any help would be most appreciated:-)



It would obviously help you to get an answere if you can explain what is that you want to do. I am really not getting what it is you want at all.
Answered 08/28/2009 by: PackDep
Senior Yellow Belt

Please log in to comment
0
Hi guys, thank you for all your replies

I will try to explain more specific what I want to do.
I have repakcage a ODBC driver (taken a snapshot before and after... in Wise Package Studio), of this snapshot I have created an MSI installation. During the installation of the snapshot I need to type in "servername", "databasename", "IPAdress" etc. All these settings are stored in the registry.
Now, I will be using this package in several different environments, that means that the "servername", "databasename", "IPAdress" will change for each environment. Instead of doing a "search and replace" in the "Registry" table in the MST file I was wondering if it was possible to create some sort of "Property" or "Custom Action" that I can call and change in the MST file?
Answered 08/28/2009 by: sabelotodo
Senior Yellow Belt

Please log in to comment
0
The simplest way would be to create public properties for the variable items e.g. IP address and use the properties for the registry entries. You could save each different version as a separate transform. Thus, you would create a property called, say, IPADDRESS and assign it the appropriate value. Then, for your registry entry, instead of using the actual address, use the property, but enclosed in square brackets - [IPADDRESS]. The brackets tell the Windows Installer engine to use a property.
Answered 08/29/2009 by: VBScab
Red Belt

Please log in to comment
0
Thank you very much joban2000 and VBScab! Based on your quick answers, I have managed to create an MSI / MST file with the needed properties.:)

Have a nice day!
Answered 08/31/2009 by: sabelotodo
Senior Yellow Belt

Please log in to comment
0
Hi,

I want to install acrobat 9.10 in approximate 300 pc & uninstall the previous version of acrobat reader.

can some one help to uninstall old reader & install new reader using msiexec or gorup policy or logon script

Please help me to do this

waiting for reply

Sanjay
sanjay.bhirud@yahoo.co.in
Answered 09/16/2009 by: sanjaybhirud
Yellow Belt

Please log in to comment
0
Answered 09/16/2009 by: bheers
Second Degree Blue Belt

Please log in to comment
0
I'm trying to think how your question could have been made more vague... :)

Exactly what do you need help with? Creating the transform (in which case, see Suresh's <bheers> post)? What command line arguments to pass to MSIExec? How to add an MSI to a Group Policy Object? How to set up a log-on script for a GPO? How to write a script?
Answered 09/17/2009 by: VBScab
Red Belt

Please log in to comment
0
Please help me too. I dont' understand what I am doing wrong. I have installed the customization wizard on my computer and opened the MSI from the server where Adobe 9 pro installation is located. I've have made a few changes like not showing the EULA and disabling the updates but none of the changes come through when I am deploying it. I save the package and the MST appears to update (date and time change). I have also tried 'generate transform' and then replacing the MST in the folder but nothing makes a difference. I have changed the setup.ini to include name and serial key and this allows the install to proceed. I'd like to also make the default preference units be centemetres.

Once I get it customised I plan to deploy via SCCM.
any advise would be appreciated.
Answered 05/26/2010 by: arrietty
Yellow Belt

Please log in to comment
0
- First, it's bad form in any forum to hijack threads, especially old ones.
- Second, please post the command line you're using when testing the package.
Answered 05/27/2010 by: VBScab
Red Belt

Please log in to comment
Answer this question or Comment on this question for clarity