Method and device for network installation of operating system

Abstract

The invention discloses a method and a device for network installation of an operating system. According to the scheme, the method comprises the following steps: executing a client in a pre-starting execution environment; sending the first data carrying the equipment category to a network management protocol server; obtaining return data returned by the network management protocol server based on the first data, the return data carrying related data of a to-be-installed operating system, and the to-be-installed operating system being determined by the network management protocol server based on a mapping relationship between a preset device category and the operating system; the related data comprises first indication information for obtaining a bootstrap program of the to-be-installed operating system; and installing the to-be-installed operating system locally based on the first indication information.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of Internet, more particularly, to a method and device for installing an operating system via a network. BACKGROUND

[0002] When installing an operating system via a network in a BIOS (Basic Input / Output System) setting, the parameter sent to a DHCP (Dynamic Host Configuration Protocol) server is a uniform resolution parameter, and cannot be customized for different systems for installation, i.e., different operating systems cannot be installed on different hosts.

[0003] Therefore, in the implementation, the DHCP server returns path data of an intermediate operating system to the client, the client needs to install the intermediate operating system first, and then obtains path information of an operating system that the client actually needs to install based on the intermediate operating system, and finally the client restarts to load and install the operating system that the client actually needs. SUMMARY

[0004] Therefore, the present application provides the following technical solutions:

[0005] The first aspect of the present application provides a method for installing an operating system via a network, applied to a client, and the method comprises the following steps:

[0006] The client executes in a pre-boot execution environment;

[0007] First data carrying a device category is sent to a network management protocol server;

[0008] Return data returned by the network management protocol server based on the first data is obtained, the return data carries related data of an operating system to be installed, the operating system to be installed is determined by the network management protocol server based on a preset mapping relationship between a device category and an operating system, and the related data includes first indication information of a boot program of the operating system to be installed;

[0009] The operating system to be installed is installed locally based on the first indication information.

[0010] In one possible implementation, the method further comprises the following steps:

[0011] A setting option of a first interface is pre-configured by a first controller, the setting option is used to represent a device category, and the first controller is a controller in the client that can assist in remotely managing the first interface.

[0012] In a possible implementation, the related data at least includes address data and name data of the boot program, and the installing the to-be-installed operating system locally based on the first indication information comprises:

[0013] accessing a path corresponding to the address data in the related data to obtain the boot program with the name data;

[0014] installing the to-be-installed operating system locally based on the boot program.

[0015] In a possible implementation, the address data corresponds to a file server, and the network management protocol server and the file server are different servers.

[0016] In a possible implementation, the installing the to-be-installed operating system locally based on the first indication information comprises:

[0017] loading and running the boot program based on the first indication information, the boot program containing second indication information of obtaining a kernel program of the to-be-installed operating system;

[0018] obtaining the kernel program of the to-be-installed operating system from the file server based on the second indication information;

[0019] running the kernel program to obtain to-be-installed operating system image data from the file server and perform installation of the to-be-installed operating system.

[0020] The second aspect of the present application provides a method for installing an operating system in a network, applied to a server side, and the method comprises:

[0021] obtaining first data sent by a client, the first data including a device category, and the client being a device performing a pre-boot execution environment;

[0022] determining an operating system corresponding to the device category as a to-be-installed operating system based on a preset mapping relationship between device categories and operating systems;

[0023] sending related data of the to-be-installed operating system to the client, so that the client installs the to-be-installed operating system based on the related data, the related data including first indication information of obtaining a boot program of the to-be-installed operating system.

[0024] In a possible implementation, the method further comprises:

[0025] preconfiguring a mapping relationship between device categories and operating systems, so that the operating system corresponding to the device category can be determined based on the mapping relationship after the first data is obtained.

[0026] In a possible implementation, the sending of the related data of the to-be-installed operating system to the client comprises at least one of the following:

[0027] sending, to the client, an Internet protocol address and an access port of a file server where a boot program of the to-be-installed operating system corresponding to the device category is located;

[0028] sending, to the client, a file path and a file name of the boot program of the to-be-installed operating system corresponding to the device category.

[0029] The third aspect of the present application provides a device for installing an operating system in a network, applied to a client, the client being executed in a pre-boot execution environment, and the device comprises:

