Upgrading Communicator.msi
I am trying to upgrade communicator.msi, version 1.0.559.0 (communicator 2005 not 2007), with a hotfix (KB 949280), communicator.msp, and end up with just an communicator.msi at the new version (1.0.559.232), so I can deploy it.
We have an updated msi, but, it's only 1.0.559.224.
I can't find how to "slipstream" the patch into the msi, and, end up with a single msi. I found some articles with Google on doing an Admin install, then, upgrading it, but, when I do that, I get a pfiles folder, not a single msi.
How to update an msi with an msp and end up with a single msi?
I have Orca, and other tools in the SDK.
Thanks.
We have an updated msi, but, it's only 1.0.559.224.
I can't find how to "slipstream" the patch into the msi, and, end up with a single msi. I found some articles with Google on doing an Admin install, then, upgrading it, but, when I do that, I get a pfiles folder, not a single msi.
How to update an msi with an msp and end up with a single msi?
I have Orca, and other tools in the SDK.
Thanks.
0 Comments
[ + ] Show comments
Answers (5)
Please log in to answer
Posted by:
Lindeberg IT
15 years ago
You cannot do this without recompiling the MSI and that will require a tool like Installshield or Wise Package Studio.
There should be no problem with deploying the administrative MSI with uncompressed files in the pfiles folder; just think about packages like Microsoft Office, which have this aswell.
There should be no problem with deploying the administrative MSI with uncompressed files in the pfiles folder; just think about packages like Microsoft Office, which have this aswell.
Posted by:
AngelD
15 years ago
Sure you could with ex. the WiMakCab.vbs script from the SDK.
However; I wouldn't recommend it, but instead apply the patch as it is.
However; I wouldn't recommend it, but instead apply the patch as it is.
Posted by:
anonymous_9363
15 years ago
I can't find how to "slipstream" the patch into the msi, and, end up with a single msi. I found some articles with Google on doing an Admin install, then, upgrading it, but, when I do that, I get a pfiles folder, not a single msi.You mean that you DO end up with a single MSI but not one which uses embedded CABs. THAT is what you want, correct?
If so, then Kim is right on both counts, in that you could use the SDK script and that this course is not to be recommended.
Posted by:
gmouse
15 years ago
Well, thanks for all the discussion, I appreciate that.
Let me explain better what's going on...
We have a deployment of Office 2007 and some other things (Communicator being one of them), and, someone in the past slipstreamed the single MSI to 1.0.559.224. This newer hotfix rollup will upgrade it to 1.0.559.332.
Since this was a "canned" install, I need to keep the same files, etc., so, can't use the subordinate PFiles folder (although, maybe, it would work), which is why I am trying to slipstream.
Might not be recommended, but, looks like it was already done to me, so...<G>
Thanks.
Let me explain better what's going on...
We have a deployment of Office 2007 and some other things (Communicator being one of them), and, someone in the past slipstreamed the single MSI to 1.0.559.224. This newer hotfix rollup will upgrade it to 1.0.559.332.
Since this was a "canned" install, I need to keep the same files, etc., so, can't use the subordinate PFiles folder (although, maybe, it would work), which is why I am trying to slipstream.
Might not be recommended, but, looks like it was already done to me, so...<G>
Thanks.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.