List of settings and detailed descriptions
Some of the configuration settings are commonly used and they have tasks already documented in the BigFix Support site for your assistance. If such a task exists, it is indicated along the Task available ? row in the tables which you can use. If no task exists, create the configuration setting manually.
Making a configuration setting
You can make a configuration setting in two ways: through the BES Console or manually on the endpoint.
- Open the BES console and navigate to the Computer section under the All Content domain.
- Select the computer(s) to which you want to apply the configuration settings. Note: To change a configuration setting for the server or relays using this mechanism, you must select the computer(s) that have the server or relays installed.
- Right-click the computer(s) and choose Edit Computer Settings.
- Create a custom setting using a Name and Value pair from the configuration table.
- Click OK to send the configuration setting through an action named
Change Multiple Settings or a similar one.
The setting takes effect after the action is complete.
- View the computer's updated setting. To view the updates, right-click the computer and select Edit Computer Settings or click the computer in the computer list and then select the Summary tab. Then, scroll down to the Client Settings section.
Manually on a Windows endpoint
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\BigFix\EnterpriseClient\Settings\Client
. To
update the settings, do the following steps: - Create a key at the registry location and give it a name.
- Create a string value (REG_SZ type) named value within the key.
- Set the value data within the value.
Manually on a Mac endpoint
On MacOS, you can manually change your BigFix Client settings from the command line.
sudo /Library/BESAgent/BESAgent.app/Contents/MacOS/BESAgentControlPanel.sh -stop
sudo "/Library/BESAgent/BESAgent.app/Contents/MacOS/BESAgent" -setSettings "/path/to/file.json"
sudo /Library/BESAgent/BESAgent.app/Contents/MacOS/BESAgentControlPanel.sh -start
{
"client_settings": [
{
"key":"setting1",
"value":"1"
},
{
"key":"setting2",
"value":"setting value 2"
}
]
}
Description, values, and references
- Plugin Portal
- Inspector behavior
- Action execution
- Action management
- Archiving client files
- Gathering content
- Deployment Encoding
- Logging
- CPU Usage
- Proxy agent
- Proxy configuration
- Registration
- Client notification
- Communication
- Download
- Reports management
- Query
- Application Usage Collection
- Bandwidth throttling
- Airgap Mode
- HTTP server
- Relay diagnostics
- User authentication
- Web Reports
- Deployment Telemetry
- UI History
- Relays in DMZ
- Peer to peer mode
- Miscellaneous
For information related to parallel FillDB configuration, see Configuring parallel FillDB.
Plugin Portal
Name/Description | References | Values | Component(s) affected | Version(s) applicable | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
The Plugin Portal |
|
Plugin Portal | 10 and later | ||||||||||
|
The Plugin Portal |
|
Plugin Portal | 10 and later | ||||||||||
|
|
Plugin Portal | 10 and later | |||||||||||
|
|
Plugin Portal | 10 and later | |||||||||||
|
The Plugin Portal |
|
Plugin Portal | 10 and up to Patch 8 | ||||||||||
|
The Plugin Portal |
|
Plugin Portal | 10 and up to Patch 8 | ||||||||||
|
The Plugin Portal |
|
Plugin Portal |
10 Patch 1 and later |
||||||||||
|
Custom Site management |
|
Plugin Portal |
10 Patch 4 and later |
||||||||||
|
The Plugin Portal |
|
Plugin Portal |
10 Patch 8 and later |
||||||||||
|
|
Plugin Portal |
10 Patch 12 and later |
Inspector behavior
Name/Description | References | Values | Component(s) affected | Version(s) applicable | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Active Directory property updating |
|
Client | All | ||||||||||
|
|
Client | 9.5.9 and later | |||||||||||
|
|
Client | All | |||||||||||
|
Problems experienced when attempting to start the Unix/Linux BigFix Client after installation Stopping the BESClientUI from running on every local user session on a Citrix Server |
|
Client | All | ||||||||||
_BESClient_Inspector_DisableWMI 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 optional retrieved properties. |
High Disk I/O and/or CPU on the client related to WMI queries |
|
Client | 9.2 and later |
Action execution
Name/Description | References | Values | Component affected | Version(s) applicable | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Prefetch plug-in took too long |
|
Client | All | ||||||||||||
|
|
Client | 9.5.7 and later | |||||||||||||
|
User interface process unable to launch |
|
Client | All | ||||||||||||
|
|
Client | 9.5.3 and later | |||||||||||||
|
Determining if a restart is needed |
|
Client | All | ||||||||||||
|
|
Client | All |
Action management
The settings described in this section are made on the BigFix Client to configure how actions are run locally.
Settings affecting data download on the Client
Whenever an action requiring the download of one or more than one files is taken, the target agent prevents the action from running on the client if the total size of the downloads associated to the action exceeds the value set in _BESClient_Download_SizeLimitMB, and the Client is not connected to a preferred relay.
The Client installed on the Server and the Client/Relay do not consider the setting _BESClient_Download_SizeLimitMB, allowing always the download (on the Relay/Client the condition is true when the Relay is active).
The connected relay is a preferred relay if:
- The relay selection associated to the Client is the Manual Relay Selection, and the connected relay is the primary or the secondary relay.
- The relay selection associated to the Client is the Automatic Selection with Affiliation, and the connected relay is member of an affiliation group belonging to the affiliation list. The number of affiliation groups belonging to the affiliation list can be configured using the setting _BESClient_PreferredRelay_MaxAffiliationsToCheck. The special affiliation group "*" is never used for setting a preferred relay.
- The connected relay is either in the same sub-network of the client, or the number of network hops from the Client to the relay is lower than the value configured in the setting _BESClient_PreferredRelay_MaximumHopCount. In this case there is no dependency from the relay association method selected on the Client.
Name/Description | References | Values | Component(s) affected | Version(s) applicable | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|
Client | 9.5.9 and later | |||||||||||
|
|
Client | 9.5.9 and later |
Settings affecting wait and waithidden commands on the client
You can use the wait command, as part of an action, to wait for the completion of a specific process or program before continuing with the next actionscript command. You can also use the waithidden command to run the process or program in a hidden window. When defining the wait command, you can optionally specify an override section to change some of the default behaviors, represented by keywords, that are applied at runtime on the target Clients. If you do so the different behavior applies only to the program or process triggered by that wait or waithidden command on all the clients where the action runs. The settings listed in the following table allow you to define the default behavior for timeout and disposition on a specific client for all the programs or processes triggered by any wait or waithidden commands, unless it is specified differently in an override section of that specific wait or waithidden command definition.
Name/Description | References | Values | Component(s) affected | Version(s) applicable | ||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|
Client | 9.5.11 and later | |||||||||
|
|
Client | 9.5.11 and later |
Archiving client files
This allows the BigFix Administrator to automatically log data from specific managed computers.
For details, see Archiving Client files on the BigFix Server.
For detailed description about Archive Manager, see Archive Manager.
Name/Description | References | Values | Component(s) affected | Version(s) applicable | ||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Archive Manager |
|
Client | 9.2 and later | ||||||||
|
Archive Manager |
|
Client | 9.2 and later | ||||||||
|
Archive Manager |
|
Client | 9.2 and later | ||||||||
|
Archive Manager |
|
Client | 9.2 and later | ||||||||
|
Archive Manager |
|
Client | 9.2 and later |
The PostFile program receives the chunks of files posted by the Upload Manager and appends them to its own copy of the file. The Upload Manager specifies the range of bytes being posted and the sha1 of the file, which is used as the filename. For details about the configuration settings related to this component, see Post File in BigFix Configuration Settings.
For details, see PostFile.
Name/Description | References | Values | Component(s) affected | Version(s) applicable | ||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Bandwidth throttling |
|
Relay, Root server | 9.2 and later | ||||||||
|
Bandwidth throttling |
|
Relay, Server | 9.2 and later |
The Upload Manager coordinates the sending of files in chunks to the Post File program. You can throttle the upload dataflow to conserve bandwidth. The file system uses 64-bits, sufficient for file sizes of up to 264 – 1 bytes in length.
_BESRelay_UploadManager_BufferDirectoryMaxSize
and
_BESRelay_UploadManager_BufferDirectoryMaxCount
described in the following table to
limit the disk space usage.Name/Description | References | Values | Component(s) affected | Version(s) applicable | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Upload Manager |
|
Relay, Root server | 9.5 and later | ||||||||||
|
Upload Manager |
|
Client | 9.2 and later | ||||||||||
|
Upload Manager |
|
Client | 9.2 and later | ||||||||||
|
Upload Manager |
|
Client | 9.2 and later | ||||||||||
|
Upload Manager |
|
Relay, Root server | 9.2 and later | ||||||||||
|
Upload Manager |
|
Relay, Root server | 9.2 and later | ||||||||||
|
Upload Manager |
|
Relay, Root server | 9.2 and later | ||||||||||
|
Upload Manager |
|
Relay, Root server | 9.2 and later | ||||||||||
|
Upload Manager |
|
Relay, Root server | 9.2 and later | ||||||||||
|
Upload Manager |
|
Relay, Root server | 9.2 and later | ||||||||||
|
Upload Manager |
|
Relay, Root server | 9.2 and later |
Gathering content
Name/Description | References | Values | Component(s) affected | Version(s) applicable | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|
Relay | 9.5.7 and later | |||||||||||
|
|
Relay | 9.5.7 and later | |||||||||||
|
|
Relay | 9.5.7 and later | |||||||||||
|
|
Relay | 9.2 and later | |||||||||||
|
Relay downloads patch from Internet directly instead of gathering from BigFix Server How to have Relays download content directly from the Internet |
|
Server, Relay | 9.2 and later | ||||||||||
|
Relay downloads patch from Internet directly instead of gathering from BigFix Server How to have Relays download content directly from the Internet |
|
Server, Relay | 9.2 and later | ||||||||||
|
|
Server, Relay | 9.2 and later | |||||||||||
|
|
Server, Relay | 9.2 and later | |||||||||||
|
|
Server, Relay | 9.2 and later | |||||||||||
|
|
Server, Relay | 9.2 and later | |||||||||||
|
|
Server, Relay | 9.2 and later | |||||||||||
|
|
Server, Relay | 9.5.7 and later | |||||||||||
|
|
Server, Relay, Agent | 9.2 and later |
Name/Description | References | Values | Component(s) affected | Version(s) applicable | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Customizing HTTPS for Gathering |
|
Server | 9.5 and later | ||||||||||
|
Customizing HTTPS for Gathering |
|
Server | 9.5 and later |
Deployment Encoding
Name/Description | References | Values | Component(s) affected | Version(s) applicable | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|
Client, Server | All |
Logging
Name/Description | References | Values | Component(s) affected | Version(s) applicable | ||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Data Collection: BigFix Client |
|
Client | 9.2 and later | ||||||||
|
Data Collection: BigFix Client |
|
Client | 9.2 and later | ||||||||
|
Data Collection: BigFix Client |
|
Client | 9.2 and later | ||||||||
|
Data Collection: BigFix Client |
|
Client | 9.2 and later | ||||||||
|
Data Collection: BigFix Client |
|
Client | 9.2 and later | ||||||||
|
Enabling debug/verbose logging for the BES Root Server and BES Relay services |
|
Relay | |||||||||
|
|
Client | 9.2 and later |
Name/Description | References | Values | Component(s) affected | Version(s) applicable | ||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|
Server components | All | |||||||||
|
Server audit logs |
|
BigFix Server | All | ||||||||
|
|
BigFix Administration Tool |
10 Patch 8 |
|||||||||
|
|
BigFix Administration Tool |
10 Patch 8 |
CPU Usage
Name/Description | References | Values | Component(s) affected | Version(s) applicable | ||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|
Client | All | |||||||||||||||||||||||||||||||||||||||||
|
How should I configure the Bigfix Client to run on an virtual server that hosts multiple images? |
|
Client | All | ||||||||||||||||||||||||||||||||||||||||
|
Configuring Client CPU Utilization |
|
Client | All | ||||||||||||||||||||||||||||||||||||||||
|
How should I configure the Bigfix Client to run on an virtual server that hosts multiple images? |
|
Client | All | ||||||||||||||||||||||||||||||||||||||||
|
Virtualized environments and virtual machines |
|
Client | All | ||||||||||||||||||||||||||||||||||||||||
|
Virtualized environments and virtual machines |
|
Client | All | ||||||||||||||||||||||||||||||||||||||||
|
Virtualized environments and virtual machines |
|
Client | All | ||||||||||||||||||||||||||||||||||||||||
|
|
Client | All | |||||||||||||||||||||||||||||||||||||||||
|
|
Client | All | |||||||||||||||||||||||||||||||||||||||||
|
|
Client | All | |||||||||||||||||||||||||||||||||||||||||
|
|
Client | All | |||||||||||||||||||||||||||||||||||||||||
|
|
Client | All | |||||||||||||||||||||||||||||||||||||||||
There are six values of
BESClient_Resource_PowerSaveTimeoutX
(where X ranges from 0 to 5) that control how
many minutes the client sleeps; they will be applied based on
both Network and Power Supply conditions.
In cases where the network is "Connected", if there is at
least one network interface with internet connection, the
battery power is evaluated as follows:
Note:
|
||||||||||||||||||||||||||||||||||||||||||||
|
Virtualized environments and virtual machines |
|
Client | All | ||||||||||||||||||||||||||||||||||||||||
|
Virtualized environments and virtual machines |
|
Client | All | ||||||||||||||||||||||||||||||||||||||||
|
Virtualized environments and virtual machines |
|
Client | All | ||||||||||||||||||||||||||||||||||||||||
|
Virtualized environments and virtual machines |
|
Client | All | ||||||||||||||||||||||||||||||||||||||||
|
Virtualized environments and virtual machines |
|
Client | All | ||||||||||||||||||||||||||||||||||||||||
|
Virtualized environments and virtual machines |
|
Client | All | ||||||||||||||||||||||||||||||||||||||||
|
Query |
|
Client | 9.5 and later | ||||||||||||||||||||||||||||||||||||||||
|
|
Client | 9.5 and later | |||||||||||||||||||||||||||||||||||||||||
|
|
Client |
10 Patch 2 |
|||||||||||||||||||||||||||||||||||||||||
|
|
Client |
10 Patch 2 |
Proxy agent
Name/Description | References | Values | Component(s) affected | Version(s) applicable | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|
Proxy agent | From 9.5.16 |
Proxy configuration
Name/Description | References | Values | Component(s) affected | Version(s) applicable | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Setting up a proxy connection on a client |
|
Client | All | ||||||||||||
|
Setting up a proxy connection on a client |
|
Client | All | ||||||||||||
|
Setting up a proxy connection on a client |
|
Client | All | ||||||||||||
|
Setting up a proxy connection on a client |
|
Client | All | ||||||||||||
|
Setting up a proxy connection on a client |
|
Client | All | ||||||||||||
|
Setting up a proxy connection on a client |
|
Client | All | ||||||||||||
|
Setting up a proxy connection on a client |
|
Client | All | ||||||||||||
|
Setting up a proxy connection on a client |
|
Client | All | ||||||||||||
|
Setting up a proxy connection on a client |
|
Client | All |
Name/Description | References | Values | Component(s) affected | Version(s) applicable | ||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Setting up a proxy connection on a relay Configuration of Microsoft Azure Cloud Plugin with proxy BigFix server cannot gather external sites (error: 17NotASignedMessage) Software Distribution task fails with error "Unexpected HTTP Response 502" |
|
Server, Relay | 9.2 and later | ||||||||
|
Setting up a proxy connection on a relay Configuration of Microsoft Azure Cloud Plugin with proxy BigFix server cannot gather external sites (error: 17NotASignedMessage) |
|
Server, Relay | 9.2 and later | ||||||||
|
Setting up a proxy connection on a relay Configuration of Microsoft Azure Cloud Plugin with proxy BigFix server cannot gather external sites (error: 17NotASignedMessage) |
|
Server, Relay | 9.2 and later | ||||||||
|
Setting up a proxy connection on a relay Configuration of Microsoft Azure Cloud Plugin with proxy Best practices to consider when defining a proxy connection BigFix server cannot gather external sites (error: 17NotASignedMessage) |
|
Server, Relay | 9.2 and later | ||||||||
|
Best practices to consider when defining a proxy connection |
|
Relay, Server | 9.2 and later | ||||||||
|
Setting up a proxy connection on a relay |
|
Relay, Server | 9.2 and later | ||||||||
|
Setting up a proxy connection on a relay |
|
Relay, Server | 9.2 and later | ||||||||
|
|
Relay, Server | 9.2 and later |
Registration
Name/Description | References | Values | Component(s) affected | Version(s) applicable | ||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|
Client | 9.5.8 and later | |||||||||
|
What is the meaning of the message "skipping relay select. Registering with current relay" in BES Client Debug log? |
|
Client | All | ||||||||
|
Client could not register with the BigFix server successfully Reasons for large group of BigFix Clients failing to register and appear offline |
|
Client | 9.5.7 and later | ||||||||
|
How can I control client relay selection for a particular Relay or DSA Server? |
|
Relay | All | ||||||||
|
How can I control client relay selection for a particular Relay or DSA Server? |
|
Client | All | ||||||||
|
Proxy Configuration (Server/Relay) |
|
Relay, Server | All | ||||||||
|
|
Relay, Server | All |
Name/Description | References | Values | Component(s) affected | Version(s) applicable | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|
Client | 9.2.8 and later | |||||||||||||
|
What is the meaning of the message "skipping relay select. Registering with current relay" in BES Client Debug log? |
|
Client, Relay | All | ||||||||||||
|
|
Client | All | |||||||||||||
|
|
Client | All | |||||||||||||
|
Automatic relay selection in a high latency and/or high hop network is failing |
|
Client, Relay | All | ||||||||||||
|
Automatic relay selection in a high latency and/or high hop network is failing |
|
Client | All | ||||||||||||
|
Configuring relay failover |
|
Client | All | ||||||||||||
|
What manual Relay selection options do I have for my clients and Relays? |
|
Client | All | ||||||||||||
|
|
Client | All | |||||||||||||
|
|
Client | All | |||||||||||||
|
What manual Relay selection options do I have for my clients and Relays? |
|
Client | All |
Name/Description | References | Values | Component(s) affected | Version(s) applicable | ||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Why are my BigFix Clients not choosing their specified BigFix Relay? |
|
Relay | All | ||||||||
|
Viewing the relay chain on the client |
|
Client | 9.5.13 and later |
Name/Description | References | Values | Component(s) affected | Version(s) applicable | ||||||
---|---|---|---|---|---|---|---|---|---|---|
|
|
Relay | All | |||||||
|
|
Client | All |
Name/Description | References | Values | Component(s) affected | Version(s) applicable | ||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Logics about automatic relay selection |
|
Server, Relay | All | ||||||||
|
Logics about automatic relay selection |
|
Server, Relay | All |
Client notification
Name/Description | References | Values | Component(s) affected | Version(s) applicable | ||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Changing the gather interval for a BigFix Client via the command polling client settings |
|
Client | 9.2 and later | ||||||||
|
Changing the gather interval for a BigFix Client via the command polling client settings |
|
Client | 9.2 and later |
Name/Description | References | Values | Component(s) affected | Version(s) applicable | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|
Server, Client, Relay | 9.2 and later | |||||||||||
|
|
Server, Client, Relay | 9.2 and later | |||||||||||
|
|
Server, Client | 9.2 and later | |||||||||||
|
|
Client | 9.2 and later |
For detailed documentation on how to manage persistent TCP connections, see Persistent connections.
Name/Description | References | Values | Component(s) affected | Version(s) applicable | ||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Persistent connections |
|
Client | 9.5.11 and later | ||||||||
|
Persistent connections |
|
Relay | 9.5.11 and later | ||||||||
|
Persistent connections |
|
Relay | 9.5.11 and later | ||||||||
|
Persistent connections |
|
Relay | 9.5.11 and later | ||||||||
|
Persistent connections |
|
Relay | 9.5.11 and later | ||||||||
|
Persistent connections |
Note: The setting takes effect after the following
client registration.
|
Client | 9.5.11 and later |
Communication
Name/Description | References | Values | Component(s) affected | Version(s) applicable | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|
Client | 9.2 and later | |||||||||||
|
|
Client | 9.2 and later |
Name/Description | References | Values | Component(s) affected | Version(s) applicable | ||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Manual key exchange |
|
Relay | 9.2 and later | ||||||||
|
|
Relay | 9.2 and later | |||||||||
|
|
Relay |
10 Patch 7 |
Download
Name/Description | References | Values | Component(s) affected | Version(s) applicable | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Managing Downloads |
|
Client | 9.5.9 and later | ||||||||||
|
Customizing HTTPS for downloads |
|
Client |
10 Patch 8 |
||||||||||
|
Customizing HTTPS for downloads |
|
Client |
10 Patch 8 |
||||||||||
|
Managing Downloads |
|
Client | All | ||||||||||
|
Managing Downloads |
|
Client | All | ||||||||||
|
Managing Downloads |
|
Client |
10 Patch 1 |
||||||||||
|
Managing Downloads |
|
Client |
10 Patch 1 |
||||||||||
|
Managing Downloads |
|
Client |
10 Patch 7 |
||||||||||
|
Managing Downloads |
|
Client |
10 Patch 7 |
||||||||||
|
Managing Downloads |
|
Client | All | ||||||||||
|
|
Client | All | |||||||||||
|
Enabling data pre-cache |
|
Client | 9.5.10 and later | ||||||||||
|
|
Client | All | |||||||||||
|
|
Client | All | |||||||||||
|
BigFixTroubleshooting Downloads |
|
Client | All | ||||||||||
|
BigFixTroubleshooting Downloads |
|
Client | All | ||||||||||
|
|
Client | All | |||||||||||
|
BigFixTroubleshooting Downloads |
|
Client | All | ||||||||||
|
|
Client | All | |||||||||||
|
|
Client | All | |||||||||||
|
Download Status Report Clean-up |
|
Relay | All | ||||||||||
|
Customizing HTTPS for downloads |
|
Server/Relay |
10 Patch 8 |
||||||||||
|
Customizing HTTPS for downloads |
|
Server/Relay |
10 Patch 8 |
||||||||||
|
|
Client |
10 Patch 2 |
|||||||||||
|
Customizing HTTPS for downloads |
|
Server/Relay |
10 Patch 9 |
||||||||||
|
Customizing HTTPS for downloads |
|
Client |
10 Patch 9 |
||||||||||
|
Customizing HTTPS for downloads |
|
Server/Relay |
10 Patch 9 |
||||||||||
|
Customizing HTTPS for downloads |
|
Client |
10 Patch 9 |
||||||||||
|
Managing Downloads |
|
Relay |
10 Patch 10 |
Reports management
Name/Description | References | Values | Component(s) affected | Version(s) applicable | ||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|
Client | All | |||||||||
|
BES Client report interval vs BES Relay post |
|
Relay | All | ||||||||
|
|
Relay | All | |||||||||
|
|
Relay | 9.5.2 and later | |||||||||
|
|
Relay | All |
Query
Name/Description | References | Values | Component(s) affected | Version(s) applicable | ||||||
---|---|---|---|---|---|---|---|---|---|---|
|
|
Client | 9.5.2 and later | |||||||
|
|
Client | 9.5.2 and later | |||||||
|
Getting client information by using BigFix Query |
|
Client | 9.5.2 and later | ||||||
|
Getting client information by using BigFix Query |
|
Relay | 9.5.2 and later | ||||||
|
Getting client information by using BigFix Query |
|
Relay | 9.5.2 and later | ||||||
|
Getting client information by using BigFix Query |
|
Relay | 9.5.2 and later | ||||||
|
Getting client information by using BigFix Query |
|
Relay | 9.5.2 and later |
Application Usage Collection
Name/Description | References | Values | Component(s) affected | Version(s) applicable | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|
Client | 9.2 and later | |||||||||||
|
|
Client | 9.2 and later | |||||||||||
|
Application usage summary |
|
Client | 9.2 and later | ||||||||||
|
|
Client | 9.5.5 and later |
Bandwidth throttling
Set on the BigFix Server or on the BigFix Relays to control how to download files during the gathering phase.
Name/Description | References | Values | Component(s) affected | Version(s) applicable | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Bandwidth throttling |
|
Server, Relay | All | ||||||||||
|
|
Relay | All | |||||||||||
|
|
Client | All | |||||||||||
|
Bandwidth throttling |
|
Server, Relay | All | ||||||||||
|
Bandwidth throttling |
|
Client | All | ||||||||||
|
Bandwidth throttling |
|
Web Reports | All | ||||||||||
|
|
Server, Relay | All | |||||||||||
|
|
Server, Relay | All | |||||||||||
|
|
Server, Relay | All | |||||||||||
|
|
Server, Relay | All | |||||||||||
|