# US 2021/0064385 A1 · Bare metal device management

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2021/0064385 A1
- Document ID: US20210064385A1
- Status: Published application
- Kind: A1
- Application number: 17/095,176
- Filed: 2020-11-11
- Published: 2021-03-04
- Earliest claimed: 2018-07-26
- Assignees: VMware, Inc.
- Applicants: VMware, Inc.
- Inventors: Ahmad Bilal; Alexey Polyakov; Tomas Vetrovsky
- Web page: https://patentgrep.com/patent/US20210064385A1

## CPC

- G06F 9/4406: {Loading of operating system}
- G06F 9/4401: Bootstrapping (security arrangements therefor G06F21/57)
- G06F 9/4416: {Network booting; Remote initial program loading [RIPL]}
- G06F 21/44: Program or device authentication
- G06F 21/57: Certifying or maintaining trusted computer platforms, e.g. secure boots or power-downs, version controls, system software checks, secure updates or assessing vulnerabilities
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

Examples described herein include systems and methods for bare metal management of computing devices. Firmware of the computing device can be configured to contact a network location as part of an HTTP boot and download a boot agent. The boot agent can be prioritized to execute before a primary OS boot loader. The boot agent can download an OS configuration including a package that is inserted into the primary OS. The primary OS, as configured, can then boot. The boot agent can also attest to OS health and device compliance on subsequent boots. For example, the boot agent can cause the firmware to track how many boots have occurred since compliance verification. If a threshold number of boots occur without verification, the boot agent can initiate restoration. Alternatively, if a decommission flag is set, the boot agent can cause the computing device to boot into its original configuration.

## Claims

### Claim at position 1

-20. (canceled)

### Claim 21

A method for bare metal device management, comprising:
retrieving, from firmware of a computing device, a network location;
before permitting a primary operating system (“OS”) to boot, contacting the network location and receiving a boot agent;
adding, by the computing device, the boot agent to a system partition of the computing device;
configuring, by the computing device, the boot agent to execute before a primary OS boot manager during boot of the computing device;
applying, by the computing device, an OS configuration to the primary OS, the OS configuration being specified by a management server;
booting the primary OS on the computing device; and
in an instance where a last boot time is more recent than a last compliance check with the management server, downloading a new instance of the boot agent and booting from the new instance of the boot agent.

### Claim 22 (depends on 21)

The method of claim 21, further comprising:
during booting from the new instance of the boot agent, confirming that the primary OS has the OS configuration specified by the management server.

### Claim 23 (depends on 21)

The method of claim 21, further comprising:
setting up, by the boot agent, a system password that the computing device uses during the boot; and
disabling other boot paths.

### Claim 24 (depends on 21)

The method of claim 21, wherein configuring the primary OS includes downloading a package specified by the management sever, wherein the package is applied as an edit to the primary OS.

### Claim 25 (depends on 21)

The method of claim 21, further comprising:
saving the last boot time to the firmware;
in an instance in which the last boot time is more recent than a last compliance check from a management server, incrementing a counter; and
in an instance in which the counter exceeds a threshold, downloading the new instance of the boot agent.

### Claim 26 (depends on 25)

The method of claim 25, further comprising:
in an instance in which the counter is less than a threshold, booting the primary OS as currently configured.

### Claim 27 (depends on 21)

The method of claim 21, further comprising:
receiving a decommissioning message from the management server;
storing a flag in the firmware; and
upon detecting the flag during a subsequent boot, loading a pre-OS boot environment without the boot agent for performing a default boot sequence.

### Claim 28

A non-transitory, computer-readable medium comprising instructions that, when executed by a processor, perform stages for bare metal device management, the stages comprising:
retrieving, from firmware of a computing device, a network location;
before permitting a primary operating system (“OS”) to boot, contacting the network location and receiving a boot agent;
adding, by the computing device, the boot agent to a system partition of the computing device;
configuring, by the computing device, the boot agent to execute before a primary OS boot manager during boot of the computing device;
applying, by the computing device, an OS configuration to the primary OS, the OS configuration being specified by a management server;
booting the primary OS on the computing device; and
in an instance where a last boot time is more recent than a last compliance check with the management server, downloading a new instance of the boot agent and booting from the new instance of the boot agent.

### Claim 29 (depends on 28)

The non-transitory, computer-readable medium of claim 28, the stages further comprising:
during booting from the new instance of the boot agent, confirming that the primary OS has the OS configuration specified by the management server.

### Claim 30 (depends on 28)

The non-transitory, computer-readable medium of claim 28, the stages further comprising:
setting up a system password used during the boot by the boot agent; and
disabling other boot paths.

### Claim 31 (depends on 28)

The non-transitory, computer-readable medium of claim 28, wherein configuring the primary OS includes downloading a package specified by a management sever, wherein the package is applied by the boot agent as an edit to the primary OS.

### Claim 32 (depends on 28)

The non-transitory, computer-readable medium of claim 28, the stages further comprising:
saving the last boot time to the firmware;
in an instance in which the last boot time is more recent than a last compliance check from the management server, incrementing a counter; and
in an instance in which the counter exceeds a threshold, downloading the new instance of the boot agent.

### Claim 33 (depends on 32)

The non-transitory, computer-readable medium of claim 32, the stages further comprising:
in an instance in which the counter is less than a threshold, booting the primary OS as currently configured.

### Claim 34 (depends on 28)

The non-transitory, computer-readable medium of claim 28, the stages further comprising:
receiving a decommissioning message from the management server;
storing a flag in the firmware; and
upon detecting the flag during a subsequent boot, loading a pre-OS boot environment without the boot agent for performing a default boot sequence.

### Claim 35

A system for bare metal device management, comprising:
a physical memory storage including a non-transitory, computer-readable medium comprising instructions; and
a management server including a processor that executes the instructions to carry out stages comprising:
receiving a request from a computing device during boot of the computing device, the computing device including firmware configured to contact a network location associated with the management server as part of booting;
sending a boot agent to the computing device, the boot agent causing the computing device to perform stages comprising:
adding the boot agent to a system partition of the computing device;
prioritizing, in a boot order, the boot agent before a primary OS boot manager;
applying an OS configuration specified by the management server to the primary OS;
booting the primary OS on the computing device; and
in an instance where a last boot time is more recent than a last compliance check with the management server, downloading a new instance of the boot agent and booting from the new instance of the boot agent.

### Claim 36 (depends on 35)

The system of claim 35, the stages performed by the computing device further comprising:
during booting from the new instance of the boot agent, confirming that the primary OS has the OS configuration specified by the management server.

### Claim 37 (depends on 35)

The system of claim 35, the stages performed by the computing device further comprising:
setting up a system password used during the boot by the boot agent; and
disabling other boot paths.

### Claim 38 (depends on 35)

The system of claim 35, wherein configuring the primary OS includes downloading a package specified by the management sever, wherein the package is applied by the boot agent as an edit to the primary OS.

### Claim 39 (depends on 35)

The system of claim 35, the stages performed by the computing device comprising:
saving the last boot time to the firmware;
in an instance in which the last boot time is more recent than a last compliance check with the management server, incrementing a counter;
in an instance in which the counter exceeds a threshold, downloading a new instance of the boot agent and booting from the new instance of the boot agent; and
in an instance in which the counter is less than a threshold, booting the primary OS as currently configured.

### Claim 40 (depends on 35)

The system of claim 35, the stages performed by the computing device further comprising:
receiving a decommissioning message from the management server;
storing a flag in the firmware;
upon detecting the flag during a subsequent boot, loading a pre-OS boot environment without the boot agent for performing a default boot sequence.
