BES Configuration Settings

This configuration setting will enable the BES Client debug log that will give information about the BES Client activity. The higher the level of detail, the greater the detail of the messages that are put into the file and/or NT event log.

• Default Value: 0 (disabled)


• Setting Type: Numeric (detail level)


• Value Range: 0-100


• Task Available: Yes

Full path to file to store activity messages. If empty string and the computer is not Win9x, activity messages are added to the NT event log. Note: The _BESClient_EMsg_Detail setting must be greater than 0 to use this option.

• Default Value: blank


• Setting Type: String (full path)


• Value Range: N/A


• Task Available: Yes

The BES Client will do work (evaluate relevance) for a designated amount of time then go to sleep for a designated amount of time. This setting controls how many milliseconds to work before going to sleep in each cycle. If this number is high in comparison to the _BESClient_Resource_SleepIdle setting, then the BES Client will evaluate Fixlet relevance faster, but the CPU usage will be higher.

• Default Value: 10


• Setting Type: Numeric (MilliSeconds)


• Value Range: 1-500


• Task Available: No

The BES Client will do work (evaluate relevance) for a designated amount of time then go to sleep for a designated amount of time. This setting controls how many milliseconds to sleep after working in each cycle. If this number is high in comparison to the _BESClient_Resource_WorkIdle setting, then the BES Client will take longer to evaluate Fixlet relevance, but the CPU usage will be lower.

• Default Value: 480


• Setting Type: Numeric (milliseconds)


• Value Range: 1-500


• Task Available: No

Quiet mode causes the BES Client to not actively process Fixlets, send in reports, respond to commands, etc. It will basically sit idle until the wakeup time is enabled. A BES Client can be put in quiet mode for a maximum of 20 hours a day. Note: If you put a BES Client in quiet mode, it will not send any reports to the BES Server or respond to any commands so use caution when enabling this setting.

• Default Value: 0 (False)


• Setting Type: Boolean


• Value Range: 1 (True) - enable quiet mode
  0 (False) - disable quiet mode


• Task Available: No

If quiet mode is enabled, you can specify a time for the BES Client to enter quiet mode. Set the time as a string in the form hh:mm where hh is number between 0 and 23, and mm is a number between 0 and 59. This is the local time for which the BES Client will quiet down to no activity. If the value is not properly formatted, the client will not enter quiet mode.

• Default Value: None


• Setting Type: String


• Value Range: hh:mm


• Task Available: No

If quiet mode is enabled, you can specify the number of seconds the BES Client should stay quiet. This number must be greater than 0 and less or equal to 72000 (20 hours) in order for the BES Client to enter quiet mode. In quiet mode, the BES Client checks once a minute to determine if the quiet time has elapsed. However, the BES Client will quickly respond to service shutdown requests at any time.

• Default Value: None


• Setting Type: Numeric


• Value Range: 0-72,000(20 Hours)


• Task Available: No

This specifies the number of days the BES Client logs are retained on a computer.

• Default Value: 10


• Setting Type: Numeric (Days)


• Value Range: 1-366


• Task Available: No

The BES Client has two methods of communication over the network. The first method uses the Windows URL Monikers API, which is a higher-level network interface that uses the computer's Internet connection settings (such as proxy settings, security settings, etc.). The second method uses the winsock API, which is a lower-level direct socket access layer that doesn't use the computer's Internet connection settings. Using winsock will allow the BES Client to connect to the BES Server regardless of the Internet connection settings, but URL Monikers should be used if the Internet connection settings are required for network access to the BES Server for some reason.

• Default Value: 0 (False)


• Setting Type: Boolean


• Value Range: 1 (True) - use URL Monikers
  0 (False) - use Winsock


• Task Available: No

Before the BES Client tries to gather it will check the Windows API connection test to determine if an internet connection is available. This setting will allow the BES Client to ignore the results of the connection test and attempt to gather anyway.

• Default Value: 0 (False)


• Setting Type: Boolean


• Value Range: 1 (True) - ignore connection test
  0 (False) - perform connection test


• Task Available: No

When set to 0 the BES Client will not listen for UDP messages. If the BES Client does not receive UDP messages it will not receive gather pings sent from the BES Server notifying the BES Client of new actions and content.

