To create an Automatic Computer Group, you need to use a Relevance expression that evaluates to true or false for each computer in your deployment 1 2 .

The Relevance expression should check two conditions: the operating system is Windows 10 and a user is signed in.

To check the operating system, you can use the  name of operating system  property, which returns a string like “Win10” or “Win7” for Windows computers 3 . You can use the  contains  operator to see if the string contains “Win10”.

To check the user status, you can use the  logged on user  property, which returns the name of the current user or an empty string if no user is logged on 4 . You can use the  exists  or  not  operators to see if the property has a value or not.

You can use the  and  operator to combine the two conditions into one Relevance expression.

The correct answer is D, which checks if the  name of operating system  contains “Win10” and if the  logged on user  exists.

The other options are incorrect because:

A uses the  windows 10 of operating system  property, which does not exist 3 .

B uses the  logged on user  property without checking if it has a value or not, which could return false for computers where a user is logged on but the property is empty 4 .

C uses the  version of windows  property, which returns a version object like “10.0.19042” for Windows 10 computers 3 .  You cannot use the  starts with  operator with a version object, you need to use the  as string  cast first 5 .  References:

1 :  Create Automatic Computer Group

2 :  Create Automatic Computer Group

3 :  Operating System Inspector

4 :  Logged On User Inspector

5 : [Version Inspector]

To upgrade a stand-alone WebUI server, the following steps are required:

Copy the BigFix WebUI installer (default location is %PROGRAM FILES%\BigFix Enterprise\BES Installers\WebUI) to the client computer that is running the BigFix WebUI.

Stop the WebUI service.

Run the installer on the computer that is running the WebUI. The installer detects the WebUI and offers to upgrade it for you. Follow the installer instructions to upgrade the BigFix WebUI.

Start the WebUI service.

References:

Upgrading the WebUI

Stand-alone Web Reports upgrade? - Platform - BigFix Forum

To reconfigure a proxy server on a Windows BigFix Root server, the administrator needs to run the command BESAdmin.exe /setproxy from the BES Server folder with the appropriate parameters 1 .

The command BESAdmin.exe /setproxy allows the administrator to edit the proxy configuration settings after installation by specifying the proxy host, port, user, password, exception list, secure tunneling, authentication methods, and downstream notification 1 .

The command BESAdmin.exe /setproxy can also be used to delete the existing proxy settings by using the /delete parameter 1 .

The command BESAdmin.exe /setproxy is only available on Windows systems.  On Linux systems, the equivalent command is BESAdmin.sh -setproxy 2 .  References:

Setting a proxy connection on the server - HCL Product Documentation

Configuring the proxy - HCL Product Documentation

The Site Administrator key is a private key that is used to perform site-level tasks such as setting global system options, editing mastheads, and administering Distributed Server Architecture (DSA) 1 .

The Site Administrator key is generated during the installation of the BigFix Server, when the site administrator is prompted to enter a password to encrypt the key 2 .

The Site Administrator key is stored in a file named  license.pvk  in the  BigFix Enterprise\BES Server  folder on the BigFix Server 3 .

The Site Administrator key is required to run the  BESAdmin.exe  tool, which is used to manage the BigFix Server configuration and settings.

The Site Administrator key is also required to create the masthead file, which is a file that contains the digital signature and configuration information of the BigFix deployment.

The Site Administrator key is different from the Master Operator key, which is used to access the BigFix Console and create other operators.

References:

1 :  The Site Administrator

2 :  Admin site key for installation

3 :  Site administrator responsibilities

: Using the BESAdmin Tool

: Creating the Masthead

: BigFix Site Administrator and Console Operators

The BES Client Usage Profiler is a tool that collects information about the client evaluation cycle, such as the average, maximum, and minimum duration, and the percentage of time spent on different tasks, such as action, api, archive, gather, etc. 1

To enable the BES Client Usage Profiler, you need to run the task 361 TROUBLESHOOTING: Enable BES Client Usage Profiler on the target clients.  This task will set the  _BESClient_UsageProfiler_Enable  client setting to  1  and restart the client service. 2

After the task is completed, you can use the analysis 362 TROUBLESHOOTING: BES Client Usage Profiler to view the results of the profiler.  This analysis will show you the evaluation cycle statistics and the breakdown of the time spent on each task. 3

You can use this information to identify any potential issues or bottlenecks in the client evaluation cycle, such as long action duration, high api percent, or excessive gather time.  You can also compare the results with other clients or the average values to see if there are any anomalies or outliers. 4