[0030] a data sending module configured to send first data carrying a device category to a network management protocol server;

[0031] a data receiving module configured to obtain return data returned by the network management protocol server based on the first data, the return data carrying related data of a to-be-installed operating system, the to-be-installed operating system being determined by the network management protocol server based on a preset mapping relationship between device categories and operating systems, and the related data comprising first indication information of a boot program of the to-be-installed operating system;

[0032] an installation control module configured to install the to-be-installed operating system locally based on the first indication information.

[0033] The fourth aspect of the present application provides a device for installing an operating system in a network, applied to a server end, and the device comprises:

[0034] a data obtaining module configured to obtain first data sent by a client, the first data comprising a device category, and the client being a device executed in a pre-boot execution environment;

[0035] a system determining module configured to determine, based on a preset mapping relationship between device categories and operating systems, an operating system corresponding to the device category as a to-be-installed operating system;

[0036] a data returning module configured to send, to the client, related data of the to-be-installed operating system, so that the client implements installation of the to-be-installed operating system based on the related data, and the related data comprising first indication information of a boot program of the to-be-installed operating system. BRIEF DESCRIPTION OF DRAWINGS

[0037] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the prior art, the accompanying drawings needed to be used in the embodiments or prior art description will be briefly introduced as follows. Obviously, the accompanying drawings in the following description only only the embodiments of the present application, and for those skilled in the art, other drawings can be obtained without creative labor on the basis of the provided drawings.

[0038] Figure 1 A flow chart of a method for installing an operating system on a network according to an embodiment of the present application is disclosed.

[0039] Figure 2 A flow chart of a method for installing an operating system on a network according to an embodiment of the present application is disclosed.

[0040] Figure 3 A flow chart of a method for installing an operating system on a network according to an embodiment of the present application is disclosed.

[0041] Figure 4 A structural schematic diagram of a device for installing an operating system on a network according to an embodiment of the present application is disclosed.

[0042] Figure 5 A structural schematic diagram of a device for installing an operating system on a network according to an embodiment of the present application is disclosed. DETAILED DESCRIPTION

[0043] The technical solutions in the embodiments of the present application will be described clearly and completely below with reference to the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, rather than all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those skilled in the art without creative labor fall within the scope of the present application.

[0044] In some large-scale device deployment, installation of an operating system through traditional methods is impossible, remote maintenance is required, and special network environment deployment (limited material resources or rapid deployment of a system) is required. In view of the problems that the implementation process of a traditional network installation operating system is complicated, the device needs to be restarted, and the operating system cannot be customized, the present application provides a method for installing an operating system on a network to overcome the foregoing problems.

[0045] Figure 1 A flow chart of a method for installing an operating system on a network according to an embodiment of the present application is disclosed. Figure 1 The method is applied to a client. Referring to Figure 1 As shown, the method for installing an operating system on a network can include the following steps.

[0046] Step 101: The client executes in a pre-boot execution environment.

[0047] The client performs in a pre-boot environment, that is, the client has not installed an operating system and cannot run in an operating system environment. The pre-boot environment can be a PXE (Preboot eXecution Environment), a network communication environment based on HTTP (Hypertext Transfer Protocol), and the like.

[0048] Step 102: sending first data carrying a device category to a network management protocol server.

[0049] The network management protocol server can be a DHCP (Dynamic Host Configuration Protocol) server or a DHCP proxy server. The device category can be, but is not limited to, at least one of the following: a device model, a name, a client identifier tag, a version number, a custom string, and the like.

[0050] After the client establishes a communication connection with the network management protocol server, the client can send the first data carrying the device category to the network management protocol server. The network management protocol server is configured with a mapping relationship between the device category and the operating system, so that after receiving the first data, the network management protocol server can determine a matching operating system based on the device category. The operating system here can be an existing or future operating system in the field, including but not limited to Windows, Windows, Linux, Android, and the like.

[0051] The first data can be a data packet, which can be a data packet conforming to a specific communication protocol. The communication protocol here includes but is not limited to PXE and HTTP. In addition to the device category, the data packet can also include other data, which can be at least one of the following: protocol control information, identity authentication and routing, service data, extension field, and the like.

