CN113608755A - Operating system deployment method, device and medium - Google Patents

Operating system deployment method, device and medium Download PDF

Info

Publication number
CN113608755A
CN113608755A CN202110981188.2A CN202110981188A CN113608755A CN 113608755 A CN113608755 A CN 113608755A CN 202110981188 A CN202110981188 A CN 202110981188A CN 113608755 A CN113608755 A CN 113608755A
Authority
CN
China
Prior art keywords
client
operating system
network
system deployment
domain
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202110981188.2A
Other languages
Chinese (zh)
Inventor
陈浩
沃君頔
张辉
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Ctrip Travel Network Technology Shanghai Co Ltd
Original Assignee
Ctrip Travel Network Technology Shanghai Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Ctrip Travel Network Technology Shanghai Co Ltd filed Critical Ctrip Travel Network Technology Shanghai Co Ltd
Priority to CN202110981188.2A priority Critical patent/CN113608755A/en
Publication of CN113608755A publication Critical patent/CN113608755A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00Arrangements for software engineering
    • G06F8/60Software deployment
    • G06F8/61Installation
    • G06F8/63Image based installation; Cloning; Build to order

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

The embodiment of the invention provides an operating system deployment method, an operating system deployment device, operating system deployment equipment and operating system deployment media, wherein the method comprises the following steps: determining a mirror image template, wherein the mirror image template comprises an operating system; generating a client system deployment automation script adapted to load the operating system to a client. The technical scheme in the embodiment of the invention can improve the efficiency of system deployment.

Description

