FORM 2
THE PATENTS ACT, 1970 (39 OF 1970) & THE PATENT RULES, 2003
COMPLETE SPECIFICATION
(See section 10 and rule 13)
“METHOD AND SYSTEM FOR OPERATING SYSTEM (OS) INSTALLATION MANAGEMENT IN ONE OR MORE
TARGET NODES”
We, Jio Platforms Limited, an Indian National, of Office - 101, Saffron, Nr. Centre Point, Panchwati 5 Rasta, Ambawadi, Ahmedabad - 380006, Gujarat, India.
The following specification particularly describes the invention and the manner in which it is to be performed.

METHOD AND SYSTEM FOR OPERATING SYSTEM (OS) INSTALLATION MANAGEMENT IN ONE OR MORE TARGET NODES
FIELD OF INVENTION
[0001] Embodiments of the present disclosure generally relate to Operating System (OS) installation management. More particularly, embodiments of the present disclosure relate to a method and system for Operating System (OS) installation management in one or more target nodes.
BACKGROUND
[0002] The following description of the related art is intended to provide background information pertaining to the field of the disclosure. This section may include certain aspects of the art that may be related to various features of the present disclosure. However, it should be appreciated that this section is used only to enhance the understanding of the reader with respect to the present disclosure, and not as admissions of the prior art.
[0003] An operating system (OS) falls into a category of a system software. The OS is responsible for managing a plurality of resources of a computer. The OS acts as an interface between the software and a plurality of components of the computer or a computer hardware. The OS has the ability to manage multiple resources and multiple operations of the computer. The OS is a fully integrated set of specialized programs designed to handle a plurality of operations of the computer such as inputting, processing, outputting, storing, and controlling. The OS controls and monitors an execution of one or more programs that are stored in the computer such as application programs. Further, the OS is a collection of software for managing one or more computer hardware resources and provides a set of services for the computer programs.

[0004] While the OS plays an important role in user-friendliness and functionality within computers, its installation process extends beyond individual systems to network nodes such as base stations in a wireless communication network. These network nodes support multiple workstations and terminals connected on the network, such as a local area network (LAN).
[0005] Conventionally, the OS is installed on network nodes manually by an operator. The manual process involves several steps, including choosing the OS, backing up data, installing the media, configuring the OS, and restoring the data. Specifically, this process includes logging into an Out-Of-Band (OOB) graphical interface (GUI), setting boot configurations, attaching a standard image uniform resource locator (URL) to virtual media, rebooting the server, and manually selecting options while the server is rebooting.
[0006] In wireless communication networks, the operator may be unaware of the OS installation progress during this process. More specifically, there is no interface through which the operator can be apprised of the OS installation status and whether the process has been completed. As a result, the operator may accidentally reinitiate the OS installation, unaware that the OS has already been installed. This can erase the previously installed OS and unnecessarily waste processing resources of the network and the computing device. Thus, there exists an imperative need in the art to provide a system and method for Operating System (OS) installation management in one or more target nodes, which the present disclosure aims to address.
SUMMARY
[0007] This section is provided to introduce certain aspects of the present disclosure in a simplified form that are further described below in the detailed description. This summary is not intended to identify the key features or the scope of the claimed subject matter.

[0008] An aspect of the present disclosure relates to a method for Operating System (OS) installation management in one or more target nodes, the method comprising initiating, by an initiation unit, at a central controller, an OS install script for installation of one or more operating systems (OS) in the one or more target nodes from one or more host servers. The method further comprises identifying, by an identification unit, at the central controller, the one or more target nodes and the one or more host servers based on the OS install script. Thereafter, the method comprises installing, by an installation unit, at the central controller, the one or more OS in the one or more target nodes from the one or more host servers. The method thereafter comprises receiving, by a transceiver unit, at the central controller, an installation status from the one or more target nodes, based on the one or more OS installation from the one or more host servers. The method comprises analysing, by an analysis unit, at the central controller, the received installation status from the one or more target nodes, wherein the installation status is at least one of a successful installation status and an unsuccessful installation status. The method comprises automatically changing, by a changing unit, at the central controller, a pre-configured out of band (OOB) login credential of the one or more target nodes, based on the successful installation status.
[0009] In an exemplary aspect of the present disclosure, before, initiating the OS install script, at the central controller, by the initiation unit, for installation of one or more OS in the one or more target nodes from one or more host servers, the method comprises configuring, by a configuration unit, at the central controller, one or more image Uniform Resource Locators (image URLs) associated with the one or more OS to be installed in the one or more target nodes, for the one or more host servers.
[0010] In an exemplary aspect of the present disclosure, before installing, by the installation unit, the one or more OS in the one or more target nodes from the one or more host servers, the method comprises logging, to the one or more target nodes;

