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: Embodiments of systems and computer implemented methods are disclosed to automatically restore operating system (OS) application software to an information handling systems (IHS) when the OS application software is removed from a computer readable storage device of the IHS. The disclosed embodiments control the version of the OS application software being deployed to an IHS when deploying the software from the boot firmware. For example, the disclosed embodiments utilize a version identifier to specify which version of the OS application software should be restored, a Content Deliver Network (CDN) server to store multiple versions of the OS application software, and a registration web server to map a device identifier corresponding to the IHS and the version identifier corresponding to the specified version of the OS application software to a universal resource locator (URL) link identifying where the specified version of the OS application software is stored within the CDN server.

Abstract: Embodiments of systems and computer implemented methods are disclosed to automatically restore operating system (OS) application software to an information handling systems (IHS) when the OS application software is removed from a computer readable storage device of the IHS. The disclosed embodiments control the version of the OS application software being deployed to an IHS when deploying the software from the boot firmware. For example, the disclosed embodiments utilize a version identifier to specify which version of the OS application software should be restored, a Content Deliver Network (CDN) server to store multiple versions of the OS application software, and a registration web server to map a device identifier corresponding to the IHS and the version identifier corresponding to the specified version of the OS application software to a universal resource locator (URL) link identifying where the specified version of the OS application software is stored within the CDN server.

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 system that implements a software tool for data leak prevention whenever a protected document containing sensitive or encrypted content is opened by a document-management application having capability to directly access an Internet Protocol (IP) network, such as the Internet, without using the HyperText Transfer Protocol (HTTP). The application is selectively blocked from accessing the Internet whenever a protected document is opened by the application. The application may be, for example, the Microsoft® Word or the Adobe® Acrobat® Reader. The software tool restores the network access for the application once the protected document is no longer open in the application. Even though one application is blocked from accessing the IP network, the software tool allows another application to access the network so long as a non-protected document is opened by the other application. Thus, application-specific, selective blocking of network access is accomplished by the software tool based on document content.

Abstract: Systems and methods for preventing leakage of protected data to unsecured applications and documents may include determining that a first document is a protected document in a managed application, detecting a request to copy protected data from the first document to a system clipboard accessible by unprotected documents, redirecting the protected data to a secure clipboard, determining that a second document is an unprotected document, detecting a request to paste the protected data into the second document, and refraining from pasting the protected data into the second document. The secure clipboard may be implemented by a data leakage prevention (DLP) client. It may be separate from the system clipboard and inaccessible by unprotected documents. Dynamic-link library injection and API hooking may allow the DLP client to intercept clipboard related function calls made by managed applications into the operating system and to transparently change the behavior of the managed application.

Abstract: In one or more embodiments, one or more systems, methods, and/or processes may redirect a request to open a document to a background process that controls access to the document; may determine policy information associated with the document and a user of an application; may provide the document to the application; may determine an area of a user interface of the application that displays information of the document; may determine watermark information based at least on the policy information; may generate one or more watermarks based at least on the watermark information; and may display the one or more watermarks, based at least on the watermark information, on the area of the user interface of the application that displays the information of the document.

Abstract: A system that implements a software tool for data leak prevention whenever a protected document containing sensitive or encrypted content is opened by a document-management application having capability to directly access an Internet Protocol (IP) network, such as the Internet, without using the HyperText Transfer Protocol (HTTP). The application is selectively blocked from accessing the Internet whenever a protected document is opened by the application. The application may be, for example, the Microsoft® Word or the Adobe® Acrobat® Reader. The software tool restores the network access for the application once the protected document is no longer open in the application. Even though one application is blocked from accessing the IP network, the software tool allows another application to access the network so long as a non-protected document is opened by the other application. Thus, application-specific, selective blocking of network access is accomplished by the software tool based on document content.

Abstract: Systems and methods for preventing leakage of protected data to unsecured applications and documents may include determining that a first document is a protected document in a managed application, detecting a request to copy protected data from the first document to a system clipboard accessible by unprotected documents, redirecting the protected data to a secure clipboard, determining that a second document is an unprotected document, detecting a request to paste the protected data into the second document, and refraining from pasting the protected data into the second document. The secure clipboard may be implemented by a data leakage prevention (DLP) client. It may be separate from the system clipboard and inaccessible by unprotected documents. Dynamic-link library injection and API hooking may allow the DLP client to intercept clipboard related function calls made by managed applications into the operating system and to transparently change the behavior of the managed application.

Abstract: In one or more embodiments, one or more systems, methods, and/or processes may redirect a request to open a document to a background process that controls access to the document; may determine policy information associated with the document and a user of an application; may provide the document to the application; may determine an area of a user interface of the application that displays information of the document; may determine watermark information based at least on the policy information; may generate one or more watermarks based at least on the watermark information; and may display the one or more watermarks, based at least on the watermark information, on the area of the user interface of the application that displays the information of the document.

Abstract: An apparatus comprising: at least one processor; and at least one memory including computer program code, the at least one memory and the computer program code configured to, with the at least one processor, cause the apparatus to perform at least the following: based on an offset, in an eye image, from an eye shape of an eye having a gaze directly at a viewer, provide a modification to a contour of an eyelid featured in the eye image for use in image manipulation to adjust the eye shape to appear as having a gaze directly at a viewer.

Abstract: A method that can stably and reliably resume SED from operating system power saving mode is disclosed. The solution comprises a storage lower filter driver and an extra external SCSI I/O queue. The storage lower filter driver is coupled to the storage class driver and configured to provide a SED power saving transaction in response to an operation system power function. An extra external SCSI queue and correspondingly a unique SCSI I/O queue state machine trigger mechanism are included in order to avoid overwhelming the capability of any particular host adapter. A dummy SCSI package is inserted into internal SCSI queue in last phase of operating system power down transaction so that internal SCSI queue can be activated during operation system power resuming.