ConfigMgr Software Updates Scan Cycle Client Action | SCCM

Let’s understand the ConfigMgr Client Action called Software Updates Scan Cycle in a bit more detail. The users/admins can initiate the Software Update (a.k.a patching) scan cycle to speed up the troubleshooting of patching related scenarios.

I have explained about Software Updates Deployment & Evaluation Cycle in the previous post. But, it’s also important to understand ConfigMgr Client Component Status details for troubleshooting. There are three different status details are available for each component of the client. Those are installed, disabled, and enabled.

I have seen many admins getting confused between ConfigMgr Client App and SCCM Software Center. Both are different and client actions are available with ConfigMgr Client App (a.k.a Configuration Manager Application) available in the control panel.

TL;DR

Software Updates Scan Cycle

Patch My PC
Advt

There are 8 (eight) client actions available in Configuration Manager client application properties as of ConfigMgr 2010 version. The Software Updates Scan Cycle client action is the Sixth (6th) one from the top.

Navigate to:

  • You can launch the client app from any computer that has an SCCM client installed.
  • Open Command Prompt
  • Run the following command – Control smscfgrc
  • Click on the Actions tab
  • Select Software Updates Scan Cycle
  • Click on OK from the Software Updates Scan Cycle popup window
ConfigMgr Software Updates Scan Cycle Client Action | SCCM
ConfigMgr Software Updates Scan Cycle Client Action | SCCM

Background Processes

Let’s understand the Software Updates scan cycle via log files. When you initiate this action from the ConfigMgr client app, you can see the Scan agent and other components are triggered. The default Software update deployment evaluation cycle can be configured on Client settings.

This SCCM client action Software Update scan cycle “immediately” triggers the patching process from Windows 10 client. As per my quick analysis of three components:

  • Scan agent
  • Location Services Agent
  • Status Agent
  • Update Store Agent

These components help to process the software updates scanning cycle and perform a full scan as you can see below. This scan is performed against all the patch deployments assigned to a particular Windows 10 client. The processes are shown in the following log snippets.

The update store component that stores the details about compliance status for each software updates (a.k.a patches) assigned to Windows 10 computer.

ConfigMgr Software Updates Scan Cycle Client Action | SCCM
ConfigMgr Software Updates Scan Cycle Client Action | SCCM
  • ScanAgent.log (Full Scan is performed)
    • UpdateSourceMessage MessageType=’ScanByUpdateSource
    • *ScanByUpdateSource request received with ForceReScan=2, ScanOptions=0x0000000a, WSUSLocationTimeout = 604800
    • Sources are current and valid. TTLs are also valid.
    • ScanJob({4DCD2800-5C1E-4BEE-A0BE-EE0128B4AAD2}): – – – – – -Locations requested for ScanJobID={4DCD2800-5C1E-4BEE-A0BE-EE0128B4AAD2} (LocationRequestID={864C949C-A18D-4869-9429-E64664397DCD}), will process the scan request once locations are available.
    • WSUSLocationUpdate received for location request guid={864C949C-A18D-4869-9429-E64664397DCD}
    • CScanJobMgr::UpdateSUPLocationList– Original WUA location count is 0, new location count is 1, WUA locations updated.
    • ScanJob({4DCD2800-5C1E-4BEE-A0BE-EE0128B4AAD2}): Performing Full Scan.
    • ScanJob({4DCD2800-5C1E-4BEE-A0BE-EE0128B4AAD2}): Scan Succeeded, Resetting Source to Current and TTLs to Valid
    • ScanJob({4DCD2800-5C1E-4BEE-A0BE-EE0128B4AAD2}): CScanJob::OnScanComplete – Scan completed successfully, ScanType=1
    • ScanJob({4DCD2800-5C1E-4BEE-A0BE-EE0128B4AAD2}): CScanJobManager::OnScanComplete –ScanJob is completed.
    • ScanJob({4DCD2800-5C1E-4BEE-A0BE-EE0128B4AAD2}): CScanJobManager::OnScanComplete – Reporting Scan request complete to clients…
    • Calling back to client on Scan request complete…
    • CScanAgent::ScanComplete- Scan completion received.
ConfigMgr Software Updates Scan Cycle Client Action | SCCM
ConfigMgr Software Updates Scan Cycle Client Action | SCCM
1E Nomad
Advt
  • LocationServices.log (Helps to find the WSUS servers)
    • Executing Task LSRefreshLocationsTask
    • Current AD site of machine is Default-First-Site-Name
    • WSUSLocationRequest : WSUSLocationRequest SchemaVersion
    • Created and Sent Location Request ‘{864C949C-A18D-4869-9429-E64664397DCD}’ for package {1074285A-82C7-474F-B242-1EE20F8C3CE5}
    • ConfigMgr is no longer managing WindowsDO GPO. Set to default values. Mode = LAN. GroupID = empty
    • Calling back with the following WSUS locations
    • WSUS Path=’http://CMMEMCM.MEMCM.COM:8530′, Server=’CMMEMCM.MEMCM.COM’, Version=’24’, LocalityEx=’BOUNDARYGROUP’, SUPFallbackIn=’0′
ConfigMgr Software Update Scan Cycle Client Action | SCCM
ConfigMgr Software Updates Scan Cycle Client Action | SCCM
  • StatusAgent.log (Probably scan event is raised through this component)
    • Raising event (#1 of 1): instance of CCM_CcmHttp_Status
    • Successfully raised 1 event(s)
    • Event forwarder SmsClientEventForwarder:Instance0 received 1 events
    • [8E42E0F0] Handling 1 events
    • [8E42E0F0] Handling event class CCM_CcmHttp_Status
    • Updating MDM_ConfigSetting.ClientHealthStatus with value 7
    • Event forwarder SmsClientEventForwarder:Instance0 successfully handled 1 events
ConfigMgr Software Updates Scan Cycle Client Action | SCCM
ConfigMgr Software Updates Scan Cycle Client Action | SCCM
  • UpdatesStore.log (Check each of the Software update deployments assigned to Windows 10 device)
    • Update status from update (075e46dd-7c09-4263-93d1-20f851ca76dd) already exists, will modify existing instance.
    • Update status from update (fca5309d-365d-4e9e-a7a0-d4129bac0914) already exists, will modify existing instance.
    • Successfully done with SetStatus() operation.
ConfigMgr Software Updates Scan Cycle Client Action | SCCM
ConfigMgr Software Updates Scan Cycle Client Action | SCCM

Logs

The following are the log files that recorded few entries when I triggered the Software Updates Scan Cycle. More details about SCCM clients logs are available here.

  • ScanAgent.log
  • LocationServices.log
  • StatusAgent.log
  • UpdatesStore.log

Resources

Sharing is caring!

Leave a Comment

This site uses Akismet to reduce spam. Learn how your comment data is processed.