Method to Dynamically Create Plug and Play Identifiers in Firmware to Facilitate Deployment of Windows Services
An information handling system includes an application installer, a gateway service, and a driver update service. The application installer retrieves an application from an online application store, and installs the application. The gateway service receives a request to enable a hardware identifier from the application, and enables the hardware identifier and trigger a driver update service. The driver update service checks for an updated driver for the hardware identifier, and downloads and installs the updated driver.
1 . An information handling system comprising:
a gateway service configured to:
in response to an application being installed, receive a request to enable a hardware identifier from the application, wherein the application is retrieved from an online application store;
receive the hardware identifier from a basic input/output system of the information handling system; and
enable the hardware identifier and trigger a driver update service; and
the driver update service configured to:
check for an updated driver for the hardware identifier; and
download and install the updated driver.
2 . The information handling system of claim 1 , wherein the driver provides service functions for the application.
3 . The information handling system of claim 2 , wherein the driver executes service functions at a higher level of access than the application executes instructions.
4 . The information handling system of claim 1 , wherein the driver is a universal driver and does not utilize co-installers and does not include dependencies.
5 . A method for updating firmware of a hardware component, comprising:
installing an updated driver for the hardware component;
obtaining dependency requirements from a companion application, wherein the dependency requirements include information to determine whether interoperable components are updated to required versions;
checking currently installed components against the dependency requirements;
trigger an update for at least one component not satisfying the dependency requirements; and
updating the firmware of the hardware component when the dependency requirements are satisfied.
6 . The method of claim 5 , further comprising detecting the associated hardware when the hardware component is connected to an information handling system.
7 . The method of claim 6 , further comprising enabling a hardware identifier corresponding to the hardware component to trigger the update.
8 . The method of claim 7 , further comprising sending a request to a gateway service to enable the hardware identifier.
9 . The method of claim 5 , wherein the hardware component is a detachable component.
10 . The method of claim 9 , wherein the detachable component is a dock.
11 . The method of claim 5 , wherein the companion application includes updated firmware code.
12 . The method of claim 5 , further comprising checking for an update to the companion application and installing the update.
13 . The method of claim 5 , further comprising obtaining dependency requirements from the companion application.
14 . The method of claim 5 , wherein the driver is a universal driver and does not utilize co-installers and does not include dependencies.
15 . A non-transitory computer-readable medium including code that when executed causes a processor to perform a method, the method comprising:
checking a version of a companion application against a minimum version;
triggering installation of an update for the companion application when the version is less than the minimum version;
obtaining a dependency requirement from the companion application, wherein the dependency requirements include information to determine whether interoperable components are updated to required versions;
checking one or more firmware or software versions against the dependency requirement;
triggering installation of updates for the firmware or software components when the dependency requirement is not satisfied; and
updating a firmware of a hardware when the dependency requirement is satisfied.
16 . The non-transitory computer-readable medium of claim 15 , wherein the hardware is detachable.
17 . The non-transitory computer-readable medium of claim 16 , wherein the hardware is a dock.
18 . The non-transitory computer-readable medium of claim 16 , wherein the companion application includes update firmware code.
19 . The non-transitory computer-readable medium of claim 15 , further comprising detecting the hardware when the hardware is connected to an information handling system.
20 . The non-transitory computer-readable medium of claim 19 , further comprising enabling a hardware identifier corresponding to the hardware component to trigger the update.