Operating system deployment method, device and medium
Technical Field
The present invention relates to the field of software, and in particular, to a method, an apparatus, a device, and a medium for deploying an operating system.
Background
In some scenarios, the operating system needs to be loaded uniformly for the client, for example, in some enterprises, the operating system needs to be loaded uniformly in a large scale, for example, the operating system needs to be booted or activated, an update patch is installed, and these operations usually need to be completed manually, which is inefficient.
How to automatically deploy an operating system for an enterprise becomes an urgent problem to be solved.
Disclosure of Invention
To solve the problems in the prior art, an embodiment of the present invention provides an operating system deployment method, including:
a method of operating system deployment, comprising: determining a mirror image template, wherein the mirror image template comprises an operating system; generating a client system deployment automation script adapted to load the operating system to a client.
Optionally, the operating system deployment method further includes: and running the client system deployment automation script on the client to load the operating system to the client.
Optionally, the running of the client system deployment automation script at the client triggers the execution of the following steps:
performing network detection on the client to ensure that the network running state of the client is normal;
loading an operating system included in the mirror image template to a client;
the write back network detects and loads the operating system's log.
Optionally, the network detecting the client includes: if the network running state is detected to be abnormal, the network is automatically recovered after the reason of the network abnormality is identified.
Optionally, the running of the client system deployment automation script at the client triggers the execution of the following steps:
detecting the local connection state of the network, and prompting to unplug and plug the network cable again through a client interface if the local connection state of the network is not connected;
if the connection is made, acquiring a domain name system suffix;
detecting network access, prompting to unplug and plug a network cable again through a client interface if the network access fails, displaying a network address, detecting the local connection state of the network again, and acquiring a mainboard serial number display serial number and a network card address if the network access fails;
if the mainboard serial number display serial number and the network card address are successfully acquired, recording the registry as an automatic mode, renaming the computer, prompting to input a computer name through a user side if the mainboard serial number display serial number and the network card address are failed to be acquired, and renaming the computer after the input host name is judged to be correct;
the operating system and application software are activated.
Optionally, the client system deployment automation script is adapted to load the client with an operating system matching the client application scenario.
Optionally, loading the operating system to the client includes performing at least one of the following operations: configuring an operating system, activating the operating system, loading a system patch, loading software, and activating the software.
Optionally, the client system deployment automation script is further adapted to add the client to the corresponding domain.
Optionally, the adding the client to the corresponding domain includes:
calling a checking interface to inquire the installation type of the operating system, if the installation type is a new machine, calling a configuration interface to write and modify a host name result and obtain a domain name system suffix, and if the installation type is an old machine, directly obtaining the domain name system suffix;
requesting to acquire a domain-added account password;
obtaining an encrypted non-interactive account password;
locally decrypting the encrypted non-interactive account password;
acquiring a computer name of a client, judging whether the name is correct, if so, adding a corresponding domain according to a domain name system suffix, judging whether the domain is in the domain, and if not, recording error reporting information to a local log;
if the judgment result of whether the new interface is in the domain is yes, calling the reinstallation interface to write data, and if the judgment result is no, calling the new interface to write back the addition result.
Optionally, the client system deployment automation script is self-deleted after completing its function.
An embodiment of the present invention further provides an operating system deployment apparatus, including:
a mirror template unit adapted to determine a mirror template, the mirror template comprising an operating system;
an automation script generation unit adapted to generate a client system deployment automation script adapted to load the operating system to a client.
An embodiment of the present invention further provides an operating system deployment apparatus, including:
and the automatic script running unit is suitable for running a client system deployment automatic script so as to load the operating system to the client, the client system deployment automatic script is generated by the automatic script generating unit, and the client system deployment automatic script is suitable for loading the operating system to the client.
An embodiment of the present invention further provides an electronic device, including:
a processor;
a memory having stored therein executable instructions of the processor;
wherein the processor is configured to execute the method for implementing the operating system deployment via execution of the executable instructions.
The embodiment of the present invention further provides a computer-readable storage medium for storing a program, and the program realizes the operating system deployment method when executed.
According to the technical scheme, the automatic loading of the operating system can be realized by determining the mirror image template and generating the client system deployment automation script for loading the operating system to the client, so that the loading efficiency in a scene of loading the operating system in a large scale can be improved.
Drawings
Other features, objects and advantages of the present invention will become more apparent upon reading of the following detailed description of non-limiting embodiments thereof, with reference to the accompanying drawings.
FIG. 1 is a flow chart of a method of operating system deployment in an embodiment of the present invention;
FIG. 2 is a flowchart of deploying an operating system at a client via a script according to an embodiment of the present invention;
FIG. 3 is a flowchart of another embodiment of deploying an operating system at a client via scripting;
FIG. 4 is a flowchart of a method for adding the client to the corresponding domain according to an embodiment of the present invention;
FIG. 5 is a flowchart of another embodiment of deploying an operating system at a client via scripting;
FIG. 6 is a schematic structural diagram of a client or a server according to an embodiment of the present invention; and
fig. 7 is a schematic structural diagram of a computer-readable storage medium according to one embodiment of the present invention.
Detailed Description
Example embodiments will now be described more fully with reference to the accompanying drawings. Example embodiments may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein; rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the concept of example embodiments to those skilled in the art. The same reference numerals in the drawings denote the same or similar structures, and thus their repetitive description will be omitted.
An embodiment of the present invention provides a method for deploying an operating system, which, with reference to fig. 1, may specifically include the following steps:
step S11, determining a mirror image template, wherein the mirror image template comprises an operating system;
step S12, generating a client system deployment automation script adapted to load the operating system to the client.
In a specific implementation, steps S11 and S12 may be executed by a computer device, which may be a computer device or a server other than the client, or may be a device that is subsequently loaded as a client to receive the system, and is not limited herein.
In a specific implementation, the operating system included in the mirror template may be an operating system customized according to the requirements of the scene, so that a wider applicable scene may be provided. It will be appreciated that the image template may include an operating system that is an entire operating system or may be a portion of an operating system (a patch to an operating system).
In a specific implementation, after the client system deployment automation script is generated, the client system deployment automation script may be run by the client, so as to load the automation script for the client. The multiple clients can run the script in parallel, so that when the multiple clients all need to load the operating system, the loading efficiency can be improved, and the problems that the traditional operating system is low in deployment efficiency and cannot meet the requirements of an enterprise at present, the automatic operation and maintenance cost of the enterprise IT is reduced and the like are solved.
In a specific implementation, the client runs the client system to load the automation script, and may perform the following steps:
step S21, performing network detection on the client to ensure the normal network running state of the client;
step S22, loading the operating system included in the mirror image template to the client;
step S23, write back the log of the network detection and loading operating system.
It will be appreciated that other steps may be performed while running the client system deployment automation script, or in some embodiments some of the steps described above may be performed while running the client automation script. For example, loading of the operating system included in the image template to the client may be performed only.
In particular implementations, network detection may be performed prior to deployment of the operating system. The network detection of the client comprises the following steps: if the network running state is detected to be abnormal, the network is automatically recovered after the reason of the network abnormality is identified. The network detection mainly comprises Domain Name System (DNS) detection, network routing information table detection and judgment of a domain to which the network routing information table belongs through a domain name system suffix. The current network state of the client can be judged through a series of network detection; in addition, the network exception can be prompted through the script, and relevant repairing operation is executed cooperatively.
In a specific implementation, referring to FIG. 3 in combination, deploying an operating system at a client via scripting may include the following steps;
step S31, detecting the local connection state of the network, if not, prompting to unplug or plug the network cable again through the client interface;
step S32, if connected, acquiring domain name system suffix;
step S33, detecting network access, if failing, prompting to unplug network cable again through client interface, displaying network address, and detecting local connection state of network again, if successful, obtaining mainboard serial number display serial number and network card address;
step S34, if the mainboard serial number display serial number and the network card address are successfully acquired, the registry is recorded as an automatic mode, and the computer is renamed, if the mainboard serial number display serial number and the network card address are failed to be acquired, the computer name is prompted to be input through a user side, and the computer is renamed after the input host name is judged to be correct;
step S35, the operating system and application software are activated.
It will be appreciated that other steps may also be performed when the client runs the client system deployment automation script, such as adding a domain, writing back a log, etc. Moreover, the steps in fig. 3 are only examples, and it is within the scope of the present invention that fewer steps or other steps that can occur to those skilled in the art based on the above steps may be included in the specific implementation.
In a specific implementation, running the client system deployment automation script may load the client with an operating system that matches the client application scenario. Therefore, the matching of the automatically deployed operating system and the client can be further improved.
In a specific implementation, loading the operating system to the client includes performing at least one of: configuring an operating system, activating the operating system, loading a system patch, loading software, and activating the software.
In particular implementations, deploying automation scripts at the running client system may also add the client to the corresponding domain. Because in an application scenario of company client system deployment, a client needs to be added to a corresponding domain, and by integrating a function of adding a domain in a client system deployment automation script, efficiency of system deployment in the scenario can be further improved.
Referring to fig. 4 in combination, in a specific implementation, adding the client to the corresponding domain may be implemented by the following steps when the script runs:
step S41, calling the checking interface to inquire the installation type of the operating system, if the installation type is a new machine, calling the configuration interface to write the result of modifying the host name and obtain the domain name system suffix, if the installation type is an old machine, directly obtaining the domain name system suffix;
step S42, requesting to acquire the account password added with the domain;
step S43, obtaining an encrypted non-interactive account password;
step S44, locally decrypting the encrypted non-interactive account password;
step S45, obtaining the computer name of the client, and judging whether the name is correct, if yes, adding the corresponding domain according to the domain name system suffix, and judging whether the domain is in, if not, recording the error information to the local log;
and step S46, if the judgment result of whether the domain is present is yes, calling the reinstallation interface to write data, and if the judgment result is no, calling the new interface to write back the result of the addition.
In particular implementations, the client system deployment automation script may be self-deleted after performing its functions, thereby conserving system resources.
In particular implementations, running a client system deployment automation script may include sub-scripts that implement different functions, or the functions may be implemented via the same script. Different sub-scripts may have self-deleting capabilities, respectively.
It will be appreciated by those skilled in the art that the steps of the method in the above embodiments may be combined to suit different scenarios.
In an embodiment of the invention, after the client runs the client system deployment automation script, the following steps are implemented to load the operating system to the client.
As can be seen from fig. 5, in the process of performing network detection on the client, the physical information of the client of the current system to be loaded may be obtained, and registration and renaming may be performed according to the physical information, so that targeted loading of different clients may be achieved. The physical information can be a main serial number and a network card address, and the matching basis can be pre-stored information when the matching interface is called to match the computer name according to the serial number. The pre-stored information may be stored locally or elsewhere through a network connection. The active operating system may be a Windows operating system, or other operating system, or a system patch, and the active software may be office software, or other software.
In specific implementation, when a client system deployment automation script is operated to add the client to a corresponding domain, the client which is currently subjected to domain addition can be distinguished, if the client is an old machine which is loaded with the system before, if the client is a new machine which is loaded with the script for the first time, when the client is the old machine and is in the domain, a reinstallation interface is called to write back a domain adding result, and the reinstallation interface is used to write back the domain adding result according to the situation, so that the operation efficiency can be improved.
An embodiment of the present invention further provides an operating system deployment apparatus, including:
a mirror template unit adapted to determine a mirror template, the mirror template comprising an operating system;
an automation script generation unit adapted to generate a client system deployment automation script adapted to load the operating system to a client.
For specific implementation and beneficial effects of the operating system deployment apparatus in the embodiment of the present invention, reference may be made to the operating system deployment method described above, which is not described herein again.
An embodiment of the present invention further provides an operating system deployment apparatus, including:
and the automatic script running unit is suitable for running a client system deployment automatic script so as to load the operating system to the client, the client system deployment automatic script is generated by the automatic script generating unit, and the client system deployment automatic script is suitable for loading the operating system to the client.
The operating system deployment apparatus may be run on the aforementioned client, and specific implementation and beneficial effects thereof may refer to the aforementioned operating system deployment method, which is not described herein again.
An embodiment of the present invention further provides an electronic device, including:
a processor;
a memory having stored therein executable instructions of the processor;
wherein the processor is configured to execute the method for implementing the aforementioned operating system deployment via execution of the executable instructions.
Embodiments of the present invention also provide a computer-readable storage medium, which can be used to store a program, and when the program is executed, the method for deploying an operating system is implemented.
As will be appreciated by one skilled in the art, aspects of the present invention may be embodied as a system, method or program product. Thus, various aspects of the invention may be embodied in the form of: an entirely hardware embodiment, an entirely software embodiment (including firmware, microcode, etc.) or an embodiment combining hardware and software aspects that may all generally be referred to herein as a "circuit," module "or" platform.
Fig. 6 is a schematic structural diagram of a client or a server in an embodiment of the present invention. An electronic device 600 for implementing the aforementioned operating system deployment method according to this embodiment of the present invention is described below with reference to fig. 6. The electronic device 600 shown in fig. 6 is only an example, and should not bring any limitation to the functions and the scope of use of the embodiments of the present invention.
As shown in fig. 6, the electronic device 600 is embodied in the form of a general purpose computing device. The components of the electronic device 600 may include, but are not limited to: at least one processing unit 610, at least one memory unit 620, a bus 630 connecting the different platform components (including the memory unit 620 and the processing unit 610), a display unit 640, etc.
Wherein the storage unit stores program code executable by the processing unit 610 to cause the processing unit 610 to perform steps according to various exemplary embodiments of the present invention described in the above-mentioned electronic prescription flow processing method section of the present specification.
The storage unit 620 may include readable media in the form of volatile memory units, such as a random access memory unit (RAM)6201 and/or a cache memory unit 6202, and may further include a read-only memory unit (ROM) 6203.
The memory unit 620 may also include a program/utility 6204 having a set (at least one) of program modules 6205, such program modules 6205 including, but not limited to: an operating system, one or more application programs, other program modules, and program data, each of which, or some combination thereof, may comprise an implementation of a network environment.
Bus 630 may be one or more of several types of bus structures, including a memory unit bus or memory unit controller, a peripheral bus, an accelerated graphics port, a processing unit, or a local bus using any of a variety of bus architectures.
The electronic device 600 may also communicate with one or more external devices 700 (e.g., keyboard, pointing device, bluetooth device, etc.), with one or more devices that enable a user to interact with the electronic device 600, and/or with any devices (e.g., router, modem, etc.) that enable the electronic device 600 to communicate with one or more other computing devices. Such communication may occur via an input/output (I/O) interface 650. Also, the electronic device 600 may communicate with one or more networks (e.g., a Local Area Network (LAN), a Wide Area Network (WAN), and/or a public network such as the Internet) via the network adapter 660. The network adapter 660 may communicate with other modules of the electronic device 600 via the bus 630. It should be appreciated that although not shown in the figures, other hardware and/or software modules may be used in conjunction with the electronic device 600, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage platforms, to name a few.
Fig. 7 is a schematic structural diagram of a computer-readable storage medium of the present invention. Referring to fig. 7, a program product 800 for implementing the above method according to an embodiment of the present invention is described, which may employ a portable compact disc read only memory (CD-ROM) and include program code, and may be run on a terminal device, such as a personal computer. However, the program product of the present invention is not limited in this regard and, in the present document, a readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.
The program product may employ any combination of one or more readable media. The readable medium may be a readable signal medium or a readable storage medium. A readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples (a non-exhaustive list) of the readable storage medium include: an electrical connection having one or more wires, a portable disk, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
A computer readable storage medium may include a propagated data signal with readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A readable storage medium may also be any readable medium that is not a readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a readable storage medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.
Program code for carrying out operations for aspects of the present invention may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, C + + or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computing device, partly on the user's device, as a stand-alone software package, partly on the user's computing device and partly on a remote computing device, or entirely on the remote computing device or server. In the case of a remote computing device, the remote computing device may be connected to the user computing device through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external computing device (e.g., through the internet using an internet service provider).
In the description herein, references to the description of "an embodiment," "a further embodiment," "specifically," or "some examples," etc., mean that a particular feature, structure, material, or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of the invention. Furthermore, the particular features, structures, materials, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples. Moreover, various embodiments or examples and features of different embodiments or examples described in this specification can be combined and combined by one skilled in the art without conflicting aspects.
Furthermore, the terms "first", "second" and "first" are used for descriptive purposes only and are not to be construed as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include at least one such feature. In the description of the present invention, "a plurality" means two or more unless specifically defined otherwise.
Any process or method descriptions in flow charts or otherwise described herein may be understood as representing modules, segments, or portions of code which include one or more executable instructions for implementing specific logical functions or steps of the process. And the scope of the preferred embodiments of the present invention includes additional implementations in which functions may be executed out of order from that shown or discussed, including substantially concurrently or in reverse order, depending on the functionality involved.
The logic and/or steps represented in the flowcharts or otherwise described herein, such as an ordered listing of executable instructions that can be considered to implement logical functions, can be embodied in any computer-readable medium for use by or in connection with an instruction execution system, apparatus, or device, such as a computer-based system, processor-containing system, or other system that can fetch the instructions from the instruction execution system, apparatus, or device and execute the instructions.
In summary, according to the technical solution in the embodiment of the present invention, by determining the mirror template and generating the client system deployment automation script for loading the operating system to the client, automatic loading of the operating system can be achieved, so that loading efficiency in a scene of loading the operating system in a large scale can be improved.
The foregoing is a more detailed description of the invention in connection with specific preferred embodiments and it is not intended that the invention be limited to these specific details. For those skilled in the art to which the invention pertains, several simple deductions or substitutions can be made without departing from the spirit of the invention, and all shall be considered as belonging to the protection scope of the invention.

