Create a Package in SCCM: The Ultimate Step-by-Step Guide

Creating a package in SCCM is the foundational step for distributing software to your endpoints. This initial action involves gathering the application files and establishing the command line necessary for execution, without necessarily defining the full deployment logic. A package serves as a container for the content and programs you want to distribute, acting as the source files that the Distribution Points will share.

Understanding the Core Concepts

Before diving into the creation process, it is essential to understand the distinction between a package and a program. The package holds the actual installer files, while the program defines how to run the installation, including the command line and requirements. Grasping this separation clarifies why you configure specific settings at each stage of the workflow.

Accessing the SCCM Console

Begin by launching the Configuration Manager console on your administrative workstation and connecting to your primary site. Navigate to the Software Library workspace, expand the Application Management node, and select the Packages node. This location is where all existing packages are managed and where you will initiate the new one.

Initiating the Creation Wizard

To start, right-click the Packages node and choose "Create Package" from the context menu. This action opens the Create Package Wizard, which guides you through the necessary steps. The first screen typically asks you to specify a name and an optional description to identify the package later.

Configuring Package Data and Security

On the Data Source page, you must point the wizard to the folder containing your application files. You can browse to the local drive or enter a UNC path. If the content is already on a distribution point, you can reference it directly to speed up the process. Additionally, on the Security page, you define the security role for administrators who need access to the package properties.

Defining the Program Command

Perhaps the most critical step is entering the command line. This text dictates how the software installs silently or with specific parameters. For instance, an MSI might use `msiexec /i app.msi /qn`, while an executable might use `setup.exe /silent`. Testing this command locally ensures the package will function correctly in the distributed environment.

Finalizing and Distribution

After configuring the program, you confirm the settings and complete the wizard. At this stage, the package exists in the database but the content is not yet on distribution points. You must manually right-click the package and select "Distribute Content" to share the files with your network. Once distributed, you can integrate the package into a Task Sequence for full operating system deployment or assign it directly for user-based installations.