configuring, one or more boot parameters on the one or more target nodes; configuring, at the one or more target nodes, the one or more image URLs associated with one or more OS to a virtual media on each of the one or more host servers; rebooting, the one or more host servers; and fetching, from the virtual media, the corresponding OS from the image URL configured on each of the one or more host servers, in response to rebooting of the one or more host servers.
[0011] In an exemplary aspect of the present disclosure, the successful installation status is detected at the analysis unit, in an event the one or more OS is installed successfully in each of the one or more target nodes, and wherein the unsuccessful installation status is detected at the analysis unit, in an event the installation of the one or more OS fails in at least one target node from the one or more target nodes.
[0012] In an exemplary aspect of the present disclosure, each host server from the one or more host servers is at least a File Transport Protocol server (FTP server).
[0013] Another aspect of the present disclosure may relate to a system for Operating System (OS) installation management in one or more target nodes, the system comprising an initiation unit, at a central controller, configured to initiate, an OS install script for installation of one or more OS in the one or more target nodes from one or more host servers. The system comprises an identification unit, connected to at least the initiation unit, wherein the identification unit, is configured to identify, the one or more target nodes and the one or more host servers based on the OS install script. The system comprises an installation unit connected to at least the identification unit, wherein the installation unit at the central controller, is configured to install, the one or more OS in the one or more target nodes from the one or more host servers. The system comprises a transceiver unit connected to at least the installation unit, wherein the transceiver unit at the central controller, is configured to receive an installation status from the one or more target nodes, based on the one or more OS installation from one or more host servers. The system comprises an analysis unit, connected to at least the transceiver unit, wherein the

analysis unit at the central controller, is configured to analyse the received installation status from the one or more target nodes, wherein the installation status is at least one of a successful installation status and an unsuccessful installation status. The system comprises a changing unit, connected to at least the analysis unit, wherein the changing unit at the central controller, is configured to, automatically change, a pre-configured out of band (OOB) login credential of the one or more target nodes, based on the successful installation status, thereby restricting further attempts to install the one or more OS in the one or more target nodes.
[0014] Yet another aspect of the present disclosure may relate to a non-transitory computer readable storage medium storing instructions for Operating System (OS) installation management in one or more target nodes, the instructions include executable code which, when executed by one or more units of a system, causes: an initiation unit of the system to initiate an OS install script for installation of one or more OS in the one or more target nodes from one or more host servers ;an identification unit of the system to identify the one or more target nodes and the one or more host servers based on the OS install script. Further, the instructions include executable code which, when executed by one or more units of a system, causes an installation unit of the system to install the one or more OS in the one or more target nodes from the one or more host servers. Further, the instructions include executable code which, when executed by one or more units of a system, causes a transceiver unit of the system to receive an installation status from the one or more target nodes, based on the one or more OS installation from one or more host servers. Further, the instructions include executable code which, when executed by one or more units of a system, causes an analysis unit of the system to analyse the received installation status from the one or more target nodes, wherein the installation status is at least one of a successful installation status and an unsuccessful installation status. Further, the instructions include executable code which, when executed by one or more units of a system, causes a changing unit of the system to automatically change, a pre-configured out of band (OOB) login credential of the one or more target nodes, based on the successful installation

status, thereby restricting further attempts to install the one or more OS in the one or more target nodes.
OBJECTS OF THE DISCLOSURE
[0015] Some of the objects of the present disclosure, which at least one embodiment disclosed herein satisfies are listed herein below.
[0016] It is an object of the present disclosure to provide a system and a method for Operating System (OS) installation management in one or more target nodes.
[0017] It is another object of the present disclosure to provide a system and a method for changing the Out-of-Band (OOB) password once the operating system has been successfully installed.
[0018] It is yet another object of the present disclosure to provide a system and a method for automatically installing OS without manual intervention using an OS image.
DESCRIPTION OF THE DRAWINGS
[0019] The accompanying drawings, which are incorporated herein, and constitute a part of this disclosure, illustrate exemplary embodiments of the disclosed methods and systems in which like reference numerals refer to the same parts throughout the different drawings. Components in the drawings are not necessarily to scale, emphasis instead being placed upon clearly illustrating the principles of the present disclosure. Also, the embodiments shown in the figures are not to be construed as limiting the disclosure, but the possible variants of the method and system according to the disclosure are illustrated herein to highlight the advantages of the disclosure. It will be appreciated by those skilled in the art that disclosure of such

drawings includes disclosure of electrical components or circuitry commonly used to implement such components.
[0020] FIG. 1 illustrates an exemplary block diagram of a computing device upon
5 which the features of the present disclosure may be implemented in accordance with
exemplary implementation of the present disclosure.
[0021] FIG. 2 illustrates an exemplary block diagram of a system for Operating
System (OS) installation management in one or more target nodes, in accordance
10 with exemplary implementations of the present disclosure.
[0022] FIG. 3 illustrates a method flow diagram for Operating System (OS) installation management in one or more target nodes, in accordance with exemplary implementations of the present disclosure. 15
[0023] FIG. 4 illustrates an exemplary architecture diagram of a system for Operating System (OS) installation management in one or more target nodes, in accordance with exemplary implementations of the present disclosure.
20 [0024] The foregoing shall be more apparent from the following more detailed
description of the disclosure.
DETAILED DESCRIPTION
25 [0025] In the following description, for the purposes of explanation, various
specific details are set forth in order to provide a thorough understanding of embodiments of the present disclosure. It will be apparent, however, that embodiments of the present disclosure may be practiced without these specific details. Several features described hereafter may each be used independently of one
30 another or with any combination of other features. An individual feature may not
8