• Default Value: 1 (True)


• Setting Type: Boolean


• Value Range: 1 (True) - Listen for UDP
  0 (False) - Ignore UDP


• Task Available: No

The BES Client will contact the ClientRegister CGI on the BES Server periodically to report its IP address (this is important if the BES Client changes IP addresses through DHCP), get the BES Server time, and get the BES Server version. If this setting is set too high, the BES Client may not receive UDP "pings" that tell it to gather the latest sites when new actions or new Fixlet content is available. If this setting is set too low, the BES Client will flood the BES Server with registration requests.

• Default Value: 21600 (6 Hours)


• Setting Type: Numeric (Seconds)


• Value Range: 1-82800 (23 Hours)


• Task Available: No

Normally, BES Clients will contact their BES Relay to receive downloads from the internet. This setting forces the BES Client to download files directly from the internet using the url specified. This setting takes precedence over other download settings.

• Default Value: 0 (False)


• Setting Type: Boolean


• Value Range: 1 (True) - download from the Internet
  0 (False) - download normally


• Task Available: No

When the BES Client fails to download a file from the BES Server or BES Relay, it can attempt to download the file directly from the Internet. Note: if there is a proxy in your network that blocks unauthenticated access to the Internet, turning this setting to 1 (True) may not work.

• Default Value: 0 (False)


• Setting Type: Boolean


• Value Range: 1 (True) - download from the Internet on failure
  0 (False) - do not download from Internet on failure


• Task Available: No

When set to 0, the BES Client will download files directly from the main BES Server if it can't find a BES Relay. When set to 1, the BES Client will not attempt to collect downloads from the main BES Server.

• Default Value: 0


• Setting Type: Numeric (Minutes)


• Value Range: 1 (True) - Bypass main BES Server
  0 (False) - Failover to main BES Server


• Task Available: No

When the BES Client fails to download a file from the BES Server or a BES Relay during an action, it will wait for the specified amount of time then try again. After each failed attempt, it will double the retry time.

• Default Value: 1


• Setting Type: Numeric (Minutes)


• Value Range: 0-480 (8 Hours)


• Task Available: No

When the BES Client fails to download a file from the BES Server or a BES Relay during an action, it will retry the specified number of times (each time it will double the amount of time it waits to retry).

• Default Value: 6


• Setting Type: Numeric (retry limit)


• Value Range: 0-100


• Task Available: No

The BES Client can simultaneously download two files at a time by using one "main channel" and one "thin channel". The main channel is used for all downloads, but if the main channel is currently downloading a large file, the thin channel can be used to download smaller files if the download size is less than the specified threshold. If this setting is set high, the BES Client will use the thin channel to download larger files, which could slow down actions because two large files may be downloading at the same time (each using half the bandwidth) instead of one file after the other. If this setting is set low, the thin channel will only be used for very small file downloads.

• Default Value: 500,000


• Setting Type: Numeric (bytes)


• Value Range: 1-100,000,000 (Set to 0 to disable the thin channel)


• Task Available: No

The BES Client can "throttle" the download speed by limiting the amount of bytes it downloads per second. This setting is especially effective if network bandwidth is a concern (such as with a dial-up connection). If the BES Server or BES Relay is also set to use throttling, the lower of the two values will be used as the download speed.

• Default Value: 0 (disabled)


• Setting Type: Numeric (bytes/second)


• Value Range: 0-4,294,967,296 (Set to 0 to disable download throttling)


• Task Available: Yes

When the BES Client is downloading a file from the BES Server or BES Relay, it sometimes will experience some inactivity because of network problems, disconnections, etc. When there is inactivity, the BES Client will wait for the specified number of seconds to receive more data before aborting the download.

• Default Value: 300 (5 minutes)


• Setting Type: Numeric (seconds)


• Value Range: 0-4,294,967,296


• Task Available: No

When the BES Clients are performing an action, they will send reports of the status of the action (Evaluating, Waiting, Running, Fixed, etc.). This setting controls the minimum number seconds between sending reports. If this number is too high, the BES Clients will take a long time update their action status. If this number is too low, it will put extra load on the BES Server to process the extra action status reports.

