This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
A new Flexera Community experience is coming on November 25th, click here for more information.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Flexera Community
- :
- AdminStudio
- :
- AdminStudio Forum
- :
- Re: Apply a new MST to existing MSI install
Subscribe
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
Apply a new MST to existing MSI install
Subscribe
- Mark as New
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Subscribe
- Mark as New
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Our company is currently using a software deployment tool to push MSI's to XP desktops. The problem we are running into is when an application needs a new MST applied to a existing install. We currently have to perform an uninstall then reinstall to get the MST to apply. Does any one know of any tricks, tips or command lines that we are missing to force a new MST to apply during an MSI upgrade, without reinstalling? Erich
‎Jan 23, 2006 08:34 AM
(6) Replies
Subscribe
- Mark as New
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Subscribe
- Mark as New
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Not really. MST's are not patches, they are database transformations.
The only thing I can think of would be to create a new database by applying the transform to the orginial, then generate a patch using the differences between the original database and the transformed database. Then push the patch.
That could be very dicey though depending on what the transform did. Frankly I'm a fan of major upgrades and I don't mind doing an uninstall then install to make sure I got it right.
The only thing I can think of would be to create a new database by applying the transform to the orginial, then generate a patch using the differences between the original database and the transformed database. Then push the patch.
That could be very dicey though depending on what the transform did. Frankly I'm a fan of major upgrades and I don't mind doing an uninstall then install to make sure I got it right.
‎Jan 23, 2006 08:53 AM
Subscribe
- Mark as New
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Subscribe
- Mark as New
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I agree with Chris- when possible, I prefer a compete wipe of the old app before installing a new one.
Try this to get the old .msi app off your systems:
Find the product code for the old install in the registry.
Run the following command line to uninstall it:
c:\windows\system32\msiexec.exe /X /QN
Then run your transform install command line.
You can even string them together in a batch file if you want.
Try this to get the old .msi app off your systems:
Find the product code for the old install in the registry.
Run the following command line to uninstall it:
c:\windows\system32\msiexec.exe /X
Then run your transform install command line.
You can even string them together in a batch file if you want.
‎Jan 23, 2006 09:59 AM
Subscribe
- Mark as New
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Subscribe
- Mark as New
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I'll make it easier then that....
Find the upgrade code of the original MSI and author a Major Upgrade transform for the new MSI. Run your new MSI with both transforms and the removal/install is one step.
Find the upgrade code of the original MSI and author a Major Upgrade transform for the new MSI. Run your new MSI with both transforms and the removal/install is one step.
‎Jan 23, 2006 10:10 AM
Subscribe
- Mark as New
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Subscribe
- Mark as New
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Cool...never thought of that.
How would the command line look?
How would the command line look?
‎Jan 23, 2006 10:12 AM
Subscribe
- Mark as New
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Subscribe
- Mark as New
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
When I populate a distribution point with an MSI, I don't want to take the chance someone would accidentally run the MSI without the transform so I "apply" the transform to the MSI before pushing it out to the DP's.
So the command would be your standard setup /s /v"/qn" or msiexec /i foo.msi /qn
The magic is in the Upgrade and InstallExecute tables of the transformed MSI. The MSI would automatically detect the previous install, remove it, and then install itself.
So the command would be your standard setup /s /v"/qn" or msiexec /i foo.msi /qn
The magic is in the Upgrade and InstallExecute tables of the transformed MSI. The MSI would automatically detect the previous install, remove it, and then install itself.
‎Jan 23, 2006 10:44 AM
Subscribe
- Mark as New
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Subscribe
- Mark as New
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Aaahhhh...light dawns on Marblehead.
I understand now.
Thx
I understand now.
Thx
‎Jan 23, 2006 10:51 AM
Related Content
- AdminStudio 2024 in AdminStudio and Workflow Manager Release Blog
- Packaging Experts Roundtable Q&A (March 2023) in AdminStudio Blog
- Docker Desktop 4.17.0.99724 from Package Feed Module detected virus (false positive?) in AdminStudio Forum
- AdminStudio 2022 is Here! in AdminStudio and Workflow Manager Release Blog
- MSIX Question for AdminStudio in AdminStudio Forum
