Abstract: An information handling system may include a processor and a program of instructions embodied in non-transitory computer-readable media, the program of instructions configured to, when read and executed by the processor: receive a touch temperature limit parameter indicative of a temperature limit; receive an acoustic noise limit parameter indicative of an acoustic noise limit; determine an estimated power capacity limit parameter indicative of an estimated power limit based on the touch temperature limit parameter and the acoustic noise limit parameter; and determine an estimated performance capability parameter based on the estimated power capacity limit parameter.

Abstract: Systems and methods for providing a Basic Input/Output System (BIOS) enforced blocklisting of harmful applications are described. In one embodiment, an Information Handling System (IHS) may include a processor and a BIOS coupled to the processor, the BIOS having program instructions that, upon execution, cause the IHS to download an Unsafe Application List (UAL) from an online source, and during a bootstrap process of the IHS, compare a plurality of Applications (Apps) installed on the IHS against a list of harmful applications included in a UAL. When a harmful application is found by the comparison, the instructions enforce one or more policies to restrict the harmful application from being executed on the IHS.

Abstract: Systems and methods for memory serviceability mitigation are described. In some embodiments, an Information Handling System (IHS) may include a processor and a memory coupled to the processor, the memory having program instructions stored thereon that, upon execution, cause the IHS to: after failure of a memory device, notify a cloud service and enter a mitigation mode of operation with respect to the memory device, receive a message from the cloud service indicative of the provisioning of a replacement memory device, and, in response to the message and upon detection of a chassis intrusion event, leave the mitigation mode of operation with respect to the replacement memory device.

Abstract: Disclosed methods for enabling flexible policies for user access to BIOS attribute settings perform operations including creating a BIOS attribute map encompassing one or more configurable BIOS attributes, generating a role-based authorization table associating an authorization role to each of the configurable BIOS attributes, and deploying the role-based authorization table to an information handling system. Responsive to a user launching a BIOS attribute configuration tool, a user role associated with the user is detected and the role-based authorization table is retrieved. Based on the role-based authorization table and the user role, configurable BIOS attributes for the user are identified. The configurable BIOS attributes may then be presented to the BIOS configuration to enable the user to perform configuration operations for the configurable BIOS attributes.

Abstract: Systems and methods for providing a Basic Input/Output System (BIOS) enforced blocklisting of harmful applications are described. In one embodiment, an Information Handling System (IHS) may include a processor and a BIOS coupled to the processor, the BIOS having program instructions that, upon execution, cause the IHS to download an Unsafe Application List (UAL) from an online source, and during a bootstrap process of the IHS, compare a plurality of Applications (Apps) installed on the IHS against a list of harmful applications included in a UAL. When a harmful application is found by the comparison, the instructions enforce one or more policies to restrict the harmful application from being executed on the IHS.

Abstract: An information handling system may include a processor, a memory communicatively coupled to the processor, and a basic input/output system (BIOS) communicatively coupled to the processor and comprising a program of executable instructions configured to, when read and executed by the processor: monitor diagnostics information associated with one or more information handling resources of the information handling system, from the diagnostics information, determine whether a trigger point associated with a prescription for initiating a firmware update has been reached, and responsive to the trigger point being reached, perform a remedial action as defined by the prescription.

Abstract: An information handling system may include a processor and instructions embodied in non-transitory computer-readable media coupled to the processor, the instructions configured to, when read and executed by the processor, in response to commencement of a meeting using a conferencing platform software of the information handling system, monitor one or more parameters indicative of a health of the information handling system, determine the health of the information handling system based on such one or more parameters, and in response to determining the information handling system is unhealthy, wirelessly communicate an alert to a second information handling system indicating that the information handling system is unhealthy.

Abstract: A firmware update method maintains a firmware resource table for multiple firmware modules. The table includes a globally unique identifier (GUID) of the module and current version information. A firmware capsule is delivered to a capsule delivery service (CDS) and pushed to a platform. The capsule includes a firmware update and firmware dependency components, indicating GUIDs and minimum current versions of one or more other firmware modules that must be found in the resource table before installing the firmware module being processed. An update may be perform for the particular firmware module responsive to confirming the current version information satisfies the dependency criteria. If the version information does not satisfy the dependency criteria, the firmware capsule may be staged to a platform store and GUID in the resource table may be removed. Conversely, successfully processing a previously staged firmware capsule may include restoring or otherwise updating the GUID.

Abstract: According to one illustrative, non-limiting embodiment, a first IHS may include computer-executable instructions for performing at least one artificial intelligence (AI) service to optimize a performance of the first IHS. In response to determining that an AI workload of the AI service exceeds a specified threshold, the first IHS selects a second IHS to perform at least a portion of the AI workload, and transmits the at least one portion of the AI workload to the second IHS. When a processed AI workload is received from the second IHS, the first IHS applies one or more profile recommendations included in the processed AI workload.

