SCCM application deployment of MSI, then MSP update(s)
We have SCCM current branch running. We would like to take advantage of "application" deployment instead of the old school "package" deployment for some of our applications that licensing considerations that need to be honored.
Take Adobe Acrobat for example.
It's easy enough to create an application to install our customized 11.0.0 version. But what I can't figure out how to do is to layer on one more MSP's to get it to the current patched version. Let's start small and say I want to layer on the 11.0.13 MSP. Is that a second deployment type within the same application?
Or can I layer on the MSP's in the same command line that does the original install? I've not had much luck with that when I tried it in the past.
What I'd like to do is find out the right way to do it so we can do this sort of thing the same way for any MSI where we have MSP's to add on later. We're not looking for a one-off. We're just using Acrobat as the example.
Take Adobe Acrobat for example.
It's easy enough to create an application to install our customized 11.0.0 version. But what I can't figure out how to do is to layer on one more MSP's to get it to the current patched version. Let's start small and say I want to layer on the 11.0.13 MSP. Is that a second deployment type within the same application?
Or can I layer on the MSP's in the same command line that does the original install? I've not had much luck with that when I tried it in the past.
What I'd like to do is find out the right way to do it so we can do this sort of thing the same way for any MSI where we have MSP's to add on later. We're not looking for a one-off. We're just using Acrobat as the example.
This question needs an answer!
Become an EE member today
7 DAY FREE TRIALMembers can start a 7-Day Free trial then enjoy unlimited access to the platform.
View membership options
or
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.
ASKER
To install the MSP, I found this - https://www.windows-noob.com/forums/topic/5522-deploy-application-and-then-after-deploy-update-to-application, which works great.
I created a second application for Acrobat MSP's. I defined a dependency for the patch MSP application on the base install application, but disabled auto-install, so the patch is only installed if the software is installed.
It looks to be working, but I've only tested with one cleanly imaged computer so far.