[0052] Step 103: obtaining return data returned by the network management protocol server based on the first data, the return data carrying related data of a to-be-installed operating system, the related data including first indication information of a boot program of the to-be-installed operating system.

[0053] The to-be-installed operating system is the operating system that the client needs to install, which is determined by the network management protocol server based on a preset mapping relationship between the device category and the operating system. Since the mapping relationship between the device category and the operating system is configurable, the independent or batch configuration of the operating system that the client device needs to install can be realized remotely, meeting different scene requirements.

[0054] The relevant data carried in the returned data is the relevant information of the boot loader of the operating system to be installed by the client, such as path, name, etc.

[0055] For example, the client of the XXX350 series is pre-configured to install the first type of operating system, and the client of the SSS270 series is pre-configured to install the second type of operating system. If the device category in the first data received by the DHCP server contains “XXX350”, the first indication information of the boot loader of the first type of operating system is added to the returned data. If the device category in the first data received by the DHCP server contains “SSS270”, the first indication information of the boot loader of the second type of operating system is added to the returned data.

[0056] Step 104: installing the operating system to be installed locally based on the first indication information.

[0057] After the client receives the returned data sent by the network management protocol server, the first indication information in the returned data is used to communicate with the corresponding file server to load the boot loader and complete the installation of the operating system to be installed locally.

[0058] In the conventional scheme, before installing the operating system that is actually needed to be installed, a middleware operating system needs to be downloaded from the server side first, and the middleware operating system guides the user to select the operating system to be installed. After the user makes a selection, the middleware operating system “informs” the client of the indication information (path, name, etc.) of the boot loader of the selected operating system. Since a middleware operating system has been installed, the operating system that is actually needed to be installed (i.e., the operating system selected by the user) needs to be restarted once, and then the relevant files of the operating system that is actually needed to be installed are loaded and installed. The scheme of the present application is that the network management protocol server (pre-installed with the mapping relationship between the device category and the operating system) directly returns the first indication information of the corresponding boot loader based on the device category, and the client directly downloads the boot loader of the operating system to be installed based on the first indication information and completes the subsequent installation of the os, so that the client does not need to be restarted.

[0059] The method for installing an operating system on a network according to the embodiments of the present application carries the device category in the first data sent to the network management protocol server, so that the network management protocol server can determine the operating system to be installed corresponding to the device category based on the pre-set mapping relationship between the device category and the operating system, return the first indication information of the boot loader of the operating system to be installed, and the client can directly load the boot loader of the operating system to be installed based on the first indication information and complete the subsequent installation of the operating system. The whole process is simple and convenient, and the client does not need to be restarted.

[0060] On the basis of the foregoing embodiment, in another implementation, the method for installing an operating system via a network can further include: pre-configuring, by a first controller, a setting option of a first interface, the setting option being used to represent a device category, the first controller being a controller in the client that can assist in remotely managing the first interface.

[0061] The first controller can be a BMC (Baseboard Management Controller), and the first interface can be a UEFI (Unified Extensible Firmware Interface). That is, the setting option of the UEFI can be configured via the BMC.

[0062] Specifically, the UEFI contains some setting items that have not been defined or developed, such as a DHCP USER CLASS. The option (i.e., the foregoing setting item) is defined in the 77 specification of the DHCP spec specification. The value of the option includes the name string of each OS (Operating System), such as Window, RHEL, SUSE, WMware, etc. Of course, the value of the option can also be other content, such as a device model number, a version number, etc.

[0063] The option (DHCP USER CLASS) needs to accept a function that can be modified via a BMC command, such as onecli (a multi-in-one command line tool supporting firmware / device driver upgrade, system information / log management, and system configuration, etc.). The command can remotely modify the string value of the DHCP USER CLASS option added in the BIOS or UEFI via the BMC ip.

[0064] For example, there are 20 work machines that need to install an operating system via a network, and the BMCs of the work machines are in the same network segment. A device in the network segment can send a command to the BMCs of the 20 work machines to set the string value of the DHCP USER CLASS option of the 20 work machines to Window. Then, the 20 work machines will install Window via the network in the future. Alternatively, a command can be sent to set the string value of the DHCP USER CLASS option of the first 10 work machines to Window, and the string value of the DHCP USER CLASS option of the remaining 10 work machines to WMware. Then, 10 work machines will install Window via the network in the future, and the other 10 work machines will install WMware via the network in the future.

