SCCM, Packaging software and deploy packages using SCCM?
How do I get software on endpoints using SCCM?
Software packaging can be vastly different depending on the installer provided and the setup needs to get the program to a point where a non-administrative user can run the program fully without problems. The complete set of steps to do this are beyond the scope of a short article.
The overall goal is to get the SCCM to run the installer silently (not prompting the user in any way, even to present a dialog indicating install progress or to indicate a successful install) and to run to completion. For many installers that aren't MSIs, this means you'll need to:
- look up what option(s) exist to make the installer or uninstaller run silently
- get the installer to accept all of the data it will need during setup (license codes, configuration details, etc.). Depending on the specifics of this configuration, this could involve specifying configuration with command-line switches, arguments pointing to a configuration file, or something the installer can find in the registry before the installer runs.
- make sure the installed application is ready for the user to run, not installing an installer.
MSI installers check against the product code to ensure that the application has correctly installed. Non-MSI installers require checking something else such as the presence of a registry key, file, or folder, or a specific value such as a version number. This will vary from app to app, and version to version.
New versions of apps may also require supersedence to be configured. This tells SCCM to install the new version where the old is present on a targeted deployment. This can be configured to uninstall previous versions rather than install over-the-top, which is sometimes necessary.
Consider visiting IT Ninja for assistance with troublesome or new installers. IT Ninja is a discussion site where IT Pros discuss how to silently install programs (typically for Windows and MacOS).