Claims (14)

1. A method of operating system deployment, comprising:
determining a mirror image template, wherein the mirror image template comprises an operating system;
generating a client system deployment automation script adapted to load the operating system to a client.
2. The method for operating system deployment according to claim 1, further comprising: and running the client system deployment automation script on the client to load the operating system to the client.
3. The operating system deployment method of claim 2, wherein the running of the client system deployment automation script at the client triggers execution of the steps of:
performing network detection on the client to ensure that the network running state of the client is normal;
loading an operating system included in the mirror image template to a client;
the write back network detects and loads the operating system's log.
4. The method of claim 3, wherein the network detection of the client comprises: if the network running state is detected to be abnormal, the network is automatically recovered after the reason of the network abnormality is identified.
5. The operating system deployment method of claim 2, wherein the running of the client system deployment automation script at the client triggers execution of the steps of:
detecting the local connection state of the network, and prompting to unplug and plug the network cable again through a client interface if the local connection state of the network is not connected;
if the connection is made, acquiring a domain name system suffix;
detecting network access, prompting to unplug and plug a network cable again through a client interface if the network access fails, displaying a network address, detecting the local connection state of the network again, and acquiring a mainboard serial number display serial number and a network card address if the network access fails;
if the mainboard serial number display serial number and the network card address are successfully acquired, recording the registry as an automatic mode, renaming the computer, prompting to input a computer name through a user side if the mainboard serial number display serial number and the network card address are failed to be acquired, and renaming the computer after the input host name is judged to be correct;
the operating system and application software are activated.
6. The operating system deployment method of claim 2, wherein the client system deployment automation script is adapted to load the client with an operating system matching the client application scenario.
7. The method of claim 2, wherein loading the operating system to the client comprises performing at least one of: configuring an operating system, activating the operating system, loading a system patch, loading software, and activating the software.
8. The operating system deployment method according to claim 1, wherein the client system deployment automation script is further adapted to add the client to the corresponding domain.
9. The system deployment method of claim 8, wherein the adding the client to the corresponding domain comprises:
calling a checking interface to inquire the installation type of the operating system, if the installation type is a new machine, calling a configuration interface to write and modify a host name result and obtain a domain name system suffix, and if the installation type is an old machine, directly obtaining the domain name system suffix;
requesting to acquire a domain-added account password;
obtaining an encrypted non-interactive account password;
locally decrypting the encrypted non-interactive account password;
acquiring a computer name of a client, judging whether the name is correct, if so, adding a corresponding domain according to a domain name system suffix, judging whether the domain is in the domain, and if not, recording error reporting information to a local log;
if the judgment result of whether the new interface is in the domain is yes, calling the reinstallation interface to write data, and if the judgment result is no, calling the new interface to write back the addition result.
10. The operating system deployment method of claim 2, wherein the client system deployment automation script is self-deleting upon completion of its functions.
11. An operating system deployment apparatus, comprising:
a mirror template unit adapted to determine a mirror template, the mirror template comprising an operating system;
an automation script generation unit adapted to generate a client system deployment automation script adapted to load the operating system to a client.
12. An operating system deployment apparatus, comprising:
and the automatic script running unit is suitable for running a client system deployment automatic script so as to load the operating system to the client, the client system deployment automatic script is generated by the automatic script generating unit, and the client system deployment automatic script is suitable for loading the operating system to the client.
13. An electronic device, comprising:
a processor;
a memory having stored therein executable instructions of the processor;
wherein the processor is configured to execute, via execution of the executable instructions, a method for implementing the operating system deployment of any of claims 1 to 10.
14. A computer-readable storage medium storing a program, wherein the program when executed implements the operating system deployment method of any one of claims 1 to 10.
CN202110981188.2A 2021-08-25 2021-08-25 Operating system deployment method, device and medium Pending CN113608755A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202110981188.2A CN113608755A (en) 2021-08-25 2021-08-25 Operating system deployment method, device and medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202110981188.2A CN113608755A (en) 2021-08-25 2021-08-25 Operating system deployment method, device and medium

