HCL-BF-PRO-10 Exam Dumps : HCLSoftware U Certified Professional-BigFix Platform 1

• The download cache size on a relay or a server can be changed by using the Fixlet ID# 148 BES Relay/Server Setting: Download Cache Size, available from the BES Support Site.
• This Fixlet allows the administrator to specify the desired cache size in MB as a parameter of the action.
• To increase the cache size to 10 GB, the administrator needs to enter 10240 as the value of the parameter, since 1 GB = 1024 MB.
• The Fixlet will then create or modify the client setting _BESGather_Download_CacheLimitMB on the target relay or server, and set its value to the specified parameter.
• The Fixlet will also restart the BES Client service on the target relay or server to apply the new setting.
• The new cache size will take effect after the service restarts, and the relay or server will be able to store more downloaded files in its cache. References:
• Managing Downloads
• BES Client download cache limit?
• The download size exceeds the maximum value set in the client setting

• If UDP is not allowed on a network segment, the BigFix clients on that segment will not receive the UDP notifications from the server or relay, and will rely on the default 45-minute polling interval to check for new actions.1
• To reduce the delay in receiving new actions, you can enable the client polling feature, which allows the clients to poll the server or relay more frequently for new commands.2
• To enable the client polling feature, you need to set two client settings on the target clients:2
• You can set these client settings either through the console or manually on the endpoint.4
• After setting these client settings, the clients will poll the server or relay at the specified interval and receive new actions faster.

References:

• 1: https://help.hcltechsw.com/bigfix/9.5/platform/Platform/Installation/c_sample_proxy_configurations.html
• 2: https://help.hcltechsw.com/bigfix/9.5/platform/Platform/Config/r_client_set.html#_BESClient_Comm_CommandPollEnable
• 3: https://forum.bigfix.com/t/an-overview-on-the-client-evaluation-cycle/28056
• 4: https://help.hcltechsw.com/bigfix/9.5/platform/Platform/Config/r_client_set.html#Making_a_configuration_setting

• A Multiple Action Group is a way to deploy a set of Fixlets or tasks in a single grouping using the Take multiple actions command1.
• As a requirement, each Fixlet or task involved in the group must have associated a default action1.
• A default action is an action script that is predefined by the Fixlet or task author and can be executed without any user input2.
• If one or more of the Fixlets that are selected do not have a default action, the Take multiple actions command will fail and display an error in the Console1.
• To resolve this issue, the operator can either select only Fixlets or tasks that have default actions, or create a Baseline that includes the Fixlets or tasks without default actions1. References:
• 1: Taking multiple actions
• 2: Action Script
• 3: Take multiple actions
• 4: Action Script Guide