Information Technology Reference
In-Depth Information
compliance scan. The client returns a list that reflects the compliance state for every
update evaluated.
3. If configured, WSUS stores the scan results in the WSUS database. This setting is not
enabled by default.
4. The client stores the compliance scan results in Windows Management
Instrumentation (WMI) and then sends the results as a batch to the management
point as state messages. The client then sends the state messages to the management
point in bulk every 15 minutes by default.
5. The management point sends the results to the site server, which then enters them in
the site database.
6. You can view the compliance scan results by using the Configuration Manager console
or by using reports in categories such as the Software Updates - D Scan category and
Software Updates - A Compliance category.
Compliance states
When a client computer performs a deployment evaluation for software updates,
Configuration Manager creates a state message that contains the software update's com-
pliance state for each update that it is evaluating. Configuration Manager then sends state
messages to the site server through the management point, which then inserts them in the
site database. A database summarization process occurs, which summarizes the results into
specific compliance states. For each update, the Configuration Manager console displays the
number of client computers in each compliance state.
Compliance states are as follows:
Required The software update is applicable to and required on the client computer.
The site server also might report this state for three scenarios:
If the software update is deployed but not installed
If the state messages have not been received on the site server
If the update requires a computer restart before it completes
The software update has installed on the computer.
Installed
The software update is not applicable to the client computer.
Not Required
Unknown The site server has not received any information about the specific update
from the client computer. The site server might report this state for three scenarios:
The client computer's compliance scan has not been reported.
The scan was not successful.
The scan was successful, but the state message has not been processed at the site
server due to a backlog state or a corrupt state message file.
 
Search WWH ::




Custom Search