State messages are sent by Configuration Manager 2007 clients to fallback status point or management point site systems to report the current state of Configuration Manager 2007 client operations. Reports can be created and used to view state messages sent by Configuration Manager 2007 clients.
Each Configuration Manager 2007 feature that uses state messages is identified by the topic type of the state message. The state message topic types listed in the following table can be used to define the Configuration Manager 2007 feature that a state message relates to.
Topic Type | Description |
---|---|
200 |
NAP |
300 |
SUM_ASSIGNMENT_COMPLIANCE |
301 |
SUM_ASSIGNMENT_ENFORCEMENT |
302 |
SUM_ASSIGNMENT_EVALUATION |
400 |
SUM_CI_DETECTION |
401 |
SUM_CI_COMPLIANCE |
402 |
SUM_CI_ENFORCEMENT |
500 |
SUM_UPDATE_DETECTION |
501 |
SUM_UPDATE_SOURCE_SCAN |
700 |
RESYNC_STATE_MSG |
701 |
SYSTEM_HEARTBEAT |
702 |
DDM ClientKeyData change |
800 |
CLIENT_DEPLOYMENT |
900 |
BRANCH_DP |
1000 |
CLIENT_FRAMEWORK_COMM |
1001 |
CLIENT_FRAMEWORK_LOCAL |
1002 |
DEVICE_CLIENT_FRAMEWORK_COMM |
1003 |
DEVICE_CLIENT_FRAMEWORK_LOCAL |
1004 |
DEVICE_CLIENT_FRAMEWORK_CERTIFICATE |
1100 |
CLIENT_FRAMEWORK_MODEREADINESS |
1500 |
CAL_TRACK_UT |
1501 |
CAL_TRACK_UL |
1502 |
CAL_TRACK_MT |
1503 |
CAL_TRACK_ML |
State Messages Sent by Configuration Manager Clients
The following table lists the ID number and description for state messages sent by Configuration Manager clients. State message IDs are used to define specific state messages for each topic type. The state message description describes the state message sent by clients.
Topic Type | State Message ID | State Message Description |
---|---|---|
300 |
0 |
Compliance state unknown |
300 |
1 |
Compliant |
300 |
2 |
Non-compliant |
300 |
3 |
Conflict detected |
301 |
0 |
Enforcement state unknown |
301 |
1 |
Installing update(s) |
301 |
2 |
Waiting for restart |
301 |
3 |
Waiting for another installation to complete |
301 |
4 |
Successfully installed update(s) |
301 |
5 |
Pending system restart |
301 |
6 |
Failed to install update(s) |
301 |
7 |
Downloading update(s) |
301 |
8 |
Downloaded update(s) |
301 |
9 |
Failed to download update(s) |
301 |
10 |
Waiting for maintenance window before installing |
302 |
0 |
Evaluation state unknown |
302 |
1 |
Evaluation activated |
302 |
2 |
Evaluation succeeded |
302 |
3 |
Evaluation failed |
400 |
0 |
Detection state unknown |
400 |
1 |
Not Required |
400 |
2 |
Not Detected |
400 |
3 |
Detected |
401 |
0 |
Compliance state unknown |
401 |
1 |
Compliant |
401 |
2 |
Non-Compliant |
401 |
3 |
Conflict Detected |
401 |
4 |
Error |
402 |
0 |
Enforcement state unknown |
402 |
1 |
Enforcement started |
402 |
2 |
Enforcement waiting for content |
402 |
3 |
Waiting for another installation to complete |
402 |
4 |
Waiting for maintenance window before installing |
402 |
5 |
Restart required before installing |
402 |
6 |
General failure |
402 |
7 |
Pending installation |
402 |
8 |
Installing update |
402 |
9 |
Pending system restart |
402 |
10 |
Successfully installed update |
402 |
11 |
Failed to install update |
402 |
12 |
Downloading update |
402 |
13 |
Downloaded update |
402 |
14 |
Failed to download update |
500 |
0 |
Detection state unknown |
500 |
1 |
Update is not required |
500 |
2 |
Update is required |
500 |
3 |
Update is installed |
501 |
0 |
Scan state unknown |
501 |
1 |
Scan is waiting for content |
501 |
2 |
Scan is running |
501 |
3 |
Scan completed |
501 |
4 |
Scan is pending retry |
501 |
5 |
Scan failed |
501 |
6 |
Scan completed with errors |
501 |
7 |
SMS 2003 client |
800 |
100 |
Client deployment started |
800 |
301 |
Unknown client deployment failure. |
800 |
302 |
Failed to create the ccmsetup service |
800 |
303 |
Failed to delete the ccmsetup service |
800 |
304 |
Cannot install over embedded operating system with File Based Write Filter (FBWF) enabled on system drive |
800 |
305 |
Native security mode is not valid on Windows 2000 |
800 |
306 |
Failed to start ccmsetup download process |
800 |
307 |
Non-valid ccmsetup command line |
800 |
308 |
Failed to download file over WINHTTP at address |
800 |
309 |
Failed to download files through BITS at address |
800 |
310 |
Failed to install BITS version |
800 |
311 |
Can't verify that prerequisite file is MS signed |
800 |
312 |
Failed to copy file because disk is full |
800 |
313 |
Client.msi installation failed with MSI error |
800 |
314 |
Failed to load ccmsetup.xml manifest file |
800 |
315 |
Failed to obtain client certificate |
800 |
316 |
Prerequisite file is not MS signed |
800 |
317 |
Reboot required to continue installation |
800 |
318 |
Cannot install the client on the MP because the MP and client versions do not match |
800 |
319 |
Operating system or service pack not supported |
800 |
400 |
Client deployment succeeded |
800 |
500 |
Client assignment started |
800 |
601 |
Unknown client assignment failure |
800 |
602 |
The following site code is invalid |
800 |
603 |
Failed to assign to MP |
800 |
604 |
Failed to discover default management point |
800 |
605 |
Failed to download site signing certificate |
800 |
606 |
Failed to auto discover site code |
800 |
607 |
Site assignment failed; client version higher than site version |
800 |
608 |
Failed to get Site Version from Active Directory Domain Services and SLP |
800 |
609 |
Failed to get client version |
800 |
700 |
Client assignment succeeded |
1000 |
1 |
Client successfully communicating with management point |
1000 |
2 |
Client failing to communicate with management point |
1001 |
1 |
Client successfully retrieving certificate from local certificate store |
1001 |
2 |
Client failing to retrieve certificate from local certificate store |
1100 |
1 |
Client not ready for native mode |
1100 |
2 |
Client ready for native mode |