Why the extensive scripting when packaging applications for SCCM 2012/Windows7?
I have worked with software packaging for many years, but for I have been focusing on other tasks for a long time. Now back in a coordinating role, I have entered a projectrole where we need to package a serious amount of applications. There are a lot of big consultancy/packaging companies involved. Now, I have seen that most of these use some form of wrapper/script when doing packaging. For me, coming from a background where you either did an MST or an own MSI this is very puzzling.
Our upcoming environment is Windows 7 with SCCM 2012. Of course, one can need to check for running processes for example, but still I fail to see why people want to use external scripts for this instead of keeping things within the MSI files. Is this something that is happening in most projects/companies, a temporary trend or just how software packaging has evolved?
Community Chosen Answer
You should always try to keep things to MSI/MST form and if it is not possible only then go to script form. There are not all but quite a lot of softwares now which require some scripting apart from MSI as well.
Don't over rule it but try to keep the max to MSI format