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

• 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 version rules for the components are as follows:12

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

• Locking a BigFix Client means preventing it from accepting any actions that could modify its state, such as installing patches, changing settings, or running scripts1.
• Locking a BigFix Client can be useful for various reasons, such as testing new actions on a subset of unlocked computers, protecting critical or sensitive systems from unwanted changes, or complying with security policies or regulations12.
• Locking a BigFix Client can be done by using the BigFix Console, the BigFix WebUI, or the BES Client API13.
• Locking a BigFix Client does not affect its other functions, such as reporting, gathering, relay selection, or client settings2.
• The locked status of a BigFix Client can be changed by sending an unlock action, which can be done by a Master Operator or a Non-Master Operator who has the Write permission to the site where the client is subscribed14.
• The locked status of a BigFix Client can also be set to expire after a certain period of time, by using a custom action script15.
• Therefore, the only valid reason among the options for locking a computer is D. When changes or updates need to be excluded from the computer. References:
• 1: Locking clients
• 2: Just how locked is “Locked”?
• 3: [BES Client API]
• 4: [The Console Operators]
• 5: [Locking a client for a specific period of time]
• 6: [Locking clients]
• 7: [Just how locked is “Locked”?]
• : [BES Client API]
• : [The Console Operators]
• : [Locking a client for a specific period of time]
• : [Locking clients]
• : [Just how locked is “Locked”?]
• : [BES Client API]
• : [The Console Operators]
• : [Locking a client for a specific period of time]
• : [Locking clients]
• : [Just how locked is “Locked”?]
• : [BES Client API]
• : [The Console Operators]
• : [Locking a client for a specific period of time]
• : [Locking clients]
• : [Just how locked is “Locked”?]
• : [BES Client API]
• : [The Console Operators]
• : [Locking a client for a specific period of time]

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