• Default Value: 15


• Setting Type: Numeric (seconds)


• Value Range: 1-3600 (1 hour)


• Task Available: No

If users are allowed to postpone running an action a dialog will appear on the BES Client computer asking the user how long they want to postpone the action. After some amount of time the action will automatically be postponed and the dialog will close. This setting controls the length of time to display the postponement dialog.

• Default Value: 120 (2 min)


• Setting Type: Numeric (seconds)


• Value Range: 0-21600 (6 hours)


• Task Available: No

This setting controls the title of the action postponement dialog that appears on BES Client computers for actions that can be postponed by users. By default the title is 'Reminder'.

• Default Value: Reminder


• Setting Type: String


• Value Range: N/A


• Task Available: No

This setting will disable the use of any inspectors that make calls to the Windows WMI. WMI has been found to cause problems on some computers, especially older versions of Windows (95 and 98). Problems include high CPU usage and 'blue screen' crashing of Windows. WMI is used by some some optional retrieved properties.

• Default Value: 0


• Setting Type: Boolean


• Value Range: 1 (True) - WMI inspectors disabled
  0 (False) - WMI inspectors enabled


• Task Available: No

String(s) residing in the key X which are to be ignored by the BES Client when determining if a restart is needed.

Note: The strings must be separated by semicolons and the last string must have a terminating semicolon (for example "exclude1;exclude2;exclude3").
Also Note: the strings are case sensitive.

• Default Value: blank


• Setting Type: String


• Value Range: N/A


• Task Available: No

This configuration setting will enable BES Clients to display non-English messages if the translation files are in place (BES 6.0+).

• Default Value: 1 (enabled)


• Setting Type: Boolean


• Value Range: 1 (enable), 0 (disable)


• Task Available: Yes

This configuration setting will remind users periodically that they have actions to run that they have postponed (BES 6.0+).

• Default Value: 0 (disabled)


• Setting Type: Boolean


• Value Range: 1 (enable), 0 (disable)


• Task Available: Yes

A value of 1 will cause the client to handle restart and shutdown operations in a forceful way that will not give applications the opportunity to cancel the operation. Terminal services systems should always have this set to 1.

• Default Value: 0 (disabled)


• Setting Type: Boolean


• Value Range: 1 (enable), 0 (disable)


• Task Available: No

This configuration setting will determine whether or not message boxes will have an entry in the Windows task bar (BES 6.0+).

• Default Value: 0 (disabled)


• Setting Type: Boolean


• Value Range: 1 (enable), 0 (disable)


• Task Available: Yes

When this configuration setting is enabled, computers will poll their parent relay for UDP commands they may have missed (BES 6.0+).

• Default Value: 0 (disabled)


• Setting Type: Boolean


• Value Range: 1 (enable), 0 (disable)


• Task Available: Yes

This configuration setting determines how often the BES Client will check with its BES Relay for any gathers or refreshes, if the "_BESClient_Comm_CommandPollEnable" setting is enabled. Avoid setting this to be less than 900 seconds due to performance implications (BES 6.0+).

• Default Value: 900


• Setting Type: Numeric (seconds)


• Value Range: 60-31536000 (1 Year)


• Task Available: Yes

This configuration setting sets the BES Client download cache limit (BES 6.0+).

• Default Value: 20


• Setting Type: Numeric (MB)


• Value Range: 0-4294967295


• Task Available: No

This configuration setting sets the Utility cache limit (BES 6.0+).

• Default Value: 10


• Setting Type: Numeric (MB)


• Value Range: 0-4294967295


• Task Available: No

This configuration setting enables a BES 6.0 Client to gather from a BES 5.1 Relay for troubleshooting purposes (BES 6.0+).

• Default Value: 0 (disabled)


• Setting Type: Boolean


• Value Range: 1 (enable), 0 (disable)


• Task Available: No

When a BES Client receives a UDP message but is too busy processing a relevance clause, this BES 6.0 configuration setting determines the length of time the BES Client will wait before it stops evaluating the relevance clause to deal with the UDP message.

• Default Value: 60


• Setting Type: Numeric (seconds)


• Value Range: 0-82800 (23 Hours)


