Abstract: An information handling system stores a hash values for firmware components for the information handling system. A processor receives an off-host image verification request from a second information handling system. In response to the off-host image verification request, the processor reads first metadata for a next firmware component, provides the first metadata to the second information handling system, and receives a golden hash value from the second information handling system. In response to the first hash value not matching the golden hash value, the processor applies a mitigation policy. In response to the first hash value matching the golden hash value, the processor provides a device verification signal.

Abstract: An information handling system stores a hash values for firmware components for the information handling system. A processor receives an off-host image verification request from a second information handling system. In response to the off-host image verification request, the processor reads first metadata for a next firmware component, provides the first metadata to the second information handling system, and receives a golden hash value from the second information handling system. In response to the first hash value not matching the golden hash value, the processor applies a mitigation policy. In response to the first hash value matching the golden hash value, the processor provides a device verification signal.

Abstract: Embodiments of information handling systems (IHS) and computer implemented methods are disclosed herein to restore system firmware to a selected restore point. In one embodiment, the IHS may include a computer readable non-volatile memory configured to store system firmware, a computer readable storage device configured to store an operating system (OS), a system registry, and an OS restore application, and a processing device configured to execute program instructions within the OS restore application to restore the system registry to a selected restore point and reboot the IHS. As the IHS is in the process of being rebooted, the processing device may execute program instructions within a firmware restore application stored within the computer readable non-volatile memory or the computer readable storage device to restore the system firmware to the selected restore point.

Abstract: Embodiments of information handling systems (IHS) and computer implemented methods are disclosed herein to restore system firmware to a selected restore point. In one embodiment, the IHS may include a computer readable non-volatile memory configured to store system firmware, a computer readable storage device configured to store an operating system (OS), a system registry, and an OS restore application, and a processing device configured to execute program instructions within the OS restore application to restore the system registry to a selected restore point and reboot the IHS. As the IHS is in the process of being rebooted, the processing device may execute program instructions within a firmware restore application stored within the computer readable non-volatile memory or the computer readable storage device to restore the system firmware to the selected restore point.

Abstract: Unauthorized code may be stored as data in a data volume of a firmware volume. To prevent or block execution of the unauthorized code, the firmware file system (FFS) file that includes the unauthorized code may be tagged, marked or deleted according to a system bios policy. These corrupted FFS files are thus blocked from execution during initialization or a boot process of a basic input/output system (BIOS) firmware as they are not published or enumerated to an execution list of the BIOS firmware.

Abstract: System and methods are provided for distributing firmware updates to groups of IHSs (Information Handling Systems) managed by an organization. The organization managing the IHSs specifies categorizations for each IHS that are used to separate the managed IHSs into firmware update groups. A GUID (Global Unique Identifier) is assigned to each IHS, in some scenarios during the manufacture of the IHS. The assigned GUID specifies one or more firmware update groups to which an IHS has been assigned. The organization, or other technical support entity, utilizes a firmware distribution system for delivery of firmware updates to supported IHSs. The organization signals the delivery of updates to a firmware update group by specifying the group's GUID to the firmware distribution service. The IHS, identified by its assigned GUID, queries a firmware distribution services in order to determine whether new firmware updates have been made available to its assigned firmware update group.

Abstract: System and methods are provided for distributing firmware updates to groups of IHSs (Information Handling Systems) managed by an organization. The organization managing the IHSs specifies categorizations for each IHS that are used to separate the managed IHSs into firmware update groups. A GUID (Global Unique Identifier) is assigned to each IHS, in some scenarios during the manufacture of the IHS. The assigned GUID specifies one or more firmware update groups to which an IHS has been assigned. The organization, or other technical support entity, utilizes a firmware distribution system for delivery of firmware updates to supported IHSs. The organization signals the delivery of updates to a firmware update group by specifying the group's GUID to the firmware distribution service. The IHS, identified by its assigned GUID, queries a firmware distribution services in order to determine whether new firmware updates have been made available to its assigned firmware update group.

Abstract: In accordance with embodiments of the present disclosure, an information handling system may include a processor, a controller, a driver, and a basic/input output system. The controller may be associated with an air mover and configured to generate an interrupt responsive to an event associated with the air mover. The driver may be embodied in an operating system configured for execution on the processor, the driver configured to, during a runtime execution of the operating system in which the event occurred, receive at least one of the interrupt from the controller or an indication of the interrupt from a basic input/output system. The basic input/output system may comprise a program of instructions executable by the processor and configured to cause the processor to, responsive to the event, receive air mover data from the air mover, and communicate the air mover data to the driver.

Abstract: Unauthorized code may be stored as data in a data volume of a firmware volume. To prevent or block execution of the unauthorized code, the firmware file system (FFS) file that includes the unauthorized code may be tagged, marked or deleted according to a system bios policy. These corrupted FFS files are thus blocked from execution during initialization or a boot process of a basic input/output system (BIOS) firmware as they are not published or enumerated to an execution list of the BIOS firmware.

Abstract: A basic input/output system (BIOS) may be automatically updated by a BIOS distribution service. In certain environments such automatic updates may not be desirable as the update may not have been tested or may cause interruptions in one or more information handling systems or applications. Updating an extensible firmware interface system resource table (ESRT) with one or more values may disable such automatic updates. A BIOS version control policy may be utilized to determine the one or more values for the ESRT such that BIOS updates are not automatic or that only predetermined, tested, or otherwise approved BIOS updates are permitted. One or more values of the BIOS version control policy may be set or determined and may be protected, for example, password protected so that all information handling systems within a given environment or network maintain the proper BIOS version.

Abstract: In accordance with embodiments of the present disclosure, an information handling system may include a processor, a controller, a driver, and a basic/input output system. The controller may be associated with an air mover and configured to generate an interrupt responsive to an event associated with the air mover. The driver may be embodied in an operating system configured for execution on the processor, the driver configured to, during a runtime execution of the operating system in which the event occurred, receive at least one of the interrupt from the controller or an indication of the interrupt from a basic input/output system. The basic input/output system may comprise a program of instructions executable by the processor and configured to cause the processor to, responsive to the event, receive air mover data from the air mover, and communicate the air mover data to the driver.

Abstract: A method, apparatus, and computer-readable medium for providing memory management functions are provided. According to one method, a memory allocation process is exposed that receives a requested memory size with a memory allocation request and returns a pointer to an area of allocated memory of the requested memory size if available. A memory deallocation process is also exposed that receives requests to deallocate previously allocated memory regions in the form of a pointer to the memory region to be deallocated. The allocation and deallocation processes maintain a list of linked lists, each of the linked lists describing an unallocated portion of the memory. Only a single linked list must be updated by the allocation process. The deallocation process adds a new linked list and rebuilds the list of linked lists to merge any linked lists corresponding to adjacent portions of memory.

Abstract: A method for providing event notification to an application is disclosed. The method may include sending a message to an operating system (OS) driver when a first event occurs. Code in a BIOS associated with the first event may be executed after the OS driver receives the message. A first notification generated by the BIOS may be provided to the OS driver.