CN114860336A - PXE-based system audit mode implementation method and device and electronic equipment - Google Patents
PXE-based system audit mode implementation method and device and electronic equipment Download PDFInfo
- Publication number
- CN114860336A CN114860336A CN202210487234.8A CN202210487234A CN114860336A CN 114860336 A CN114860336 A CN 114860336A CN 202210487234 A CN202210487234 A CN 202210487234A CN 114860336 A CN114860336 A CN 114860336A
- Authority
- CN
- China
- Prior art keywords
- file
- pxe
- mode
- directory
- kickstar
- 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.)
- Granted
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/445—Program loading or initiating
- G06F9/44505—Configuring for program initiating, e.g. using registry, configuration files
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3684—Test management for test design, e.g. generating new test cases
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/61—Installation
- G06F8/63—Image based installation; Cloning; Build to order
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/34—Network arrangements or protocols for supporting network services or applications involving the movement of software or configuration parameters
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Security & Cryptography (AREA)
- Stored Programmes (AREA)
Abstract
The invention provides a PXE-based system audit mode implementation method, which comprises the following steps: receiving an opening instruction, and opening a DHCP, a TFTP and an HTTP service program according to the opening instruction; according to the address of the TFTP server, transmitting the boot file, the kernel file, the virtual file system and the option menu configuration file to a working directory of the TFTP service program; acquiring a compact disc mirror image and a KickStar automatic response file, and respectively configuring the compact disc mirror image and the KickStar automatic response file to corresponding working directories of an HTTP service program; according to the optical disk mirror image and the KickStar automatic response file, installing an operating system and restarting; and entering an auditing mode and executing an auditing function after the operating system is restarted according to the option menu configuration file. The invention automatically runs the detection script after the installation and the restart so as to detect whether the hardware function of the equipment is normal in batch and improve the working efficiency.
Description
Technical Field
The invention belongs to the field of computers, and particularly relates to a PXE-based system audit mode implementation method, a PXE-based system audit mode implementation device and electronic equipment.
Background
The server hardware equipment is the basis for ensuring the normal operation of all software, and in an actual production environment, in order to ensure the quality, the equipment of a server manufacturer generally needs to detect the hardware functions before leaving the warehouse, including the detection of hardware configurations such as a CPU (central processing unit), a hard disk, a memory and the like. With the increase of the number of servers, if an operator completes the detection of each server device one by one, a great amount of time and energy are consumed.
A Preboot execution Environment (PXE) is a mainstream technology at present, and is mainly applied to a Client/Server (Client/Server, C/S) for downloading a boot image file from a remote Server through a network, where the boot image file may be a boot program or an operating system, and the Client guides the operating system pre-installed in the remote Server according to the boot image file, so as to start the operating system on the Client.
The operating principle of Kickstar is to record various parameters that typically require manual intervention to fill in during installation and to generate a file of ks. If parameters need to be filled in during the installation process, the installation program firstly searches files generated by the Kickstar, and if proper parameters are found, the found parameters are adopted. Thus if the Kickstar file covers all the parameters that need to be filled out that may occur during the installation process, the operator can specify in advance where the ks.
Disclosure of Invention
In order to solve the problems in the prior art, the invention provides a method, a device and an electronic device for implementing a system audit mode based on PXE.
In a first aspect of the present invention, a PXE-based system audit mode implementation method is provided, where the method includes:
receiving an opening instruction, and opening a DHCP, a TFTP and an HTTP service program according to the opening instruction;
according to the address of the TFTP server, transmitting a boot file, a kernel file, a virtual file system and an option menu configuration file to a work directory/var/lib/tftpboot of the TFTP service program;
acquiring a compact disc mirror image and a KickStar automatic response file, and respectively configuring the compact disc mirror image and the KickStar automatic response file to corresponding working directories of an HTTP service program;
according to the optical disk mirror image and the KickStar automatic response file, installing an operating system and restarting, wherein the option menu configuration file comprises an auti-mode field;
and entering an auditing mode and executing an auditing function after the operating system is restarted according to the option menu configuration file.
Preferably, the method further comprises:
according to the working directory of the HTTP service program, creating a QC directory under/var/www/html, and copying a test script to the directory;
according to the HTTP service program working directory, an auti-mode directory is created under/var/www/html, and an audit mode configuration script is copied to the directory, wherein specifically, an eula-acquired field is contained in the KickStar automatic response file.
Preferably, the method further comprises:
acquiring an editable% post field in the Kickstar automatic response file;
and acquiring and running an audit mode configuration script according to the editable% post field.
Preferably, the method further comprises:
creating a test script directory/usr/share/oem-test at the PXE client;
and copying the test script under the QC directory to a test script directory by using a wget tool.
Preferably, the method further comprises:
after the execution of the auditing function is finished, detecting whether the test script comprises/usr/sbin/oem-exit;
if the test script comprises/usr/sbin/oem-exit, automatically exiting the auditing mode;
and if the/usr/sbin/oem-exit is not included in the test script, prompting the user to manually exit the audit mode.
In a second aspect of the present invention, a PXE-based system audit mode implementing apparatus is provided, including:
the starting module is used for receiving the starting instruction and starting the DHCP, the TFTP and the HTTP service program according to the starting instruction;
the file operation module is used for editing a file field instruction and transmitting a file to a corresponding position;
and the execution module is used for executing the corresponding function according to the file field instruction.
In a third aspect of the present invention, an electronic device for implementing a PXE-based system audit mode is provided, which includes a memory, a processor, and a computer program stored in the memory and executable on the processor, where the processor implements the steps of the PXE-based system audit mode function implementing method when executing the computer program.
In a fourth aspect of the present invention, a computer-readable storage medium is provided, where a computer program is stored, and the computer program, when executed by a processor, implements the steps of the above-mentioned system audit mode function implementation method.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings used in the embodiments or the prior art descriptions will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art to obtain other drawings based on the drawings without creative efforts.
Fig. 1 is a schematic flowchart of a procedure for opening an audit mode according to an embodiment of the present invention;
fig. 2 is a schematic flowchart of a method for implementing a PXE-based system audit mode according to an embodiment of the present invention;
fig. 3 is a schematic view of a specific implementation flow of the audit mode according to an embodiment of the present invention;
FIG. 4 is a block diagram illustrating a structure of a PXE-based system audit mode implementation apparatus according to an embodiment of the present invention;
fig. 5 is a schematic block diagram of an electronic device according to an embodiment of the present invention.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
Fig. 1 is a schematic flow chart of a procedure for starting an audit mode according to an embodiment of the present invention, in this embodiment:
the method comprises the steps that after a PXE client (namely a host needing to start an audit mode) obtains a start file and a boot file from a PXE server, a system is started according to a configuration file, and kernel parameters are required to be added into the configuration file to determine whether the audit mode is started after installation is completed; detecting whether an auti-mode field exists in a configuration file grub, if so, automatically responding to the file according to KickStar, acquiring and executing an audit mode configuration script and a test script, automatically logging in a root user after the system is restarted, and executing the test script; if the field does not exist, prompting the user to manually check the protocol and prompting the user to manually log in a user account to execute the auditing mode and the testing script.
Based on the embodiment shown in fig. 1, fig. 2 is a schematic flowchart of a method for implementing a PXE-based system audit mode according to an embodiment of the present invention, and fig. 3 is a schematic flowchart of a specific implementation of an audit mode according to an embodiment of the present invention.
Combining S201 in fig. 2 and S301 in fig. 3:
s201, receiving an opening instruction, and opening a DHCP service program, a TFTP service program and an HTTP service program according to the opening instruction;
s301, a PXE client (namely a host needing to start an audit mode) acquires an IP address and a TFTP server address from a PXE server;
in this embodiment, using the PXE + DHCP + TFTP + HTTP + KickStar server, the client obtains the IP address and the address of the TFTP server from the PXE server through the DHCP server.
Combining S202 in fig. 2 and S302 in fig. 3:
s202, according to the address of the TFTP server, transmitting the boot file, the kernel file, the virtual file system and the option menu configuration file to a work directory/var/lib/tftpboot of the TFTP service program;
s302, editing grub.cfg, adding an auti-mose field, and reading and configuring a start Linux kernel according to a start file;
in this embodiment, the TFTP service is configured, and a boot file pxelinux.0 (in this embodiment, the ARM architecture uses gruba 64.efi, and the x86 architecture uses grubx64. efi), a kernel and a virtual file system (i.e., vmlinux, initrd. img), and an option menu configuration file grub.cfg at startup are placed in a default working directory/var/lib/tftpbot/, where the configuration file grub.cfg includes an auti-mode field to open an audit mode function, and is effective for all clients.
In this embodiment, if only the client needs to be validated, the grub can be entered into the grub after the installation starts, and the grub can be edited by e, so as to add the quti-mode field.
S203, acquiring the optical disc image and the KickStar automatic response file, and respectively configuring the optical disc image and the KickStar automatic response file to the corresponding working directory of the HTTP service program:
in this embodiment, an HTTP service program is configured, and the optical disc image and the KickStar auto-response file are placed in a work directory of the HTTP service, so as to ensure that the client can automatically install the operating system. Further, in combination with S303 in fig. 3, the/var/www/html/QC directory in the PXE server places the test script, and the/var/www/html/auti-mode directory places the audit mode configuration script. Wherein, the example test script part content can be represented by the following code:
#!/bin/sh
time=`date`
echo $time > /dmid1.c
dmidecode >> /dmid1.c
in conjunction with S304 in fig. 3 and S204 in fig. 2:
s304, editing a% post field of a KickStart automatic response file, transmitting a file related to an audit mode to a client specified directory/usr/share/oem-test, and adding an eula-acquired field default agreement permission protocol;
s204, according to the optical disk mirror image and the KickStar automatic response file, installing an operating system and restarting;
in this embodiment, the kilkstart auto-answer file contains eula-acquired field default agreement permission protocol to ensure that the root user can be automatically logged in and the test file under the/user/share/oem-test directory can be executed without manual intervention after the system installation is restarted;
in this embodiment, the% post field in the Kickstart automatic response file includes content of acquiring and running the audit mode configuration script, and the audit mode configuration script is acquired and run according to the editable% post field. The relevant files of the checking mode are placed in a working directory of an HTTP service program, after being downloaded by a client, the files are placed in a specified directory of the checking mode, specifically, a directory/usr/share/oem-test for a user to add a checking script is created at the client, a test script under a QC directory of the server is copied to the directory by using a wget tool, and an execution permission is added. Furthermore, if there are multiple test scripts, multiple wget commands are added to obtain the test scripts.
Furthermore, in the audit mode configuration script, the administrator user root is set to automatically log in each time the system is started, oem-qc commands are provided to facilitate the user to manually execute the test script, and the operation is added to the startup automatic start item. Additionally, the oem-exit command is provided to allow the user to manually exit the audit mode, execute the oem-exit command to exit the audit mode, and prompt "Auti mode exited successful review!" indicating that the audit mode exit was successful. The content of/usr/sbin/oem-exit is added in the test script, and the audit mode is exited after the test script is executed.
The auditing mode quitting operation comprises deletion of three files of/usr/sbin/oem-qc,/usr/sbin/oem-exit,/etc/xdg/autostart/qc.desktop and recovery of the automatic login configuration file/etc/lightdm/lightdm.conf, and no other additional operation is carried out, and processing needs to be added in the test script if the/usr/share/oem-test directory or other test files need to be deleted.
And S205, entering an auditing mode and executing an auditing function after the operating system is restarted according to the option menu configuration file.
In this embodiment, after the system is restarted, it is detected whether the option menu configuration file contains an auti-mode field, and if the option menu configuration file contains the auti-mode field, the system enters an audit mode and pre-executes an audit function. With reference to S305 in fig. 3, system installation is completed according to the auto-response file, and the root user is automatically logged in to enter an audit mode after restarting; in this embodiment, it is detected whether the kiskstar auto-answer file agrees with the license agreement by default, and if so, the root user is automatically logged in, and the test script and audit mode functions are executed.
Further, after the execution of the audit function is finished, whether the test script comprises/usr/sbin/oem-exit is detected, and if the test script comprises/usr/sbin/oem-exit, the audit mode is automatically exited; and if the/usr/sbin/oem-exit is not included in the test script, prompting the user to manually exit the audit mode.
The method for realizing the system audit mode based on the PXE is based on the PXE technology, realizes batch detection of functions of hardware equipment of the client while deploying the operating system of the client, automatically logs in a root user by the system after the audit mode is started, executes a test script under an audit mode working directory, and provides a specified directory for the user to add the audit script by self, so that the method is flexible to use, and greatly saves labor input. In addition, an interface for manually executing the test script and an exit interface for an auditing mode are provided, so that a user can conveniently open or close the test script according to actual requirements.
Referring to fig. 4, fig. 4 is a schematic block diagram of a structure of a PXE-based system audit mode implementation apparatus according to an embodiment of the present invention, and for convenience of description, only a part related to the embodiment of the present invention is shown. As shown in fig. 4, the apparatus 400 includes:
the starting module 401 is configured to receive a start instruction, and start a DHCP, a TFTP, and an HTTP service program according to the start instruction;
a file operation module 402, configured to edit a file field instruction and transmit a file to a corresponding location;
and an executing module 403, configured to execute a corresponding function according to the file field instruction.
Preferably, the starting module 401 is further configured to:
and installing an operating system and restarting according to the optical disk image and the KickStar automatic response file.
Preferably, the file operation module 402 is further configured to:
according to the address of the TFTP server, transmitting a boot file, a kernel file, a virtual file system and an option menu configuration file to a work directory/var/lib/tftpboot of the TFTP service program;
and acquiring the optical disc image and the KickStar automatic response file, and respectively configuring the optical disc image and the KickStar automatic response file to the corresponding working directory of the HTTP service program.
Preferably, the execution module 403 is further configured to:
and entering an auditing mode and executing an auditing function after the operating system is restarted according to the option menu configuration file.
Preferably, the file operation module 402 is further configured to:
according to the working directory of the HTTP service program, creating a QC directory under/var/www/html, and copying a test script to the directory;
creating an auti-mode directory under the condition of/var/www/html according to the HTTP service program working directory, and copying an audit mode configuration script to the directory;
acquiring an editable% post field in the Kickstar automatic response file;
acquiring an audit mode configuration script according to the editable% post field;
creating a test script directory/usr/share/oem-test at the PXE client;
and copying the test script under the QC directory to a test script directory by using a wget tool.
Preferably, the execution module 403 is further configured to:
executing an audit mode configuration script according to the editable% post field;
after the audit function is executed, detecting whether the test script comprises/usr/sbin/oem-exit;
if the test script comprises/usr/sbin/oem-exit, automatically exiting the auditing mode;
and if the/usr/sbin/oem-exit is not included in the test script, prompting the user to manually exit the audit mode.
Referring to fig. 5, fig. 5 is a schematic block diagram of an electronic device according to an embodiment of the present invention. The electronic device 500 in the present embodiment as shown in fig. 5 may include, but is not limited to, at least one of the following: one or more processors 501, one or more input devices 502, one or more output devices 503, and one or more memories 504. The processor 501, the input device 502, the output device 503 and the memory 504 are all communicated with each other through a communication bus 505. The memory 504 is used to store a computer program comprising program instructions. The processor 501 is configured to execute program instructions stored in the memory 504.
It should be understood that, in the embodiment of the present invention, the Processor 501 may be a Central Processing Unit (CPU), and may also be other general-purpose processors, Digital Signal Processors (DSPs), Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs) or other Programmable logic devices, discrete Gate or transistor logic devices, discrete hardware components, and the like. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
The input device 502 may include a touch pad, a fingerprint sensor (for collecting fingerprint information of a user and direction information of the fingerprint), a microphone, etc., and the output device 503 may include a display (LCD, etc.), a speaker, etc.
The memory 504 may include a read-only memory and a random access memory, and provides instructions and data to the processor 501. A portion of the memory 504 may also include non-volatile random access memory. For example, the memory 504 may also store device type information.
In a specific implementation, the processor 501, the input device 502, and the output device 503 described in the embodiments of the present invention may execute the implementation manner described in the method embodiments provided in the embodiments of the present invention, and are not described herein again.
In another embodiment of the present invention, a computer-readable storage medium is provided, in which a computer program is stored, where the computer program includes program instructions, and the program instructions, when executed by a processor, implement all or part of the processes in the method of the above embodiments, and may also be implemented by a computer program instructing associated hardware, and the computer program may be stored in a computer-readable storage medium, and the computer program, when executed by a processor, may implement the steps of the above methods embodiments. Wherein the computer program comprises computer program code, which may be in the form of source code, object code, an executable file or some intermediate form, etc. The computer readable medium may include: any entity or device capable of carrying computer program code, recording medium, U.S. disk, removable hard disk, magnetic disk, optical disk, computer Memory, Read-Only Memory (ROM), Random Access Memory (RAM), electrical carrier wave signals, telecommunications signals, software distribution media, and the like. It should be noted that the computer readable medium may include any suitable increase or decrease as required by legislation and patent practice in the jurisdiction, for example, in some jurisdictions, computer readable media may not include electrical carrier signals and telecommunications signals in accordance with legislation and patent practice.
The computer readable storage medium may be an internal storage unit of the terminal of any of the foregoing embodiments, for example, a hard disk or a memory of the terminal. The computer readable storage medium may also be an external storage device of the terminal, such as a plug-in hard disk provided on the terminal, a Smart Media Card (SMC), a Secure Digital (SD) Card, a Flash memory Card (Flash Card), and the like. Further, the computer-readable storage medium may also include both an internal storage unit and an external storage device of the terminal. The computer-readable storage medium is used for storing a computer program and other programs and data required by the terminal. The computer-readable storage medium may also be used to temporarily store data that has been output or is to be output.
Those of skill in the art will appreciate that the elements and algorithm steps of the examples described in connection with the embodiments disclosed herein may be embodied in electronic hardware, computer software, or combinations of both, and that the components and steps of the examples have been described in a functional general in the foregoing description for the purpose of clearly illustrating the interchangeability of hardware and software. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the technical solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.
Claims (10)
1. A PXE-based system audit mode implementation method is characterized by comprising the following steps:
receiving an opening instruction, and opening a DHCP, a TFTP and an HTTP service program according to the opening instruction;
acquiring a TFTP server address, and transmitting a boot file, a kernel file, a virtual file system and an option menu configuration file to the TFTP service program working directory/var/lib/tftpboot;
acquiring a compact disc mirror image and a KickStar automatic response file, and respectively configuring the compact disc mirror image and the KickStar automatic response file to a working directory corresponding to the HTTP service program;
installing an operating system and restarting the operating system according to the optical disc mirror image and the KickStar automatic response file;
and entering an auditing mode and executing an auditing function after the operating system is restarted according to the option menu configuration file.
2. The PXE-based system audit mode implementation method of claim 1, wherein the option menu configuration file contains an auti-mode field.
3. The PXE-based system audit mode implementing method of claim 2, wherein said method further includes:
according to the working catalog of the HTTP service program, creating a QC catalog under/var/www/html, and copying a test script to the catalog;
and according to the working directory of the HTTP service program, creating an auti-mode directory under the/var/www/html, and copying the audit mode configuration script to the directory.
4. The PXE-based system audit mode implementing method as claimed in claim 3, wherein said KickStar auto-answer file contains eula-acquired field.
5. The method for implementing a PXE-based system audit mode function as claimed in claim 4, wherein said method further includes:
acquiring an editable% post field in the Kickstar automatic response file;
and acquiring and running the audit mode configuration script according to the editable% post field.
6. The PXE-based system audit mode implementation method of claim 3, wherein the method further comprises:
creating a test script directory/usr/share/oem-test at the PXE client;
and copying the test script under the QC directory to the test script directory by using a wget tool.
7. The PXE-based system audit mode implementation method of claim 3, wherein the method further comprises:
after the audit function is executed, detecting whether the test script comprises/usr/sbin/oem-exit;
if the test script comprises/usr/sbin/oem-exit, automatically exiting the auditing mode;
and if the/usr/sbin/oem-exit is not included in the test script, prompting the user to manually exit the auditing mode.
8. A PXE-based system audit mode implementation device is characterized by comprising:
the starting module is used for receiving a starting instruction and starting a DHCP, a TFTP and an HTTP service program according to the starting instruction;
the file operation module is used for editing a file field instruction and transmitting the file to a corresponding position;
and the execution module is used for executing corresponding functions according to the file field instruction.
9. An electronic device comprising a memory, a processor and a computer program stored in the memory and executable on the processor, characterized in that the processor performs the method steps according to any of claims 1 to 7.
10. A computer-readable storage medium, in which a computer program is stored which, when being executed by a processor, carries out the steps of a method according to any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210487234.8A CN114860336B (en) | 2022-05-06 | 2022-05-06 | System auditing mode implementation method based on PXE and electronic equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210487234.8A CN114860336B (en) | 2022-05-06 | 2022-05-06 | System auditing mode implementation method based on PXE and electronic equipment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN114860336A true CN114860336A (en) | 2022-08-05 |
| CN114860336B CN114860336B (en) | 2023-09-26 |
Family
ID=82636095
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210487234.8A Active CN114860336B (en) | 2022-05-06 | 2022-05-06 | System auditing mode implementation method based on PXE and electronic equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114860336B (en) |
Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6385766B1 (en) * | 1999-05-20 | 2002-05-07 | Dell Usa L.P. | Method and apparatus for windows-based installation for installing software on build-to-order computer systems |
| CN1399194A (en) * | 2001-07-24 | 2003-02-26 | 微软公司 | Method and system for creating and using operation system with optional functions |
| US6810478B1 (en) * | 2000-12-12 | 2004-10-26 | International Business Machines Corporation | System for remote booting of muntliple operating systems using chained bootstrap mechanism in a network |
| CN102195978A (en) * | 2011-04-26 | 2011-09-21 | 深圳市共济科技有限公司 | Software distribution deployment method and system |
| CN104932919A (en) * | 2015-06-04 | 2015-09-23 | 浪潮电子信息产业股份有限公司 | Implementation method of Linux unattended setup |
| US20170090896A1 (en) * | 2015-09-29 | 2017-03-30 | Quanta Computer Inc. | Automatic system software installation on boot |
| US20190163502A1 (en) * | 2017-11-29 | 2019-05-30 | Forcepoint Llc | Method for securely configuring an information system |
| US20200371770A1 (en) * | 2019-05-21 | 2020-11-26 | Vmware, Inc. | Management platform recovery for a user device |
| CN112306784A (en) * | 2020-10-29 | 2021-02-02 | 深圳宝新创科技股份有限公司 | Test method, test device, electronic equipment and test system |
| CN112527327A (en) * | 2020-12-07 | 2021-03-19 | 苏州浪潮智能科技有限公司 | Method, system, terminal and storage medium for factory restoration of UOS operating system |
-
2022
- 2022-05-06 CN CN202210487234.8A patent/CN114860336B/en active Active
Patent Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6385766B1 (en) * | 1999-05-20 | 2002-05-07 | Dell Usa L.P. | Method and apparatus for windows-based installation for installing software on build-to-order computer systems |
| US6810478B1 (en) * | 2000-12-12 | 2004-10-26 | International Business Machines Corporation | System for remote booting of muntliple operating systems using chained bootstrap mechanism in a network |
| CN1399194A (en) * | 2001-07-24 | 2003-02-26 | 微软公司 | Method and system for creating and using operation system with optional functions |
| CN102195978A (en) * | 2011-04-26 | 2011-09-21 | 深圳市共济科技有限公司 | Software distribution deployment method and system |
| CN104932919A (en) * | 2015-06-04 | 2015-09-23 | 浪潮电子信息产业股份有限公司 | Implementation method of Linux unattended setup |
| US20170090896A1 (en) * | 2015-09-29 | 2017-03-30 | Quanta Computer Inc. | Automatic system software installation on boot |
| US20190163502A1 (en) * | 2017-11-29 | 2019-05-30 | Forcepoint Llc | Method for securely configuring an information system |
| US20200371770A1 (en) * | 2019-05-21 | 2020-11-26 | Vmware, Inc. | Management platform recovery for a user device |
| CN112306784A (en) * | 2020-10-29 | 2021-02-02 | 深圳宝新创科技股份有限公司 | Test method, test device, electronic equipment and test system |
| CN112527327A (en) * | 2020-12-07 | 2021-03-19 | 苏州浪潮智能科技有限公司 | Method, system, terminal and storage medium for factory restoration of UOS operating system |
Non-Patent Citations (1)
| Title |
|---|
| MIKIGO: "PXE&OEM服务配置及使用说明", pages 1 - 7, Retrieved from the Internet <URL:《https://www.cnblogs.com/mikigo/p/14800310.html》> * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN114860336B (en) | 2023-09-26 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US6550021B1 (en) | Internet-implemented method supporting component repair services | |
| US6330669B1 (en) | OS multi boot integrator | |
| EP2192516A1 (en) | Method for upgrading antivirus software and terminal and system thereof | |
| US7313685B2 (en) | Unattended BIOS recovery | |
| US20080320466A1 (en) | Automatic software installation and cleanup | |
| CN107463388B (en) | UEFI diskless starting method | |
| JP2002196945A (en) | Upgrading system and method of device driver | |
| CN110908753B (en) | Intelligent fusion cloud desktop server, client and system | |
| CN101807152B (en) | Basic output and input system for self verification of selection read only memory and verification method thereof | |
| CN111581095A (en) | Self-starting USB debugging method and device based on barrier-free service and storage medium | |
| CN104036194A (en) | Vulnerability detection method and device for revealing private data in application program | |
| CN112162795A (en) | Plug-in starting method and device, computer equipment and storage medium | |
| CN107220085B (en) | Method for automatically upgrading RAID card firmware | |
| CN114138283A (en) | Remote automatic deployment method, device, terminal and storage medium for operating system | |
| CN111078305A (en) | Information acquisition method and device, server and information management system | |
| CN111090546A (en) | Method, device and equipment for restarting operating system and readable storage medium | |
| CN109471665B (en) | Method for automatically installing Windows operating system | |
| US20030120827A1 (en) | Method and apparatus for automatically detecting machine states during an operating system installation through a network | |
| CN114860336B (en) | System auditing mode implementation method based on PXE and electronic equipment | |
| CN113821264B (en) | Operating system installation control method, installation control system and computing device | |
| US6260140B1 (en) | Operating system multi boot integrator | |
| US20050289537A1 (en) | System and method for installing software on a computing device | |
| CN115167947A (en) | Installation method, device and medium of operating system | |
| CN113900693A (en) | Firmware upgrading method, device and system, electronic equipment and storage medium | |
| CN115033182A (en) | Processing method and device |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |