Author: admin
Set default download behavior for BITS jobs on costed networks
This policy setting defines the default behavior that the Background Intelligent Transfer Service (BITS) uses for background transfers when the system is connected to a costed network (3G etc. ). Download behavior policies further limit the network usage of background transfers. If you enable this policy setting you can define a default download policy for each BITS job priority. This setting does not override a download policy explicitly configured by the application that created the BITS job but does apply to jobs that are created by specifying only a priority. For example you can specify that background jobs are by default to transfer only when on uncosted network connections but foreground jobs should proceed only when not roaming. The values that can be assigned are: – Always transfer – Transfer unless roaming – Transfer unless surcharge applies (when not roaming or overcap) – Transfer unless nearing limit (when not roaming or nearing cap) – Transfer only if unconstrained – Custom–allows you to specify a bitmask in which the bits describe cost states allowed or disallowed for this priority: (bits described here) 0x1 – The cost is unknown or the connection is unlimited and is considered to be unrestricted of usage charges and capacity constraints. 0x2 – The usage of this connection is unrestricted up to a certain data limit 0x4 – The usage of this connection is unrestricted up to a certain data limit and plan usage is less than 80 percent of the limit. 0x8 – Usage of this connection is unrestricted up to a certain data limit and plan usage is between 80 percent and 100 percent of the limit. 0x10 – Usage of this connection is unrestricted up to a certain data limit which has been exceeded. Surcharge applied or unknown. 0x20 – Usage of this connection is unrestricted up to a certain data limit which has been exceeded. No surcharge applies but speeds are likely reduced. 0x40 – The connection is costed on a per-byte basis. 0x80 – The connection is roaming. 0x80000000 – Ignore congestion.
Limit the maximum network bandwidth used for Peercaching
This policy setting limits the network bandwidth that BITS uses for peer cache transfers (this setting does not affect transfers from the origin server). To prevent any negative impact to a computer caused by serving other peers by default BITS will use up to 30 percent of the bandwidth of the slowest active network interface. For example if a computer has both a 100 Mbps network card and a 56 Kbps modem and both are active BITS will use a maximum of 30 percent of 56 Kbps. You can change the default behavior of BITS and specify a fixed maximum bandwidth that BITS will use for peer caching. If you enable this policy setting you can enter a value in bits per second (bps) between 1048576 and 4294967200 to use as the maximum network bandwidth used for peer caching. If you disable this policy setting or do not configure it the default value of 30 percent of the slowest active network interface will be used. Note: This setting has no effect if the “Allow BITS peer caching” policy setting is disabled or not configured.
Do not allow the computer to act as a BITS Peercaching server
This policy setting specifies whether the computer will act as a BITS peer caching server. By default when BITS peer caching is enabled the computer acts as both a peer caching server (offering files to its peers) and a peer caching client (downloading files from its peers). If you enable this policy setting the computer will no longer cache downloaded files and offer them to its peers. However the computer will still download files from peers. If you disable or do not configure this policy setting the computer will offer downloaded and cached files to its peers. Note: This setting has no effect if the “Allow BITS peer caching” setting is disabled or not configured.
Do not allow the computer to act as a BITS Peercaching client
This policy setting specifies whether the computer will act as a BITS peer caching client. By default when BITS peer caching is enabled the computer acts as both a peer caching server (offering files to its peers) and a peer caching client (downloading files from its peers). If you enable this policy setting the computer will no longer use the BITS peer caching feature to download files; files will be downloaded only from the origin server. However the computer will still make files available to its peers. If you disable or do not configure this policy setting the computer attempts to download peer-enabled BITS jobs from peer computers before reverting to the origin server. Note: This policy setting has no effect if the “Allow BITS peer caching” policy setting is disabled or not configured.
Limit the BITS Peercache size
This policy setting limits the maximum amount of disk space that can be used for the BITS peer cache as a percentage of the total system disk size. BITS will add files to the peer cache and make those files available to peers until the cache content reaches the specified cache size. By default BITS will use 1 percent of the total system disk for the peercache. If you enable this policy setting you can enter the percentage of disk space to be used for the BITS peer cache. You can enter a value between 1 percent and 80 percent. If you disable or do not configure this policy setting the default size of the BITS peer cache is 1 percent of the total system disk size. Note: This policy setting has no effect if the “Allow BITS peer caching” setting is disabled or not configured.
Limit the age of files in the BITS Peercache
This policy setting limits the maximum age of files in the Background Intelligent Transfer Service (BITS) peer cache. In order to make the most efficient use of disk space by default BITS removes any files in the peer cache that have not been accessed in the past 90 days. If you enable this policy setting you can specify in days the maximum age of files in the cache. You can enter a value between 1 and 120 days. If you disable or do not configure this policy setting files that have not been accessed for the past 90 days will be removed from the peer cache. Note: This policy setting has no effect if the “Allow BITS Peercaching” policy setting is disabled or not configured.
Allow BITS Peercaching
This policy setting determines if the Background Intelligent Transfer Service (BITS) peer caching feature is enabled on a specific computer. By default the files in a BITS job are downloaded only from the origin server specified by the job’s owner. If BITS peer caching is enabled BITS caches downloaded files and makes them available to other BITS peers. When transferring a download job BITS first requests the files for the job from its peers in the same IP subnet. If none of the peers in the subnet have the requested files BITS downloads them from the origin server. If you enable this policy setting BITS downloads files from peers caches the files and responds to content requests from peers. Using the “Do not allow the computer to act as a BITS peer caching server” and “Do not allow the computer to act as a BITS peer caching client” policy settings it is possible to control BITS peer caching functionality at a more detailed level. However it should be noted that the “Allow BITS peer caching” policy setting must be enabled for the other two policy settings to have any effect. If you disable or do not configure this policy setting the BITS peer caching feature will be disabled and BITS will download files directly from the origin server.
Set up a maintenance schedule to limit the maximum network bandwidth used for BITS background transfers
This policy setting limits the network bandwidth that Background Intelligent Transfer Service (BITS) uses for background transfers during the maintenance days and hours. Maintenance schedules further limit the network bandwidth that is used for background transfers. If you enable this policy setting you can define a separate set of network bandwidth limits and set up a schedule for the maintenance period. You can specify a limit to use for background jobs during a maintenance schedule. For example if normal priority jobs are currently limited to 256 Kbps on a work schedule you can further limit the network bandwidth of normal priority jobs to 0 Kbps from 8:00 A. M. to 10:00 A. M. on a maintenance schedule. If you disable or do not configure this policy setting the limits defined for work or nonwork schedules will be used. Note: The bandwidth limits that are set for the maintenance period supersede any limits defined for work and other schedules.
Set up a work schedule to limit the maximum network bandwidth used for BITS background transfers
This policy setting limits the network bandwidth that Background Intelligent Transfer Service (BITS) uses for background transfers during the work and nonwork days and hours. The work schedule is defined using a weekly calendar which consists of days of the week and hours of the day. All hours and days that are not defined in a work schedule are considered non-work hours. If you enable this policy setting you can set up a schedule for limiting network bandwidth during both work and nonwork hours. After the work schedule is defined you can set the bandwidth usage limits for each of the three BITS background priority levels: high normal and low. You can specify a limit to use for background jobs during a work schedule. For example you can limit the network bandwidth of low priority jobs to 128 Kbps from 8:00 A. M. to 5:00 P. M. on Monday through Friday and then set the limit to 512 Kbps for nonwork hours. If you disable or do not configure this policy setting BITS uses all available unused bandwidth for background job transfers.
Limit the maximum network bandwidth for BITS background transfers
This policy setting limits the network bandwidth that Background Intelligent Transfer Service (BITS) uses for background transfers. (This policy setting does not affect foreground transfers. ) You can specify a limit to use during a specific time interval and at all other times. For example limit the use of network bandwidth to 10 Kbps from 8:00 A. M. to 5:00 P. M. and use all available unused bandwidth the rest of the day’s hours. If you enable this policy setting BITS will limit its bandwidth usage to the specified values. You can specify the limit in kilobits per second (Kbps). If you specify a value less than 2 kilobits BITS will continue to use approximately 2 kilobits. To prevent BITS transfers from occurring specify a limit of 0. If you disable or do not configure this policy setting BITS uses all available unused bandwidth. Note: You should base the limit on the speed of the network link not the computer’s network interface card (NIC). This policy setting does not affect Peercaching transfers between peer computers (it does affect transfers from the origin server); the “Limit the maximum network bandwidth used for Peercaching” policy setting should be used for that purpose. Consider using this setting to prevent BITS transfers from competing for network bandwidth when the client computer has a fast network card (10Mbs) but is connected to the network via a slow link (56Kbs).