System Center 2012 Configuration Manager Unleashed

Compliance Scanning

Each system is responsible for scanning itself and reporting the results to ConfigMgr. The ConfigMgr agent initiates the actual compliance scanning, which is performed by the WUA at various times throughout the software update lifecycle, shown in Table 14.5. Clients use the metadata retrieved from their active software update point to perform compliance scanning. When retrieved, this update metadata is cached by the WUA for future use. The scan types in Table 14.5 are defined as follows:

• Forced Scan: A scan always occurs.

• Unforced Scan: Scan occurs only if the locally cached copy of the metadata is more than 24 hours old. This is called the time to live (TTL) of the update metadata and refers to how long a cached copy ...