Abstract: In one or more embodiments, one or more systems, one or more methods, and/or one or more methods may: execute a first information handling system (IHS) initialization executable via an environment associated with IHS firmware; register, by the first IHS initialization executable, a process configured to store multiple IHS initialization executable/OS executable pairs via a volatile memory medium of the IHS; for each IHS initialization executable/OS executable pair of the multiple IHS initialization executable/OS executable pairs: call, by an IHS initialization executable of the IHS initialization executable/OS executable pair, the process; and copy, by the process, an OS executable of the IHS initialization executable/OS executable pair from the first non-volatile memory medium to the volatile memory medium; retrieve a driver via a network; execute the driver; and copy, by the driver, each OS executable, which was copied to the volatile memory medium, to a non-volatile memory medium of the IHS.

Abstract: In one or more embodiments, one or more systems, one or more methods, and/or one or more methods may: register a subroutine configured to store multiple addresses of a volatile memory medium VMM of an information handling system (IHS); for each IHS initialization executable/OS executable pair of multiple IHS initialization executable/OS executable pairs: retrieve, from a first non-volatile memory medium (NVMM), an IHS initialization executable of the IHS initialization executable/OS executable pair; copy, by the IHS initialization executable, an OS executable of the IHS initialization executable/OS executable pair from the first NVMM to the VMM; call, by the IHS initialization executable, the subroutine; store, by the subroutine, an address associated with the OS executable via a data structure stored by the VMM; and copy, by a first OS executable, the OS executable from the VMM to a second NVMM based at least on the address associated with the OS executable.

Abstract: In one or more embodiments, one or more systems, one or more methods, and/or one or more methods may: execute a first information handling system (IHS) initialization executable via an environment associated with IHS firmware; register, by the first IHS initialization executable, a process configured to store multiple IHS initialization executable/OS executable pairs via a volatile memory medium of the IHS; for each IHS initialization executable/OS executable pair of the multiple IHS initialization executable/OS executable pairs: call, by an IHS initialization executable of the IHS initialization executable/OS executable pair, the process; and copy, by the process, an OS executable of the IHS initialization executable/OS executable pair from the first non-volatile memory medium to the volatile memory medium; retrieve a driver via a network; execute the driver; and copy, by the driver, each OS executable, which was copied to the volatile memory medium, to a non-volatile memory medium of the IHS.

Abstract: In one or more embodiments, one or more systems, one or more methods, and/or one or more methods may: register a subroutine configured to store multiple network resource addresses via a volatile memory medium; for each information handling system (IHS) initialization executable of multiple IHS initialization executables: retrieve, from a non-volatile memory medium, the IHS initialization executable; execute the IHS initialization executable via an environment associated with IHS firmware; call, by the IHS initialization executable, the subroutine; and store, by the subroutine, a network resource address associated with an operating system (OS) executable via command line arguments, where the command line arguments are stored via a data structure in the volatile memory medium; and for each network resource address of the command line arguments: retrieve, based at least on the network resource address, an OS executable associated with the network resource address from another IHS via a network.

Abstract: In one or more embodiments, one or more systems, one or more methods, and/or one or more methods may: register a subroutine configured to store multiple network resource addresses via a volatile memory medium; for each information handling system (IHS) initialization executable of multiple IHS initialization executables: retrieve, from a non-volatile memory medium, the IHS initialization executable; execute the IHS initialization executable via an environment associated with IHS firmware; call, by the IHS initialization executable, the subroutine; and store, by the subroutine, a network resource address associated with an operating system (OS) executable via command line arguments, where the command line arguments are stored via a data structure in the volatile memory medium; and for each network resource address of the command line arguments: retrieve, based at least on the network resource address, an OS executable associated with the network resource address from another IHS via a network.

Abstract: In one or more embodiments, one or more systems, one or more methods, and/or one or more methods may: register a subroutine configured to store multiple network resource addresses via a volatile memory medium; for each information handling system (IHS) initialization executable of multiple IHS initialization executables: retrieve, from a non-volatile memory medium, the IHS initialization executable; execute the IHS initialization executable via an environment associated with IHS firmware; call, by the IHS initialization executable, the subroutine; and store, by the subroutine, a network resource address associated with an operating system (OS) executable via command line arguments, where the command line arguments are stored via a data structure in the volatile memory medium; and for each network resource address of the command line arguments: retrieve, based at least on the network resource address, an OS executable associated with the network resource address from another IHS via a network.

