SCCM 2012 best practice, create an application for an msi and a deployment for an exe?
New to SCCM 2012 and have a lot of applications with msi's that I am creating applications for. I've also been able to create a few applications with exe's. Is the only reason to use a package, if you need to run multiple programs or apps in succession?
Answers (2)
You can run multiple applications/programs in Application as well. You can chain them together and SCCM 2012 actually gives a better functionality of this than any of it predicessors.
It also gives you a graphical structure in which your applications will be installed. You can also put requirements which is a great feature and the tress structure changes for install for multiple applications.
Really cool feature.. Should check it out.
Cheers,
Piyush
http://msiworld.blogspot.com.au/
My understanding is that the package support is more legacy functionality while the application model is the future. So it essentially provides backwards support for those updating from older SCCM versions. There may also be one off things you need to do that aren't applications that can be done with it.
We only use application deployments in our environment at this point and haven't found a need to use the package support yet.