Packages and programs - Configuration Manager (2023)

  • Article

Applies to: Configuration Manager (current branch)

Configuration Manager continues to support packages and programs that were used in Configuration Manager 2007. A deployment that uses packages and programs might be more suitable than an application when you deploy any of the following tools or scripts:

  • Administrative tools that don't install an application on a computer
  • "One-off" scripts that don't need to be continually monitored
  • Scripts that run on a recurring schedule and can't use global evaluation


Consider using the Scripts feature in the Configuration Manager console. Scripts may be a better solution for some of the preceding scenarios instead of using packages and programs.

When you migrate packages from an earlier version of Configuration Manager, you can deploy them in your Configuration Manager hierarchy. After migration is complete, the packages appear in the Packages node in the Software Library workspace.

You can modify and deploy these packages in the same way you did by using software distribution. The Import Package from Definition Wizard remains in Configuration Manager to import legacy packages. Advertisements are converted to deployments when you migrate from Configuration Manager 2007 to a Configuration Manager hierarchy.


Use Package Conversion Manager to convert packages and programs into Configuration Manager applications. Package Conversion Manager is integrated with Configuration Manager. For more information, see Package Conversion Manager.

Packages can use some new features of Configuration Manager, including distribution point groups and monitoring. You can't deploy Microsoft Application Virtualization (App-V) applications with packages and programs in Configuration Manager. To distribute virtual applications, create them as Configuration Manager applications. For more information, see Deploy App-V virtual applications.

Create a package and program

Use the Create Package and Program wizard

  1. In the Configuration Manager console, go to the Software Library workspace, expand Application Management, and select the Packages node.

  2. In the Home tab of the ribbon, in the Create group, choose Create Package.

  3. On the Package page of the Create Package and Program Wizard, specify the following information:

    • Name: Specify a name for the package with a maximum of 50 characters.

    • Description: Specify a description for this package with a maximum of 128 characters.

    • Manufacturer (optional): Specify a manufacturer name to help you identify the package in the Configuration Manager console. This name can be a maximum of 32 characters.

    • Language (optional): Specify the language version of the package with a maximum of 32 characters.

    • Version (optional): Specify a version number for the package with a maximum of 32 characters.

    • This package contains source files: This setting indicates whether the package requires source files to be present on client devices. By default, the wizard doesn't enable this option, and Configuration Manager doesn't use distribution points for the package. When you select this option, specify the package content to distribute to distribution points.

    • Source folder: If the package contains source files, choose Browse to open the Set Source Folder dialog box, and then specify the location of the source files for the package.


      (Video) How to Create, Manage, and Deploy Applications in Microsoft SCCM | Application Deployment SCCM 2012

      The computer account of the site server must have read access permissions to the source folder that you specify.

      Windows limits the source path to 256 characters or less. This limit applies to package source as well as applications. For more information, see Naming Files, Paths, and Namespaces.

    • If you want to pre-cache content on a client, specify the Architecture and Language of the package. For more information, see Configure pre-cache content.

  4. On the Program Type page of the Create Package and Program Wizard, select the Standard program type for computers. Or you can skip this step and create a program later.


    To create a new program for an existing package, first select the package. Then, in the Home tab, in the Package group, choose Create Program to open the Create Program Wizard.

    The Program for device type is a legacy option that only applies to mobile devices, which aren't currently managed by Configuration Manager.

Custom icons for packages

Starting in version 2203, add custom icons for packages. These icons appear in Software Center when you deploy the package and program. Instead of a default icon, a custom icon can improve the user experience to better identify the software.

On the General tab of package properties, in the section for the icon, select Browse. Select an icon from the default shell library, or browse to another file in a local or network path.

  • It supports the following file types:
    • Programs (.exe)
    • Libraries (.dll)
    • Icons (.ico)
    • Images (.png, .jpeg, .jpg)
  • The file doesn't need to be on clients that you target with the deployment. Configuration Manager includes the image with the deployment policy.
  • The maximum file size for an image is 256 KB.
  • Icons can have pixel dimensions of up to 512 x 512.

When clients receive the deployment policy, they'll display the icon in Software Center.


To take full advantage of new Configuration Manager features, after you update the site, also update clients to the latest version. While new functionality appears in the Configuration Manager console when you update the site and console, the complete scenario isn't functional until the client version is also the latest.

