Abstract: Disclosed method for supporting multi-component capabilities in a multiservice framework provisions a host system with a platform capabilities manifest (PCM) indicative of platform supported capabilities including at least one multi-component capability enabled or otherwise associated with a plurality of modular components. Upon detecting a modular component installation, comprising an installation of a new version of a modular component, a verification of the multi-component capability is performed to confirm authenticity and integrity of the capability as a whole and its individual components. If verification is not confirmed, one or more responsive actions may be performed. Responsive actions may include notifying a user or information technology (IT) administrator regarding the non-compliance and/or rolling back the installed modular component to a prior version.

Abstract: Disclosed methods and systems for managing diagnostic tools for an information handling system associated with a platform provision the system with an intelligent install service configured to orchestrate installation of runtime capabilities. Responsive to detecting a request for field service assist (FSA) capability, the intelligent install service may be invoked to identify one or more FSA modules indicated in the request and determine a supplementary capability manifest corresponding to each requested FSA module. User input requesting FSA capabilities may be indicated via user input provided to an FSA user interface or via command line interface (CLI) entries from the end user or included in a CLI script. Each manifest extension may indicate an installation repository for the corresponding FSA. The intelligent install service may then access each installation repository to install the FSA module on the information handling system.

Abstract: Disclosed methods and systems provision an information handling system with an installation status verification (ISV) service configured to perform ISV operations. The ISV operations monitor the system to detect new device driver installations and, responsive to detecting a new device driver installation, determine a companion software status indicating whether companion software associated with the driver has been successfully installed. If the companion software status is not indicative of successful installation of the companion software, one or one or actions may be taken in response. Representative actions include notifying an end user of the companion software status and explicitly installing the companion software.

Abstract: Disclosed system management methods and systems support scalable installation and association of customized capabilities for specific end users. Disclosed methods and systems may first provision the system with a multiservice framework, such as described herein, suitable for creating a PCM and installing one or more capabilities in accordance with the PCM. Upon detecting user login information indicating a user-specific capability (USC) option, disclosed features may access a USC manifest extension, residing in a cloud resource or elsewhere, indicative of one or more extended capabilities associated with the user and, after confirming authenticity and integrity of the USC manifest extension, invoke the multiservice framework to install the extended capabilities in accordance with the USC manifest extension.

Abstract: Disclosed methods and systems leverage a multiservice framework and a platform capability manifest (PCM) to enable dynamic management of service-based capabilities by provisioning and launching a service-focused capability in response to a triggering condition. One or more function-specific monitors may monitor for a trigger to enable and perform a corresponding service capability. Upon detection of the trigger, service capability operations may be performed to modify the PCM to include an indication of an installation payload associated with the service capability, install one or more files included in the installation payload to enable the service capability, and exercising the service capability to perform a service-based function. Representative service capabilities may include telemetry collection capabilities, diagnostic capabilities, system reset capabilities, remediation capabilities, etc. Service capability operations may be initiated in response to user input.

Abstract: Disclosed methods and systems implement scalable monitoring of resource installations, including, e.g., software services, drivers, hardware components and subcomponents to perform proactive remediation based on system policy requirements including policies defining one or more mandatory resources. After generating a PCM in accordance with a platform associated with the system and provisioning the system with one or more of the platform supported capabilities indicated in the PCM, mandatory resource information, identifying mandatory resources for the platform, is retrieved or otherwise obtained. Discloses methods and systems may monitor resource installations and, upon detecting a new installation, a determination of whether the corresponding resource is a mandatory resource and, accordingly, whether installation of the resource modifies a setting indicated in the PCM.

Abstract: An intelligent install service running on a host OS of a system provisioned with a PCM, upon detecting an installation request from an installation-approved requestor, performed dynamic installation operations including identifying capabilities requested by the requestor and determining whether the system includes resources sufficient for the capabilities requested. If so, installation of the requested capabilities may be initiated. The installation request may indicate one of a plurality of installation options corresponding to predetermined groups of capabilities. A first installation option may correspond to base drivers for mandatory capabilities and services, a second installation option may correspond to OEM-provided services, etc. Representative OEM-provided services may include, as illustrative examples, an optimizing service and a collaboration touchpad service. The optimizing service improves system performance based, at least in part, on historical usage data.