address any of the problems discussed above or might address only some of the problems discussed above.
[0026] The ensuing description provides exemplary embodiments only, and is not
5 intended to limit the scope, applicability, or configuration of the disclosure. Rather,
the ensuing description of the exemplary embodiments will provide those skilled in
the art with an enabling description for implementing an exemplary embodiment.
It should be understood that various changes may be made in the function and
arrangement of elements without departing from the spirit and scope of the
10 disclosure as set forth.
[0027] Specific details are given in the following description to provide a thorough
understanding of the embodiments. However, it will be understood by one of
ordinary skill in the art that the embodiments may be practiced without these
15 specific details. For example, circuits, systems, processes, and other components
may be shown as components in block diagram form in order not to obscure the embodiments in unnecessary detail.
[0028] Also, it is noted that individual embodiments may be described as a process
20 which is depicted as a flowchart, a flow diagram, a data flow diagram, a structure
diagram, or a block diagram. Although a flowchart may describe the operations as
a sequential process, many of the operations may be performed in parallel or
concurrently. In addition, the order of the operations may be re-arranged. A process
is terminated when its operations are completed but could have additional steps not
25 included in a figure.
[0029] The word “exemplary” and/or “demonstrative” is used herein to mean
serving as an example, instance, or illustration. For the avoidance of doubt, the
subject matter disclosed herein is not limited by such examples. In addition, any
30 aspect or design described herein as “exemplary” and/or “demonstrative” is not
necessarily to be construed as preferred or advantageous over other aspects or
9

designs, nor is it meant to preclude equivalent exemplary structures and techniques
known to those of ordinary skill in the art. Furthermore, to the extent that the terms
“includes”, “has”, “contains” and other similar words are used in either the detailed
description or the claims, such terms are intended to be inclusive in a manner similar
5 to the term “comprising” as an open transition word without precluding any
additional or other elements.
[0030] As used herein, a “processing unit” or “processor” or “operating processor” includes one or more processors, wherein processor refers to any logic circuitry for
10 processing instructions. A processor may be a general-purpose processor, a special
purpose processor, a conventional processor, a digital signal processor, a plurality of microprocessors, one or more microprocessors in association with a Digital Signal Processing (DSP) core, a controller, a microcontroller, Application Specific Integrated Circuits, Field Programmable Gate Array circuits, any other type of
15 integrated circuits, etc. The processor may perform signal coding data processing,
input/output processing, and/or any other functionality that enables the working of the system according to the present disclosure. More specifically, the processor or processing unit is a hardware processor.
20 [0031] As used herein, “a user equipment”, “a user device”, “a smart-user-device”,
“a smart-device”, “an electronic device”, “a mobile device”, “a handheld device”, “a wireless communication device”, “a mobile communication device”, “a communication device” may be any electrical, electronic and/or computing device or equipment, capable of implementing the features of the present disclosure. The
25 user equipment/device may include, but is not limited to, a mobile phone, smart
phone, laptop, a general-purpose computer, desktop, personal digital assistant, tablet computer, wearable device or any other computing device which is capable of implementing the features of the present disclosure. Also, the user device may contain at least one input means configured to receive an input from unit(s) which
30 are required to implement the features of the present disclosure.
10

[0032] As used herein, “storage unit” or “memory unit” refers to a machine or
computer-readable medium including any mechanism for storing information in a
form readable by a computer or similar machine. For example, a computer-readable
medium includes read-only memory (“ROM”), random access memory (“RAM”),
5 magnetic disk storage media, optical storage media, flash memory devices or other
types of machine-accessible storage media. The storage unit stores at least the data that may be required by one or more units of the system to perform their respective functions.
10 [0033] As used herein “interface” or “user interface” refers to a shared boundary
across which two or more separate components of a system exchange information or data. The interface may also be referred to a set of rules or protocols that define communication or interaction of one or more modules or one or more units with each other, which also includes the methods, functions, or procedures that may be
15 called.
[0034] All modules, units, components used herein, unless explicitly excluded
herein, may be software modules or hardware processors, the processors being a
general-purpose processor, a special purpose processor, a conventional processor,
20 a digital signal processor (DSP), a plurality of microprocessors, one or more
microprocessors in association with a DSP core, a controller, a microcontroller, Application Specific Integrated Circuits (ASIC), Field Programmable Gate Array circuits (FPGA), any other type of integrated circuits, etc.
25 [0035] As used herein the transceiver unit include at least one receiver and at least
one transmitter configured respectively for receiving and transmitting data, signals, information or a combination thereof between units/components within the system and/or connected with the system.
30 [0036] As discussed in the background section, the current known solutions have
several shortcomings. The present disclosure aims to overcome the above-
11

mentioned and other existing problems in this field of technology by providing method and system of Operating System (OS) installation management in one or more target nodes.
5
[0037] Out-Of-Band (OOB) refers to a communication or management channel that is separate from the primary data pathway in a computer network or system. It provides an alternative means for accessing and controlling the network or system, typically used for monitoring, troubleshooting, and management purposes. The
10 OOB communication allows administrators or operators to remotely access and
manage devices or systems, even when the primary data network is unavailable or experiencing issues. This separate channel provides a reliable and independent method for performing tasks such as remote configuration, firmware updates, system monitoring, diagnostics, and recovery procedures. The OOB
15 communication often utilizes dedicated hardware, protocols, or interfaces to ensure
secure and uninterrupted access to critical network components or systems.
[0038] Conventionally, the OS is installed on network nodes manually by an operator. The manual process involves several steps, including choosing the OS,
20 backing up data, installing the media, configuring the OS, and restoring the data.
Specifically, this process includes logging into an Out-Of-Band (OOB) graphical interface (GUI), setting boot configurations, attaching a standard image uniform resource locator (URL) to virtual media, rebooting the server, and manually selecting options while the server is rebooting.
25
[0039] The present disclosure aims to overcome the above-mentioned and other existing problems in this field of technology by providing a mechanism to prevent OS installation by changing the OOB login credentials.
30 [0040] Hereinafter, exemplary embodiments of the present disclosure will be
described with reference to the accompanying drawings.
12