Create a program

  1. On the Program Type page of the Create Package and Program Wizard, choose Standard Program, and then choose Next.

  2. On the Standard Program page, specify the following information:

    • Name: Specify a name for the program with a maximum of 50 characters.


      The program name must be unique within a package. After you create a program, you can't modify its name.

    • Command Line: Enter the command line to use to start this program, or choose Browse to browse to the file location.

      If you don't specify an extension for a file name, Configuration Manager attempts to use .com, .exe, and .bat as possible extensions.

      When the client runs the program, Configuration Manager searches for the file in the following locations:

      • Within the package
      • The local Windows folder
      • The local %path%

      If it can't find the file, the program fails.

    • Startup folder (optional): Specify the folder from which the program runs, up to 127 characters. This folder can be an absolute path on the client. It can also be a path that's relative to the distribution point folder that contains the package.

      (Video) Managing Software Deployment by using Packages and Programs in SCCM 2019

    • Run: Specify the mode in which the program runs on client computers. Select one of the following options:

      • Normal: The program runs in the normal mode based on system and program defaults. This mode is the default.

      • Minimized: The program runs minimized on client devices. Users might see installation activity in the notification area or on the taskbar.

      • Maximized: The program runs maximized on client devices. Users see all installation activity.

      • Hidden: The program runs hidden on client devices. Users don't see any installation activity.

    • Program can run: Specify whether the program runs only when a user is signed in, only when no user is signed in, or regardless of whether a user is signed in to the client computer.

    • Run mode: Specify whether the program runs with administrative permissions or with the permissions of the user who's currently signed in.

    • Allow users to view and interact with the program installation: Use this setting, if available, to specify whether to allow users to interact with the program installation. This option is only available if the following conditions are met:

      • Program can run setting is Only when a user is logged on or Whether or not a user is logged on
      • Run mode setting is to Run with administrative rights
    • Drive mode: Specify information about how this program runs on the network. Choose one of the following options:

      • Runs with UNC name: Specify that the program runs with a Universal Naming Convention (UNC) name. This setting is the default.

      • Requires drive letter: Specify that the program requires a drive letter to fully qualify its location. For this setting, Configuration Manager can use any available drive letter on the client. This setting requires the deployment to use the Deployment option Run program from distribution point and the package's Data Access option enabled to Copy the content in this package to a package share on distribution points.

      • Requires specific drive letter: Specify that the program requires a specific drive letter that you specify to fully qualify its location. For example, Z:. If the client is already using the specified drive letter, the program doesn't run. This setting requires the deployment to use the Deployment option Run program from distribution point and the package's Data Access option enabled to Copy the content in this package to a package share on distribution points.

    • Reconnect to distribution point at log on: Indicate whether the client reconnects to the distribution point when the user signs in. By default, the wizard doesn't enable this option.

  3. On the Requirements page of the Create Package and Program Wizard, specify the following information:

    • Run another program first: Identify a package and program that runs before this package and program runs.

    • Platform requirements: Select This program can run on any platform or This program can run only on specified platforms. Then choose the OS versions that clients must have to install this package and program.

    • Estimated disk space: Specify the amount of disk space that the program requires to run on the computer. The default setting is Unknown. If necessary, specify a whole number greater than or equal to zero. If you set a value, also select units for the value.

    • Maximum allowed run time (minutes): Specify the maximum time that you expect the program to run on the client computer. The default value is 120 minutes. Only use whole numbers greater than zero.


      If you use maintenance windows on the same collection to which you deploy this program, a conflict could occur if the Maximum allowed run time is longer than the scheduled maintenance window. If you set the maximum run time to Unknown, the program starts to run during the maintenance window. It then continues to run as needed after the maintenance window is closed. If you set the maximum run time to a specific period that's greater than the length of any available maintenance window, then the client doesn't run the program.

      If you set this value to Unknown, Configuration Manager sets the maximum allowed run time as 12 hours (720 minutes).


      If the program exceeds the maximum run time, Configuration Manager stops it if the following conditions are met:

      (Video) SCCM Training - How to Create Software Update Group and Deployment Packages in Configuration Manager

      • You enable the option to Run with administrative rights
      • You don't enable the option to Allow users to view and interact with the program installation

