Shulou(Shulou.com)05/31 Report--

How to analyze packages and applications in SCCM management? I believe many inexperienced people don't know what to do about it. Therefore, this article summarizes the causes and solutions of the problem. Through this article, I hope you can solve this problem.

SCCM packages and applications

The following mainly discusses the concepts of Package and program in ConfigMgr

Bag

Package is a logical concept in ConfigMgr, which is mainly used to meet the deployment and management needs of enterprises, such as installing software to the client and executing specific programs. The package is mainly composed of the following elements:

Basic information: name, version, developer, language, etc.

Programs: see below. A package can contain multiple programs or no programs at all.

Source file: defines the file location to be used when executing the program

program

A program is a logical concept that defines how the client executes the software program to be installed, including the following main definitions:

Command line: defines how the ConfigMgr client handles the source files in the package

Start with: define the execution location of the command line, if not specified, the default execution starts from the location of the source file in the package

Maximum allowed run time: tells the ConfigMgr client to specify the maximum time allowed to run a command on the command line

When the actual time for the client to run the command specified on the command line exceeds the defined time, the client does not actually stop running the command, but does not wait for the return result of the command line run and thinks that the command line operation has failed

Operation mode: defines whether to run the command line with the permissions of the currently logged in user or the system account

Deployment

The basic unit of package deployment is the program, that is, if the package contains multiple programs, we must explicitly specify a program to be deployed to the client.

Application program

Application is a new model introduced by ConfigMgr 2012, which is different from the concept of package. It mainly simplifies and reduces the difficulty of distributing programs to clients.

The application is a container that contains the following main information:

Basic information: name, developer, version, etc.

Application directory information: contains information that users see this program on the application directory site, such as language, localized name, classification, description, keywords, etc.

Replacement: if this application replaces another application (possibly an older version of the program), you can define to uninstall the replaced application before installing it

Deployment type: see below, an application can contain multiple deployment types

Deployment Typ

The deployment type contains the following definitions:

Basic information: description of this deployment type

Content: define the source file location required for this deployment type

Program: define the command line that is invoked when installing and uninstalling this deployment type

Detection method: the decision logic that defines whether this application already exists on the target computer

The detection method can be determined by folder, file, script, registry, etc.

User experience: define whether to install this deployment type with the system or currently logged in user credentials

Requirements: used to define the specific conditions that the client needs to meet before the deployment type is installed, such as operating system version, CPU frequency, disk space size, memory size, Active Directory site, etc.

Dependency: used to define whether this deployment type depends on other applications. If there is a dependency, ConfigMgr will install the dependent application before installing this application.

Deployment

The basic unit of application deployment is the application itself. if an application contains multiple deployment types, the client evaluates the requirements defined in the deployment type sequentially and runs this deployment type once the requirements in a deployment type are met.

The difference between packages and applications

Based on the deployment characteristics of the application, we can see that the application model is suitable for the deployment of cross-platform programs. For example, we can define an application, such as Office 2016, and add three types of deployment types to it:

Windows 10

IOS

Android

The application simplifies the difficulty for the administrator to deploy the program to the client, because the application model itself already contains definition information such as detection methods, requirements, dependencies, and so on. If the package is to achieve the same effect, it must be determined by specifying a script on the command line, and the difference in difficulty is self-evident.

Since the package itself does not have a mechanism to detect whether the program is installed (the application is defined by the detection method), it is suitable for the client to run commands that have no specific requirements for its own state. for example, regularly copy some specific files to the client, clean up some files on the client, registry, and so on.

After reading the above, have you mastered how to analyze packages and applications in SCCM management? If you want to learn more skills or want to know more about it, you are welcome to follow the industry information channel, thank you for reading!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.