# US 12,596,540 B2 · Cloud initiated bare metal as a service for on-premises servers > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 12,596,540 B2 - Document ID: US12596540B2 - Status: Granted - Kind: B2 - Application number: 18/251,052 - Filed: 2022-11-29 - Published: 2025-09-04 - Granted: 2026-04-07 - Earliest claimed: 2022-11-29 - Assignees: Rakuten Symphony, Inc. - Applicants: Rakuten Symphony, Inc. - Inventors: Sree Nandan Atur; Ravi Kumar Alluboyina - Web page: https://patentgrep.com/patent/US12596540B2 ## CPC - G06F 8/61: Installation - G06F 9/45541: {Bare-metal, i.e. hypervisor runs directly on hardware} - G06F 9/45558: {Hypervisor-specific management and integration aspects} - G06F 21/31: User authentication - G06F 2009/45595: {Network integration; Enabling network access in virtual machine instances} - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) ## Abstract Systems and methods for remotely configuring a bare metal server located on-premises. A method includes registering a bare metal server with a cloud native platform, wherein the bare metal server is located on-premises at a client location and remotely installing an operating system on the bare metal server. The method includes causing the bare metal server to install the operating system on a plurality of other bare metal servers located on-premises at the client location. ## Claims ### Claim 1 A method comprising: registering a bare metal server with a cloud native platform, wherein the bare metal server is located on-premises at a client location; remotely installing an operating system on the bare metal server from the cloud native platform; remotely installing an orchestration software on the bare metal server from the cloud native platform, wherein the orchestration software receives commands from the cloud native platform and orchestrates installation of the operating system on a plurality of other bare metal servers located on-premises at the client location; and causing the bare metal server to install the operating system on the plurality of other bare metal servers located on-premises at the client location via the orchestration software. ### Claim 2 (depends on 1) The method of claim 1, wherein registering the bare metal server comprises registering based on one or more of a baseboard management controller (BMC) Internet Protocol (IP) address, a BMC username, a BMC password, or Virtual Private Network (VPN) credentials for the bare metal server. ### Claim 3 (depends on 1) The method of claim 1, further comprising: onboarding a user account associated with the client location; and receiving Virtual Private Network (VPN) credentials for the bare metal server from the user account, wherein the VPN credentials enable one or more workers of the cloud native platform to remotely communicate with the bare metal server. ### Claim 4 (depends on 1) The method of claim 1, further comprising remotely installing a containerized workload management system on the bare metal server. ### Claim 5 (depends on 1) The method of claim 1, further comprising remotely installing software for a multi-data center automation platform on the bare metal server. ### Claim 6 (depends on 1) The method of claim 1, wherein the remotely installing the operating system on the bare metal server comprises installing without communicating with a dynamic host configuration protocol (DHCP) server at the client location. ### Claim 7 (depends on 6) The method of claim 6, wherein the remotely installing the operating system on the bare metal server further comprises installing without communicating with a trivial file transfer protocol (TFTP) server at the client location or a hypertext transfer protocol (HTTP) server at the client location. ### Claim 8 (depends on 1) The method of claim 1, further comprising communicating with the bare metal server by way of a virtual private network (VPN) connection enabling communication between the cloud native platform and the bare metal server. ### Claim 9 (depends on 8) The method of claim 8, wherein the remotely installing the operating system on the bare metal server comprises installing only by way of the VPN connection and without locally installing the operating system at the client location. ### Claim 10 (depends on 8) The method of claim 8, further comprising adding a unique identifier for the VPN connection to a schema for the bare metal server. ### Claim 11 A system comprising: one or more processors; and non-transitory computer readable storage medium storing instructions, wherein the instructions, when executed by the one or more processors, to perform operations comprising: registering a bare metal server with a cloud native platform, wherein the bare metal server is located on-premises at a client location; remotely installing an operating system on the bare metal server from the cloud native platform; remotely installing an orchestration software on the bare metal server from the cloud native platform, wherein the orchestration software receives commands from the cloud native platform and orchestrates installation of the operating system on a plurality of other bare metal servers located on-premises at the client location; and causing the bare metal server to install the operating system on the plurality of other bare metal servers located on-premises at the client location via the orchestration software. ### Claim 12 (depends on 11) The system of claim 11, wherein the operations further comprise: registering the bare metal server comprises registering based on one or more of a baseboard management controller (BMC) Internet Protocol (IP) address, a BMC username, a BMC password, or Virtual Private Network (VPN) credentials for the bare metal server. ### Claim 13 (depends on 11) The system of claim 11, wherein the operations further comprise: onboarding a user account associated with the client location; and receiving Virtual Private Network (VPN) credentials for the bare metal server from the user account, wherein the VPN credentials enable one or more workers of the cloud native platform to remotely communicate with the bare metal server. ### Claim 14 (depends on 11) The system of claim 11, wherein the operations further comprise remotely installing a containerized workload management system on the bare metal server. ### Claim 15 (depends on 11) The system of claim 11, wherein the operations further comprise remotely installing software for a multi-data center automation platform on the bare metal server. ### Claim 16 (depends on 11) The system of claim 11, wherein remotely installing the operating system on the bare metal server comprises installing without communicating with a dynamic host configuration protocol (DHCP) server at the client location. ### Claim 17 (depends on 16) The system of claim 16, wherein remotely installing the operating system on the bare metal server further comprises installing without communicating with a trivial file transfer protocol (TFTP) server at the client location or a hypertext transfer protocol (HTTP) server at the client location. ### Claim 18 (depends on 11) The system of claim 11, wherein the operations further comprise communicating with the bare metal server by way of a virtual private network (VPN) connection enabling communication between the cloud native platform and the bare metal server. ### Claim 19 (depends on 18) The system of claim 18, wherein the operations further comprise installing the operating system on the bare metal server comprises installing only by way of the VPN connection and without locally installing the operating system at the client location. ### Claim 20 (depends on 18) The system of claim 18, wherein the operations further comprise adding a unique identifier for the VPN connection to a schema for the bare metal server.