Deploy packages and programs

  1. In the Configuration Manager console, go to the Software Library workspace, expand Application Management, and select the Packages node.

  2. Select the package that you want to deploy. In the Home tab of the ribbon, in the Deployment group, choose Deploy.

  3. On the General page of the Deploy Software Wizard, specify the name of the package and program that you want to deploy. Select the collection to which you want to deploy the package and program, and any optional comments.

    To store the package content on the collection's default distribution point group, select the option to Use default distribution point groups associated to this collection. If you didn't associate this collection with a distribution point group, this option is unavailable.

  4. On the Content page, choose Add. Select the distribution points or distribution point groups to which you want to distribute the content for this package and program.

  5. On the Deployment Settings page, configure the following settings:

    • Purpose: Choose one of the following options:

      • Available: The user sees the published package and program in Software Center and can install it on demand.

      • Required: The package and program is deployed automatically, according to the configured schedule. In Software Center, you can track its deployment status and install it before the deadline.


      If multiple users are signed into the device, package and task sequence deployments may not appear in Software Center.

    • Send wake-up packets: If you set the deployment purpose to Required and select this option, the site first sends a wake-up packet to computers at the installation deadline time. Before you can use this option, configure computers for Wake On LAN. For more information, see How to configure Wake on LAN.

    • Allow clients on a metered Internet connection to download content after the installation deadline, which might incur additional costs


    When you deploy a package and program, the option to Pre-deploy software to the user's primary device isn't available.

  6. On the Scheduling page, configure when to deploy this package and program to client devices.

    The options on this page vary depending on whether you set the deployment action to Available or Required.

    For Required deployments, configure the rerun behavior for the program from the Rerun behavior drop-down menu. Choose from the following options:

    Rerun behaviorDescription
    Never rerun deployed programThe client won't rerun the program. This behavior happens even if the program originally failed or if the program files are changed.
    Always rerun programThe client always reruns the program when the deployment is scheduled. This behavior happens even if the program has already successfully run. It's useful with recurring deployments when you update the program.
    Rerun if failed previous attemptThe client reruns the program when the deployment is scheduled, only if it failed on the previous run attempt.
    Rerun if succeeded on previous attemptThe client reruns the program only if it previously ran successfully on the client. This behavior is useful with recurring deployments when you routinely update the program, and each update requires the previous update to be successfully installed.
  7. On the User Experience page, specify the following information:

    • Allow users to run the program independently of assignments: Users can install this software from Software Center regardless of any scheduled installation time.

    • Software installation: Allows the software to be installed outside of any configured maintenance windows.

    • System restart (if required to complete the installation): If the software installation requires a device restart to finish, allow this action to happen outside of any configured maintenance windows.

    • Embedded devices: When you deploy packages and programs to Windows Embedded devices that are write-filter-enabled, you can specify that they install packages and programs on the temporary overlay and commit changes later. Alternately, commit the changes on the installation deadline or during a maintenance window. When you commit changes on the installation deadline or during a maintenance window, a restart is required, and the changes persist on the device.

      (Video) creating a configuration manager client upgrade package in SCCM


      When you deploy a package or program to a Windows Embedded device, make sure that the device is a member of a collection that has a configured maintenance window. For more information about how maintenance windows are used when you deploy packages and programs to Windows Embedded devices, see Creating Windows Embedded applications.

  8. On the Distribution Points page, specify the following information:

    • Deployment options: Specify the action that a client when it uses a distribution point in its current boundary group. Also select the action for the client when it uses a distribution point from a neighbor boundary group or the default site boundary group.


      If you configure the deployment option to Run program from distribution point, make sure to enable the option to Copy the content in this package to a package share on distribution points on the Data Access tab of the package properties. Otherwise the package is unavailable to run from distribution points.

    • Allow clients to use distribution points from the default site boundary group: When this content isn't available from any distribution point in the current or neighbor boundary groups, enable this option to let them try distribution points in the site default boundary group.

  9. Complete the wizard.

View the deployment in the Deployments node of the Monitoring workspace and in the details pane of the package deployment tab when you select the deployment. For more information, see Monitor packages and programs.

Monitor packages and programs