• Task Available: Yes

The BES Relay selection algorithm will run this often. If a closer BES Relay is found, the closer BES Relay will be used. Note that if the BES Relay selection is failing, this interval is ignored.

• Default Value: 21600 (6 hours)


• Setting Type: Numeric (number of seconds)


• Value Range: 0-31,536,000 (1 year)


• Task Available: Yes

If the BES Relay selection algorithm fails (no BES Relays are found), the BES Client will try again after this many seconds. The BES Client will double this value on each successive retry that fails to locate a BES Relay.

• Default Value: 60


• Setting Type: Numeric (number of seconds)


• Value Range: 0-31,536,000 (1 year)


• Task Available: Yes

After failing to find a BES Relay, the BES Client will continue to try to find a BES Relay. Each time it fails, the BES Client will double the time it spends until this maximum is exceeded. Then the BES Client will try with this maximum retry interval until it successfully selects a BES Relay.

• Default Value: 7200 (2 Hours)


• Setting Type: Numeric (Seconds)


• Value Range: 0-31,536,000 (1 year)


• Task Available: Yes

The maximum number of network hops (Time To Live) a BES Client will search over before considering its automatic relay selection attempt a failure. A BES Client will only be able to find BES Relays that are less then the maximum number of network hops away from the BES Client. This setting can be used to limit the ICMP traffic generated by the automatic relay selection algorithm.

• Default Value: 255


• Setting Type: Numeric


• Value Range: 1-255


• Task Available: Yes

During the automatic relay selection algorithm, the BES Client will wait this long between each iteration. On each iteration the BES Client sends ICMP packets with a TTL greater then the last iteration. This setting can be used to slow down the automatic relay selection algorithm and reduce the network traffic generated.

• Default Value: Default Value: 200 (MicroSeconds)


• Setting Type: Setting Type: Numeric


• Value Range: Value Range: 0-1,000,000 (1 Second)


• Task Available: Task Available: No

This setting controls the time interval that the BES Client will ignore communications errors before performing BES Relay selection. Once a BES Relay has been selected and the BES Client has successfully registered, it will ignore errors when it attempts to post its results to the BES Relay or BES Server for this long before deciding to choose another BES Relay.

• Default Value: 600 (10 Minutes)


• Setting Type: Numeric (Seconds)


• Value Range: 0-21,600 (6 Hours)


• Task Available: Yes

This setting determines what the BES Client will do in the event that no BES Relays respond to TTL pings up to the maximum configured distance. In this event, the BES Client will attempt to register with the defined failover BES Relay before trying the BES Server. This setting was first introduced in BES 5.1.
Note: This format is the same as for the settings __RelayServer1 and __RelayServer2. For example:http://servername:port/bfmirror/downloads/

• Default Value: None


• Setting Type: String (Failover Relay)


• Value Range: Registration URL


• Task Available: No

If the BES Relay is using a DNS name that is not accessible by all BES Clients, an override can be used. If this value is set on the BES Relay computer, it will return this setting for the dns name inspector, which will be reported to the BES Server and used by other BES Clients to locate the BES Relay. You can also use this value if you want your BES Clients to locate their relays by IP address, rather than DNS name lookup. For example, if the BES Relay is reported at relay1:52311, you can use this setting to make the BES Relay be accessible at relay1.company.com:52311 or even 192.168.100.123:52311. (Note: this value needs only to be set on the one BES Relay computer and not on all the BES Client computers.)

• Default Value: None


• Setting Type: String (override name)


• Value Range: hostname OR ipaddress (do not include port number)


• Task Available: Yes

Setting this setting to 0 will cause the BES Client to only use the BES Relay system to collect downloads and all other interactions will interact directly with the main BES Server. This setting is provided in order to allow a configuration where the load on a BES Relay does not significantly change from the 3.x BES Relay implementation. Note that the BES Clients with this setting of 0 will not manage their BES Relays configuration automatically. BES Clients with this setting will ignore the automatic configuration setting and will collect downloads from their primary and then secondary BES Relays.

• Default Value: 1 (True)


• Setting Type: Boolean


• Value Range: 1 (True) - All BES Client communications will go through the BES Relay
  0 (False) - Only download files from the BES Relay (all other network transactions will use the BES Server)


