Shulou(Shulou.com)06/02 Report--

Software updates-Update deployment

This article mainly discusses the related contents of ConfigMgr software update deployment.

Status scanning

The client evaluates its update status based on the update metadata provided by SUP and generates a state for each update metadata (installed, not installed, not applicable, etc.)

Mandatory scan type: this type of scan indicates that the client actually performs an unforced scan: if the last synchronization "update metadata" does not exceed 24 hours, then the scan action triggered within these 24 hours will not actually take place. If it exceeds 24 hours, conduct a status scan online scan: indicates that the client will check the updated metadata version on the SUP and synchronize it to the local cache. If the local cache version is the same as the metadata version on SUP Then scan offline using locally cached version: directly use locally cached update metadata to scan the scene corresponding to the scan type online scan forced scanning by the software update scan cycle in the client settings whether triggered by the ConfigMgr client action page is triggered by the re-evaluation update deployment cycle in the client settings before downloading the update content Whether it is an update deployment after the system restart triggered by the installation update before installing the update

The software update deployment mechanism is consistent with the deployment of applications and packages, which is carried out through the client pulling policies from the management point and downloading content from the distribution point.

The basic unit of update deployment is that the actual content of a single update or update group (Update Group) update is organized by the way of "deployment package (Deployment Package)". If the deployment package contains multiple update files, the client can download the contents of the deployment package as needed. An update deployment contains up to 1000 update deployments as well as applications and packages. There is a "maximum allowable running time (Maximum Runtime)". For a software update deployment, the maximum allowable runtime for all updates in this deployment and the automatic deployment rule (Automatic Deployment Rules)

Like automatic approval of WSUS, SUP automates the deployment and distribution of updates through ADR

You can set when ADR runs after software update point synchronization and filters updates for automatic deployment based on multiple criteria in a specified time period. ADR deployment can only be based on update groups. Only after ADR runs, SCCM actually downloads qualified update files to local deployment packages. ADR runs based on site server computer accounts to download update files.

It is the original intention of this series of articles to refine the basic knowledge, precautions, operating mechanism and troubleshooting methods involved in SCCM for readers. There are already many articles in the network to refer to the information on the various components and functional deployment steps of SCCM, so this series of articles do not focus on providing deployment guides similar to Step-by-Step, please forgive me. At the same time, due to the limitations of personal ability and knowledge, there are inevitably some mistakes and mistakes in the article. I hope you can correct them. Thank you very much.

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.