Abstract: An information handling system may include at least one processor, and a memory coupled to the at least one processor. The information handling system may be configured to: detect a problem during a boot of the information handling system; transmit telemetry data associated with the problem to at least one remote telemetry server, wherein the at least one remote telemetry server is configured to analyze the telemetry data and other telemetry data from other information handling systems; receive resolution instructions from the at least one remote telemetry server; and implement a resolution of the detected problem based on the resolution instructions.

Abstract: An information handling system may include a central processing unit (CPU), a graphics processing unit (GPU) including a plurality of processing cores, a memory coupled to the CPU and to the GPU, and a basic input/output system (BIOS). While the information handling system is in a pre-boot environment and prior to initialization of an operating system of the information handling system, the BIOS may cause the central processing unit to select respective portions of the memory for failure testing; and cause individual ones of the plurality of processing cores of the GPU to carry out the failure testing of the respective portions of the memory.

Abstract: A method includes receiving a request from a protocol publisher to install a protocol at the protocol database, the request including a global unique identifier (GUID) and a first protocol pointer. The GUID and the first protocol pointer are stored at an entry at a protocol database. A root key received from the protocol publisher is stored at the entry at the protocol database. A request including the GUID is received from a protocol consumer, and in response, the protocol consumer is provided with a random number. A reference GUID is generated based on the random number and the root key, and the reference GUID is stored at the entry of the protocol database.

Abstract: An information handling system may include a processor, a memory coupled to the processor, a storage resource, and a basic input/output system (BIOS). The BIOS may be configured to, while the information handling system is in a pre-boot environment and prior to initialization of an operating system of the information handling system: detect a security vulnerability of the information handling system; and store data regarding the security vulnerability in a portion of the storage resource that is accessible to both the BIOS and the operating system. The information handling system may be further configured to, after the initialization of the operating system, execute a security management service to access, from within the operating system, the data regarding the security vulnerability.

Abstract: An information handling system may include at least one processor, an information handling resource including a firmware, and a memory having an initial identifier stored therein. The information handling system may receive a first firmware update package specifying the initial identifier, wherein the first firmware update package includes therein an intermediate identifier different from the initial identifier; based on the first firmware update package specifying the initial identifier, update the firmware with contents of the first firmware update package, and update the initial identifier in the memory with the intermediate identifier; receive a second firmware update package specifying the intermediate identifier; and based on the second firmware update package specifying the intermediate identifier, update the firmware with contents of the second firmware update package.

Abstract: An information handling system may include at least one processor, an information handling resource including a firmware, and a memory having an initial identifier stored therein. The information handling system may receive a first firmware update package specifying the initial identifier, wherein the first firmware update package includes therein an intermediate identifier different from the initial identifier; based on the first firmware update package specifying the initial identifier, update the firmware with contents of the first firmware update package, and update the initial identifier in the memory with the intermediate identifier; receive a second firmware update package specifying the intermediate identifier; and based on the second firmware update package specifying the intermediate identifier, update the firmware with contents of the second firmware update package.

Abstract: An information handling system may include a central processing unit (CPU), a graphics processing unit (GPU) including a plurality of processing cores, a memory coupled to the CPU and to the GPU, and a basic input/output system (BIOS). While the information handling system is in a pre-boot environment and prior to initialization of an operating system of the information handling system, the BIOS may cause the central processing unit to select respective portions of the memory for failure testing; and cause individual ones of the plurality of processing cores of the GPU to carry out the failure testing of the respective portions of the memory.

Abstract: An information handling system may include a processor, a memory coupled to the processor, a storage resource, and a basic input/output system (BIOS). The BIOS may be configured to, while the information handling system is in a pre-boot environment and prior to initialization of an operating system of the information handling system: detect a security vulnerability of the information handling system; and store data regarding the security vulnerability in a portion of the storage resource that is accessible to both the BIOS and the operating system. The information handling system may be further configured to, after the initialization of the operating system, execute a security management service to access, from within the operating system, the data regarding the security vulnerability.

Abstract: An information handling system may include at least one processor, and a memory coupled to the at least one processor. The information handling system may be configured to: detect a problem during a boot of the information handling system; transmit telemetry data associated with the problem to at least one remote telemetry server, wherein the at least one remote telemetry server is configured to analyze the telemetry data and other telemetry data from other information handling systems; receive resolution instructions from the at least one remote telemetry server; and implement a resolution of the detected problem based on the resolution instructions.

Abstract: A BIOS of an information may transmit information regarding events detected by the BIOS to an OS of an information handling system for logging in an OS event log. A BIOS of an information handling system may detect an event and may log information regarding the event in a memory of an information handling system. An OS of the information handling system may retrieve at least a portion of the information regarding the event from the event log and may add at least a portion of the retrieved information to an OS event viewer.

Abstract: A method includes receiving a firmware update package at an information handling system. The update package includes a payload containing a transition basic input-output system (BIOS) and another payload containing a new BIOS. The new BIOS is stored at an Extensible Firmware Interface system partition (ESP). A firmware image at a BIOS flash device at the information handling system is updated using the new BIOS retrieved from the ESP.