[BESAdmin-Announcements] Content Modification Announcement - BES Support - Dynamic Throttling Tasks

[Announcements for BES Administrators]

BigFix has modified content in the BES Support site. The behavior and
content of the dynamic throttling tasks has been changed.

Dynamic throttling needs to be enabled on both the BES Clients and BES
Relays to function properly. Previously published tasks did not function
as intended: they only enabled dynamic throttling on BES Clients since
the BES Relay tasks were separate and there wasn't any indication that
you would need to deploy the BES Relay tasks to get the BES Client
throttling to work.

We have added a new task which is designed to enable dynamic throttling
in your entire deployment. This task should be deployed first globally
to activate this feature.  Afterwards, you can use the other tasks to
set specific dynamic throttling rates.  Dynamic throttling will not go
into effect until it is activated and throttling values are put in
place.


The new task to globally enable dynamic throttling is:

ID: 605  BES Client/Relay/Server Setting: Enable/Disable Dynamic
Throttling


These tasks have been modified to become relevant after the previous
task has been run:

ID: 457  BES Client Setting: Dynamic Download Throttling 
ID: 458  BES Relay Setting: Dynamic Download Throttling 
ID: 459  BES Relay Setting: Dynamically Throttle Outgoing Traffic  
ID: 462  BES Server Setting: Dynamically Throttle Outgoing Traffic 

Fixlet 457 has also been modified to apply to non-Windows systems, as
these clients can take advantage of the dynamic throttling feature.


This analysis has been modified to correspond with the behavior changes
above:

ID: 218     Bandwidth Throttling Status 


BES administrators are encouraged to verify open actions and synchronize
baselines that contain the modified content.  Instructions for
synchronizing baselines can be found here:
http://support.bigfix.com/cgi-bin/kbdirect.pl?id=401.  Please contact
BigFix Technical Support if you have any questions regarding this
change.

--
BigFix Application Engineering Team