Tag: Computer Configuration
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.
Allow Corporate redirection of Customer Experience Improvement uploads
If you enable this setting all Customer Experience Improvement Program uploads are redirected to Microsoft Operations Manager server. If you disable this setting uploads are not redirected to a Microsoft Operations Manager server. If you do not configure this setting uploads are not redirected to a Microsoft Operations Manager server.
Do not allow the BITS client to use Windows Branch Cache
This setting affects whether the BITS client is allowed to use Windows Branch Cache. If the Windows Branch Cache component is installed and enabled on a computer BITS jobs on that computer can use Windows Branch Cache by default. If you enable this policy setting the BITS client does not use Windows Branch Cache. If you disable or do not configure this policy setting the BITS client uses Windows Branch Cache. Note: This policy setting does not affect the use of Windows Branch Cache by applications other than BITS. This policy setting does not apply to BITS transfers over SMB. This setting has no effect if the computer’s administrative settings for Windows Branch Cache disable its use entirely.
Limit the maximum number of ranges that can be added to the file in a BITS job
This policy setting limits the number of ranges that can be added to a file in a BITS job. By default files in a BITS job are limited to 500 ranges per file. You can use this setting to raise or lower the maximum number ranges per file. If you enable this policy setting BITS will limit the maximum number of ranges that can be added to a file to the specified number. If you disable or do not configure this policy setting BITS will limit ranges to 500 ranges per file. Note: BITS Jobs created by services and the local administrator account do not count toward this limit.
Limit the maximum number of files allowed in a BITS job
This policy setting limits the number of files that a BITS job can contain. By default a BITS job is limited to 200 files. You can use this setting to raise or lower the maximum number of files a BITS jobs can contain. If you enable this policy setting BITS will limit the maximum number of files a job can contain to the specified number. If you disable or do not configure this policy setting BITS will use the default value of 200 for the maximum number of files a job can contain. Note: BITS Jobs created by services and the local administrator account do not count toward this limit.
Limit the maximum number of BITS jobs for each user
This policy setting limits the number of BITS jobs that can be created by a user. By default BITS limits the total number of jobs that can be created by a user to 60 jobs. You can use this setting to raise or lower the maximum number of BITS jobs a user can create. If you enable this policy setting BITS will limit the maximum number of BITS jobs a user can create to the specified number. If you disable or do not configure this policy setting BITS will use the default user BITS job limit of 300 jobs. Note: This limit must be lower than the setting specified in the “Maximum number of BITS jobs for this computer” policy setting or 300 if the “Maximum number of BITS jobs for this computer” policy setting is not configured. BITS jobs created by services and the local administrator account do not count toward this limit.
Limit the maximum number of BITS jobs for this computer
This policy setting limits the number of BITS jobs that can be created for all users of the computer. By default BITS limits the total number of jobs that can be created on the computer to 300 jobs. You can use this policy setting to raise or lower the maximum number of user BITS jobs. If you enable this policy setting BITS will limit the maximum number of BITS jobs to the specified number. If you disable or do not configure this policy setting BITS will use the default BITS job limit of 300 jobs. Note: BITS jobs created by services and the local administrator account do not count toward this limit.
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.