Abstract: A method may be provided in a basic input/output system embodied in persistent memory including two data areas for storing data associated with the basic input/output system and a code area comprising firmware for performing functionality of the basic input/output system. The method may include, at any given time, designating one of the data areas as a non-transitory data area and designating the other of the data areas as a transitory data area; and for each item of data associated with the basic input/output system, determining if such item of data is non-transitory-type data or transitory-type data, storing such item of data in the non-transitory data area if such item of data is determined to be non-transitory-type data, and storing such item of data in the transitory data area if such item of data is determined to be transitory-type data.

Abstract: An information handling system includes a cloud device including an on-the-cloud analytics device, and a node device. The node device includes an on-the-box analytics device, a data collector device, a data management device, and a load mitigator device. The data collector device sources a plurality of data-producing agents within the information handling system. The data management device receives and manages data produced by the data collector. The load mitigator device receives the data from the data management device, and analyzes the data and additional system data. The additional system data is associated with the information handling system. The load mitigator device also determines whether to route analytics for the information handling system to the on-the box analytics device or to the on-the-cloud analytics. Based on the determination, the load mitigator device routes the analytics to either the on-the box analytics device or to the on-the-cloud analytics device.

Abstract: A BIOS may include a plurality of BIOS attributes associated with the information handling system, each attribute of the plurality of BIOS attributes having metadata defining a priority for such attribute. The BIOS may also include an attribute engine configured to execute a preboot process prior to booting of an operating system of the information handling system, wherein the preboot process is configured to identify boot-critical attributes of the plurality of BIOS attributes based on the metadata and load the boot-critical attributes. The attribute engine may also execute a steady-state process after booting of the operating system of the information handling system, wherein the steady-state process is configured to load attributes of the plurality of BIOS attributes other than the boot-critical attributes in an order based on the metadata.

Abstract: An information handling system includes a cloud device including an on-the-cloud analytics device, and a node device. The node device includes an on-the-box analytics device, a data collector device, a data management device, and a load mitigator device. The data collector device sources a plurality of data-producing agents within the information handling system. The data management device receives and manages data produced by the data collector. The load mitigator device receives the data from the data management device, and analyzes the data and additional system data. The additional system data is associated with the information handling system. The load mitigator device also determines whether to route analytics for the information handling system to the on-the box analytics device or to the on-the-cloud analytics. Based on the determination, the load mitigator device routes the analytics to either the on-the box analytics device or to the on-the-cloud analytics device.

Abstract: Information handling systems (IHS) and methods are provided to automatically synchronize operating system (OS) and boot firmware languages. In one embodiment, a method may detect a change in an active OS language from a first language pack to a second language pack, notify the boot firmware that the active OS language was changed, and provide an identity of the second language pack to the boot firmware during OS runtime. When the IHS is subsequently rebooted, the active boot firmware language may be synchronized to the active OS language. In another embodiment, the method may detect a change in an active boot firmware language from a first language pack to a second language pack, notify the OS that the active boot firmware language was changed, and provide an identity of the second language pack to the OS during a pre-boot phase. When the OS is subsequently booted, the active OS language may be synchronized to the active boot firmware language.

Abstract: An information handling system includes a basic input/output system having a virtual advanced configuration and power interface device. A processor may download a device driver for a particular virtual advanced configuration and power interface device, wherein the device driver includes a code for a security feature and a signed file that includes a list of identifiers of compromised information handling systems. The processor may determine whether the information handling system is compromised based on the list of identifiers of compromised information handling systems in the signed file, and execute the code for the security feature.

Abstract: An information handling system may include a processor and a basic input/output system communicatively coupled to the processor and comprising a plurality of firmware volumes embodied in non-transitory computer readable media, each firmware volume comprising executable code for a respective functionality of the basic input/output system, wherein the basic input/output system is configured to, based on the presence or absence of an action or event associated with the basic input/output system, select a boot path for execution from a plurality of boot paths, each of the plurality of boot paths comprising a respective trust chain of a subset of the plurality of firmware volumes and execute the boot path selected.

Abstract: A method may include receiving telemetry data from an information handling system communicatively coupled to the information handling system and store the telemetry data based on uniquely identifying information of the information handling system, generating a firmware recovery image for the information handling system based on the telemetry data, storing the recovery image in a recovery image database indexed by the uniquely identifying information, responsive to a condition for initiating firmware recovery of the information handling system, retrieving the firmware recovery image for the information handling system from the recovery image database, and communicating the firmware recovery image to a companion device associated with the information handling system, such that preboot firmware of the information handling system may load and execute the firmware recovery image from the companion device to restore the information handling system.

Abstract: Firmware updates can be packaged in a manner that enables a firmware update utility to be executed to provide control functionality for the deployment of the firmware updates while leveraging an operating system provided update framework to deliver the firmware updates to the pre-boot environment. Accordingly, control over the deployment of the firmware updates is provided without the difficulties and security risks of employing a custom kernel-mode driver to deliver the firmware updates.

Abstract: An SMI task to be completed across multiple SMI events. An OS agent can be employed to determine a current load on a computing device. Based on the load, the OS agent can create an SMI message that specifies a maximum duration for an SMI event and that segments the SMI data for the SMI task. The OS agent can provide the SMI message to BIOS as part of requesting that the SMI task be performed. During the resulting SMI event, the BIOS can reassemble the segmented SMI data and then perform the SMI task. If this processing cannot be completed within the specified maximum duration for an SMI event, the BIOS can pause its processing and cause a subsequent SMI event to occur during which the processing can be resumed. In this way, the SMI task can be completed across multiple SMI events while ensuring that no single SMI event exceeds the specified maximum duration.