• Task Available: No

Setting this setting to 1 will cause the BES Client to poll for new gathers or refreshes. Please refer to the setting _BESClient_Comm_CommandPollIntervalSeconds for the timing of the poll. Setting this to a value of 0 will disable this mechanism. This setting was first added in BES 6.0.

• Default Value: 0 (False)


• Setting Type: Boolean


• Value Range: 1 (True) - The BES Client will check with its BES Relay for any new gathers or refreshes
  0 (False) - The BES Client will not check with its BES Relay for any new gathers or refreshes


• Task Available: No

This setting determines how often the BES Client will check with its BES Relay for any new gathers or refreshes. It must be enabled with the setting _BESClient_Comm_CommandPollEnable

• Default Value: 0 (disabled)


• Setting Type: Numeric (Seconds)


• Value Range: 0-82800 (23 Hours)


• Task Available: No

This configuration setting will enable the BES Gather debug log that will give information about the BES Gather activity. The higher the level of detail, the greater the detail of the messages that are put into the file and/or NT event log.

• Default Value: 0 (disabled)


• Setting Type: Numeric (detail level)


• Value Range: 0-100


• Task Available: No

Full path to file that stores activity messages. If empty string and the computer is not Win9x, activity messages are added to the NT event log. Note: The _BESClient_EMsg_Detail setting must be greater than 0 to use this option.

• Default Value: blank


• Setting Type: String (full path)


• Value Range: N/A


• Task Available: No

The BES Gather service has two methods of communication over the network. The first method uses the Windows URL Monikers API, which is a higher-level network interface that uses the computer's Internet connection settings (such as proxy settings, security settings, etc.). The second method uses the winsock API, which is a lower-level direct socket access layer that doesn't use the computer's Internet connection settings. URL Monikers are used by default to connect to the Internet using the Internet connection settings. Using winsock will allow BES Gather to connect to the Internet without using the Internet connection settings.

• Default Value: BES Server: 1 (True)
  BES Relay: 0 (False)


• Setting Type: Boolean


• Value Range: 1 (True) - use URL Monikers
  0 (False) - use Winsock


• Task Available: No

When a file is requested from the BES Relay, it can either download the file from the BES Server or download the file directly from the Internet. If this setting is set to 1 (True), then the BES Relay will first attempt to download the file from the BES Server. Note: This setting should stay at 0 (False) for the BES Server.

• Default Value: BES Server: 0 (False)
  BES Relay: 1 (True)


• Setting Type: Boolean


• Value Range: 1 (True) - Check the BES Server first to download the file
  0 (False) - Do not check the BES Server when to download the file


• Task Available: No

When a file is requested from the BES Relay, it can download the file directly from the Internet instead of from the BES Server. If this setting is set to 1 (True), then the BES Relay will first attempt to connect to the BES Server (if the _BESGather_Download_CheckParentFlag is set to 1) then directly connect to the Internet if the download from the BES Server fails. Note: This setting should stay at 1 (True) for the BES Server.

• Default Value: BES Server: 1 (True)
  BES Relay: 0 (False)


• Setting Type: Boolean


• Value Range: 1 (True) - Download the file directly from the Internet
  0 (False) - Do not download the file directly from the Internet


• Task Available: No

BES Gather will cache downloaded files on the BES Server or BES Relay computer so that the file will not need to be downloaded again if the action is reissued. This setting will specify how many MB to cache before overwriting the old files. When the cache is full, the least recently used files will be replaced.

Note: This caching number applies to both cached files and cached action folders so the total space that the BES Relay will take up is actually 2x cache size (by default this is 2 GB).

• Default Value: 1024


• Setting Type: Numeric (MB)


• Value Range: 1-4,294,967,296


• Task Available: Yes

When BES Gather fails to download a file from the Internet or its parent during an action, it will wait for the specified amount of time then try again. After each failed attempt, it will double the retry time.

• Default Value: 1


• Setting Type: Numeric (minutes)


• Value Range: 0-1440 (24 hours)


• Task Available: No

When BES Gather fails to download a file from the Internet or its parent during an action, it will retry the specified number of times (each time it will double the amount of time it waited to retry the last time).

