Abstract: Systems and methods for mitigating Information Handling System (IHS) startup latency in hoteling environments due to driver and firmware updates are described. In an embodiment, an IHS configured to: receive an indication of a selected one of a plurality of workspaces; in response to the indication, retrieve a list of driver or firmware updates corresponding to peripheral devices available in the selected workspace; identify a subset of driver or firmware updates among the list of driver or firmware updates based, at least in part, upon a comparison between the list of driver or firmware updates and a list of one or more drivers or firmware installed in the IHS; and initiate installation of the subset of one or more driver or firmware updates before the IHS arrives at the selected workspace.

Abstract: Micro swipes for generating custom user interface responses can be supported. A mobile application can include a micro swipe handler that is configured to detect when a user has performed a micro swipe on a user interface element. The micro swipe handler can interface with a micro swipe management service to determine if any custom user interface response to a micro swipe is associated with the user interface element. If so, the micro swipe management service can provide the custom user interface response to the micro swipe handler which in turn can update the user interface of the mobile application in accordance with the custom user interface response.

Abstract: Systems and methods for deploying software updates in heterogeneous workspace environments are described. The system for managing workspaces includes computer-executable instructions for obtaining multiple inventories corresponding to multiple workspaces of an IHS, wherein the inventories each include information associated with the applications deployed in its respective workspace. The instructions are further executed to, for each inventory, identify the workspace associated with the inventory, determine which of the applications are to be updated with new software, and deploy the determined new software to the identified workspace.

Abstract: Storage drives can be configured to provide a component ID. An update tool on an end user device can be configured to retrieve this component ID in response to receiving a catalog that defines available firmware updates and to use the retrieved component ID to dynamically identify which firmware update applies to a particular storage drive. The firmware update can then be installed on the storage drive. The update tool may also perform a health assessment to dynamically determine whether the storage drive's health is sufficient to proceed with a firmware update.

Abstract: Methods and systems are provided that may be implemented to methods and systems may be implemented to automatically identify types and status of vulnerabilities in identified software or firmware components (e.g., libraries), and then automatically deploy security vulnerability fixes (e.g., patches or updates) in these identified components across different affected software or firmware applications. In one example, the disclosed methods and systems may operate to dynamically and automatically aggregate identified third party software and/or firmware vulnerabilities into a centralized repository, and may be further implemented to automatically handle the roll out and deployment of vulnerability fixes to patch or update third party libraries to solve any security vulnerability reported on these third party libraries.

Abstract: Systems and methods for deploying software updates in hybrid workspace environments are described. In some embodiments, an Information Handling System (IHS) may include a processor and a memory coupled to the processor, the memory having program instructions stored thereon that, upon execution, cause the IHS to: consolidate an Operating System (OS) and Basic Input/Output System (BIOS) inventory with a plurality of workspace inventories; resolve dependencies among a plurality of updates based upon the consolidated inventories to identify an order of deployment; and deploy the plurality of updates in the order of deployment.

Abstract: System resource compatible update packages can be detected and deployed. An update package's update metadata can include a system resource compatibility profile. Prior to installing an update package, an update tool on an end user device can evaluate the end user device's system resource information against the update package's system resource compatibility profile. If the system resource information does not comply with the update package's system resource compatibility profile, the update tool can forego installing the update package. In this way, the update package can ensure that otherwise compatible update packages are not installed because their installation may reduce the performance of the end user device.

Abstract: An information handling system may include at least one processor; and a Non-Volatile Memory Express (NVMe) solid state drive (SSD) communicatively coupled to the at least one processor; wherein the information handling system is configured to: collect telemetry information regarding the information handling system; and log the telemetry information in a vendor-specific portion of the NVMe SSD via an NVMe set command.

Abstract: The last successful device update can be recovered on a computing system. An update tool can be employed to detect whether an update package is installed successfully. When an update package is successfully installed, the update tool can define a last successful device update that associates the update package with the device that the update package targets. In contrast, when the update package does not install successfully, the update tool can access the last successful device update for the targeted device and use it to obtain and install the previous update package that the last successful device update represents. In this way, the related components for a device can be rolled back to a common state to prevent incompatibilities that may otherwise exist due to the failed installation.

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: Software updates can be deployed in end user devices in coordination with end-user productivity. A system monitoring engine can be employed on end user devices to compile productivity impact data from which heat maps may be created. An optimal deployment detection engine can employ the heat maps to create or maintain period-based groupings. When software updates are available, the optimal deployment detection engine can employ the period-based groupings to create optimal deployment plans specific to the end user devices. The installation of the software updates can then be performed on each end user device in accordance with that end user device's optimal deployment plan.