Abstract: Disclosed methods support modifications of self-contained features bundled within a multi-feature installation payload package. A platform capability module (PCM) indicative of platform supported capabilities and their corresponding installation payload sources is accessed. The platform supported capabilities include a capability bundle encompassing a plurality of bundled features. The installation payload sources may be monitored. Upon detecting a modification of the bundled payload source, a modified feature, comprising a bundled feature associated with the modification, and a corresponding installation payload are identified. If the modified feature is verified and otherwise confirmed, the modified feature is installed in accordance with the installation payload. If the modified feature is not confirmed, the installation payload corresponding to the modified feature may be removed or restored to a prior version. A modified PCM reflecting the modified feature may be generated.

Abstract: Disclosed methods and system may determine one or more platform-supported capabilities of an information handling system associated with an end user and one or more installed capabilities, i.e., a supported capability installed on the information handling system and available to the end user. A multiservice framework may be leveraged to generate a platform capability manifest (PCM) indicative of supported capabilities. Installed capabilities may be determined with a task automation resource, e.g., executing a PowerShell get-WindowsFeature cmdlet.

Abstract: Systems and methods for prioritizing loading of agents and plugins during boot time of an IHS are described. In an illustrative, non-limiting embodiment, a first Information Handling System (IHS) may include: a processor; and a memory coupled to the processor, wherein the memory comprises program instructions store thereon that, upon execution by the processor, cause the IHS to: obtain behavior information of one or more users of the IHS regarding at least one application of the IHS; and launch an agent associated with the application during a boot of the IHS, or load a plugin associated with the application during the boot of the IHS, based, at least in part, on the behavior information.

Abstract: Disclosed methods and systems leverage a multiservice framework to provision a host system with capabilities indicated in a platform capability manifest (PCM). Responsive to detecting an identification of a particular capability as a restricted capability updates of the restricted capability are blocked. The particular capability and a version of the capability may be identified within a restriction manifest, thereby ensuring that the specified version of the capability will not be altered by conventional OS and OEM update services. The restricted capability may be a hardware component of the host and the restriction may prevent updates to a device driver of the component. The restriction manifest may be created by an IT administrator and delivered to the multiservice framework. Exemplary implementations of software services enabling this managed restriction functionality is also disclosed.

Abstract: Dependency compliance features for assessing software dependencies in a host information handling system and remediating dependency non-compliance exceptions are disclosed. Disclosed methods and systems obtain a platform capability manifest (PCM) including capability information for each of one or more supported capabilities and identify at least one enabled capability. The enabled capability may correspond to a software service installed and enabled on the host. A dependency compliance of the host is evaluated based, at least in part, on dependency information included in the PCM. If a dependency non-compliance is detected, the enabled capability may leverage the multiservice framework to remediate the applicable service to achieve dependency compliance. Dependency compliance may include version compliance wherein the dependency information may include version criteria for each software library and/or version criteria for the enabled software service.

Abstract: Disclosed methods obtain, from a cloud licensing server, licensing information for an end user of a host system. The licensing information indicates valid end user licenses for accessing licensable capabilities. The licensing information may be provided to an intelligent installation service (IIS) running in the host operating system (OS). The IIS leverages a multiservice framework installer to provision the host system with capabilities, including licensable capabilities, in accordance with the licensing information. The licensable capabilities may include licensable capabilities pertaining to audio performance capabilities, including hardware and software coders/decoders (codecs), telemetry capabilities, and overclocking capabilities. The IIS may be configured to scan one or more file depositories to determine available software services and scan the host to determine capabilities available to the end user.

Abstract: Disclosed methods retrieve ad hoc configuration information for an enabled capability of a host system. The enabled capability is associated with a component included in a platform capability manifest (PCM) for the host. Prior to receiving the ad hoc configuration, a multiservice installation may have been performed to provision the host with platform capabilities indicated in the PCM. Upon receiving the ad hoc configuration information, the configuration of the enabled capability is modified in accordance with the ad hoc configuration information. The ad hoc configuration information may correspond to a component configuration indicated by a privileged user such as an IT administrator via a remote console communicatively coupled to the host. The component may be a plug and play (PnP) component and modifying the configuration may include modifying settings in a host OS configuration database, e.g., Windows registry, and invoking a PnP device manager to install the component.