• Default Value: 6


• Setting Type: Numeric (retry limit)


• Value Range: 0-100


• Task Available: No

BES Gather can simultaneously download two files at a time by using one "main channel" and one "thin channel". The main channel is used for all downloads, but if the main channel is currently downloading a large file, the thin channel can be used to download smaller files if the download size is less than the specified threshold. If this setting is set high, BES Gather will use the thin channel to download larger files, which could slow down actions because two large files may be downloading at the same time (each using half the bandwidth) instead of one file after the other. If this setting is set low, the thin channel will only be used for very small file downloads.

• Default Value: 500,000


• Setting Type: Numeric (bytes)


• Value Range: 1-100,000,000 (Set to 0 to disable the thin channel)


• Task Available: No

BES Gather can "throttle" the download speed by limiting the amount of bytes it downloads per second. This setting is especially effective if network bandwidth is a concern (such as with a dial-up connection). When this setting is used on the BES Relay, the BES Relay will limit its download speed when downloading from the BES Server or parent BES Relay. When set on the BES Server, the BES Server will throttle downloading from the internet. As of BES 5.0, this setting throttles all downloading traffic.

• Default Value: 0 (disabled)


• Setting Type: Numeric (bytes/sec)


• Value Range: 0-4,294,967,296 (Set to 0 to disable download throttling and use the maximum possible bandwidth)


• Task Available: No

When the BES Gather service is downloading a file from the Internet or its parent, it sometimes will experience some inactivity because of network problems, disconnections, etc. When there is inactivity, BES Gather will wait for the specified number of seconds to receive more data before aborting the download.

• Default Value: 300 (5 minutes)


• Setting Type: Numeric (seconds)


• Value Range: 0-4,294,967,296 (Set to 0 to disable time-out mechanism)


• Task Available: No

A value of "0" makes the BES Relay unavailable for auto seletion after the next actionsite propagation. A value of "1" allows the BES Relay to be used by BES Clients for auto selection.

• Default Value: 1 (enabled)


• Setting Type: Boolean


• Value Range: 1 (True) - Enable Auto Selection
  0 (False) - Disable Auto Selection


• Task Available: No

Maximum number of clients the BES relay will allow to register. Once this limit is reached, connections will be rejected.

• Default Value: 0 (no limit)


• Setting Type: Numeric (number of BES Clients)


• Value Range: 0-65536


• Task Available: No

Maximum allowed number of BES Clients that are BES Relays. This limit is calculated independently of the MaxChildCount -- it can be used to keep a BES Relay from indirectly acquiring a lot of BES Clients by picking up too many children that are BES relays.

• Default Value: 0 (no limit)


• Setting Type: Numeric (number of BES Clients)


• Value Range: 0-65536


• Task Available: No

A non-zero value will enable verbose logging on the BES Relay for troubleshooting purposes. This setting increases the information written to the existing logfile.txt and should not be left on during normal operation.

• Default Value: 0 (disabled)


• Setting Type: Boolean


• Value Range: 1 (True) - Enable Verbose Logs
  0 (False) - Disable Verbose Logs


• Task Available: No

Maximum number of simultaneous connections, once this limit is reached, connections will be rejected.

• Default Value: 1024


• Setting Type: Numeric (number of threads)


• Value Range: 1-65536


• Task Available: No

'Global' throttling on outgoing data to BES Clients from the BES Relay/Server (0 means no limit). If its value is 1000 and there are 100 clients downloading simultaneously, the BES Relay/Server will send data to each BES Client at 10kbps (for a total of 1000kbps). Throttling is implemented by sending a chunk of data at full speed, and then waiting chunksize/kbps seconds before sending the next chunk so if all requests are smaller than the chunk size, then there may be no throttling at all. Uploaded data to other BES Relays/Server is not throttled by this setting (PostResults data).

• Default Value: 0 (disabled)


• Setting Type: Numeric (kbps)


• Value Range: 1-65536


• Task Available: Yes

The BES Relay accumulates reports from the BES Clients and then compresses them and sends them to the parent BES Relay or BES Server. This setting sets the maximum number of reports in each compressed report. Results are forwarded once the ResultCountLimit or ResultTimeLimit is reached. Setting a low value will cause more network traffic with increased response time. A higher value will result in less network traffic with slower response time.