Abstract: Software updates can be deployed in end user devices in coordination with end-user productivity. A system monitoring engine can be employed on end user devices to compile productivity impact data from which heat maps may be created. An optimal deployment detection engine can employ the heat maps to create or maintain period-based groupings. When software updates are available, the optimal deployment detection engine can employ the period-based groupings to create optimal deployment plans specific to the end user devices. The installation of the software updates can then be performed on each end user device in accordance with that end user device's optimal deployment plan.

Abstract: Best known configurations can be automatically created for particular platforms. An update tool can be installed on end user devices and can include a health monitor engine that creates health reports for drivers and/or firmware installed on the corresponding end user device. The health reports generated on the end user devices can be provided to a best known configuration engine that can evaluate them to calculate a best known configuration for each platform. The best known configurations can then be distributed to the update tool on the end user devices to cause them to configure the end user devices to match the corresponding best known configuration.

Abstract: Best known configurations can be automatically created for particular platforms. An update tool can be installed on end user devices and can include a health monitor engine that creates health reports for drivers and/or firmware installed on the corresponding end user device. The health reports generated on the end user devices can be provided to a best known configuration engine that can evaluate them to calculate a best known configuration for each platform. The best known configurations can then be distributed to the update tool on the end user devices to cause them to configure the end user devices to match the corresponding best known configuration.

Abstract: Storage drives can be configured to provide a component ID. An update tool on an end user device can be configured to retrieve this component ID in response to receiving a catalog that defines available firmware updates and to use the retrieved component ID to dynamically identify which firmware update applies to a particular storage drive. The firmware update can then be installed on the storage drive. The update tool may also perform a health assessment to dynamically determine whether the storage drive's health is sufficient to proceed with a firmware update.

Abstract: The last successful device update can be recovered on a computing system. An update tool can be employed to detect whether an update package is installed successfully. When an update package is successfully installed, the update tool can define a last successful device update that associates the update package with the device that the update package targets. In contrast, when the update package does not install successfully, the update tool can access the last successful device update for the targeted device and use it to obtain and install the previous update package that the last successful device update represents. In this way, the related components for a device can be rolled back to a common state to prevent incompatibilities that may otherwise exist due to the failed installation.

Abstract: A system includes a systems manager configured to retrieve an update package that includes an update installer for updating the information handling system, and to install the update package with the update installer. The update installer retrieves an operating system build number from the information handling system, and parses a metadata file included in the update package to determine a device group based on the operating system build number, wherein the device group includes the applicable updates for the information handling system. The update installer determines a mode of installation based on the operating system build number of the device group, determines a sequence of installation of the applicable updates, and installs the applicable updates according to the sequence of installation and the mode of installation.

Abstract: An enterprise computing management system includes an on-premise computing management system for deploying an update to a first resource and for triggering synchronization of the update to a second resource after deploying the update. The first resource is managed by the on-premise computing management system. A cloud-based computing management system deploys the update to the second resource that is managed by the cloud-based computing management system. In response to the triggering of the synchronization of the update to the second resource, a processor retrieves metadata information of the update, generates a catalog based on the metadata information of the update, publishes the catalog to a repository, and deploys the update to the second resource.

Abstract: A system includes a systems manager configured to retrieve an update package that includes an update installer for updating the information handling system, and to install the update package with the update installer. The update installer retrieves an operating system build number from the information handling system, and parses a metadata file included in the update package to determine a device group based on the operating system build number, wherein the device group includes the applicable updates for the information handling system. The update installer determines a mode of installation based on the operating system build number of the device group, determines a sequence of installation of the applicable updates, and installs the applicable updates according to the sequence of installation and the mode of installation.

Abstract: An enterprise computing management system includes an on-premise computing management system for deploying an update to a first resource and for triggering synchronization of the update to a second resource after deploying the update. The first resource is managed by the on-premise computing management system. A cloud-based computing management system deploys the update to the second resource that is managed by the cloud-based computing management system. In response to the triggering of the synchronization of the update to the second resource, a processor retrieves metadata information of the update, generates a catalog based on the metadata information of the update, publishes the catalog to a repository, and deploys the update to the second resource.