This is an overview of the Windows Update process from a SCCM client’s perspective through the Software Update Point (SUP). The following flow chart illustrates this general process: If a maintenance window has been defined, updates will install during that window unless the ADR overrides it or the deployment has been set to less than one hour prior to the maintenance window. Generally, if a maintenance window has not been defined, updates are installed according to the settings in the ADR. SCCM’s powerful scheduler can then be used to automatically push out updates to target clients according to Automated Deployment Rules (ADRs). Once a package is created, it is sent to one or more distribution points. SCCM also allows you to create collections of devices to be updated and to set up maintenance windows with a start date, a start and finish time, and a recurrence pattern. A Software Update Point (SUP) is a system role installed on a Windows Server Update Service (WSUS) server that allows you to create packages of updates according to various criteria. There are three primary considerations when managing the update process - the clients to be updated, the patches to be deployed and the time period when they can be deployed.

Microsoft System Center Configuration Manager (SCCM) provides tools for streamlining the deployment of software updates in Windows clients across the enterprise. IT teams recognize the importance of timely patching but can become overwhelmed by the frequency of software updates across large numbers of devices. A recent study by research firm Voke Media found that 82 percent of security breaches since 2015 occurred due to unapplied patches that had been available for up to a year. Computer Emergency Readiness Team (US-CERT) said that about 85 percent of successful security breaches involve systems that have not been patched.

Sccm 2012 past due will be installed