Application Management Overview
Deploying and managing software is one of the most important things that you will do as a SCCM administrator. It is important that you setup your lab and practice the examples that will be given in this section.
So let’s get started. There are two methods to create software in Configuration Manager
- Packages
- Applications
- Packages are the older method of creating software.
- Applications are software that fully support the newer SCCM Application model.
Advantages of Applications over Packages.
- Applications – Have the ability to Supersede old software, or automatically install prerequisites. So what do you mean by supersede? For example, if you have deployed version 1604 7-zip and there is a newer version available. You can configure a new application to either uninstall the older version or just update the current version to the latest version. This is called Supersedence.
- The easiest software to deploy is the MSI version of the software, which stands for Microsoft Installer. The MSI version of software is optimized for the Application Model.
- Packages – Still have their uses, but packages can’t handle all the new functionality of the Application model. For example, packages have no supersede function.
- You can create packages from MSI’s or EXE’s
- MSI’s automatically detect a lot of the installation information right from the install file.
Such and the install and uninstall command line. Where as for the EXE, you will need to get the command line information from the vender or other sources.
Creating Applications
- First, you’ll want to create your source folder
Create a folder for each version of the software you intend to deploy
In our example, I have created a folder for version 1604 and another folder for version 1900. That way, you avoid confusion, and you have lessened the chances of making a mistake and deploying the wrong version to the client.
No comments yet. Add the first comment to start the discussion.