Although the default throttling configuration for the fallback status point in Configuration Manager 2007 is sufficient for most circumstances, you might need to change the throttling configuration for the scenario in the following table.
|Scenario||More Information||Throttling Setting|
The fallback status point accepts connections only from the intranet, and will be used during a client deployment rollout for a high number of computers.
During a deployment of many computers, the default throttling settings might result in a backlog of state messages.
This can result in a delay in displaying up-to-date information in the client deployment reports.
Consider changing one of the following throttling settings:
The default throttle settings for a Configuration Manager 2007 fallback status point are the following:
- Number of Messages: 10,000
- Throttle interval (in seconds):
These throttle settings limit the number of state messages that can be sent to the Configuration Manager 2007 site server in a specified period.
Without throttling, a continuous stream of state messages could negatively affect the performance of the Configuration Manager 2007 site server.
State Messages Sent by the Fallback Status Point
Each computer that successfully installs the Configuration Manager 2007 client sends the following four state messages to the fallback status point:
- Client deployment started
- Client deployment succeeded
- Client assignment started
- Client assignment succeeded
In addition, computers that fail to install or assign the Configuration Manager 2007 client will send further state messages.
For a client deployment up to 20,000 computers, this could result in 80,000 state messages being sent to the fallback status point. Because the default throttling configuration allows 10,000 state messages to be sent to the fallback status point each 3600 seconds (1 hour), state messages might become backlogged on the fallback status point as a result of the throttling configuration.
You also need to take into account the available network bandwidth between the fallback status point and the site server, and the processing power of the site server to process a high number of state messages.
Considerations for Configuring the Throttling Settings on the Fallback Status Point
Consider changing one of the throttle values for the fallback status point if the following condition applies:
- You calculate that the default throttle
values will not process state messages from your client deployment
in a reasonable timescale.
Reset the throttle values for the fallback status point if either of the following conditions applies:
- You calculate that the current throttle
values are higher than required to process state messages from the
fallback status point.
- You find that the current throttle settings
result in a high CPU load on your Configuration Manager 2007 site
|Do not change the fallback status point throttle settings unless you understand the consequences. For example, if you increase the throttle settings too high, you could cause high CPU load on your Configuration Manager 2007 site server that negatively affects the operation of your site.|
For information about how to change the default throttling values for the fallback status point throttle, see How to Configure the Fallback Status Point in Configuration Manager.
TasksHow to Create a Fallback Status Point in Configuration Manager
How to Configure the Fallback Status Point in Configuration Manager
ConceptsAbout the Fallback Status Point in Configuration Manager
Determine If You Should Install a Fallback Status Point for Configuration Manager Clients
Overview of Configuration Manager Client Deployment