# "SCCM Management-package and Application deployment Assessment

Deployment assessment

This article focuses on the evaluation process for ConfigMgr packages and applications when deployed

When the client receives the package or application deployment information from the Management Point, it adds the corresponding deployment information to its own computer or user policy, and immediately evaluates the deployment.

For an introduction to applications and packages, see blog.51cto.com/nodium/2154964

application

For application deployment, ConfigMgr client makes decisions based on these elements because the application itself contains Detection Method and Requirement elements

Requirements: Requirements are used to determine whether the current client meets various conditions defined by the administrator to install this program. If the requirements are not met, the client determines that this application program is not suitable for this device.

If the deployment action is Unload, the client does not evaluate the Requirements element

Requirements can be OS version, OS language, CPU frequency, memory size, disk space, Active Directory site, ConfigMgr site, OU location, primary user device, etc.

Detection method: The application is "stateful". The detection method is used to determine whether the client has installed this application. If the deployment action is:

Installation: No installation is required for devices with applications installed: Uninstall is performed for devices with applications installed

Detection methods can be judged by MSI, registry, folder, script form, administrator can set according to actual needs

Dependency: If the application contains other dependent applications, ConfigMgr client will evaluate the dependent applications. If the client lacks relevant dependencies, ConfigMgr can automatically install the corresponding dependent programs.

Dependency is judged by taking dependency groups as units. If the application programs in any dependency group are judged to be installed, it is judged that the dependency group is satisfied. The relationship between multiple dependency groups is "and", that is, it is judged that the dependency conditions are satisfied only if all dependency groups are satisfied.

Substitute program: If the application contains a substitute program, it will also determine whether the source program exists in the current device according to the above logic during deployment, and then you can choose whether to uninstall it automatically.

package

Package evaluation mainly includes "Re-run" factor, ConfigMgr will remember the running records and results of programs contained in the package, so it will evaluate based on this result

Rerun no longer runs deployed programs: does not run when a previous program has already run Always reruns programs: always reruns the current deployment regardless of whether the previous program has run Rerun when the previous program deployment failed Rerun: runs the current deployment only when the previous program has failed Rerun when the previous program has successfully deployed: runs the current deployment only when the previous program has successfully run When to download content

When Deployment Information is received and available by ConfigMgr clients, based on the purpose of the deployment:

If required deployment: downloads all required content first in the background If available deployment: downloads only start when user clicks Install When to execute

When ConfigMgr evaluates the application or package to be executed, ConfigMgr will comprehensively evaluate when to run the deployment according to the "User Experience" in the deployment information, the "Maintenance Window" of the collection, and the "Working Time" set by the user. For details, see:

https://blog.51cto.com/nodium/2351087

https://blog.51cto.com/nodium/2351124

The original intention of this series of articles is to extract the basic knowledge, precautions, operation mechanism and troubleshooting methods involved in SCCM for readers. There are many articles in the network that can be referenced for information on various components and function deployment steps of SCCM. Therefore, this series of articles does not focus on providing deployment guidelines similar to Step-by-Step. Please forgive me. At the same time, due to the limitations of personal ability and knowledge level, there are inevitably flaws and mistakes in the text, but also hope that everyone can correct, thank you very much.