Abstract: In one or more embodiments, one or more systems, one or more methods, and/or one or more methods may: register a subroutine configured to store multiple addresses of a volatile memory medium VMM of an information handling system (IHS); for each IHS initialization executable/OS executable pair of multiple IHS initialization executable/OS executable pairs: retrieve, from a first non-volatile memory medium (NVMM), an IHS initialization executable of the IHS initialization executable/OS executable pair; copy, by the IHS initialization executable, an OS executable of the IHS initialization executable/OS executable pair from the first NVMM to the VMM; call, by the IHS initialization executable, the subroutine; store, by the subroutine, an address associated with the OS executable via a data structure stored by the VMM; and copy, by a first OS executable, the OS executable from the VMM to a second NVMM based at least on the address associated with the OS executable.

Abstract: In one or more embodiments, one or more systems, one or more methods, and/or one or more methods may: register a subroutine configured to store multiple addresses of a volatile memory medium VMM of an information handling system (IHS); for each IHS initialization executable/OS executable pair of multiple IHS initialization executable/OS executable pairs: retrieve, from a first non-volatile memory medium (NVMM), an IHS initialization executable of the IHS initialization executable/OS executable pair; copy, by the IHS initialization executable, an OS executable of the IHS initialization executable/OS executable pair from the first NVMM to the VMM; call, by the IHS initialization executable, the subroutine; store, by the subroutine, an address associated with the OS executable via a data structure stored by the VMM; and copy, by a first OS executable, the OS executable from the VMM to a second NVMM based at least on the address associated with the OS executable.

Abstract: In one or more embodiments, one or more systems, one or more methods, and/or one or more methods may: register a subroutine configured to store multiple network resource addresses via a volatile memory medium; for each information handling system (IHS) initialization executable of multiple IHS initialization executables: retrieve, from a non-volatile memory medium, the IHS initialization executable; execute the IHS initialization executable via an environment associated with IHS firmware; call, by the IHS initialization executable, the subroutine; and store, by the subroutine, a network resource address associated with an operating system (OS) executable via command line arguments, where the command line arguments are stored via a data structure in the volatile memory medium; and for each network resource address of the command line arguments: retrieve, based at least on the network resource address, an OS executable associated with the network resource address from another IHS via a network.

Abstract: In one or more embodiments, one or more systems, one or more methods, and/or one or more methods may: register a subroutine configured to store multiple addresses of a volatile memory medium VMM of an information handling system (IHS); for each IHS initialization executable/OS executable pair of multiple IHS initialization executable/OS executable pairs: retrieve, from a first non-volatile memory medium (NVMM), an IHS initialization executable of the IHS initialization executable/OS executable pair; copy, by the IHS initialization executable, an OS executable of the IHS initialization executable/OS executable pair from the first NVMM to the VMM; call, by the IHS initialization executable, the subroutine; store, by the subroutine, an address associated with the OS executable via a data structure stored by the VMM; and copy, by a first OS executable, the OS executable from the VMM to a second NVMM based at least on the address associated with the OS executable.

Abstract: A pre-boot authentication (PBA) credential sharing system includes a secure subsystem including an off-host processing system and a secure storage. A credential management application is coupled to the off-host processing system. A data protection engine is coupled to the off-host processing system and a PBA database. The data protection engine receives a notification from the off-host processor of the enrollment of an authentication credential in the secure storage by the credential management application, and provides PBA object information for association with the authentication credential to create a PBA object that is stored in the secure storage. Subsequently, while in a pre-boot environment, the data protection engine requests the PBA object from the secure storage, retrieves storage authentication information from the PBA database using the PBA object, and performs a pre-boot authentication process using the storage authentication information.

Abstract: A pre-boot authentication (PBA) credential sharing system includes a secure subsystem including an off-host processing system and a secure storage. A credential management application is coupled to the off-host processing system. A data protection engine is coupled to the off-host processing system and a PBA database. The data protection engine receives a notification from the off-host processor of the enrollment of an authentication credential in the secure storage by the credential management application, and provides PBA object information for association with the authentication credential to create a PBA object that is stored in the secure storage. Subsequently, while in a pre-boot environment, the data protection engine requests the PBA object from the secure storage, retrieves storage authentication information from the PBA database using the PBA object, and performs a pre-boot authentication process using the storage authentication information.