[0065] Of course, the foregoing is realized on the premise that the DHCP server is added with parsing and identifying logic for identifying the DHCP USER CLASS option, and the mapping relationship between the device type and various operating systems is specified. In a specific implementation, the configuration file of the DHCP server side can be modified, and the 77 category of the DHCP USER CLASS option transmitted by UEFI can be added in the pxe, http, and other protocol categories. The string value transmitted by the 77 category of the DHCP USER CLASS option is determined in the configuration file of the DHCP server. The matching operating system is determined according to the value of the different string, and the IP address of the file server where the determined operating system is located, and the specific path and name of the bootloader in the file server are returned.

[0066] The foregoing describes in detail the implementation of the foregoing network installation operating system scheme by configuring the setting option of the first interface, so as to facilitate the better understanding and implementation of the technical scheme of the present application by the person skilled in the art.

[0067] Figure 2 The flowchart of installing an operating system disclosed in the embodiments of the present application. In combination with Figure 2 The related data at least includes address data and name data of the bootloader, and the local installation of the to-be-installed operating system based on the first indication information can include:

[0068] Step 201: accessing the path corresponding to the address data in the related data to obtain the bootloader with the name data.

[0069] The address data includes the IP address of the file server where the to-be-installed operating system is located, and the path and name of the bootloader of the to-be-installed operating system, so that the client can download the bootloader of the to-be-installed operating system from the file server based on the address data. The address data corresponds to the file server where the to-be-installed operating system is located, and the network management protocol server and the file server can be different servers, or can be deployed on the same physical machine.

[0070] Step 202: installing the to-be-installed operating system locally based on the bootloader.

[0071] After the bootloader is downloaded, it can run in the UEFI environment. Then, the bootloader runs to obtain the kernel program of the to-be-installed operating system, further obtains the to-be-installed operating system image data by running the kernel program, and installs the to-be-installed operating system.

[0072] Based on the above, the locally installing the to-be-installed operating system based on the first indication information comprises: loading and running the boot program based on the first indication information, the boot program comprising second indication information for obtaining a kernel program of the to-be-installed operating system; obtaining the kernel program of the to-be-installed operating system from the file server based on the second indication information; and running the kernel program to obtain the to-be-installed operating system image data from the file server and perform installation of the to-be-installed operating system.

[0073] Figure 3 Another method flowchart for network installation of an operating system is disclosed in the embodiments of the present application. Figure 3 The method is applied to a server side. Referring to Figure 3 As shown, the method for network installation of an operating system can comprise:

[0074] Step 301: obtaining first data sent by a client, the first data comprising a device category, the client being a device performing a pre-boot execution environment.

[0075] The first data can be a data packet, which can be a data packet conforming to a specific communication protocol, the communication protocol herein including but not limited to PXE and HTTP. In addition to the device category, the data packet can further comprise other data, which can be at least one of the following: protocol control information, identity authentication and routing, service data, extension field, etc.

[0076] The device category can be, but is not limited to, at least one of the following: device model, name, client identifier tag, version number, custom string, etc.

[0077] Step 302: determining an operating system corresponding to the device category as a to-be-installed operating system based on a preset mapping relationship between device categories and operating systems.

[0078] The to-be-installed operating system is the operating system that needs to be installed by the client, which is determined by the network management protocol server based on the preset mapping relationship between device categories and operating systems. Since the mapping relationship between device categories and operating systems is configurable, independent or batch configuration of the operating system that needs to be installed by the client device can be realized remotely, meeting different scene requirements.

[0079] Step 303: sending related data of the to-be-installed operating system to the client, so that the client installs the to-be-installed operating system based on the related data, the related data comprising first indication information for obtaining a boot program of the to-be-installed operating system.

[0080] The first indication information includes but is not limited to a server IP, a path, a name and the like where the boot program is located.

[0081] The execution subject of the network installation operating system method described in the embodiments of the present application can be a network management protocol server, which is pre-built with a mapping relationship between device categories and operating systems, and thus, after receiving the first data sent by the client and containing the device category, the network management protocol server can determine the operating system to be installed and return related data including the first indication information of the boot program, so that the client can load the boot program of the operating system to be installed based on the first indication information and complete the subsequent installation of the operating system, and the whole process of network installation of the operating system is simple and convenient.

