An administrator managing BigFix on a Windows Root server is planning an automatic upgrade of the BigFix platform to version 10.0.8. Which of the…

The recommended and most efficient method for updating the BigFix installation packages (Console, Agent, Relay) on the root server is by using the dedicated Fixlet provided in the "BES Support" site. When a new platform version is released, HCL publishes a Fixlet, such as "Updated Windows Installation Folders - BigFix version 10.0.8 Now Available!", which automates the process. Taking action on this Fixlet ensures that the correct files are downloaded and placed in the appropriate wwwrootbes\Installers directory, making them available for future component deployments and upgrades. This leverages the native automation capabilities of BigFix for self-management.

A. Manually downloading and replacing files is not the best practice. It is prone to human error, such as placing files in the wrong location or downloading incorrect versions, and bypasses the integrated, audited BigFix process.

B. The installer packages are not updated automatically. An administrator must explicitly initiate the update process by taking action on the relevant Fixlet to ensure the server is ready to deploy the new version's components.

C. The BigFix Administration Tool is primarily used for initial installation, license authorization, and database configuration. It is not used for operational tasks like updating the installation folders for a platform version upgrade.

1. HCL BigFix Platform 10.0 Installation Guide

"Upgrading on Windows systems

" Section: "Step 4: Update the installation folders." This section explicitly states: "To update the installation folders

run the task with the title Updated Windows Installation Folders - BigFix version Now Available! from the BES Support site." This confirms that using the specified Fixlet is the correct procedure.

2. HCL BigFix Platform 10.0 Installation Guide

"BigFix Installation Generator." This section describes how the installation folders are created initially. The upgrade process leverages a Fixlet to update the content created by this tool

rather than re-running the tool or using the Administration Tool.