In a normal Windows environment BITS Bandwidth is controlled through two Schedules (typically set via GPO). A regular “Work” schedule setting that controls how much bandwidth each individual client is allowed to use on a day to day basis. There is also a special Maintenance Schedule setting that overrides the general Work schedule in order to set bandwidth during these periods.
In order to control Bandwidth usage, StifleR makes changes to the Maintenance Schedule Policy Setting.
NOTE: StifleR cannot be used if there is an Active Directory Group Policy Object configured for the BITS Maintenance Schedule. Please remove any such Policy before using StifleR bandwidth controls.
The Work Schedule (day to day)
This is the general day to day Windows Policy setting used throughout your network and is not configured by StifleR. This section is included for information only.
This policy setting limits the network bandwidth that Background Intelligent Transfer Service (BITS) uses for background transfers during the work and non-work 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 non-work 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 non-work hours.
If you disable or do not configure this policy setting, BITS uses all available unused bandwidth for background job transfers.
Figure 16 shows the Work schedule, which is split into two sections; One for Work Hours and one for Non-Work Hours.
The Maintenance Schedule
NOTE: StifleR cannot be used if there is an Active Directory Group Policy Object configured for the BITS Maintenance Schedule. Please remove any such Policy in order to enable StifleR bandwidth controls.
This is the Policy that takes precedence over the Work Schedule settings. StifleR makes configuration changes to the Local Maintenace Schedule Policy and can thus control the machine bandwidth usage. StifleR manages this policy transparently and there is no need to manually modify or configure this policy.
The following notes on the function if this Policy type are for information only to give you an idea of how the maintenance Schedule works in relation to the Work Schedule.
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. This means that it overrides the work schedule and these values take presence.
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 non-work schedules will be used.
The bandwidth limits that are set for the maintenance period supersede any limits defined for work and other schedules. This is how the StifleR controls the bandwidth, through setting the BITS maintenance transfer policy to the value that the StifleR server calculates.
Figure 17 shows how the local policy created by StifleR appears when the client assigned as the Red Leader has been configured to use 1024 Kbp/s.
Figure 18 shows how the local policy created by StifleR appears on a client is NOT assigned as Red Leader and has therefore been configured to only use 2 Kbp/s thus blocking excess WAN data consumption.