To disable the BES Client Usage Profiler, you need to run the task 363 TROUBLESHOOTING: Disable BES Client Usage Profiler on the target clients. This task will set the  _BESClient_UsageProfiler_Enable  client setting to  0  and restart the client service.

References:

1 : evaluation cycle | BigFix Developer

2 : https://help.hcltechsw.com/bigfix/9.5/platform/Platform/Config/c_usage_profiler.html

3 : https://help.hcltechsw.com/bigfix/9.5/platform/Platform/Config/r_usage_profiler_analysis.html

4 : https://forum.bigfix.com/t/an-overview-on-the-client-evaluation-cycle/28056

An external site is a site that is created and maintained by HCL or a third-party vendor, and is subscribed by the BigFix administrator 1 .  External sites provide content such as fixlets, tasks, analyses, and dashboards for various purposes, such as patching, compliance, inventory, and security 1 .

The site properties for an external site in the Console show the following information 2 :

Name:  The name of the site.

Publisher:  The name of the organization that created and maintains the site.

Description:  A brief summary of the site’s content and purpose.

Current Version:  The version number of the site that is currently subscribed by the BigFix server.

Gather Status:  The status of the site’s subscription, such as Active, Pending, or Failed.

Gather Date:  The date and time when the site was last gathered by the BigFix server.

Gather URL:  The URL from which the site’s content is downloaded by the BigFix server.

Subscription:  The subscription expression that determines which BigFix clients are subscribed to the site.

Therefore, the correct answer is C. Description, as it is one of the information that is displayed in the site properties for an external site in the Console, along with Publisher and Current Version. The other options, A. Creator, B. Gather URL, and D. Created Date, are not correct, as they are either not shown or not relevant for the question.  References:

Sites

Viewing site properties

To create a patch policy, you need to follow these steps 1 2 :

On the Policies page, click Add Policy. The Add Policy page is displayed.

Provide the following information under Policy Criteria page: Policy Name, Site, Description, Custom Content Criteria, and External Content Criteria.

Click Next to configure the Pre-Patch and Post-Patch behaviour of the new policy.

Click Next to configure the Schedule for the new policy. You can set the Start Date, End Date, Frequency, and Execution Window for the policy deployment.

Click Next to select the Targets for the new policy. You can choose from Manual Selection, Automatic Group, or Relevance Expression.

Review the Summary of the new policy and click Save to activate it.  References:

Patch Policy Overview

Create a Patch Policy

BigFix Clients use  UDP  (User Datagram Protocol) to automatically find their closest relay based on network hops 1 2 .

UDP is a connectionless protocol that does not guarantee reliable delivery of packets, but is faster and more efficient than TCP (Transmission Control Protocol) 3 .

BigFix Clients send UDP packets to the BigFix Server and all the BigFix Relays in their subnet, and wait for responses 1 2 .

The BigFix Server and the BigFix Relays reply with UDP packets containing their relay information and the number of hops to reach them 1 2 .

The BigFix Client compares the responses and selects the relay with the lowest number of hops as its closest relay 1 2 .

If the BigFix Client does not receive any response within a timeout period, it assumes that there is no relay in its subnet and falls back to the BigFix Server 1 2 .  References:

Automatically assigning relays to existing clients

Configuring BigFix for automatic Relay selection Blog

UDP (User Datagram Protocol)

To upgrade the BigFix platform components, you need to follow the recommended order and the version rules as documented in the  Upgrade Paths  and the  BigFix Upgrade Best Practices .

The recommended order of upgrading the components is as follows: 1

The BigFix servers and consoles. These components must match their versions and must be upgraded at the same time (consoles with a version earlier than or later than the server version are not allowed to connect to the server and database).

The BigFix relays

The BigFix agents

The version rules for the components are as follows: 1 2

server version > = relay version > = client version

This means that the server version must be equal to or higher than the relay version, and the relay version must be equal to or higher than the client version.

This ensures that the components are compatible and can communicate with each other without any issues.

For example, if the server version is 10.0.2, the relay version can be 10.0.2, 10.0.1, or 10.0.0, and the client version can be 10.0.2, 10.0.1, 10.0.0, or any lower version.

References:

1 : Upgrade paths for BigFix 10 - HCL Product Documentation

2 : Upgrading on Windows systems - HCL Product Documentation

3 : BigFix Wiki - BigFix Upgrade Best Practices

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