Manual Script Application Installer Method

Unfortunately, SCCM is unable to automatically detect and configure an application installer for every installation. SCCM isn't necessarily very good at doing this with an MSI. For this reason, most installations, outside of the absolute most common, are customized or batch scripted. Batch scripting requires manual deployment.

Create a new application package. Manually configure.

Fill in the application information.

If you have only ever deployed MSI, this will be new to you. Add...

If you have an MSI that is part of your package, leave the Type as Windows Installer, and Browse..., if you do not, change the type to Script and skip the next step.

*Select an MSI and click next. Copy the {PRODUCT-CODE}, then click back to the beginning of this wizard.

Change the Type to Script, and click next.

Name your deployment, I add Script to the name of all batch deployments, and put (.cmd) at the end.

If you've selected an MSI that was part of the deployment package, you may just need to select the Installation Program, which I always name "install.cmd". The uninstall program will only uninstall the selected MSI, so it doesn't really matter here, anyway. If you have not selected an MSI, select the package folder and the installation program now, and click Next.

This is where the MSI makes a difference. If you've selected an MSI before going back, the setting type should be set to Windows Installer, and the product code should be filled in. If not, you've also copied the product code. Select Windows Installer and paste the product code here. If you did not have an MSI in your package, install the program on your reference computer, and detect either the uninstaller (registry) or a file in the installed folder. Click OK.

It's pretty satisfying to have a product code for detection, but be sure it's a part of the installation, or you'll end up with deployment errors. I'll be working on a tutorial for detection. Click Next.

Set experience as necessary. Next until finished.

I've used this for lots of quick installation configurations early on, but I use it mostly to script post installation configurations that keep users from having to do anything but use programs as intended.