• Default Value: 500


• Setting Type: Numeric (Number of results)


• Value Range: 1-4,294,967,296


• Task Available: No

The BES Relay accumulates reports from the BES Clients and then compresses them and sends them to the parent BES Relay or BES Server after waiting a specified amount of time. This setting sets the amount of time to wait before sending the reports. The longer the wait, the more latency before the BES Server receives the reports from the BES Clients, but the greater the efficiency of the system (lower network traffic).

• Default Value: 3


• Setting Type: Numeric (Number of seconds)


• Value Range: 1-4,294,967,296


• Task Available: No

If set a connection log will be written to this path. A new log file will be created each day with the days date as teh name of the file. Connection logs can get quite big, gigabytes per day, so this setting should only be used for troubleshooting purposes.

• Default Value: none


• Setting Type: String (Path)


• Value Range: N/A


• Task Available: No

Sets the number of days to keep connection logs for. After this many days the older connection logs will be deleted.

• Default Value: 3


• Setting Type: Numeric


• Value Range: 1-4,294,967,296


• Task Available: No

A BES Relay can be set up to use a proxy server when downloading files. This could be useful if their is a proxy between the BES Relay and the BES Server or if the BES Relay is connecting directly to the internet for downloads and must use a proxy. This setting controls the username used to authenticate with the proxy if the proxy requires authentication.

• Default Value: None


• Setting Type: String (username)


• Value Range: N/A


• Task Available: No

A BES Relay can be set up to use a proxy server when downloading files. This could be useful if their is a proxy between the BES Relay and the BES Server or if the BES Relay is connecting directly to the internet for downloads and must use a proxy. This setting controls the password used to authenticate with the proxy if the proxy requires authentication. Warning: The password will be stored in plain text within the registry.

• Default Value: None


• Setting Type: String


• Value Range: N/A


• Task Available: No

A BES Relay can be set up to use a proxy server when downloading files. This could be useful if their is a proxy between the BES Relay and the BES Server or if the BES Relay is connecting directly to the internet for downloads and must use a proxy. This setting controls the hostname used to reach the proxy.

• Default Value: None


• Setting Type: String


• Value Range: N/A


• Task Available: No

A BES Relay can be set up to use a proxy server when downloading files. This could be useful if their is a proxy between the BES Relay and the BES Server or if the BES Relay is connecting directly to the internet for downloads and must use a proxy. This setting controls the port used by the proxy server.

• Default Value: None


• Setting Type: String


• Value Range: N/A


• Task Available: No

This setting controls the number of UDP pings the BES Relay will send before delaying for a period of time. The length of the delay is controlled by _BESRelay_ClientRegister_BatchDelay. This setting could be used to limit the rate at which a BES Relay sends out UDP pings if this network traffic is harmful in some way.

• Default Value: 100


• Setting Type: Numeric (number of pings)


• Value Range: 1-4,294,967,296


• Task Available: No

This setting controls how long the BES Relay will wait between sending out a batch of UDP pings to BES Clients. This setting could be used to limit the rate at which a BES Relay sends out UDP pings if this network traffic is harmful in some way.

• Default Value: 1000


• Setting Type: Numeric (Milliseconds)


• Value Range: 1-4,294,967,296


• Task Available: No

This setting is used to control the maximum length a chain of BES Relays can extend. The setting prevents circular chains of BES Relays from forming by automatic BES Relay selection. This setting could be used to stop long chains of BES Relays from forming or create a maximum depth a BES Relay can be from the BES Server.

• Default Value: 32


• Setting Type: Numeric


• Value Range: 1-4,294,967,296


• Task Available: No

This setting controls how quickly BES Relays mark BES Clients as expired. BES Clients have this length of time to register again before their license is made available for use by another BES Client. This setting could be used to increase the rate at which licenses are transfered from offline BES Clients to active BES Clients when the total number of clients gets above the license seat count.

• Default Value: 1440 (1 Day)


• Setting Type: Numeric (Minutes)


• Value Range: 1-4,294,967,296


• Task Available: No