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

• When creating roles in Web Reports, you can define the permissions that you want to grant to the users who are assigned to that role.
• There are some check boxes that you can use to specify the permissions, such as:
• These check boxes are available in the Create Roles page, which you can access from Administration > User Management > Manage Roles > Create role.
• The other options (A, D, and F) are not available as check boxes when creating roles in Web Reports. They are either irrelevant or controlled by other settings. References:
• Manage Roles
• Create Roles
• Permissions Set in the BigFix Console

• To create a schedule to delete duplicate computer records from the BigFix database, you need to use the BigFix Administration Tool1.
• The BigFix Administration Tool is a separate application that allows you to perform various administrative tasks on the BigFix server, such as creating users, managing licenses, configuring encryption, and removing computers1.
• To use the BigFix Administration Tool, you need to have the Master Operator role and access to the BigFix server machine1.
• To create a schedule to delete duplicate computer records, you need to use the BES Computer Remover tool, which is a component of the BigFix Administration Tool2.
• The BES Computer Remover tool allows you to automatically detect and remove inactive or duplicate computers from the BigFix database based on various criteria, such as last report time, computer name, IP address, or a custom property2.
• To create a schedule to delete duplicate computer records, you need to follow these steps2:
• 1: Using the BigFix Administration Tool
• 2: Removing computers from the BigFix database
• 3: Using the BigFix Administration Tool
• 4: Removing computers from the BigFix database

• The WebUI is a web-based interface that provides access to the flexibility and power of BigFix.
• The WebUI has some upper use limits that depend on many factors, such as the number of endpoints, the workload, the time of day, the server location, and the number of concurrent users.
• Concurrent users are defined as highly active users who perform multiple actions per minute on the WebUI.
• According to the BigFix Capacity Planning Guide, both the Windows and Linux WebUI instances support 36 concurrent users on a 250k deployment base. This is the recommended scalability limit for the WebUI server on BigFix v10.x.
• The WebUI also requires additional hardware resources, such as CPU, memory, and storage, to power the WebUI. These resources are in addition to the BigFix root server requirements and depend on the number of concurrent users.
• The WebUI also implements a database cache for several counters to improve the WebUI response times. The cache has a default refresh interval of 10 minutes. References:
• Hardware Requirements
• WebUI Administrators Guide
• BigFix WebUI

According to the BigFix Platform documentation1, the standard Relay configuration can support up to 5,000 endpoints per Relay, while the high scale Relay configuration can support up to 10,000 endpoints per Relay. The high scale Relay configuration requires more hardware resources and tuning parameters than the standard Relay configuration. To configure a high scale Relay, you need to follow these steps2:

• Install the Relay on a dedicated server with at least 8 CPU cores, 16 GB of RAM, and 500 GB of disk space.
• Set the _BESRelay_HTTPServer_MaxConnections setting to 2000 on the Relay.
• Set the _BESRelay_PostResults_ParentRelayBufferDirectoryMaxSize setting to 10000000000 on the Relay.
• Set the _BESRelay_PostResults_ParentRelayBufferDirectoryMaxCount setting to 100000 on the Relay.
• Set the _BESRelay_PostResults_ChildRelayBufferDirectoryMaxSize setting to 10000000000 on the Relay.
• Set the _BESRelay_PostResults_ChildRelayBufferDirectoryMaxCount setting to 100000 on the Relay.
• Set the _BESRelay_Download_LimitBytesPerMinute setting to 0 on the Relay.
• Set the _BESRelay_Download_LimitBytesPerMinutePerClient setting to 0 on the Relay.
• Set the _BESRelay_Download_PreCacheStageDiskLimitMB setting to 100000 on the Relay.
• Set the _BESRelay_Download_PreCacheStageDiskLimitPercent setting to 0 on the Relay.
• Set the _BESRelay_Download_CacheLimitMB setting to 100000 on the Relay.
• Set the _BESRelay_Download_CacheLimitPercent setting to 0 on the Relay.
• Restart the Relay service after applying the settings. References:
• Relay scalability
• Configuring a high scale Relay

• A BigFix Relay is a special type of BigFix Client that can cache and distribute files to other BigFix Clients, reducing the workload and bandwidth usage of the BigFix Server1.
• A BigFix Relay can be installed on any BigFix Client that runs on a supported BigFix Relay operating system, which includes Windows, Linux, and Solaris23.
• A BigFix Relay does not require a server operating system or a dedicated endpoint, as long as it meets the minimum system requirements and recommendations for a relay, which are similar to those for a workgroup file server23.
• A BigFix Relay must have a two-way TCP connection to its parent, which can be another relay or the BigFix Server23.
• A BigFix Relay can be installed using a Fixlet from the BigFix Console or the command line4. References:
• 1: Relays and Servers
• 2: Relay requirements and recommendations
• 3: Relay requirements
• 4: Installing a relay