Abstract: A first firmware volume of a Unified Extensible Firmware Interface (UEFI) compliant information handling system is accessed. Authentication information is retrieved from the first firmware volume using a UEFI Secure Architecture Protocol. Based on the authentication information, it is determined if the first firmware volume is a first type of firmware volume. If the first firmware volume is the first type of firmware volume, the first firmware volume is authenticated using the first authentication information and an authentication procedure other than Secure Boot authentication. If the first firmware volume is a second type of firmware volume, the second type different than the first type, the first firmware volume is authenticated using the first authentication information and the Secure Boot authentication.

Abstract: An information handling system includes a non-volatile memory device for storing basic input-output system (BIOS) firmware. The system also includes a service processor that is coupled to the first non-volatile memory. The service processor initiates access to the first non-volatile memory, and stores configuration information at the non-volatile memory device. The configuration information can include Unified Extensible Firmware Interface (UEFI) Human Interface Infrastructure (HII) strings.

Abstract: A first firmware volume of a Unified Extensible Firmware Interface (UEFI) compliant information handling system is accessed. Authentication information is retrieved from the first firmware volume using a UEFI Secure Architecture Protocol. Based on the authentication information, it is determined if the first firmware volume is a first type of firmware volume. If the first firmware volume is the first type of firmware volume, the first firmware volume is authenticated using the first authentication information and an authentication procedure other than Secure Boot authentication. If the first firmware volume is a second type of firmware volume, the second type different than the first type, the first firmware volume is authenticated using the first authentication information and the Secure Boot authentication.

Abstract: An information handling system includes a memory and a first controller. The memory stores a mapping table. The first controller is configured to communicate with the memory.

Abstract: A method and information handling system (IHS) that optimizes boot time. The method includes a basic input output system (BIOS) performing an authentication check of drivers during an initial boot process. The results of the authentication check are stored along with an unified extensible firmware interface (UEFI) image for each driver in an authentication results data structure (ARDS). In response to receipt of a subsequent request to enable a secure boot of the IHS, when the initial boot process was performed with the secure boot disabled, the ARDS is accessed to determine if any of the drivers failed the authentication check. When none of the drivers have failed the authentication check, the boot process is continued using the UEFI images of the drivers. When at least one of the drivers has failed its authentication check, a notification is output indicating a failure of the authentication check.

Abstract: A solution to optimize system boot-up time by selectively collecting device inventory for only the devices that have configuration changes and for skipping for all other devices. More specifically, the solution includes a selective driver binding operation which in certain embodiments executes within an inventory application. After the selective driver binding operation gathers data for a certain device, the selective driver binding operation gathers data for that certain device again only when data relating to the particular device has changed. Instead of binding to every device, the selective driver binding operation selectively binds only to devices with changes, thus executing system management code only for specific devices and saving boot time.

Abstract: A first firmware volume of a Unified Extensible Firmware Interface (UEFI) compliant information handling system is accessed. Authentication information is retrieved from the first firmware volume using a UEFI Secure Architecture Protocol. Based on the authentication information, it is determined if the first firmware volume is a first type of firmware volume. If the first firmware volume is the first type of firmware volume, the first firmware volume is authenticated using the first authentication information and an authentication procedure other than Secure Boot authentication. If the first firmware volume is a second type of firmware volume, the second type different than the first type, the first firmware volume is authenticated using the first authentication information and the Secure Boot authentication.

Abstract: A method of performing an out of band (OOB) job at a host is disclosed. A boot option query is transmitted from the host to a service processor. It is then determined if a current boot option is an OOB job. At least one of a job type and a device type associated with the OOB job is identified if the current boot option is an OOB job. An Option ROM and a driver relating to the identified job type and the identified device type is then selectively loaded and the OOB job is performed.

Abstract: A solution to optimize system boot-up time by selectively collecting device inventory for only the devices that have configuration changes and for skipping for all other devices. More specifically, the solution includes a selective driver binding operation which in certain embodiments executes within an inventory application. After the selective driver binding operation gathers data for a certain device, the selective driver binding operation gathers data for that certain device again only when data relating to the particular device has changed. Instead of binding to every device, the selective driver binding operation selectively binds only to devices with changes, thus executing system management code only for specific devices and saving boot time.

Abstract: A method of performing an out of band (OOB) job at a host is disclosed. A boot option query is transmitted from the host to a service processor. It is then determined if a current boot option is an OOB job. At least one of a job type and a device type associated with the OOB job is identified if the current boot option is an OOB job. An Option ROM and a driver relating to the identified job type and the identified device type is then selectively loaded and the OOB job is performed.