MSI, Properties and MST
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
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
Answers (13)
Please log in to answer
Posted by:
joban2000
15 years ago
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,
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,
Posted by:
anonymous_9363
15 years ago
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
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
Posted by:
anonymous_9363
15 years ago
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.
Posted by:
joban2000
15 years ago
Posted by:
PackDep
15 years ago
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.
Posted by:
sabelotodo
15 years ago
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?
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?
Posted by:
anonymous_9363
15 years ago
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.
Posted by:
sabelotodo
15 years ago
Posted by:
sanjaybhirud
15 years ago
Posted by:
bheers
15 years ago
Adobe Customization Wizard 9
http://www.adobe.com/support/downloads/detail.jsp?ftpID=3993
http://www.adobe.com/support/downloads/detail.jsp?ftpID=3993
Posted by:
anonymous_9363
15 years ago
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?
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?
Posted by:
arrietty
14 years ago
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.
Once I get it customised I plan to deploy via SCCM.
any advise would be appreciated.
Posted by:
anonymous_9363
14 years ago
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
so that the conversation will remain readable.