Body
Objective
There are two types of software that can be deployed using Microsoft Configuration Manager (SCCM); an Application and a Package. While they are indistinguishable to the average user, SCCM performs different processes for creating and deploying applications and packages. Understanding the differences between them will make the process of troubleshooting software considerably faster and easier. This article will provide a general overview of the similarities and differences between an Application and a Package within the SCCM admin console.
In this article:
Audience
This article is intended for IT Support technicians who have completed the Enterprise Endpoint Management Level 2 - Endpoint Administrator training course.
Applications
What is an Application?
- Applications install programs based on the client's system requirements.
- Application file types are Windows Installer Package (
.msi), Windows App (.appx/.msix), or Web Application (no filetype suffix).
- Applications utilize detection methods and dependencies during installation to monitor progress.
Applications Are Good For...
- Installing programs on a wide variety of systems.
- Software that uses product codes or license keys.
- Reliable software version reporting.
- Software using
.msi files to install.
- Self-contained, pre-configured installation.
Packages
What is a Package?
- Packages install programs using a What You See Is What You Get (WYSIWYG) style. The entire folder of a package is copied onto a client machine before running.
- Package file types are Windows Executable (
.exe), scripts (.ps1, .vbs), or Batch files (.bat).
- Packages cannot be created from Windows App installers.
- Packages do not perform detection or progress monitoring. If the file successfully executes, the installation is considered successful, regardless of the program's actual installation status.
Packages Are Good For...
- Installations that require additional arguments.
- Software that uses configuration files (
.ini, .config, .properties file types).
- Software that uses .NET Framework or other prerequisites.
- Software with infrequent updates.
- Executing scripts or configuration items.
- Anything that doesn’t want to install as an application.
- System/hardware drivers.
Converting Packages Into Applications
Packages can be converted into Applications if sufficient information is applied to it. Packages can be checked using the Analyze Package option, which will determine if a Package:
- CAN be converted without additional info (Automatic)
- CAN be converted after supplying additional info (Manual)
- CANNOT be converted (Not Applicable)
The Readiness column in the Packages view will display these results.
Package Conversion
The option Fix and Convert provides information regarding what information needs to be added to a Package to successfully convert it. Typically, this will be providing a detection method, which tells SCCM where to look to determine if an application is already installed.
Most applications use their Global Unique Identifier (GUID) (example: {DE0D08B4-C35B-4407-918F-19742B978117}). Other methods include using a Registry Key associated with the application or a specific version number of the application's executable file.
Creating a detection method by using a file/folder's existence is not recommended as it can be easy to fool the client if a file or folder is renamed to something that the application uses for detection.