[0041] FIG. 1 illustrates an exemplary block diagram of a computing device [100]
upon which the features of the present disclosure may be implemented in
accordance with exemplary implementation of the present disclosure. In an
5 implementation, the computing device [100] may also implement a method for
Operating System (OS) installation management in one or more target nodes,
utilising the system. In another implementation, the computing device [100] itself
implements the method for Operating System (OS) installation management in one
or more target nodes, using one or more units configured within the computing
10 device [100], wherein said one or more units are capable of implementing the
features as disclosed in the present disclosure.
[0042] The computing device [100] may include a bus [102] or other communication mechanism for communicating information, and a hardware
15 processor [104] coupled with bus [102] for processing information. The hardware
processor [104] may be, for example, a general-purpose microprocessor. The computing device [100] may also include a main memory [106], such as a random-access memory (RAM), or other dynamic storage device, coupled to the bus [102] for storing information and instructions to be executed by the processor [104]. The
20 main memory [106] also may be used for storing temporary variables or other
intermediate information during execution of the instructions to be executed by the processor [104]. Such instructions, when stored in non-transitory storage media accessible to the processor [104], render the computing device [100] into a special-purpose machine that is customized to perform the operations specified in the
25 instructions. The computing device [100] further includes a read only memory
(ROM) [108] or other static storage device coupled to the bus [102] for storing static information and instructions for the processor [104].
[0043] A storage device [110], such as a magnetic disk, optical disk, or solid-state
30 drive is provided and coupled to the bus [102] for storing information and
instructions. The computing device [100] may be coupled via the bus [102] to a
13

display [112], such as a cathode ray tube (CRT), Liquid crystal Display (LCD),
Light Emitting Diode (LED) display, Organic LED (OLED) display, etc. for
displaying information to a computer user. An input device [114], including
alphanumeric and other keys, touch screen input means, etc. may be coupled to the
5 bus [102] for communicating information and command selections to the processor
[104]. Another type of user input device may be a cursor controller [116], such as
a mouse, a trackball, or cursor direction keys, for communicating direction
information and command selections to the processor [104], and for controlling
cursor movement on the display [112]. This input device typically has two degrees
10 of freedom in two axes, a first axis (e.g., x) and a second axis (e.g., y), that allow
the device to specify positions in a plane.
[0044] The computing device [100] may implement the techniques described herein using customized hard-wired logic, one or more ASICs or FPGAs, firmware
15 and/or program logic which in combination with the computing device [100] causes
or programs the computing device [100] to be a special-purpose machine. According to one implementation, the techniques herein are performed by the computing device [100] in response to the processor [104] executing one or more sequences of one or more instructions contained in the main memory [106]. Such
20 instructions may be read into the main memory [106] from another storage medium,
such as the storage device [110]. Execution of the sequences of instructions contained in the main memory [106] causes the processor [104] to perform the process steps described herein. In alternative implementations of the present disclosure, hard-wired circuitry may be used in place of or in combination with
25 software instructions.
[0045] The computing device [100] also may include a communication interface
[218] coupled to the bus [102]. The communication interface [118] provides a two-
way data communication coupling to a network link [120] that is connected to a
30 local network [122]. For example, the communication interface [118] may be an
integrated services digital network (ISDN) card, cable modem, satellite modem, or
14

a modem to provide a data communication connection to a corresponding type of
telephone line. As another example, the communication interface [118] may be a
local area network (LAN) card to provide a data communication connection to a
compatible LAN. Wireless links may also be implemented. In any such
5 implementation, the communication interface [118] sends and receives electrical,
electromagnetic or optical signals that carry digital data streams representing various types of information.
[0046] The computing device [100] can send messages and receive data, including
10 program code, through the network(s), the network link [120] and the
communication interface [118]. In the Internet example, a server [130] might
transmit a requested code for an application program through the Internet [228], the
ISP [126], the local network [122], the host [124] and the communication interface
[218]. The received code may be executed by the processor [104] as it is received,
15 and/or stored in the storage device [110], or other non-volatile storage for later
execution.
[0047] Referring to FIG. 2, an exemplary block diagram of a system [200] for Operating System (OS) installation management in one or more target nodes, is
20 shown, in accordance with the exemplary implementations of the present
disclosure. In one example, the system [200] may be implemented as a computing device [100] as explained in conjunction with FIG. 1. In such case, the system [200], for performing OS management in one or more target nodes may use one or more components as explained in computing device [100]. In another example, the
25 system [200] may be implemented as a central controller. Such central controller
may be implemented as a centralized entity in the network and may be in communication with the one or more target nodes.
[0048] As depicted in FIG. 2, the system [200] comprises at least one initiation unit
30 [201], at least one identification unit [203], at least one installation unit [205], at
least one transceiver unit [207], at least one analysis unit [209], at least one
15

