Policy CSP - BITS
BandwidthThrottlingEndTime
| Scope | Editions | Applicable OS |
|---|---|---|
| ✅ Device ❌ User |
✅ Pro ✅ Enterprise ✅ Education ✅ Windows SE ✅ IoT Enterprise / IoT Enterprise LTSC |
✅ Windows 10, version 1809 [10.0.17763] and later |
./Device/Vendor/MSFT/Policy/Config/BITS/BandwidthThrottlingEndTime
This policy setting limits the network bandwidth that Background Intelligent Transfer Service (BITS) uses for background transfers. (This policy setting doesn't 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 don't 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 doesn't 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).
Description framework properties:
| Property name | Property value |
|---|---|
| Format | int |
| Access Type | Add, Delete, Get, Replace |
| Allowed Values | Range: [0-23] |
| Default Value | 17 |
Group policy mapping:
| Name | Value |
|---|---|
| Name | BITS_MaxBandwidth |
| Friendly Name | Limit the maximum network bandwidth for BITS background transfers |
| Element Name | to. |
| Location | Computer Configuration |
| Path | Network > Background Intelligent Transfer Service (BITS) |
| Registry Key Name | Software\Policies\Microsoft\Windows\BITS |
| ADMX File Name | Bits.admx |
BandwidthThrottlingStartTime
| Scope | Editions | Applicable OS |
|---|---|---|
| ✅ Device ❌ User |
✅ Pro ✅ Enterprise ✅ Education ✅ Windows SE ✅ IoT Enterprise / IoT Enterprise LTSC |
✅ Windows 10, version 1809 [10.0.17763] and later |
./Device/Vendor/MSFT/Policy/Config/BITS/BandwidthThrottlingStartTime
This policy setting limits the network bandwidth that Background Intelligent Transfer Service (BITS) uses for background transfers. (This policy setting doesn't 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 don't 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 doesn't 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).
Description framework properties:
| Property name | Property value |
|---|---|
| Format | int |
| Access Type | Add, Delete, Get, Replace |
| Allowed Values | Range: [0-23] |
| Default Value | 8 |
Group policy mapping:
| Name | Value |
|---|---|
| Name | BITS_MaxBandwidth |
| Friendly Name | Limit the maximum network bandwidth for BITS background transfers |
| Element Name | From. |
| Location | Computer Configuration |
| Path | Network > Background Intelligent Transfer Service (BITS) |
| Registry Key Name | Software\Policies\Microsoft\Windows\BITS |
| ADMX File Name | Bits.admx |
BandwidthThrottlingTransferRate
| Scope | Editions | Applicable OS |
|---|---|---|
| ✅ Device ❌ User |
✅ Pro ✅ Enterprise ✅ Education ✅ Windows SE ✅ IoT Enterprise / IoT Enterprise LTSC |
✅ Windows 10, version 1809 [10.0.17763] and later |
./Device/Vendor/MSFT/Policy/Config/BITS/BandwidthThrottlingTransferRate
This policy setting limits the network bandwidth that Background Intelligent Transfer Service (BITS) uses for background transfers. (This policy setting doesn't 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 don't 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 doesn't 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).
Description framework properties:
| Property name | Property value |
|---|---|
| Format | int |
| Access Type | Add, Delete, Get, Replace |
| Allowed Values | Range: [0-4294967200] |
| Default Value | 1000 |
Group policy mapping:
| Name | Value |
|---|---|
| Name | BITS_MaxBandwidth |
| Friendly Name | Limit the maximum network bandwidth for BITS background transfers |
| Element Name | Limit background transfer rate (Kbps) to. |
| Location | Computer Configuration |
| Path | Network > Background Intelligent Transfer Service (BITS) |
| Registry Key Name | Software\Policies\Microsoft\Windows\BITS |
| ADMX File Name | Bits.admx |
CostedNetworkBehaviorBackgroundPriority
| Scope | Editions | Applicable OS |
|---|---|---|
| ✅ Device ❌ User |
✅ Pro ✅ Enterprise ✅ Education ✅ Windows SE ✅ IoT Enterprise / IoT Enterprise LTSC |
✅ Windows 10, version 1809 [10.0.17763] and later |
./Device/Vendor/MSFT/Policy/Config/BITS/CostedNetworkBehaviorBackgroundPriority
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 doesn't 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.
Description framework properties:
| Property name | Property value |
|---|---|
| Format | int |
| Access Type | Add, Delete, Get, Replace |
| Default Value | 1 |
Allowed values:
| Value | Description |
|---|---|
| 1 (Default) | Always transfer. |
| 2 | Transfer unless roaming. |
| 3 | Transfer unless surcharge applies (when not roaming or over cap). |
| 4 | Transfer unless nearing limit (when not roaming or nearing cap). |
| 5 | Transfer only if unconstrained. |
Group policy mapping:
| Name | Value |
|---|---|
| Name | BITS_SetTransferPolicyOnCostedNetwork |
| Friendly Name | Set default download behavior for BITS jobs on costed networks |
| Element Name | Normal. |
| Location | Computer Configuration |
| Path | Network > Background Intelligent Transfer Service (BITS) |
| Registry Key Name | Software\Policies\Microsoft\Windows\BITS\TransferPolicy |
| ADMX File Name | Bits.admx |
CostedNetworkBehaviorForegroundPriority
| Scope | Editions | Applicable OS |
|---|---|---|
| ✅ Device ❌ User |
✅ Pro ✅ Enterprise ✅ Education ✅ Windows SE ✅ IoT Enterprise / IoT Enterprise LTSC |
✅ Windows 10, version 1809 [10.0.17763] and later |
./Device/Vendor/MSFT/Policy/Config/BITS/CostedNetworkBehaviorForegroundPriority
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 doesn't 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.
Description framework properties:
| Property name | Property value |
|---|---|
| Format | int |
| Access Type | Add, Delete, Get, Replace |
| Default Value | 1 |
Allowed values:
| Value | Description |
|---|---|
| 1 (Default) | Always transfer. |
| 2 | Transfer unless roaming. |
| 3 | Transfer unless surcharge applies (when not roaming or over cap). |
| 4 | Transfer unless nearing limit (when not roaming or nearing cap). |
| 5 | Transfer only if unconstrained. |
Group policy mapping:
| Name | Value |
|---|---|
| Name | BITS_SetTransferPolicyOnCostedNetwork |
| Friendly Name | Set default download behavior for BITS jobs on costed networks |
| Element Name | Foreground. |
| Location | Computer Configuration |
| Path | Network > Background Intelligent Transfer Service (BITS) |
| Registry Key Name | Software\Policies\Microsoft\Windows\BITS\TransferPolicy |
| ADMX File Name | Bits.admx |
JobInactivityTimeout
| Scope | Editions | Applicable OS |
|---|---|---|
| ✅ Device ❌ User |
✅ Pro ✅ Enterprise ✅ Education ✅ Windows SE ✅ IoT Enterprise / IoT Enterprise LTSC |
✅ Windows 10, version 1809 [10.0.17763] and later |
./Device/Vendor/MSFT/Policy/Config/BITS/JobInactivityTimeout
This policy setting specifies the number of days a pending BITS job can remain inactive before the job is considered abandoned. By default BITS will wait 90 days before considering an inactive job abandoned. After a job is determined to be abandoned, the job is deleted from BITS and any downloaded files for the job are deleted from the disk.
Note
Any property changes to the job or any successful download action will reset this timeout.
Consider increasing the timeout value if computers tend to stay offline for a long period of time and still have pending jobs.
Consider decreasing this value if you are concerned about orphaned jobs occupying disk space.
If you enable this policy setting, you can configure the inactive job timeout to specified number of days.
If you disable or don't configure this policy setting, the default value of 90 (days) will be used for the inactive job timeout.
Description framework properties:
| Property name | Property value |
|---|---|
| Format | int |
| Access Type | Add, Delete, Get, Replace |
| Allowed Values | Range: [1-999] |
| Default Value | 90 |
Group policy mapping:
| Name | Value |
|---|---|
| Name | BITS_Job_Timeout |
| Friendly Name | Timeout for inactive BITS jobs |
| Element Name | Inactive Job Timeout in Days. |
| Location | Computer Configuration |
| Path | Network > Background Intelligent Transfer Service (BITS) |
| Registry Key Name | Software\Policies\Microsoft\Windows\BITS |
| ADMX File Name | Bits.admx |