Examples of using State message in English and their translations into Russian
{-}
-
Official
-
Colloquial
Specify the throttle interval for state message processing.
The state message serial number tracking is performed at every site in the hierarchy.
Specifies that the site server has not received a state message from the client computer, typically because.
The state message description describes the state message sent by clients.
The scan completed successfully on the client computer, but the state message has not been received from the child site.
State message IDs are used to define specific state messages for each topic type.
Look for specific state message changes logged on the client.
For more informationabout this issue and how to prevent it, see Troubleshooting State Message Backlogs.
Site assignment will fail,with the client sending a state message to its fallback status point(if one is assigned).
If you suspect that state message processing is slow for a Configuration Manager 2007 site, the following actions should be taken.
When the deadline is reached for a mandatory deployment, client computers create a state message for each software update in the deployment.
This report displays the SMS State Message processing rates for all applicable Configuration Manager2007 server roles.
The impact of both software update andclient installation activities can quickly cause a state message processing backlog on the site server computer.
For each software update, a state message is created that contains the compliance state for the update.
After system restart: When a client computer was pending a system restart for the software update installation to complete,a scan is initiated after the restart to verify that the update is no longer required and to create a state message that indicates the update has been installed.
A large or persistent state message processing backlog can prevent Configuration Manager 2007 from reporting critical information.
The software update has been installed on the client computer, butthe most recent state message has not yet been inserted into the database on the site server.
If the state message processing for a site appears to be slower than expected, the following solution might help resolve the slow message processing condition.
Client resynchronization is triggered when the state message system believes that data is missing from a client computer.
The state message system allows client computers to send short messages to the fallback status point or to the management point that indicate changes of state, for instance, success or failure.
A smaller interval allows moretimely state message reporting, but increases the load on the state message system.
Click the Report Link icon in the first column on any row to open the States 4- Computers in a specific state for a deployment< secondary>report to display the computer information, the last time a state message was received from the client computer, the evaluation state for the deployment, and the error status if one exists.
For example, for information about using state message changes in client logs, see How to Verify Clients are Successfully Remediated with Network Access Protection.
When the installation completes, it is verified that the software update is no longer required and a state message is sent to the management point that indicates that the update is now installed.
While it is normal to have some state message processing backlog, it is important to plan for the impact of site server state message processing when performing activities that generate large numbers of state messages. .
For more information about troubleshooting state message backlogs, see Troubleshooting State Message Backlogs.
If the resynchronization completion state message is not processed after three days, a state message resynchronization request will be reissued to the client- even if the client's resynchronization complete message has already been sent but not processed yet.
In particular, planning for client features that generate state messages should be considered to avoid state message processing backlogs.
When a scan is run on a client computer, a state message is created for each update source- for example, Microsoft Update or the Inventory Tool for Microsoft Updates.
The scan completed successfully on the client computer, but the state message has not been processed yet on the site server, possibly due to backlog state message backlog.