[0082] In other implementations, the method can further include pre-configuring a mapping relationship between device categories and operating systems, so that the operating system corresponding to the device category can be determined based on the mapping relationship after the first data is obtained.

[0083] In other implementations, the sending of the related data of the operating system to be installed to the client includes at least one of the following: sending an Internet protocol address and an access port of a file server where the boot program of the operating system to be installed corresponding to the device category is located to the client; and sending a file path and a file name of the boot program of the operating system to be installed corresponding to the device category to the client.

[0084] When the network management protocol server and the file server where the operating system to be installed are deployed on the same physical machine, the file path and the file name of the boot program of the operating system to be installed can be sent to the client. When the network management protocol server and the file server where the operating system to be installed are deployed on different physical machines, the Internet protocol address and the access port of the file server where the boot program of the operating system to be installed is located can be sent to the client.

[0085] For the foregoing method embodiments, in order to simply describe, they are all expressed as a series of action combinations, but those skilled in the art should know that the present application is not limited to the action sequence described, because according to the present application, certain steps can be performed in other sequences or simultaneously. Secondly, those skilled in the art should know that the embodiments described in the specification all belong to preferred embodiments, and the actions and modules involved are not necessarily necessary for the present application.

[0086] The method is described in detail in the embodiments disclosed in the present application, and the method of the present application can be implemented in various forms of devices, and thus the present application further discloses a device, and the following specific embodiments are given for detailed description.

[0087] Figure 4A structural schematic diagram of a device for network installation of an operating system is disclosed in the embodiments of the present application. Figure 4 The device is applied to a client. Referring to Figure 4 As shown, the device for network installation of an operating system 40 can include:

[0088] A data sending module 401 is configured to send first data carrying a device category to a network management protocol server.

[0089] A data receiving module 402 is configured to obtain return data returned by the network management protocol server based on the first data, the return data carrying relevant data of an operating system to be installed, the operating system to be installed being determined by the network management protocol server based on a preset mapping relationship between device categories and operating systems, and the relevant data including first indication information of a boot program of the operating system to be installed.

[0090] An installation control module 403 is configured to install the operating system to be installed locally based on the first indication information.

[0091] The device for network installation of an operating system disclosed in the embodiments of the present application carries a device category in the first data sent to the network management protocol server in the implementation process, so that the network management protocol server can determine an operating system to be installed corresponding to the device category based on a preset mapping relationship between device categories and operating systems, and return first indication information of a boot program of the operating system to be installed, and the client can directly load the boot program of the operating system to be installed based on the first indication information and complete the installation of the subsequent operating system, so that the whole process is simple and convenient, and the client does not need to be restarted.

[0092] In one implementation, the device can further include a configuration module configured to pre-configure a setting option of the first interface through a first controller, the setting option being used to represent a device category, and the first controller being a controller in the client that can assist in remotely managing the first interface.

[0093] In one implementation, the relevant data at least includes address data and name data of the boot program, the installation control module includes a program obtaining module configured to access a path corresponding to the address data in the relevant data to obtain the boot program with the name data, and an installation processing module configured to install the operating system to be installed locally based on the boot program.

[0094] In one implementation, the address data corresponds to a file server, and the network management protocol server and the file server are different servers.

[0095] In one implementation, the installation control module can be specifically configured to: load and run the boot program based on the first indication information, the boot program containing second indication information of obtaining a kernel program of the to-be-installed operating system; obtain the kernel program of the to-be-installed operating system from the file server based on the second indication information; run the kernel program to obtain the to-be-installed operating system image data from the file server and perform installation of the to-be-installed operating system.

[0096] The specific implementation of the apparatus for network installation of an operating system and each module included in the apparatus can be referred to the introduction of the corresponding content in the method embodiments, which will not be repeated here.

[0097] Figure 5 Another structural schematic diagram of an apparatus for network installation of an operating system disclosed in the embodiments of the present application. Figure 5 The apparatus shown is applied to a server side. Referring to Figure 5 As shown, the apparatus 50 for network installation of an operating system can include:

[0098] The data obtaining module 501 is configured to obtain first data sent by a client, the first data including a device category, the client being a device executing a preboot execution environment.

[0099] The system determining module 502 is configured to determine an operating system corresponding to the device category as a to-be-installed operating system based on a preset mapping relationship between device categories and operating systems.

[0100] The data returning module 503 is configured to send related data of the to-be-installed operating system to the client, so that the client implements installation of the to-be-installed operating system based on the related data, the related data including first indication information of obtaining a boot program of the to-be-installed operating system.

[0101] In the embodiments of the present application, the server has a mapping relationship between device categories and operating systems pre-built therein, so that after receiving the first data sent by the client and including the device category, the to-be-installed operating system can be determined, and related data including first indication information of the boot program is returned, so that the client can load the boot program of the to-be-installed operating system based on the first indication information and complete subsequent installation of the operating system, and the whole process of network installation of the operating system is simple and convenient.

[0102] In one implementation, the apparatus can further include a mapping configuration module configured to pre-configure a mapping relationship between device categories and operating systems, so that after the first data is obtained, the operating system corresponding to the device category can be determined based on the mapping relationship.

[0103] In one implementation, the data returning module can be specifically configured to: send an Internet protocol address and an access port of a file server where a boot program of the operating system to be installed corresponding to the device category is located to the client; and send a file path and a file name of the boot program of the operating system to be installed corresponding to the device category to the client.

[0104] The specific implementation of the device for installing an operating system over a network and each module included in the device can be referred to the introduction of the corresponding content in the method embodiments, which will not be repeated here.

[0105] The device for installing an operating system over a network in any of the above embodiments includes a processor and a memory, and the data sending module, the data receiving module, the installation control module, the data obtaining module, the system determining module, the data returning module, and the like in the above embodiments are stored in the memory as program modules, and the corresponding functions are realized by the processor executing the above program modules stored in the memory.

[0106] The processor includes a kernel, and the kernel retrieves the corresponding program modules from the memory. The kernel can be set as one or more, and the processing of the revisit data is realized by adjusting the kernel parameters.

[0107] The memory can include a non-permanent memory in a computer readable medium, a random access memory (RAM), and / or a non-volatile memory such as a read-only memory (ROM) or a flash memory (flash RAM), and the memory includes at least one memory chip.

[0108] In an exemplary embodiment, a computer readable storage medium directly loadable into the internal memory of a computer is also provided, which contains software codes. The computer program can be loaded and executed by the computer to realize the steps shown in any of the above method embodiments for installing an operating system over a network.

[0109] In an exemplary embodiment, a computer program product directly loadable into the internal memory of a computer is also provided, which contains software codes. The computer program can be loaded and executed by the computer to realize the steps shown in any of the above method embodiments for installing an operating system over a network.

[0110] Further, the embodiments of the present application provide an electronic device. The electronic device includes at least one processor, at least one memory connected with the processor, and a bus; wherein the processor and the memory complete mutual communication through the bus; the processor is configured to call program instructions in the memory to execute the above method for installing an operating system over a network applied to a client.

[0111] The embodiment of the present application provides a server. The server comprises at least one processor, and at least one memory connected with the processor, and a bus; wherein the processor and the memory complete mutual communication through the bus; the processor is used for calling program instructions in the memory, so as to execute the method for installing the network operating system on the server side.

[0112] The various embodiments in the specification are described in a progressive manner, and each embodiment focuses on the difference from other embodiments. The same or similar parts between the various embodiments can be referred to each other. For the device disclosed by the embodiments, since it corresponds to the method disclosed by the embodiments, the description is relatively simple, and the related parts can be referred to the method part.

[0113] It should also be noted that the relational terms herein such as first and second and the like are used only to differentiate one entity or operation from another, and do not necessarily require or imply that there is any such actual relationship or order between these entities or operations. In addition, the terms "comprises", "comprising" or any other variant thereof are intended to cover non-exclusive inclusion, so that a process, method, article or apparatus including a series of elements includes not only those elements, but also other elements not explicitly listed or inherent to such a process, method, article or apparatus. Without more limitations, the element defined by the statement "comprises a" does not exclude the presence of additional identical elements in the process, method, article or apparatus including the element.

