Running a MSI with MSP patches
We have used Group Policy to deploy MSI files in our environment. You can of course run your MSI and call a .MST but there is no place to specify more command line switches. We have an application that has the main MSI as well as 4 .MSP files. So we have this command line when we run it manually.
"DFS-SHARE\Deploy\Adobe\Acrobat913\AcroPro.msi" /QB! TRANSFORMS="DFS-SHARE\Deploy\Adobe\Acrobat913\AcroPro.mst" ALLUSERS=1 /update "DFS-SHARE\Deploy\Adobe\Acrobat913\Patches\1 AcroProStdUpd910_T1T2_incr.msp;DFS-SHARE\Deploy\Adobe\Acrobat913\Patches\2 AcrobatUpd911_all_incr.msp;DFS-SHARE\Deploy\Adobe\Acrobat913\Patches\3 AcrobatUpd912_all_incr.msp;DFS-SHARE\Deploy\Adobe\Acrobat913\Patches\4 AcrobatUpd913_all_incr.msp" REBOOT=R /L*V+! "c:\program files\wise\logs\AcroPro9.log"
How can you run/call this using GPO's? Or can you?
"DFS-SHARE\Deploy\Adobe\Acrobat913\AcroPro.msi" /QB! TRANSFORMS="DFS-SHARE\Deploy\Adobe\Acrobat913\AcroPro.mst" ALLUSERS=1 /update "DFS-SHARE\Deploy\Adobe\Acrobat913\Patches\1 AcroProStdUpd910_T1T2_incr.msp;DFS-SHARE\Deploy\Adobe\Acrobat913\Patches\2 AcrobatUpd911_all_incr.msp;DFS-SHARE\Deploy\Adobe\Acrobat913\Patches\3 AcrobatUpd912_all_incr.msp;DFS-SHARE\Deploy\Adobe\Acrobat913\Patches\4 AcrobatUpd913_all_incr.msp" REBOOT=R /L*V+! "c:\program files\wise\logs\AcroPro9.log"
How can you run/call this using GPO's? Or can you?
0 Comments
[ + ] Show comments
Answers (10)
Please log in to answer
Posted by:
anonymous_9363
15 years ago
How can you run/call this using GPO's? Or can you?No, you can't. But, since you have a deployment system, you should be patching that and running from there, rather than trying to patch clients. Make back-ups of the MSIs and changed files, if you can.
Posted by:
AngelD
15 years ago
I don't know if Ian tries to say: perform an admin install and apply the patches on the AIP-MSI, you can then deploy this MSI (which now includes the patches) through the GPO.
You'll need to create a new transform from out the AIP-MSI.
You'll need to create a new transform from out the AIP-MSI.
Posted by:
anonymous_9363
15 years ago
Use the App Deploy Repackager to create a custom MSI.The AD re-packaging tool is designed for creating MSIs from legacy installers. Adobe, of course, is already in MSI form and re-packaging MSIs is A Really Bad Idea. If you perhaps meant that the OP should create an MSI to call the Adobe MSI with the extra arguments, then again, it's now generally accepted that nested MSIs are A Really Bad Idea.
As Kim says in tidying-up for me, you should create an Administrative Installation Point (AIP), patch that, then execute the resulting MSI/MST.
Posted by:
airwolf
15 years ago
I don't use the AD repackager, but it was my understanding that it simply used before and after snapshots to create an MSI. The installation mechanism used between snapshots should be irrelevant.
Posted by:
anonymous_9363
15 years ago
Andy, theOP wanted to know how he can apply a patch (or patches) to his Acrobat Professional deployment via GP. At no point does he or anyone else mention a requirement for snapshotting.
Posted by:
airwolf
15 years ago
The OP wanted to install an MSI and an MSP in sequence. Couldn't he use the AD Repackager to take a snapshot, install both, then take the 2nd snapshot to create an MSI? There are a number of ways the OP could solve this problem, I was just suggesting what I thought to be the simplest one. Personally, I'd create a custom wrapper in AutoIT with the MSI and MSP embedded in the compiled EXE - which would run them in sequence. I've also setup custom deployments to do the same thing in KBOX, but I don't know if the OP is using any centralized management system, much less KBOX specifically.
Posted by:
Jsaylor
15 years ago
For a wide variety of reasons, it's a less than stellar idea to try and snapshot a vendor MSI, much less one from Adobe, a company that dedicates its entire existence to snuffing out the hopes and dreams of application deployment specialists everywhere.
Snapshot-style packaging is really only appropriate to use in conjunction with legacy installers. Beyond that, you're asking for trouble by getting rid of all the logic and custom actions present in your average MSI package.
Snapshot-style packaging is really only appropriate to use in conjunction with legacy installers. Beyond that, you're asking for trouble by getting rid of all the logic and custom actions present in your average MSI package.
Posted by:
airwolf
15 years ago
Adobe, a company that dedicates its entire existence to snuffing out the hopes and dreams of application deployment specialists everywhere.
Agreed. LOL
Posted by:
mhsl808
15 years ago
quote:
Adobe, a company that dedicates its entire existence to snuffing out the hopes and dreams of application deployment specialists everywhere.
Very well said !!!!!
Adobe, a company that dedicates its entire existence to snuffing out the hopes and dreams of application deployment specialists everywhere.
Very well said !!!!!
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.