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 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: A BIOS image can be selectively updated. An image loader of the BIOS can be configured to detect whether a BIOS image to be loaded includes a selective update capability field, and if so, employ a value defined in the selective update capability field to determine whether an updated BIOS image exists. When an updated BIOS image exists, the image loader can load the updated BIOS image rather than the BIOS image. In this way, an individual BIOS image can be selectively updated without needing to update the entire BIOS.

Abstract: An information handling system may include a processor, a network interface, and a basic input/output system (BIOS) configured to execute a pre-boot environment. The information handling system may be configured to: during execution of the pre-boot environment, establish a pre-boot network connection to a remote information handling system via the network interface; receive operating system data from the remote information handling system; create a pseudo-device at a specified address of the information handling system; perform direct memory access (DMA) remapping between the pseudo-device and an address range of memory of the information handling system to create a ram disk; and based on the operating system data received from the remote information handling system, initialize an operating system on the ram disk via the specified address of the pseudo-device.

Abstract: A disclosed fault analysis solution and method includes provisioning an NVMe boot directory of an information handling system with a notification module configured to perform certain operations in a pre-OS context, The operations may include detecting a pre-OS error event, determining a faulty component associated with the error event, identifying one or more executable scripts and tools associated with the faulty component, invoking a support app to download the one or more executable scripts and tools, and executing the one or more executable scripts and tools to generate a fault analysis report. The executable scripts may perform script operations including retrieving event data including one or more logs and system parameters associated with either the error event or the faulty component and storing the event data in an error log file. The executable tools may perform remedial measures associated with the error event or the faulty component.

Abstract: A basic input/output system may be configured to, during a boot of the information handling system and responsive to a condition for launching the secondary operating system: initialize a network driver for communicating with a network via a network interface, download from a secure, verified network location within the network a security manifest file for a most recent version of the secondary operating system, the security manifest file comprising metadata regarding a file system layout for the most recent version of the secondary operating system, based on the file system layout of the security manifest file and an actual file system layout of the secondary operating system as stored within an information handling system, determine one or more portions of the secondary operating system requiring update, and download the one or more portions of the secondary operating system and apply the one or more portions to the secondary operating system as stored within the information handling system.

Abstract: A capsule-based firmware update process is provided. After an operating system has provided a firmware update in the form of a capsule and the computing system is rebooted, a module can be loaded to locate a memory subsystem separate from the system memory. The module can initialize the separate memory subsystem and then identify a contiguous block of memory within the separate memory subsystem. The module can then cause the capsule to be coalesced from the system memory into the separate memory subsystem. Once the capsule is coalesced into the separate memory subsystem and the system memory is registered, the module can cause the coalesced capsule to be copied back into system memory where it can be accessed by other components that are subsequently loaded during the boot process.

Abstract: In one or more embodiments, one or more systems, methods, and/or processes may receive an interrupt from a device associated with the information handling, the device different from a memory medium; retrieve an executable from the device; store the executable via the memory medium; provide a signal to an operating system executing on the information handling system, the signal indicating that the executable was stored via the memory medium; and execute the executable via the processor, the executable configured to: retrieve, from the device, a device driver and firmware for the device; and install the device driver and the firmware for the device.

Abstract: An information handling system may load first data from a location information area of a first memory, specifying a plurality of locations of metadata for a plurality of stages of basic input/output system (BIOS) initialization. The information handling system may then load first metadata for a first stage of BIOS initialization from a first metadata location of the plurality of locations specified by the first data. The first metadata may contain information for indexing first initialization data located at a first initialization data location. The information handling system may then index the first initialization data of the first initialization data location based, at least in part, on the first metadata. The information handling system may then perform the first stage of BIOS initialization based, at least in part, on the first initialization data.

Abstract: An information handling system may include a processor subsystem and non-transitory computer-readable media communicatively coupled to the processor subsystem and storing instructions, the instructions configured to, when read and executed by the processor subsystem: execute a basic/input output service to create a link aggregation table with details based on wireless and wired network interface modules present within the information handling system; execute a first operating system service on a container instantiated on a hypervisor of the information handling system to instantiate virtual link aggregation tables for the container based on a network bandwidth policy of the container and link aggregation capabilities as set forth in the link aggregation table; and execute a second operating system service on the hypervisor to instantiate an operating system driver based on operating systems for network instances of link aggregation drivers and dynamic detection of network driver requirements determined by the