Abstract: Software updates can be deployed in end user devices in coordination with end-user productivity. A system monitoring engine can be employed on end user devices to compile productivity impact data from which heat maps may be created. An optimal deployment detection engine can employ the heat maps to create or maintain period-based groupings. When software updates are available, the optimal deployment detection engine can employ the period-based groupings to create optimal deployment plans specific to the end user devices. The installation of the software updates can then be performed on each end user device in accordance with that end user device's optimal deployment plan.

Abstract: Software updates can be deployed in end user devices in coordination with end-user productivity. A system monitoring engine can be employed on end user devices to compile productivity impact data from which heat maps may be created. An optimal deployment detection engine can employ the heat maps to create or maintain period-based groupings. When software updates are available, the optimal deployment detection engine can employ the period-based groupings to create optimal deployment plans specific to the end user devices. The installation of the software updates can then be performed on each end user device in accordance with that end user device's optimal deployment plan.

Abstract: An information handling system includes a non-volatile memory (NVRAM) and a processor. The NVRAM stores a plurality of NVRAM variables and a basic input/output system (BIOS) of the information handling system. The BIOS includes system BIOS variable services. The processor executes the system BIOS variable services. While executing the system BIOS variable services, the processor determines whether a holding area of a first NVRAM variable of the NVRAM variables is completely used. In response to the storage being completely used, the processor calculates a new size of the holding area based on metadata of the first NVRAM variable, and creates a new storage area for the first NVRAM variable. The size of a second holding area of the new storage area equals the new size.

Abstract: A BIOS may include a plurality of protocol drivers and a protocol notification manager configured to receive a protocol notification registration from a consumer driver of the plurality of protocol drivers, receive a unique key associated with the consumer driver, receive a pre-authorized list from a producer driver of the plurality of protocol drivers, the pre-authorized list comprising one or more signed consumer identifiers, each of the one or more signed consumer identifiers identifying a respective one of the plurality of protocol drivers authorized to receive a protocol notification from the producer driver, determine if the unique key successfully decrypts a signed consumer identifier associated with the consumer driver, and perform access control of protocol notification from the producer driver to the consumer driver based on whether the unique key successfully decrypts the signed consumer identifier associated with the consumer driver.

Abstract: An information handling system may include a processor and a program of instructions embodied in non-transitory computer-readable media and configured to, when read and executed by the processor: in response to a request to write a variable to a solid state device, store the variable to a memory location of the solid state device, the variable including variable data and a variable status indicative of a validity of the variable data, the variable status having a plurality of bits wherein each of the plurality of bits are set to an initial value and in response to a request to modify the variable, modify the variable status by changing one of the plurality of bits from the initial value to a logical complement of the initial value to change the validity of the variable data. The validity of the variable data may be based on whether an even number or odd number of the plurality of bits are equal to the complement of the initial value.

Abstract: Systems and methods are provide that may be implemented to modify boot operation for an information handling system using commands of a script that is detected and authenticated by boot code of the information handling system. The script may include at least one command that modifies a boot operation of the information handling system when performed by the processor. The boot code may be executed by the processor during startup, to detect and authenticate the script, and to process the at least one command after the script is authenticated. Multiple commands may be defined including triggerless actions or trigger actions which are performed in response to a trigger event. A trigger event may be a hardware interaction, such as the pressing of a button.

Abstract: Best known configurations can be automatically created for particular platforms. An update tool can be installed on end user devices and can include a health monitor engine that creates health reports for drivers and/or firmware installed on the corresponding end user device. The health reports generated on the end user devices can be provided to a best known configuration engine that can evaluate them to calculate a best known configuration for each platform. The best known configurations can then be distributed to the update tool on the end user devices to cause them to configure the end user devices to match the corresponding best known configuration.

Abstract: An information handling system may include at least one processor, and a computer-readable medium having instructions thereon that are executable by the at least one processor. The instructions may be executable for: in response to detection of a first trigger event, enabling an accelerated boot process; and in response to detection of a second, different trigger event, enabling a non-accelerated boot process. The non-accelerated boot process may include parsing an internal forms representation (IFR), and the accelerated boot process may include not parsing the IFR.

Abstract: An information handling system may include a processor, non-transitory computer readable media communicatively coupled to the processor and having stored thereon a primary operating system of the information handling system and a secondary operating system of the information handling system, and a basic input/output system communicatively coupled to the processor and having provisioned thereon a signed signature of the secondary operating system signed with a private key of a public-private key pair and a public key of the public-private key pair. The basic input/output system is configured to, responsive to a determination to boot to the secondary operating system in lieu of booting to the primary operating system of the information handling system verify the secondary operating system using the signed signature of the secondary operating system and the public key and responsive to verifying the secondary operating system, allow the information handling system to boot to the secondary operating system.

Abstract: An information handling system may include a processor and a basic input/output system communicatively coupled to the processor and comprising a plurality of firmware volumes embodied in non-transitory computer readable media, each firmware volume comprising executable code for a respective functionality of the basic input/output system, wherein the basic input/output system is configured to, based on the presence or absence of an action or event associated with the basic input/output system, select a boot path for execution from a plurality of boot paths, each of the plurality of boot paths comprising a respective trust chain of a subset of the plurality of firmware volumes and execute the boot path selected.