Publications (1)

Publication Number Publication Date
CN113608755A true CN113608755A (en) 2021-11-05

Family

ID=78309308

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202110981188.2A Pending CN113608755A (en) 2021-08-25 2021-08-25 Operating system deployment method, device and medium

Country Status (1)

Country Link
CN (1) CN113608755A (en)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20060072422A (en) * 2004-12-23 2006-06-28 김재명 The p2p-based network segmentation method for specific software distribution and installtion automatically and it's production method and software asset and patch management system
CN1916846A (en) * 2005-08-17 2007-02-21 联想(北京)有限公司 Method for automatic deploying operate system
CN106406951A (en) * 2016-09-20 2017-02-15 杭州昆海信息技术有限公司 An installing method and device for an operating system
CN111464347A (en) * 2020-03-27 2020-07-28 北京云端智度科技有限公司 Automatic deployment device and method for large-scale heterogeneous equipment application
CN111786810A (en) * 2020-05-19 2020-10-16 中国科学院信息工程研究所 Automatic deployment method and system for large-scale test bed nodes

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20060072422A (en) * 2004-12-23 2006-06-28 김재명 The p2p-based network segmentation method for specific software distribution and installtion automatically and it's production method and software asset and patch management system
CN1916846A (en) * 2005-08-17 2007-02-21 联想(北京)有限公司 Method for automatic deploying operate system
CN106406951A (en) * 2016-09-20 2017-02-15 杭州昆海信息技术有限公司 An installing method and device for an operating system
CN111464347A (en) * 2020-03-27 2020-07-28 北京云端智度科技有限公司 Automatic deployment device and method for large-scale heterogeneous equipment application
CN111786810A (en) * 2020-05-19 2020-10-16 中国科学院信息工程研究所 Automatic deployment method and system for large-scale test bed nodes

