Applies to: Configuration Manager (current branch)
State messages contain concise information about conditions on the Configuration Manager client. The state messaging system is used by specific components of Configuration Manager, such as software updates and configuration settings.
Configuration Manager clients send state messages to the fallback status point or the management point to report the current state of operations. You can create reports to view state messages sent by clients.
Each Configuration Manager feature that uses state messages is identified by the topic type of the state message. The state message topic types listed in this article can be used to define the Configuration Manager feature that a state message relates to.
Note
A state message ID value of zero (0) typically indicates that the topic type is in an unknown state.
Software updates
300 STATE_TOPICTYPE_SUM_ASSIGNMENT_COMPLIANCE
State message ID
State message description
1
Compliant
2
Non-compliant
301 STATE_TOPICTYPE_SUM_ASSIGNMENT_ENFORCEMENT
State message ID
State message description
1
Installing updates
2
Waiting for restart
3
Waiting for another installation to complete
4
Successfully installed updates
5
Pending system restart
6
Failed to install the updates
7
Downloading the updates
8
Downloaded updates
9
Failed to download updates
10
Waiting for the maintenance window before installing
11
Waiting for orchestration
12
Waiting for superseding update
302 STATE_TOPICTYPE_SUM_ASSIGNMENT_EVALUATION
State message ID
State message description
1
Evaluation activated
2
Evaluation succeeded
3
Evaluation failed
400 STATE_TOPICTYPE_SUM_CI_DETECTION
State message ID
State message description
1
Not required
2
Not detected
3
Detected
401 STATE_TOPICTYPE_SUM_CI_COMPLIANCE
State message ID
State message description
1
Compliant
2
Non-compliant
3
Conflict detected
4
Error
5
Unknown
6
Partial compliance
7
Compliance not configured
402 STATE_TOPICTYPE_SUM_CI_ENFORCEMENT
State message ID
State message description
1
Enforcement started
2
Enforcement waiting for content
3
Waiting for another installation to complete
4
Waiting for the maintenance window before installing
5
Restart required before installing
6
General failure
7
Pending installation
8
Installing update
9
Pending system restart
10
Successfully installed update
11
Failed to install the update
12
Downloading update
13
Downloaded update
14
Failed to download the update
500 STATE_TOPICTYPE_SUM_UPDATE_DETECTION
State message ID
State message description
1
Update isn't required
2
Update is required
3
Update is installed
501 STATE_TOPICTYPE_SUM_UPDATE_SOURCE_SCAN
State message ID
State message description
1
Scan is waiting for content
2
Scan is running
3
Scan complete
4
Scan is pending retry
5
Scan failed
6
Scan completed with errors
Client deployment
The following topic types have no state IDs:
Topic type
Description
700
STATE_TOPICTYPE_RESYNC_STATE_MSG
701
STATE_TOPICTYPE_SYSTEM_HEARTBEAT
702
STATE_TOPICTYPE_CKD_UPDATE
801
STATE_TOPICTYPE_DEVICE_CLIENT_DEPLOYMENT
800 STATE_TOPICTYPE_CLIENT_DEPLOYMENT
State message ID
State message description
100
Client deployment started
101
Waiting for download
102
Deployment Scheduled
103
Waiting for the window before deploying
104
Deployment skipped
301
Unknown client deployment failure
302
Failed to create the ccmsetup service
303
Failed to delete the ccmsetup service
304
Can't install over embedded OS with File-Based Write Filter (FBWF) enabled on the system drive
305
Native security mode isn't valid on Windows 2000
306
Failed to start ccmsetup download process
307
Non-valid ccmsetup command line
308
Failed to download the file over WINHTTP at address
309
Failed to download the files through BITS at address
310
Failed to install BITS version
311
Can't verify that prerequisite file is MS signed
312
Failed to copy the file because the disk is full
313
Client.msi installation failed with MSI error
314
Failed to load ccmsetup.xml manifest file
315
Failed to obtain a client certificate
316
Prerequisite file isn't MS signed
317
Reboot required to continue the installation
318
Can't install the client on the MP because the MP and client versions do not match
319
Operating system or service pack not supported
320
Deployment not supported
321
Bits Missing
322
Source folder is unavailable
323
App-V not supported
324
Incorrect Site Version
325
Prerequisite hash mismatch
326
MDM Deregistration Failed
327
MDM Registration Detected
328
Intune Detected
329
Metered Network Disallowed
400
Client deployment succeeded
401
Deployment Succeeded Reboot Required
402
Deployment Succeeded Reboot Succeeded
500
Client assignment started
601
Unknown client assignment failure
602
The following site code is invalid
603
Failed to assign to MP
604
Failed to discover default management point
605
Failed to download site signing certificate
606
Failed to auto discover site code
607
Site assignment failed; client version higher than site version
608
Failed to get Site Version from Active Directory Domain Services and SLP
609
Failed to get client version
700
Client assignment succeeded
810 STATE_TOPICTYPE_CLIENT_COMANAGEMENT
State message ID
State message description
100
Enrollment status
101
Enrollment scheduled
102
Enrollment canceled
105
Enrollment started
106
Enrollment succeeded but isn't provisioned
107
Enrollment succeeded and is provisioned
108
Enrollment no active user
110
Enrollment failed
820 STATE_TOPICTYPE_CLIENT_WUFB
State message ID
State message description
1
Windows Update for Business client status
Content
The following topic types have no state IDs:
Topic type
Description
901
STATE_TOPICTYPE_REMOTE_DP_MONITORING
902
STATE_TOPICTYPE_PULL_DP_MONITORING
903
STATE_TOPICTYPE_DP_USAGE
900 STATE_TOPICTYPE_BRANCH_DP
State message ID
State message description
1
Disk Space
Client operations
1000 STATE_TOPICTYPE_CLIENT_FRAMEWORK_COMM
State message ID
State message description
1
Client is successfully communicating with the management point
2
Client failed to communicate with the management point
1001 STATE_TOPICTYPE_CLIENT_FRAMEWORK_LOCAL
State message ID
State message description
1
Client successfully retrieved the certificate from the local certificate store
2
Client failed to retrieve the certificate from the local certificate store