changing unit [211] and at least one configuration unit [213]. Also, all the
components/ units of the system [200] are assumed to be connected to each other
unless otherwise indicated below. As shown in the FIG. 2 all units shown within
the system [200] should also be assumed to be connected to each other. Also, in
5 FIG. 2 only a few units are shown, however, the system [200] may comprise
multiple such units or the system [200] may comprise any such numbers of said units, as required to implement the features of the present disclosure. Further, in an implementation, the system [200] may be present in a user device/ user equipment [100] to implement the features of the present disclosure. The system [200] may be
10 a part of the user device [100]/ or may be independent of but in communication
with the user device [100] (may also referred herein as a UE). In another implementation, the system [200] may reside in a server or a network entity. In yet another implementation, the system [200] may reside partly in the server/ network entity and partly in the user device.
15
[0049] The system [200] is configured for Operating System (OS) installation management in one or more target nodes, with the help of the interconnection between the components/units of the system [200].
20 [0050] In operation, the initiation unit [201] may initiate an OS install script for
installation of one or more OS in the one or more target nodes from one or more host servers. The present disclosure encompasses that the initiation unit [201] is configured to start or trigger an operating system (OS) installation process. As a part of the OS installation process, the initiation unit [201] activates an OS install
25 script, which is a set of instructions, or a program specifically developed to handle
the OS installation. The OS installation may be intended for one or more target nodes. Further, these nodes may be the systems or devices where the OS will be installed.
30 [0051] In one example, the OS installation files and scripts may be sourced from
one or more host servers. Such host servers may be referred to as servers that store
16

the necessary OS images and related files for OS installation on the one or more
target nodes. In another example, each host server from the one or more host servers
may be at least a File Transport Protocol server (FTP server). As would be
understood, FTP is a standard network protocol used for the transfer of files from
5 one host to another over a TCP based network, such as the Internet. In the context
of the present invention, every host server may be equipped with the capability to operate as an FTP server, allowing it to handle file transfers via the FTP protocol.
[0052] As would be further understood, the OS Install Script is a script or series of
10 commands that automates the installation of the operating system.
[0053] The system [200] further comprises the identification unit [203] connected to at least the initiation unit [201]. The identification unit [203] may be configured to identify the one or more target nodes and the one or more host servers based on
15 the OS install script. The present disclosure encompasses the identification unit
[203] has the specific function of identifying both the one or more target nodes and the host servers involved in the OS installation process. The identification unit [203] performs this identification based on the information and instructions provided within the OS install script.
20
[0054] The system [200] further comprises the installation unit [205] connected to at least the identification unit [203] and the initiation unit [201]. The installation unit [205] may be configured to install the one or more OS in the one or more target nodes from the one or more host servers. The present disclosure encompasses the
25 installation unit [205] is responsible for the actual installation of the OS on the one
or more target nodes.
[0055] In one example, the system [200] may further include a configuration unit
[213]. Before the initiation unit [201] initiates the OS install script, at a central
30 controller, for installation of one or more OS in the one or more target nodes from
one or more host servers, the configuration unit [213] is configured to, configure,
17

one or more image Uniform Resource Locators (image URLs) associated with the
one or more OS to be installed in the one or more target nodes, for the one or more
host servers. The central controller serves as a centralized server entity that
integrates and manages the various units and components involved in deploying
5 operating systems to target nodes. This includes initiating, configuring, and
executing OS installation scripts across the network of nodes and servers. For example, the configuration unit [213] performs necessary arrangements. The configuration unit [213] sets up image URLs at the node for the OS that needs to be installed. These URLs point to the OS images located on the host servers.
10
[0056] In another example, before installing the one or more OS in the one or more target nodes from the one or more host servers, the installation unit [205] may be further configured to log in to the one or more target nodes. The installation unit [205] may configure one or more boot parameters on the one or more target nodes.
15 After the configuration, the installation unit [205] may reboot the one or more host
servers. After that, in response to rebooting of the one or more host servers, the installation unit [205] may fetch the corresponding OS from the image URL configured on each of the one or more host servers from the virtual media.
20 [0057] For example, the system [200] gets access to the target nodes, possibly using
network credentials or secure protocols, and then sets the necessary boot parameters on the target nodes to prepare them for OS installation. At each target node, the configuration unit [213] configures URLs for the OS images that are associated with the virtual media on the host servers. This ensures that the target nodes know
25 from where to fetch the OS files. Then, the initiation unit [201] initiates a reboot of
the host servers to ensure that the host servers are ready for the OS installation process. After the host servers reboot, the target nodes fetch the corresponding OS from the configured image URLs on the virtual media of the host servers.
30 [0058] The system further comprises the transceiver unit [207] connected to at least
the installation unit [205], wherein the transceiver unit [207] at the central
18

controller, is configured to receive an installation status from the one or more target
nodes, based on the one or more OS installation from one or more host servers. The
present disclosure encompasses the transceiver unit [207] receives status updates
from the target nodes regarding the progress or completion of the OS installation.
5 The present disclosure encompasses that the one or more host servers are pre-
deployed and associated with the one or more target nodes.
[0059] The system further comprises the analysis unit [209], connected to at least the transceiver unit [207], wherein the analysis unit [209] at the central controller,
10 is configured to analyse the received installation status from the one or more target
nodes, wherein the installation status is at least one of a successful installation status and an unsuccessful installation status. The present disclosure encompasses the analysis unit [209] receives data from the transceiver unit [207], which collects installation status updates from the target nodes. The primary function of the
15 analysis unit [209] is to process and evaluate the received installation status
information. It determines whether the installation was successful or unsuccessful. The successful installation status indicates that the OS installation on a target node was completed without issues and unsuccessful installation status indicates that the OS installation on a target node encountered problems or failed.
20
[0060] The system [200] further comprises the changing unit [211], connected to at least the analysis unit [209], wherein the changing unit [211] at the central controller, is configured to, automatically change, a pre-configured out of band (OOB) login credential of the target node, based on the successful installation
25 status, thereby restricting further attempts to install the one or more OS in the one
or more target nodes. The present disclosure encompasses that the changing unit [211] receives data from the analysis unit [209], specifically the successful installation status of the OS on the target nodes. Upon receiving a successful installation status, the changing unit [211] automatically changes the preconfigured
30 out of band login credentials (such as username, password, etc.) of the target node.
19