Similar Documents

Publication Publication Date Title
US9710363B2 (en) Deployment and deployment planning as a service
US7523340B2 (en) Support self-heal tool
US10467085B2 (en) Fault processing method, system, and computer program product
US8468226B2 (en) Management server, boot server, network boot system, and network boot method
US10171315B2 (en) Orchestration process template for generation of orchestration process to tolerate errors
US9665465B1 (en) Automated determination of application permissions
JP2015165417A (en) networked Recovery System
CN106648724B (en) Application program hot repair method and terminal
US11334338B2 (en) Operating system update management
CN109683970A (en) A kind of amending method of server FRU information, modification system and relevant apparatus
CN108874441B (en) Board card configuration method, device, server and storage medium
US20210141632A1 (en) Automated software patching for versioned code
CN110597662A (en) Backup data automatic verification method and device, user equipment and storage medium
CN112631621A (en) Dependency package management method, device, server and storage medium
CN112579330B (en) Processing method, device and equipment for abnormal data of operating system
JPWO2005103909A1 (en) Security maintenance method, data storage device, security maintenance server, and recording medium recording the program
CN113608755A (en) Operating system deployment method, device and medium
CN114489704A (en) Version compiling and deploying method and device based on strategy
CN112559006A (en) Enterprise client automatic upgrading method, system, equipment and storage medium
WO2020119138A1 (en) Method for verifying credibility of bios restored file and relevant device
CN113204359A (en) Online server upgrading method and device
CN112256289A (en) Automatic deployment method, device and equipment
US20070061227A1 (en) Determining a computer system inventory
US9298445B1 (en) Systems and methods for correlating software inventory information with delivered software
CN112083939A (en) Batch upgrading method, device, system and medium

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination