Why a install wrapper???
Hi there,
why do so many people/companys uses a install wrapper to install the software out of SCCM?
For example a standard MSI can also be deployed and installed directly out of the console but a lot of people link at first to a vbs/batch or powershell script to do the execution.
Can anyone tell me what is the advantage?
Thx
Stephan
Answers (6)
There is no advantage over the direct handling of the MSI in SCCM - unless the script is doing something else as well.
I guess that the packager has tested the package with the script, therefore he (edit: or she) knows that it works. So if the deployment guys (edit: or gals) are given the script it removes any margin of error with them creating the package directly in SCCM.
It's not a method I use, I document the command line and expect that that is how the package/program will be configured in SCCM.
Hope that helps,
Dunnpy
Comments:
-
totally agree.. It has to be some customization which is done outside the MSI. - piyushnasa 11 years ago
Hi
I normaly use a setup.vbs file that takes the MSI filename as a parameter
My script is created so that it checks if the program is allready installed if installed then the program vill uninstall first and the install again.
This is a great way to easy replace a program with a newer version, but the new MSI must have same Package guid for this to work.
I agree. There are plenty of softwares that are better called with their bootstrappers (setup.exe i.e. MS Office, Oracle, SAP.. etc) and also some vendor MSIs do not have an UpgradeCode used for upgrading, so many reasons.. a pure MSI cannot really be done at all times and a wrapper is the best tool for the job..
when u use a wrapper it would actually saves you time when u deploying softwares. One of which is you dont really have to create task sequences for multiple installations. Bootstrapper does really help you that ways. If at all if you are not using Bootstrapper you got to create programs and then you have create task sequence which is a pain.
