Passed Exam Today HCL-BF-PRO-10

• A BigFix Enterprise Server (BES) is the central component of the BigFix architecture that manages and communicates with the BigFix agents and relays1.
• The BES consists of several subcomponents, such as the root server, the console, the web reports, the web UI, and the server API1.
• The BES can support up to 300,000 endpoints in a single deployment, depending on the hardware configuration, network bandwidth, and workload2.
• The BES capacity planning document provides guidelines and recommendations for sizing and scaling the BES components based on various factors, such as cores, memory, network, storage, cloud, and concurrent users2.
• The BES capacity planning document also provides examples of typical deployments and best practices for optimizing the BES performance and stability2. References:
• BigFix Platform Overview
• BigFix Capacity Planning

To create a new retrieved property in BigFix, the following steps are required:

• From the BigFix Console, select Manage Properties from the Tools menu. The Manage Properties dialog is displayed.
• You can filter the properties by using the left filter panel to select a subset of the properties to view on the right. If you cannot find what you want in this list, create a new property: click Add New, then enter a name for the property and a valid Relevance expression. This can access hardware characteristics, registry entries, and even data in specific files on the client computers.
• After you define the new property, the Clients automatically compute the value of the corresponding relevance expression and return it to the Database. Click the OK button.
• The new property will be available in the column headers of computer listings, allowing you to sort and filter on its values. It can also be used to target Fixlet actions and generate Web Reports.

References:

• Creating Retrieved Properties
• Adding new properties under “By retrieved properties”

A Top Level Relay is a relay that directly communicates with the BigFix Server and has other relays as its children. A Top Level Relay has no limit as to the number of relays they can manage, but it is recommended to have no more than 1000 relays per Top Level Relay for optimal performance. When designing a relay hierarchy, the BigFix Administrator should consider the following factors:

• The network bandwidth and latency between the relays and the server
• The number and size of the fixlets, actions, and reports that are exchanged between the relays and the server
• The CPU and memory resources of the relays and the server
• The relay affiliation and selection settings of the clients and the relays
• The encryption and decryption of the client reports by the relays and the server

References:

• Creating top-level decrypting relays
• Top-Level Relays - Platform - BigFix Forum
• Relay Health - BigFix
• Creating top-level decrypting relays - IBM

• When creating a scheduled activity in Web Reports, the Activity Actions box allows the user to specify what actions to take when the activity runs1.
• The available options are:
• The user can select one or more of these options for each scheduled activity. For example, the user can email and archive the report, or email and run the executable, or archive and run the executable, or do all three1.

References:

• 1: Creating Scheduled Activities