To monitor package and program deployments, use the same procedures that you use to monitor applications as detailed in Monitor applications.

Packages and programs also include a number of built-in reports, which enable you to monitor information about the deployment status of packages and programs. These reports have the report category of Software Distribution - Packages and Programs and Software Distribution - Package and Program Deployment Status.

For more information about how to configure reporting in Configuration Manager, see Introduction to reporting.

Manage packages and programs

In the Software Library workspace, expand Application Management, and select the Packages node. Select the package that you want to manage, and then choose a management task.

Create Prestage Content File

Opens the Create Prestaged Content File Wizard, to create a file that contains the package content. Use this file to manually import the package to a remote distribution point. This action is useful when you have low network bandwidth between the site server and the distribution point.

Create Program

Opens the Create Program Wizard, to create a new program for this package.


Opens the Export Package Wizard, to export the selected package and its content to a file. Use this file to import the file to another hierarchy.


Opens the Deploy Software Wizard, to deploy the selected package and program to a collection. For more information, see Deploy packages and programs.

Distribute content

Opens the Distribute Content Wizard, to send the content for a package and program to selected distribution points or distribution point groups.


Opens the Import Package Wizard, to import a previously exported package from a .zip file.


When you import an object in the Configuration Manager console, it imports to the current folder. In earlier versions, Configuration Manager always put imported objects in the root node.

Update distribution points

Updates distribution points with the latest content for the selected package and program.

(Video) SCCM Microsoft Endpoint Configuration Manager for Entry Level Tech Support

Next steps

  • Scripts

  • Package Conversion Manager

  • Package definition files


What is the difference between package and program in SCCM? ›

The main difference between SCCM applications and packages is that the app workload is only one actively adding new/additional features. The SCCM application model is the workload that adds new features. Here we have Detection logic to use, which helps in detecting whether the application is already present or not.

What is SCCM packaging? ›

Application packaging in SCCM is a process where a software installation is prepared and packaged in a format that can be distributed and installed on devices within an organization. It helps to standardize and centralize software installations, making it easier to monitor and manage software versions and updates.

How do I create a package in Configuration Manager? ›

In the Configuration Manager console, go to the Software Library workspace, expand Application Management, and select the Packages node. In the Home tab of the ribbon, in the Create group, choose Create Package.

What is the difference between SCCM and MECM? ›

Theory. The System Center Configuration Manager (SCCM), now (since 2020) known as Microsoft Endpoint Configuration Manager (MECM), is a software developed by Microsoft to help system administrators manage the servers and workstations in large Active Directory environments.

What is the difference between system program and application package? ›

A System Software acts as an interface between the system and the application software. The various Operating systems are the best example as it allows the user to download and work with various applications on their device. On the other hand, Application Software is designed for users.

What is the purpose behind using a package manager to install software? ›

A package manager keeps track of what software is installed on your computer, and allows you to easily install new software, upgrade software to newer versions, or remove software that you previously installed.

What is SCCM called now? ›

SCCM has now been renamed to Microsoft Endpoint Configuration Manager and is one of several services that make up Microsoft Endpoint Manager including Device Management Admin Center (DMAC) and Desktop Analytics.

Is SCCM a deployment tool? ›

System Center Configuration Manager or SCCM is a deployment tool which can control and distribute software to desktops, servers, laptops and mobiles over a vast network. Software and updates can be remotely and silently installed on target location.

Where are SCCM packages stored? ›

What is the CCMCache Folder? The CCMCache folder is the location where the SCCM downloads all the files needed for various installations. This applies not only to applications but also to patches, task sequences, and other items. By default, this folder is set to C:\Windows\ccmcache.

How do I run SCCM Configuration Manager? ›

The simplest method to open the console on a Windows computer is to go to Start and start typing Configuration Manager console . You may not need to type the entire string for Windows to find the best match.

How do I deploy a managed package? ›

Creating and Deploying Packages in Salesforce
  1. Create the Package. ...
  2. Populate the Package with Components. ...
  3. Finalize the Package Details. ...
  4. Upload the Package to the AppExchange. ...
  5. Access your Package from the alternate Environment. ...
  6. Deploy your Package to the alternate Environment. ...
  7. Manage your Packages.

What is SCCM package for Windows 10? ›

Microsoft System Center Configuration Manager [SCCM]

Microsoft SCCM enables administrators to simplify system management for computers and other devices. It can deploy drivers and applications, manage operating system deployment, control network access, and more.

Is SCCM still being used? ›

Despite the emergence of newer tools and technologies, SCCM plays a critical role in managing and deploying software, updates, and operating systems across large-scale networks (for Server Operating Systems as well). Microsoft fully supports SCCM. Now it is part of a new product umbrella called Microsoft Intune.

Is Active Directory and SCCM the same thing? ›

Microsoft Endpoint Configuration Manager, formerly known as System Center Configuration Manager (SCCM), is a Windows-centric endpoint management tool for devices within an Active Directory domain.

Is Microsoft getting rid of SCCM? ›

Microsoft Endpoint Configuration Manager (SCCM) Version 2111 End of Life. Microsoft Endpoint Configuration Manager version 2111 will go end of life on the 1st of June, 2023. Make sure to update your installation to version 2203 or higher in order to stay fully supported.

What are the 3 types of system software? ›

The 3 types of computer software
  • System software. If you think of software as being in layers, the system software is the bottom layer: it sits between the hardware and the application software. ...
  • Utility software. ...
  • Application software.

What are the four types of system programs? ›

Types of System Software. System software is essential for a computer to function properly. And the most common types of system software are operating systems, device drivers, middleware, utilities, and programming language interpreters.

What are six types of application software packages? ›

Types of Application Software
  • Word Processing Software. ...
  • Spreadsheet Software. ...
  • Presentation Software. ...
  • Multimedia Software. ...
  • Web Browsers. ...
  • Educational Software. ...
  • Graphics Software. ...
  • Freeware.
May 26, 2023

What are the biggest advantages of using a package manager? ›

Package managers track all components of the software you install, making updates, reinstalls, and troubleshooting much easier.

What are the three biggest advantages of using a package manager? ›

Safe, secure and reliable automation of installation by sources is very tricky due to many reasons such as: Detection of whether package is already installed in hard. Ensuring existing important files are not overwritten is not easy.

What is an example of a package manager? ›

Examples of Package Managers: npm and Yarn for Javascript. Bundler for Ruby. Apache and Gradle for Java.

What is SCCM being replaced with? ›

Microsoft Intune is a cloud-based endpoint manager that includes patching capabilities. As Intune is able to perform the same tasks as SCCM, many businesses might prefer Intune over SCCM as they migrate more services to the cloud.

Is SCCM easy to learn? ›

Mastery of SCCM will make you a go-to pro in your organization. It won't be easy. They don't hand out 'superhero' badges for nothing — but there are lots of places to get trained up. First, try Microsoft Docs, where you'll find a comprehensiveIntroduction to System Center Configuration Manager.

Is SCCM still in demand? ›

The answer is yes (arguably). The only option is to keep learning new technologies like Azure AD, Microsoft Intune, Windows Autopilot, and SCCM/ConfigMgr. As I mentioned above, we still see many job openings for SCCM admins.

What database does SCCM use? ›

Note: SCCM utilizes a normalized Microsoft SQL Server (MSSQL) database (data is spread across many tables).

What is SCCM and how it works? ›

Microsoft System Center Configuration Manager (SCCM) is a Windows product that enables the management, deployment and security of devices and applications across an enterprise. Amongst other potential uses, administrators will commonly use SCCM for endpoint protection, patch management and software distribution.

Can SCCM be used for monitoring? ›

Applications in Configuration Manager support state-based monitoring, which enables you to track the last application deployment state for users and devices.

Where is SCCM on server? ›

Launch the SCCM (Configuration Manager) console. Go to Assets and Compliance\Overview\Devices. Right-click Windows Server 2022 machine and select Install Client.

How to collect software inventory in SCCM? ›

Introduction to software inventory in Configuration Manager

Software inventory is collected when you select the Enable software inventory on clients setting in client settings. You can also schedule the operation in client settings.

Where is SCCM default location? ›

The default path to find the SCCM server logs files is in your SCCM Installation Directory\Logs. If you've used the default installation directory, it will be located in C:\Program Files\Microsoft Configuration Manager\Logs. The problem is that when opening this directory, you'll find dozens of SCCM logs files.

What are SCCM tools? ›

SCCM is designed by Microsoft to help its users update their hardware and software configuration. The SCCM tools perform different activities like Inventory, troubleshooting software, software distribution configuration, etc.

How do I know if Configuration Manager is installed? ›

Go to Control Panel and select Configuration Manager. If the Configuration Manager item is not there, the SCCM client may not be installed.

Where is Configuration Manager installed? ›

The Configuration Manager console is always installed on the site server for the CAS or a primary site. To install the console separate from site server installation, run the standalone installer.

How do I create and Deploy a package in SCCM? ›

Create a new SCCM package
  1. Open the New Package wizard. Open the SCCM console. ...
  2. In the New Package Wizard, name the new SCCM package. ...
  3. Specify the data source for the SCCM package. ...
  4. Specify where the SCCM package will be stored on distribution points. ...
  5. Specify distribution settings. ...
  6. View the new SCCM package summary.
Jun 12, 2022

What is a managed package vs unmanaged package? ›

An unmanaged package keeps count of the overall limits of your Salesforce org, such as app, tab, object limits, and custom objects. Managed packages set you free by not keeping track of the total limit of tabs and custom objects of your Salesforce org.

How do I assign a managed package to a user? ›

Mass assign 'managed package' licenses with Data Loader
  1. Prepare a csv file with the following columns: User ID. Package License ID.
  2. Perform an 'Insert' operation using Data Loader on 'UserPackageLicense' object and map the columns accordingly. For more, please review Insert, Update, or Delete Data Using Data Loader.
Oct 13, 2022

How does SCCM deployment work? ›

SCCM application deployment refers to the distribution of Microsoft as well as third-party applications to client machines in the network. The deployment of applications is usually carried out from SCCM Application Management tab located under 'Overview' tab of the console.

How to deploy operating system using SCCM? ›

On Configuration Manager console, click Software Library workspace -> Operating Systems -> right-click Boot Images -> Create Boot Image using MDT. On the Package Source page of the SCCM console, under the Package source folder to be created (UNC Path): type SRV1Sources$OSDBootZero Touch WinPE x64, and then click Next.

What is the advantage of SCCM? ›

With SCCM, it has become easy to maintain the computer system's integrity as it lets you discover software vulnerabilities, distribute the latest security updates, and regulate the installation without consuming much time.

What is the old name of SCCM? ›

Product branding and naming

In 2007, System Management Service (SMS) became System Center Configuration Manager (SCCM).

What is replacing Intune? ›

The rebranding Intune as Endpoint Manager initially caused some confusion because of the tools' overlap. However, companies that use Endpoint Manager now understand the full suite of capabilities available to them, said Dan Wilson, senior director analyst at Gartner.

Is Microsoft replacing WSUS? ›

The changes, which would replace WSUS and are part of an effort by Microsoft to pull IT to the cloud, are due out by the end of June.

What is Active Directory called now? ›

The main Active Directory service is Active Directory Domain Services (AD DS), which is part of the Windows Server operating system. The servers that run AD DS are called domain controllers (DCs).

Can you use SCCM without Active Directory? ›