Abstract: A method, and systems and articles of manufacture for performing the method, may be provided for use in an information handling system comprising one or more processors and a memory system communicatively coupled to the one or more processors. The method may include enumerating memory modules of the memory system and installing a concurrent firmware protocol to each of the memory modules, wherein the concurrent firmware protocol is configured to individually execute an update routine on each of the memory modules. The update routine may be configured to, on each memory module, store a to-be-applied firmware update in a protected non-volatile region of the memory module and pull the to-be-applied firmware update from the protected non-volatile region of the memory module and perform a self-update of firmware for the memory module.

Abstract: A preboot module of BIOS may be configured to create a partition mapping table for namespace identifiers of sub-partitions of a boot partition, determine a configuration policy for the information handling system, store the configuration policy in a partition of non-volatile memory, launch execution of an embedded operating system kernel, and communicate the partition mapping table to the embedded operating system kernel based on the configuration policy, such that the embedded operating system kernel is enabled to load the configuration policy from the non-volatile memory and load and execute one or more applications based on the partition mapping table and the configuration policy.

Abstract: A system for configuring a processor is disclosed that includes a processor, a memory, and a firmware startup algorithm stored in the memory at a first predetermined location, the firmware start-up algorithm has one or more user-configurable driver algorithm memory storage locations. A driver algorithm stored at one of the user-configurable driver algorithm memory storage locations is configured to modify an operating system memory storage location for use by the firmware startup algorithm.

Abstract: A BIOS boot and update failover process is provided. A computing system can include flash storage on which the BIOS is stored, an embedded controller and an NVMe drive. After the BIOS successfully performs a boot process, a failover module can be executed to create a BIOS namespace on an NVMe namespace and then store a copy of the BIOS on the NVMe namespace. The failover module can also create a device path that identifies where the copy of the BIOS is stored on the NVMe namespace and store the device path on the embedded controller. The embedded controller can be configured to detect when the BIOS on the flash storage fails to initiate a subsequent boot process and, in response, employ the device path to locate and load the copy of the BIOS from the NVMe namespace to thereby cause the computing system to be booted.

Abstract: A method includes receiving a firmware update package at an information handling system, the package including a payload containing a first firmware image. In response to executing the firmware update package while the information handling system is under control of an operating system, identifying a non-volatile storage device; authenticating the first firmware image; and storing the first firmware image at the non-volatile storage device. In response to successfully authenticating the first firmware image, initiating a reboot of the information handling system to invoke an initialization routine. The initialization routine includes retrieving the first firmware image from the non-volatile storage device and installing the first firmware image at a first device.

Abstract: An information handling system includes a virtual network access module configured to access a virtual network drive that has a first partition in a local storage resource and a second partition in a remote storage resource. In response to detection of an exception, a processor may trigger a exception handler that directs a service processor to initialize a network stack. The processor initializes a mailbox to transmit a mailbox request to retrieve network configuration settings to be used in the initialization of the network stack. The service processor transmits a request to the processor to initialize the mailbox, and initializes the network stack based on the network configuration settings. Subsequent to the initialization of the network stack, a universal network device interface request may be sent to mount and secure communication with the virtual network drive.

Abstract: A method for secure data communications using an insecure protocol, comprising generating a data message at a data processor client. Adding a security key to the data message using the data processor client. Transmitting the data message to a remote data processor receiver over a data network. Determining whether the data message is authentic at the remote data processor receiver. Automatically responding to the data message with a location where additional data can be obtained from the remote data processor receiver if it is determined by the remote data processor receiver that the data message is authentic.

Abstract: A basic input/output system may be configured to, during a boot of the information handling system and responsive to a condition for launching the secondary operating system: initialize a network driver for communicating with a network via a network interface, download from a secure, verified network location within the network a security manifest file for a most recent version of the secondary operating system, the security manifest file comprising metadata regarding a file system layout for the most recent version of the secondary operating system, based on the file system layout of the security manifest file and an actual file system layout of the secondary operating system as stored within an information handling system, determine one or more portions of the secondary operating system requiring update, and download the one or more portions of the secondary operating system and apply the one or more portions to the secondary operating system as stored within the information handling system.

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: A BIOS boot and update failover process is provided. A computing system can include flash storage on which the BIOS is stored, an embedded controller and an NVMe drive. After the BIOS successfully performs a boot process, a failover module can be executed to create a BIOS namespace on an NVMe namespace and then store a copy of the BIOS on the NVMe namespace. The failover module can also create a device path that identifies where the copy of the BIOS is stored on the NVMe namespace and store the device path on the embedded controller. The embedded controller can be configured to detect when the BIOS on the flash storage fails to initiate a subsequent boot process and, in response, employ the device path to locate and load the copy of the BIOS from the NVMe namespace to thereby cause the computing system to be booted.