Extract files from an MSP
Hello all,
I have a package that was captured using the IS packager a while back and now the vendor has released a patch (MSP File). Well, the patch won't run because it can't find the product to update.
There is only about 5-6 files in the patch and I want to extract the files.
I think in the future, if we're capturing an install, we'll need to make sure we copy the Product code and upgrade codes to the new project so the vendor patches work in the future, if any.
So, how can I extract the files?
How do you/should you normally deal with this type of issue?
Thanks
lane
I have a package that was captured using the IS packager a while back and now the vendor has released a patch (MSP File). Well, the patch won't run because it can't find the product to update.
There is only about 5-6 files in the patch and I want to extract the files.
I think in the future, if we're capturing an install, we'll need to make sure we copy the Product code and upgrade codes to the new project so the vendor patches work in the future, if any.
So, how can I extract the files?
How do you/should you normally deal with this type of issue?
Thanks
lane
0 Comments
[ + ] Show comments
Answers (5)
Please log in to answer
Posted by:
turbokitty
17 years ago
Since no one has taken you to task yet... Why did you repackage a vendor MSI? This is precisely why you're not supposed to do that.
If you want the files out of the MSP... why not just (on a clean machine):
- install the original vendor MSI
- run a repackager snapshot
- install the MSP
- then another snapshot
It's probably better to do this then hack the MSP. You don't know what else it's doing.. like CA's.
If you want the files out of the MSP... why not just (on a clean machine):
- install the original vendor MSI
- run a repackager snapshot
- install the MSP
- then another snapshot
It's probably better to do this then hack the MSP. You don't know what else it's doing.. like CA's.
Posted by:
wiseapp
17 years ago
I would agree with Turbo, you should avoid repackaging a vendor MSI. However you should follow the way that Turbo has discussed. However still you want to extract the MSP then do this:
Go to run type in the following command :
c:\abc.msp /xp or /extract (whichever works)
Note: Some patches are meant not to be extracted.
Revert back in case you face any issues anywhere...
Go to run type in the following command :
c:\abc.msp /xp or /extract (whichever works)
Note: Some patches are meant not to be extracted.
Revert back in case you face any issues anywhere...
Posted by:
edocshare
17 years ago
OK.. I know that, but apparently the individual before and the random people throughout this org do not know that. We have a few thousand packages here.
We figured it out, there is a little util here, called MSIX, that worked great!
http://blogs.msdn.com/heaths/archive/2006/04/07/571138.aspx
Thanks for the help,
edoc
We figured it out, there is a little util here, called MSIX, that worked great!
http://blogs.msdn.com/heaths/archive/2006/04/07/571138.aspx
Thanks for the help,
edoc
Posted by:
edocshare
17 years ago
ORIGINAL: wiseapp
Go to run type in the following command :
c:\abc.msp /xp or /extract (whichever works)
This did not work, but as I stated, we found a util that works very well.
Thanks for the help,
edoc
Posted by:
wiseapp
17 years ago
Thanks! for sharing that tool Edoc. However as said earlier this command works for certain patches who are programmed to accept these switches I thought may be you're using one of them? Anyhow it works on .Net and other patches of microsoft. Thanks! once again for sharing that information.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.