Abstract: Disclosed methods and systems may initially leverage a multiservice framework to provision a host system in accordance with platform capabilities indicated in a platform capability manifest (PCM). Thereafter, available hardware support applications (HSAs) are detected and an HSA list enumerating the available HSAs is generated. An HSA policy approved by an IT administrator and indicative of one or more HSA permissions and restrictions is obtained and used to generate an HSA manifest extension indicative of permitted HSAs and prohibited HSAs in accordance with the HSA policy and the available HSAs. Based, at least in part, on the permitted and prohibited HSAs indicated in the HSA manifest, an HSA-aware PCM is generated in accordance with the HSA manifest.

Abstract: Disclosed methods and systems leverage a multiservice framework to provision a host system based on platform supported capabilities indicated in a platform capability manifest (PCM). Upon receiving a candidate manifest, indicative of one or more requested capabilities, manifest conflict information, identifying the requested capabilities, is generated. After obtaining arbitration policy information for resolving capability conflicts and requests, a resolved manifest is generated based on the PCM, the manifest conflict information, and the arbitration policy. In this manner, the resolved manifest enables the host to deny or accommodate capability requests in accordance with the arbitration policy. The multiservice framework may be again leveraged to provision the host system in accordance with the resolved manifest.

Abstract: Disclosed systems and methods perform or include provisioning a host with platform-supported capabilities identified in a platform capability manifest (PCM) and detecting, by an auto-uninstall service running in an operating system (OS) of the host, a runtime uninstallation of a device driver for a hardware device identified in the PCM. In response, the method identifies companion software associated with the device driver and uninstalls the companion software. The companion software may include software augmenting device functionality. The driver uninstallation may correspond to a manual uninstallation such as an uninstallation initiated in response to end user input. Identifying companion software may include identifying changes in an OS-level configuration database, e.g., a file path in a Windows OS registry; identifying changes in a device driver store; changes in a directory listing of the device driver store and file size changes for one or more files in the device driver store.

Abstract: Disclosed methods and systems invoke a multiservice framework to provision a host system with platform capabilities in accordance with capabilities identified in a platform capability manifest (PCM). Responsive to detecting installation of a service-dependent application (SDA), SDA management operations are performed. An SDA may include an application that has a dependency on a platform service. The SDA management operations may include accessing a PCM extension associated with the SDA. The PCM extension may identify the platform service and calculate or otherwise determine an updated PCM incorporating the platform capability of the PCM extension. The multiservice framework may then be invoked to install the platform service in accordance with the updated PCM. Exemplary implementations may include a first operating system (OS) software service to perform a customized installation process that includes installing the SDA.

Abstract: Disclosed methods and systems for detecting a new resource on a host information handling system that encompasses multiple ecosystem layers including a hardware/firmware layer, an operating system layer, and a cloud layer. Responsive to detecting the new resource, a multilayer orchestration is performed. The multilevel orchestration includes detecting included components within each of two or more ecosystem layers, accessing a platform capability manifest (PCM) indicative of platform supported capabilities, and responsive to identifying one or more open dependencies based on the platform supported capabilities and the included components, installing or updating one or more included resources to resolve one or more of the open dependencies.

Abstract: Disclosed methods and systems leverage a multiservice distribution framework to monitor and, when necessary, remediate enabled capabilities running on a host to comply with configuration criteria indicated in a platform capability manifest (PCM) including capability information for supported capabilities. When a new capability is enabled, a manifest compliance of the enabled capability is determined based on PCM capability information for the corresponding supported capability. If the enabled capability is not manifest compliant, the enabled capability is remediated to obtain manifest compliance. The enabled capability may correspond to a software service and non-compliance may be based on a version of the enabled software service in conflict with version criteria included in the PCM. Remediation may include a PCM-assisted installation of a manifest compliant version of the software service.