The default for every Microsoft System Center Configuration Manager 2007 advertisement and software update deployment is to not download software packages and software updates when the client is connected within a slow or unreliable network boundary. This default assumes that you do not want clients downloading content over slow or unreliable network connections, thereby saving network bandwidth.
However, in some scenarios, this default setting might unexpectedly prevent clients from installing the software packages and software updates that you want them to have. Consider changing this default if you want to ensure that clients always install software packages and software updates when requested and if any of the following scenarios apply:
- Clients are not within a configured boundary
for their assigned site because boundaries are not configured
correctly or because the clients have been incorrectly
In this scenario, clients will never install the software package or software updates. For these clients to install the software package or software update with the default configuration, all boundaries must be configured correctly.
- Clients are within a boundary that is
configured as slow or unreliable, such as a virtual private network
(VPN) or wireless network.
In this scenario, clients will not be able to install the software package or software updates unless their network location changes to a fast and reliable boundary. Alternatively, reconfigure the slow or unreliable boundary to be fast and reliable.
- Clients have roamed into another site that
does not host the content.
In this scenario, clients will not be able to install the software package or software updates until they return to their assigned site.
For more information about planning and configuring boundaries, see the following:
ReferenceAdvertisement Name Properties: Distribution Points Tab
Deployment Name Properties: Download Settings Tab
Deployment Name Properties: SMS 2003 Settings Tab
ConceptsAbout Client Roaming in Configuration Manager
Configuration Manager and Content Location (Package Source Files)
Example Roaming Scenarios for Configuration Manager: Complex