[0114] The steps of the method or algorithm described in conjunction with the embodiments disclosed herein can be implemented directly by hardware, a software module executed by a processor, or a combination thereof. The software module can be placed in a random access memory (RAM), a memory, a read-only memory (ROM), an electrically programmable ROM, an electrically erasable programmable ROM, a register, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art.

[0115] The above description of the disclosed embodiments enables a person skilled in the art to implement or use the present application. Various modifications to these embodiments will be apparent to those skilled in the art, and the general principles defined herein can be implemented in other embodiments without departing from the spirit or scope of the present application. Therefore, the present application will not be limited to the embodiments shown herein, but will conform to the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A method for installing an operating system via a network, applied to a client, the method comprising: the client executing in a pre-boot execution environment; sending first data carrying a device category to a network management protocol server; obtaining return data returned by the network management protocol server based on the first data, the return data carrying relevant data of an operating system to be installed, the operating system to be installed being determined by the network management protocol server based on a preset mapping relationship between device categories and operating systems, the relevant data including first indication information of a boot program of the operating system to be installed; locally installing the operating system to be installed based on the first indication information. 2.The method of claim 1, further comprising: pre-configuring setting options of a first interface by a first controller, the setting options being used to represent device categories, the first controller being a controller in the client that can assist in remotely managing the first interface. 3.The method of claim 1, wherein the relevant data at least includes address data and name data of a boot program, and the locally installing the operating system to be installed based on the first indication information comprises: accessing a path corresponding to the address data in the relevant data to obtain the boot program with the name data; locally installing the operating system to be installed based on the boot program.

4. The method of installing an operating system for a network of claim 3, wherein, The address data corresponds to a file server, and the network management protocol server and the file server are different servers. 5.The method of claim 3, wherein the locally installing the operating system to be installed based on the first indication information comprises: loading and running the boot program based on the first indication information, the boot program containing second indication information of a kernel program of the operating system to be installed; obtaining the kernel program of the operating system to be installed from the file server based on the second indication information; running the kernel program to obtain image data of the operating system to be installed from the file server and perform installation of the operating system to be installed. 6.A method for installing an operating system via a network, applied to a server, the method comprising: obtaining first data sent by a client, the first data including a device category, the client being a device executing in a pre-boot execution environment; determining an operating system corresponding to the device category as an operating system to be installed based on a preset mapping relationship between device categories and operating systems; sending relevant data of the operating system to be installed to the client, so that the client performs installation of the operating system to be installed based on the relevant data, the relevant data including first indication information of a boot program of the operating system to be installed. 7.The method of claim 6, further comprising: pre-configuring the mapping relationship between device categories and operating systems, so that the operating system corresponding to the device category can be determined based on the mapping relationship after the first data is obtained.

8. The method of claim 6, wherein the sending the related data of the to-be-installed operating system to the client comprises at least one of the following: sending an Internet protocol address and an access port of a file server where a boot program of the to-be-installed operating system corresponding to the device category is located to the client; and sending a file path and a file name of the boot program of the to-be-installed operating system corresponding to the device category to the client.

9. An apparatus for network installation of an operating system, applied to a client, wherein the client is executed in a pre-boot execution environment, and the apparatus comprises: a data sending module configured to send first data carrying a device category to a network management protocol server; a data receiving module configured to obtain return data returned by the network management protocol server based on the first data, wherein the return data carries related data of a to-be-installed operating system, the to-be-installed operating system is determined by the network management protocol server based on a preset mapping relationship between device categories and operating systems, and the related data comprises first indication information of a boot program of the to-be-installed operating system; an installation control module configured to install the to-be-installed operating system locally based on the first indication information.

10. An apparatus for network installation of an operating system, applied to a server, and the apparatus comprises: a data obtaining module configured to obtain first data sent by a client, wherein the first data comprises a device category, and the client is a device executed in a pre-boot execution environment; a system determining module configured to determine an operating system corresponding to the device category as a to-be-installed operating system based on a preset mapping relationship between device categories and operating systems; a data returning module configured to send related data of the to-be-installed operating system to the client, so that the client implements installation of the to-be-installed operating system based on the related data, and the related data comprises first indication information of a boot program of the to-be-installed operating system.

Images