[0061] As would be appreciated, this change ensures that the credentials used
during the installation process are altered to prevent unauthorized or repeat
installations. Further, by changing the OOB login credentials, the system restricts
further attempts to install the OS on the target nodes. This security measure helps
5 ensure that once the OS is successfully installed, the target nodes are protected from
unauthorized reinstallation attempts.
[0062] Referring to FIG. 3, an exemplary method flow diagram [300] for Operating System (OS) installation management in one or more target nodes, in accordance
10 with exemplary implementations of the present disclosure is shown. In an
implementation the method [300] is performed by the system [200]. Further, in an implementation, the system [200] may be present in a server device to implement the features of the present disclosure. Also, as shown in FIG. 3, the method [300] starts at step [302].
15
[0063] At step 304, the method [300] comprises, initiating, by an initiation unit [201], at a central controller, an OS install script for installation of one or more OS in the one or more target nodes from one or more host servers. The present disclosure encompasses that the initiation unit [201] is configured to start or trigger
20 an operating system (OS) installation process. As a part of the OS installation
process, the initiation unit [201] activates an OS install script, which is a set of instructions, or a program specifically developed to handle the OS installation. The OS installation may be intended for one or more target nodes. Further, these target nodes may be the systems or devices where the OS will be installed.
25
[0064] In one example, the OS installation files and scripts may be sourced from one or more host servers. Such host servers may be referred to as servers that store the necessary OS images and related files for OS installation on the target nodes. In another example, each host server from the one or more host servers may be at least
30 a File Transport Protocol server (FTP server). As would be understood, FTP is a
standard network protocol used for the transfer of files from one host to another
20

over a TCP based network, such as the Internet. In the context of the present invention, every host server may be equipped with the capability to operate as an FTP server, allowing it to handle file transfers via the FTP protocol.
5 [0065] As would be further understood, the OS Install Script is a script or series of
commands that automates the installation of the operating system.
[0066] At step 306, the method [300] comprises, identifying, by an identification unit [203], at the central controller, the one or more target nodes and the one or
10 more host servers based on the OS install script. The present disclosure
encompasses the identification unit [203] has the specific function of identifying both the target nodes and the host servers involved in the OS installation process. The identification unit [203] performs this identification based on the information and instructions provided within the OS install script.
15
[0067] At step 308, the method [300] comprises, installing, by an installation unit [205], at the central controller, the one or more OS in the one or more target nodes from the one or more host servers. The installation unit [205] may be configured to install the one or more OS in the one or more target nodes from the one or more
20 host servers. The present disclosure encompasses the installation unit [205] is
responsible for the actual installation of the OS on the target nodes.
[0068] In one example, the method [300] further comprises a configuration unit [213]. Before the initiation unit [201] initiates the OS install script, at the central
25 controller, for installation of one or more OS in the one or more target nodes from
one or more host servers, the configuration unit [213] is configured to, configure, one or more image Uniform Resource Locators (image URLs) associated with the one or more OS to be installed in the one or more target nodes, for the one or more host servers. The central controller serves as a centralized server entity that
30 integrates and manages the various units and components involved in deploying
operating systems to target nodes. This includes initiating, configuring, and
21

executing OS installation scripts across the network of target nodes and servers. For example, the configuration unit [213] performs necessary arrangements. The configuration unit [213] sets up image URLs at the target node for the OS that needs to be installed. These URLs point to the OS images located on the host servers. 5
[0069] In another example, before installing the one or more OS in the one or more target nodes from the one or more host servers, the installation unit [205] may be further configured to log in to the one or more target nodes. The installation unit [205] may configure one or more boot parameters on the one or more target nodes.
10 After the configuration, the installation unit [205] may reboot the one or more host
servers. After that, in response to rebooting of the one or more host servers, the installation unit [205] may fetch the corresponding OS from the image URL configured on each of the one or more host servers from the virtual media. [0070] For example, installation unit [205] gets access to the target nodes, possibly
15 using network credentials or secure protocols, and then sets the necessary boot
parameters on the target nodes to prepare them for OS installation. At each target node, the configuration unit [213] configures URLs for the OS images that are associated with the virtual media on the host servers. This ensures that the target nodes know from where to fetch the OS files. Then, the initiation unit [201] initiates
20 a reboot of the host servers to ensure that the host servers are ready for the OS
installation process. After the host servers reboot, the target nodes fetch the corresponding OS from the configured image URLs on the virtual media of the host servers.
25 [0071] At step 310, the method [300] comprises, receiving, by a transceiver unit
[207], at the central controller, an installation status from the one or more target nodes, based on the one or more OS installation from the one or more host servers. The present disclosure encompasses the transceiver unit [207] receives status updates from the target nodes regarding the progress or completion of the OS
30 installation. The present disclosure encompasses that the one or more host servers
are pre-deployed and associated with the one or more target nodes.
22

