IP Library Granted Patent US 11,630,660
Granted Patent B2
US 11,630,660 · App. 17/068,746 · Granted Apr 18, 2023

Firmware management

Inventors: Ahmad Bilal (Bellevue, WA); Thanhy Mather (Bellevue, WA); Tomas Vetrovsky (Bellevue, WA); Pavel Zeman (Atlanta, GA)
Assignee: VMware, Inc.
G06F8/71G06F1/3206G06F9/44505
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 11,630,660
App. No.
17/068,746
Granted
Apr 18, 2023
Kind
B2
Abstract

Disclosed are various examples for enforcing firmware profiles. First, it is determined that a device record associated with a client device fails to specify a firmware profile. A firmware profile is then generated for the client device. Subsequently, a command is generated that causes a firmware of the client device to be configured based at least in part on the firmware profile. The firmware profile is then stored in the device record.

Claims (40)

1. A system, comprising:

a computing device comprising a processor and a memory; and

machine-readable instructions stored in the memory that, when executed by the processor, cause the computing device to at least:

determine that a firmware profile associated with a client device has been created;

determine a firmware of the client device based at least in part on querying at least one configuration settings of the client device, the at least one configuration setting comprising an operating system registry value;

generate a command to configure a firmware setting of the client device based at least in part on a value of a field in a user interface accessible to the computing device, the command comprising the firmware profile; and

cause the command to be provided to the client device.

2. The system of claim 1 , wherein the command to configure the firmware setting of the client device comprises a client identifier for the client device and the firmware profile.

3. The system of claim 1 , wherein the machine-readable instructions, when executed by the processor, further cause the computing device to at least determine that the command has been executed on the client device.

4. The system of claim 1 , wherein the machine-readable instructions, when executed by the processor, further cause the computing device to at least:

receive a firmware value from the client device; and

store the firmware value in a device record associated with the client device.

5. The system of claim 4 , wherein the firmware value indicates a current status of the firmware setting.

6. The system of claim 1 , wherein the machine-readable instructions, when executed by the processor, further cause the computing device to at least determine a compliance of the client device with at least one compliance rule.

7. The system of claim 1 , wherein the machine-readable instructions, when executed by the processor, further cause the computing device to at least cause to be rendered an indication of the firmware setting of the client device in the user interface.

8. A non-transitory computer-readable medium embodying executable instructions, which, when executed by a computing device, cause the computing device to at least:

determine that a firmware profile associated with a client device has been created;

determine a firmware of the client device based at least in part querying at least one configuration settings of the client device, the at least one configuration setting comprising an operating system registry value;

generate a command to configure a firmware setting of the client device based at least in part on a value of a field in a user interface accessible to the computing device, the command comprising the firmware profile; and

cause the command to be provided to the client device.

9. The non-transitory computer-readable medium of claim 8 , wherein the command to configure the firmware setting of the client device comprises a client identifier for the client device and the firmware profile.

10. The non-transitory computer-readable medium of claim 8 , wherein the executable instructions, when executed by the computing device, further cause the computing device to at least determine that the command has been executed on the client device.

11. The non-transitory computer-readable medium of claim 8 , wherein the executable instructions, when executed by the computing device, further cause the computing device to at least:

receive a firmware value from the client device; and

store the firmware value in a device record associated with the client device.

12. The non-transitory computer-readable medium of claim 11 , wherein the firmware value indicates a current status of the firmware setting.

13. The non-transitory computer-readable medium of claim 8 , wherein the executable instructions, when executed by the computing device, further cause the computing device to at least determine a compliance of the client device with at least one compliance rule.

14. The non-transitory computer-readable medium of claim 8 , wherein the executable instructions, when executed by the computing device, further cause the computing device to at least cause to be rendered an indication of the firmware setting of the client device in the user interface.

15. A computer-implemented method, comprising:

determining that a firmware profile associated with a client device has been created;

determining a firmware of the client device based at least in part on querying at least one configuration settings of the client device, the at least one configuration setting comprising an operating system registry value;

generating a command to configure a firmware setting of the client device based at least in part on a value of a field in a user interface, the command comprising the firmware profile; and

causing the command to be provided to the client device.

16. The computer-implemented method of claim 15 , wherein the command to configure the firmware setting of the client device comprises a client identifier for the client device and the firmware profile.

17. The computer-implemented method of claim 15 , further comprising determining that the command has been executed on the client device.

18. The computer-implemented method of claim 15 , further comprising:

receiving a firmware value from the client device; and

storing the firmware value in a device record associated with the client device.

19. The computer-implemented method of claim 15 , further comprising determining a compliance of the client device with at least one compliance rule.

20. The computer-implemented method of claim 15 , further comprising causing to be rendered an indication of the firmware setting of the client device in the user interface.

Assignments (3)
PATENT ASSIGNMENT Recorded Aug 5, 2024
From: VMWARE LLC
To: OMNISSA, LLC
Reel/Frame 068327/0365 →
SECURITY INTEREST Recorded Jul 3, 2024
From: OMNISSA, LLC
To: UBS AG, STAMFORD BRANCH
Reel/Frame 068118/0004 →
CHANGE OF NAME Recorded Apr 15, 2024
From: VMWARE, INC.
To: VMWARE LLC
Reel/Frame 067102/0395 →
Continuity (2)
Continuation 16043366 · Jul 24, 2018
Related Publication 20210042109A1 · Feb 11, 2021