Topic last updated—November 2007
Use this tab to specify how many concurrent communications the Microsoft System Center Configuration Manager 2007 sender can make, and how often the sender should retry a failed communication.
 Important |
|---|
| When configuring the total number of concurrent sending threads to be used when communicating with other sites, the total number of sending threads should be configured as a greater number than the threads configured for the per site setting. If the total number of sending threads is equal to the number configured to be used per site, and a receiving site is unavailable, it could cause all sending threads to become used when attempting to communicate with the unavailable site and prevent site-to-site communication to other sites. |
| Term | Definition |
|---|---|
|
Maximum concurrent sendings |
Specify the maximum number of simultaneous communications allowed for this sender and for each destination site. Keep in mind that higher numbers potentially allow more throughput, but at the expense of available network bandwidth. If your network becomes too busy, lower these numbers. |
|
All sites |
The maximum number of simultaneous communications allowed for this sender. The default value is 5. These communications can be destined for different sites, or all for the same site, except as restricted by the maximum value specified in Per site. |
|
Per site |
The maximum number of simultaneous communications allowed to any single destination site. The default value is 3. For RAS Senders, this field is disabled and set to 1. |
|
Retry settings |
Specify the action taken by the sender if the first communication fails. |
|
Number of retries |
The number of times that a failed communication is retried. The default value is 2. |
|
Delay before retrying |
The number of minutes to wait between retries of a failed communication. The default value is 1. |