[0072] At step 312, the method [300] comprises, analysing, by an analysis unit
[209], at the central controller, the received installation status from the one or more
target nodes, wherein the installation status is at least one of a successful installation
5 status and an unsuccessful installation status. The present disclosure encompasses
the analysis unit [209] receives data from the transceiver unit [207], which collects
installation status updates from the target nodes. The primary function of the
analysis unit [209] is to process and evaluate the received installation status
information. It determines whether the installation was successful or unsuccessful.
10 The successful installation status indicates that the OS installation on a target node
was completed without issues and unsuccessful installation status indicates that the OS installation on a target node encountered problems or failed.
[0073] At step 314, the method [300] comprises automatically changing, by a
15 changing unit [211], at the central controller, a pre-configured out of band (OOB)
login credential of the target node, based on the successful installation status. The
present disclosure encompasses the changing unit [211] receives data from the
analysis unit [209], specifically the successful installation status of the OS on the
target nodes. Upon receiving a successful installation status, the changing unit [211]
20 automatically changes the preconfigured out of band login credentials (such as
username, password, etc.) of the target node, thereby restricting further attempts to install the one or more OS in the one or more target nodes.
[0074] As would be appreciated, this change ensures that the credentials used
25 during the installation process are altered to prevent unauthorized or repeat
installations. Further, by changing the OOB login credentials, the system restricts further attempts to install the OS on the target nodes. This security measure helps ensure that once the OS is successfully installed, the target nodes are protected from unauthorized reinstallation attempts. 30
[0075] Thereafter, the method terminates at step ([316]).
23

[0076] Referring to FIG. 4, an exemplary architecture diagram of a system for
Operating System (OS) installation management in one or more target nodes, in
accordance with exemplary implementations of the present disclosure, is shown.
5 Further, the system architecture [400] as shown in FIG. 4 is intended to be read in
conjunction with the exemplary method flow diagram [300] as shown in FIG. 3.
The systems as shown in FIG. 3 and FIG. 4 complement each other. In an
implementation the system architecture [400] is performed by the system [200].
The system architecture [400] begins with a command entered via the Command-
10 Line Interface (CLI) [402] to initiate the installation process. This is handled by the
initiation unit [201] at the central controller, which triggers an OS install script. The
script contains instructions for installing the OS on the target nodes. Before the OS
installation can proceed, docker is installed on the OS service [404]. The docker is
for the installation scripts to run.
15
[0077] After docker installation, makes an API call to initiate the OS installation
on the target nodes [408]. The identification unit [203] identifies the target nodes
[408]and host servers [406] involved in the process based on the OS install script.
The target nodes [408] are the devices where the OS will be installed, and the host
20 servers store the necessary OS images and related files.
[0078] Further, the installation unit [205] is responsible for downloading the ISO file from the ISO host server [410]. The ISO file contains the OS image required for installation. The server that hosts the OS images, which are downloaded to the
25 target nodes [408] for installation. After that, the analysis unit [209] processes the
received installation status to determine if the installation was successful or unsuccessful. Upon successful installation, the changing unit [211] automatically updates the OOB login credentials of the target nodes [408] to prevent unauthorized reinstallation attempts.
30
24

[0079] The system architecture [400] terminates after ensuring that the OS installation is complete, and the target nodes [408] are secured with updated OOB login credentials.
5
[0080] Therefore, the present disclosure automates the installation of OS on multiple target nodes with no manual intervention and enables an association with the one or more image URLs with the one or more target nodes, thereby balancing a network load.
10
[0081] The present disclosure further discloses a non-transitory computer readable storage medium storing instructions for Operating System (OS) installation management in one or more target nodes, the instructions include executable code which, when executed by one or more units of a system [200], causes: : an initiation
15 unit [201] of the system [200], to initiate an OS install script for installation of one
or more OS in the one or more target nodes from one or more host servers ;an identification unit [203] of the system [200] to identify the one or more target nodes and the one or more host servers based on the OS install script; an installation unit [205] of the system [200] to install the one or more OS in the one or more target
20 nodes from the one or more host servers; a transceiver unit [207] of the system [200]
to receive an installation status from the one or more target nodes, based on the one or more OS installation from one or more host servers; an analysis unit [209] of the system [200] to analyse the received installation status from the one or more target nodes, wherein the installation status is at least one of a successful installation status
25 and an unsuccessful installation status; and a changing unit [211] of the system
[200] to automatically change, a pre-configured out of band (OOB) login credential of the target node, based on the successful installation status, thereby restricting further attempts to install the one or more OS in the one or more target nodes.
30 [0082] As is evident from the above, the present disclosure provides a technically
advanced solution for Operating System (OS) installation management in one or
25

more target nodes. The present solution provides a technically advanced solution for securely and automatically installing operating system. The present solution encompasses many advantages as compared to known solutions such as changing OOB password to disable OS installation after first attempt and automatic OS installation on multiple target nodes hence speeds up deployment process. Further, the present solution allows OS installation without manual intervention with the help of kickstart OS image and allows users to assign OS image URL in such a way that network load can be distributed.
[0083] While considerable emphasis has been placed herein on the disclosed implementations, it will be appreciated that many implementations can be made and that many changes can be made to the implementations without departing from the principles of the present disclosure. These and other changes in the implementations of the present disclosure will be apparent to those skilled in the art, whereby it is to be understood that the foregoing descriptive matter to be implemented is illustrative and non-limiting.
[0084] Further, in accordance with the present disclosure, it is to be acknowledged that the functionality described for the various components/units can be implemented interchangeably. While specific embodiments may disclose a particular functionality of these units for clarity, it is recognized that various configurations and combinations thereof are within the scope of the disclosure. The functionality of specific units as disclosed in the disclosure should not be construed as limiting the scope of the present disclosure. Consequently, alternative arrangements and substitutions of units, provided they achieve the intended functionality described herein, are considered to be encompassed within the scope of the present disclosure.