No, not for use with ConfigMgr. ConfigMgr requires AD. the workstations (for example) that will be ConfigMgr clients do not *have* to be domain members (but it's much easier if they are). The ConfigMgr site servers *do* need to be AD domain members.

What are the two types of Active Directory? ›

Active Directory has two types of groups:
  • Security groups: Use to assign permissions to shared resources.
  • Distribution groups: Use to create email distribution lists.
Apr 10, 2023

What is end of life for SCCM? ›

Microsoft Endpoint Configuration Manager (SCCM) end of life version 2107. Microsoft Endpoint Configuration Manager version 2107 will go end of life on February 2, 2023. To ensure that your SCCM version is fully supported, you are advised to upgrade to version 2111 or higher.

Can SCCM run on Windows 10? ›

SCCM Version

You need at least SCCM 2207 in order to support it as a Windows 10 client. See the following support matrix if you're running an outdated SCCM version and make sure to update your site.

Is SCCM part of Office 365? ›

Deployment and Scheduling options for Office 365 ProPlus Microsoft 365 Apps using SCCM. Deployment options/settings are also part of Office 365 Client Installation Wizard.

What is the difference between a package and module and function? ›

A Python package defines the code as a separate unit for each function when using a library. While the modules themselves are a distinct library with built-in functionality, the advantage of packages over modules is their reusability. So this is the difference between a module and a package in Python.

Is application package the same as application software? ›

Application Software is a program that does real work for the user. It is mostly created to perform a specific task for a user. Application Software acts as a mediator between the end-user and System Software. It is also known as an application package.

What is the difference between deploy and distribute in SCCM? ›

In SCCM there are no difference between distribution and deployment, they both mean to distribute/deploy software (operating system, software update, etc.) to clients.

What is the difference between module and package? ›

In simple terms, a module is a single file containing python code, whereas a package is a collection of modules that are organized in a directory hierarchy.

What is the difference between framework and module? ›

The difference between a framework and other kinds of modules in a program is that the former emphasizes a mostly complete, freezed but adaptive and extensible solution of some common work, so the user of the framework can focus on the domain-specific and project-specific problems instead of writing glue code to put ...

What is the difference between __ init __ and __ main __? › , among other things, labels a directory as a python directory and lets you set variables on a package wide level. , among other things, is run if you try to run a compressed group of python files. allows you to execute packages.

What is the difference between a module package and script? ›

Scripts are runnable Python programs that do something when executed. Modules are Python files that are intended to be imported into scripts and other modules so that their defined members—like classes and functions—can be used. 04:41 Packages are a collection of related modules that aim to achieve a common goal.

What are the 4 types of application package? ›

Some of the commonly used application software include:
  • Word Processing Software.
  • Graphics Software.
  • Spreadsheet Software.
  • Presentation Software.
  • Web Browsers.

What are 5 example of application packages? ›

A collection of Microsoft software including MS Office, PowerPoint, Word, Excel, and Outlook. Common Internet browsers like Google Chrome, Safari, Firefox, etc. Graphics and designing software such as Canva, Adobe Photoshop, CorelDraw, and AutoCAD.

What is the difference between deployment and provisioning? ›

Provisioning and deployment: A lot of the time, people who work in or around IT use the two terms interchangeably. But they don't mean the same thing. At a high level, provisioning is the act of getting a device ready for a user. Deployment is the whole process of getting a device to a user.

What is package example? ›

A package is simply a container that groups related types (Java classes, interfaces, enumerations, and annotations). For example, in core Java, the ResultSet interface belongs to the java. sql package. The package contains all the related types that are needed for the SQL query and database connection.

What is the difference between module and interface? ›

A module is used to specify the functionality of the logic. For example if you are building a counter you would use a module to define the functionality (up behavior/down behavior/reset behavior) of the counter. An interface as the name suggests is used to specify the interface behaviour.

Why is it called a module? ›

Why are they called modules? We call them modules because they're, well, modular. This means that a module can function as a standalone class or be combined with other modules to build courses and earn degrees, certificates, and diplomas.


1. How to create SCCM package - PowerShell Script
(Carson Cloud)
2. SCCM Tutorial 21- How to Create Package, Program and Deployment | Deep Dive
(Harvansh Singh)
3. SCCM Microsoft Endpoint Configuration Manager Application Configuration and Deployment
4. Managing Microsoft 365 Apps using Microsoft Configuration Manager
(Microsoft 365 Apps Deployment Insiders)
5. Deploying Office with Configuration Manager
(Microsoft Mechanics)
6. Packages - Application Deployment Part 2


Top Articles
Latest Posts
Article information

Author: Carmelo Roob

Last Updated: 02/11/2023

Views: 5914

Rating: 4.4 / 5 (45 voted)

Reviews: 92% of readers found this page helpful

Author information

Name: Carmelo Roob

Birthday: 1995-01-09

Address: Apt. 915 481 Sipes Cliff, New Gonzalobury, CO 80176

Phone: +6773780339780

Job: Sales Executive

Hobby: Gaming, Jogging, Rugby, Video gaming, Handball, Ice skating, Web surfing

Introduction: My name is Carmelo Roob, I am a modern, handsome, delightful, comfortable, attractive, vast, good person who loves writing and wants to share my knowledge and understanding with you.