Applies to

StifleR Server 1.4

Symptoms

After installation of the StifleR Client a check of the BITS local policy settings indicates that some of the features of the Work Schedule have been configured to be disabled. This may cause confusion as StifleR Bandwidth control is administered through the Maintenance Schedule settings.

Cause

During the installation of the StifleR client a number of BITS policy settings are configured as follows-

 

                _pols.Add(new Policies("HKLM\\Software\\Policies\\Microsoft\\Windows\\BITS\\Throttling!EnableBandwidthLimits", "1", RegistryValueKind.DWord));

                _pols.Add(new Policies("HKLM\\Software\\Policies\\Microsoft\\Windows\\BITS\\Throttling!EnableMaintenanceLimits", "1", RegistryValueKind.DWord));

                _pols.Add(new Policies("HKLM\\Software\\Policies\\Microsoft\\Windows\\BITS\\Throttling!IgnoreBandwidthLimitsOnLan", "1", RegistryValueKind.DWord));

 

 

                _pols.Add(new Policies("HKLM\\Software\\Policies\\Microsoft\\Windows\\BITS\\Throttling\\MaintenanceSchedule!StartDay", "0", RegistryValueKind.DWord));

                _pols.Add(new Policies("HKLM\\Software\\Policies\\Microsoft\\Windows\\BITS\\Throttling\\MaintenanceSchedule!EndDay", "6", RegistryValueKind.DWord));

                _pols.Add(new Policies("HKLM\\Software\\Policies\\Microsoft\\Windows\\BITS\\Throttling\\MaintenanceSchedule!StartHour", "0", RegistryValueKind.DWord));

                _pols.Add(new Policies("HKLM\\Software\\Policies\\Microsoft\\Windows\\BITS\\Throttling\\MaintenanceSchedule!EndHour", "0" ,RegistryValueKind.DWord));

                _pols.Add(new Policies("HKLM\\Software\\Policies\\Microsoft\\Windows\\BITS\\Throttling\\MaintenanceSchedule!HighBandwidthLimit", speed,  RegistryValueKind.DWord));

                _pols.Add(new Policies("HKLM\\Software\\Policies\\Microsoft\\Windows\\BITS\\Throttling\\MaintenanceSchedule!HighBandwidthType", speedType,  RegistryValueKind.DWord));

                _pols.Add(new Policies("HKLM\\Software\\Policies\\Microsoft\\Windows\\BITS\\Throttling\\MaintenanceSchedule!NormalBandwidthLimit", speed, RegistryValueKind.DWord));

                _pols.Add(new Policies("HKLM\\Software\\Policies\\Microsoft\\Windows\\BITS\\Throttling\\MaintenanceSchedule!NormalBandwidthType", speedType,  RegistryValueKind.DWord));

                _pols.Add(new Policies("HKLM\\Software\\Policies\\Microsoft\\Windows\\BITS\\Throttling\\MaintenanceSchedule!LowBandwidthLimit", speed, RegistryValueKind.DWord));

                _pols.Add(new Policies("HKLM\\Software\\Policies\\Microsoft\\Windows\\BITS\\Throttling\\MaintenanceSchedule!LowBandwidthType", speedType, RegistryValueKind.DWord));

 

Note that the firs three settings are General and for the default Work Schedule while the rest are Maintenance Schedule settings. 

It is the first three that make the Work Schedule Policy appear “enabled”. This is misleading as no Work Schedule is actually set. The reason that this has been configured is simply to set the value for IgnoreBandwidthLimitsOnLAN.  This allows customers to trigger StifleR on events (transfers) but have a regular work schedule for distributions when StifleR is not running. 

In the latest release these Work Schedule Policy setting are not removed by the installation process (the Maintenance Policy settings are) but this should be fixed in a future release.