We Claim:
1. A method [300] for Operating System (OS) installation management in one or
more target nodes, the method comprising:
- initiating, by an initiation unit [201], at a central controller, an OS install script for installation of one or more OS in the one or more target nodes from one or more host servers;
- identifying, by an identification unit [203], at the central controller, the one or more target nodes and the one or more host servers based on the OS install script;
- installing, by an installation unit [205], at the central controller, the one or more OS in the one or more target nodes from the one or more host servers;
- receiving, by a transceiver unit [207], at the central controller, an installation status from the one or more target nodes, based on the one or more OS installation from the one or more host servers;
- analyzing, by an analysis unit [209], at the central controller, the received installation status from the one or more target nodes, wherein the installation status is at least one of a successful installation status and an unsuccessful installation status; and
- automatically changing, by a changing unit [211], at the central controller, a pre-configured out of band (OOB) login credential of the one or more target nodes, based on the successful installation status.
2. The method [300] as claimed in claim 1, wherein, before, initiating the OS
install script, at the central controller, by the initiation unit [201], for
installation of one or more OS in the one or more target nodes from one or
more host servers, the method comprises:
configuring, by a configuration unit [213], at the central controller, one or more image Uniform Resource Locators (image URLs) associated with the one or more OS to be installed in the one or more target nodes, for the one or more host servers.

3. The method [300] as claimed in claim 1, wherein, before installing, by the
installation unit [205], the one or more OS in the one or more target nodes
from the one or more host servers, the method comprises:
- logging in to the one or more target nodes;
- configuring, one or more boot parameters on the one or more target nodes;
- configuring, at the target node, the one or more image URLs associated with one or more OS to a virtual media on each of the one or more host servers;
- reboot the one or more host servers; and
- fetching, from the virtual media, the corresponding OS from the image URL configured on each of the one or more host servers, in response to rebooting of the one or more host servers.

4. The method [300] as claimed in claim 1, wherein the successful installation status is detected at the analysis unit [209], in an event the one or more OS is installed successfully in each of the one or more target nodes, and wherein the unsuccessful installation status is detected at the analysis unit, in an event the installation of the one or more OS fails in at least one target node from the one or more target nodes.
5. The method [300] as claimed in claim 1, wherein each host server from the one or more host servers is at least a File Transport Protocol server (FTP server).
6. A system [200] for Operating System (OS) installation management in one or more target nodes, the system comprising:
- an initiation unit [201], at a central controller, configured to initiate an OS install script for installation of one or more OS in the one or more target nodes from one or more host servers;

- an identification unit [203], connected to at least the initiation unit [201], wherein the identification unit [203] is configured to identify, the one or more target nodes and the one or more host servers based on the OS install script;
- an installation unit [205] connected to at least the identification unit [203], wherein the installation unit [205] at the central controller, is configured to install, the one or more OS in the one or more target nodes from the one or more host servers
- a transceiver unit [207] connected to at least the installation unit [205], wherein the transceiver unit [207] at the central controller, is configured to receive an installation status from the one or more target nodes, based on the one or more OS installation from one or more host servers
- an analysis unit [209], connected to at least the transceiver unit [207], wherein the analysis unit [209] at the central controller, is configured to analyze the received installation status from the one or more target nodes, wherein the installation status is at least one of a successful installation status and an unsuccessful installation status; and
- a changing unit [211], connected to at least the analysis unit [209], wherein the changing unit [211] at the central controller, is configured to automatically change a pre-configured out of band (OOB) login credential of the one or more target nodes, based on the successful installation status, thereby restricting further attempts to install the one or more OS in the one or more target nodes.
7. The system [200] as claimed in claim 6, further comprising a configuration unit [213], wherein before, initiating the OS install script, at the central controller, by the initiation unit [201], for installation of one or more OS in the one or more target nodes from one or more host servers, the configuration unit [213] is configured to:

configure, one or more image Uniform Resource Locators (image URLs) associated with the one or more OS to be installed in the one or more target nodes, for the one or more host servers.
8. The system [200] as claimed in claim 6, wherein, before installing, by the
installation unit [205], the one or more OS in the one or more target nodes
from the one or more host servers, the installation unit [205] is configured to:
- log in to the one or more target nodes;
- configure one or more boot parameters on the one or more target nodes;
- configure, at the target node, the one or more image URLs associated with one or more OS to a virtual media on each of the one or more host servers;
- reboot the one or more host servers; and
- fetch, from the virtual media, the corresponding OS from the image URL configured on each of the one or more host servers, in response to rebooting of the one or more host servers.
9. The system [200] as claimed in claim 6, wherein the analysis unit [209] is to:
detect the successful installation status, in an event when the one or more OS
is installed successfully in each of the one or more target nodes; and
detect the unsuccessful installation status in an event when the installation of the one or more OS fails in at least one target node from the one or more target nodes.
10. The system [200] as claimed in claim 6, wherein each host server from the one
or more host servers is at least a File Transport Protocol server (FTP server).