applying MSP to MSI
This may sound a bit silly..
If I want to apply a MSP file (service pack released by the vendor) to an MSI file, should I do it to the original MSI file or the one at the administrative install? Under normal practise, I will do the following.
1. Extract the MSI file to an administrative install location. msiexec /a abc.msi targetdir=c:\admindir. It extracted another MSI file (i.e. xyz.msi and some directories)
2. Apply the msp file to the administrative install location. msiexec /a c:\admindir\xyz.msi /p xxx.msp
For some reason, I was trying this and that and managed to apply the msp file to the original abc.msi file. How could that happen? I run the original patched msi file on the workstation, the program installed but was behaving abnormally.
Any info will be appreciated.
If I want to apply a MSP file (service pack released by the vendor) to an MSI file, should I do it to the original MSI file or the one at the administrative install? Under normal practise, I will do the following.
1. Extract the MSI file to an administrative install location. msiexec /a abc.msi targetdir=c:\admindir. It extracted another MSI file (i.e. xyz.msi and some directories)
2. Apply the msp file to the administrative install location. msiexec /a c:\admindir\xyz.msi /p xxx.msp
For some reason, I was trying this and that and managed to apply the msp file to the original abc.msi file. How could that happen? I run the original patched msi file on the workstation, the program installed but was behaving abnormally.
Any info will be appreciated.
0 Comments
[ + ] Show comments
Answers (6)
Please log in to answer
Posted by:
kkaminsk
15 years ago
Your method for patching the MSI is correct but some MSIs do not properly create an administrative installation when supplied the /a switch. I would talk to your vendor about the issue before trying to fix it yourself.
Posted by:
nheim
15 years ago
Hi AH,
this is ok like this. The admin install in front of applying a patch is needed to make the files accessible for the patching process.
If you have a package without compressed files, you can apply the patch right away, by temporary checking the admin install in the summary info dialog.
BTW: What app are we talking about here?
Regards, Nick
this is ok like this. The admin install in front of applying a patch is needed to make the files accessible for the patching process.
If you have a package without compressed files, you can apply the patch right away, by temporary checking the admin install in the summary info dialog.
BTW: What app are we talking about here?
Regards, Nick
Posted by:
anonymous_9363
15 years ago
1. Extract the MSI file to an administrative install location. msiexec /a abc.msi targetdir=c:\admindir. It extracted another MSI file (i.e. xyz.msi and some directories)Actually, it doesn't extract another MSI, it "rebuilds" the original MSI such that it points to the extracted uncompressed files (rather than, say, any embedded CABS) and marks the MSI as an admin image (by changing the WordCount property in the Summary stream.)
Posted by:
ahcash
15 years ago
BTW, the app is AutoDesk Design Review 2009. I was trying to apply Service Pack 1 MSP to the MSI. So, in other words, it's best to patch the administrative install rather than patching the original MSI itself?
Posted by:
timmsie
15 years ago
Yes patching the admin install is the way to go.
If you've already deployed the msi you can simply deploy the patch (with sms or whatever tool you use):
msiexec.exe /p xxx.msp /qb
If you've already deployed the msi you can simply deploy the patch (with sms or whatever tool you use):
msiexec.exe /p xxx.msp /qb
Posted by:
parrs
15 years ago
Hi Ah
I packaged that app with MSP. Deployment via zenworks so a little different, but same principals.
Went like this:
1. Run SetupDesignReview2009.exe and copy extracted folder when it runs from from c:\documents and settings\username\temp\WZSE0.tmp to c:.
2. Copy msp to c:\WZSE0.tmp and at run prompt - msiexec.exe /p "C:\WZSE0.tmp\DesignReview2009SP1.msp" /a "C:\WZSE0.tmp\SetupDesignReview2009.msi"
3. Copy SetupDesignReview2009.msi plus two new folders created by MSP (C:\WZSE0.tmp\program files and Common) to network for deployment.
It's not SMS but hope that helps.
Cheers
Steve
I packaged that app with MSP. Deployment via zenworks so a little different, but same principals.
Went like this:
1. Run SetupDesignReview2009.exe and copy extracted folder when it runs from from c:\documents and settings\username\temp\WZSE0.tmp to c:.
2. Copy msp to c:\WZSE0.tmp and at run prompt - msiexec.exe /p "C:\WZSE0.tmp\DesignReview2009SP1.msp" /a "C:\WZSE0.tmp\SetupDesignReview2009.msi"
3. Copy SetupDesignReview2009.msi plus two new folders created by MSP (C:\WZSE0.tmp\program files and Common) to network for deployment.
It's not SMS but hope that helps.
Cheers
Steve
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.