Windows service batch installation management method and system and related equipment

Abstract

The invention provides a batch installation management method and system of Wi-Fi services and related equipment, and the method comprises the steps: constructing an installation management program of the Wi-Fi services, and the installation management program has Wi-Fi service downloading, dependency association and installation functions; installing the installation management program in the service management equipment; establishing communication connection between the service management equipment and the batch Wi-Fi system equipment; generating a list of batch Wi-Fi system equipment in the interactive interface of the installation management program; downloading the target Wi-Fi service file and the target service dependent file to a local service management device through an installation management program; and sending the target Wi-Fi service file and the target service dependent file to the selected Wi-Fi system equipment in the list in batches for installation. According to the method provided by the invention, the Wi-Fi services can be installed on the equipment system in batches without professional knowledge of personnel, and efficient batch management of the Wi-Fi services is realized.

Description

Technical Field

[0001] The present invention relates to the technical field of Windows service installation, and particularly to a method, system and related devices for batch installation and management of Windows services. Background Art

[0002] At present, there are many limitations in the way of batch installing the required service environment for Windows systems. Traditional methods often rely on manual installation and configuration. Each installation requires gradually executing multiple complex operation steps. Moreover, there is no installation program for some specified versions of application services under Windows, and they can only be manually decompressed and then installed as Windows services. This not only takes time and effort, but also easily leads to the inability of the service to run properly due to incorrect version installation or configuration by humans. Therefore, the existing technology has obvious deficiencies in terms of usability, installation efficiency, controllability and service management, and there is an urgent need for a solution that can simplify the installation process, have stronger controllability, optimize service configuration and provide efficient management functions.

[0003] Therefore, the existing technology still needs to be improved and developed. Summary of the Invention

[0004] The present invention provides a method, system and related devices for batch installation and management of Windows services. The main purpose of the present invention is to solve the technical problems mentioned in the background art of the existing technology.

[0005] The first aspect of the present invention provides a method for batch installation and management of Windows services, including:

[0006] Construct an installation management program for Windows services, and the installation management program has functions of Windows service download, Windows service dependency association and Windows service installation;

[0007] Install the installation management program into a service management device;

[0008] Establish a communication connection between the service management device and a batch of Windows system devices;

[0009] Generate a list of the batch of Windows system devices in the interactive interface of the installation management program;

[0010] Download a target Windows service file and a target service dependency file to the local of the service management device through the installation management program;

[0011] Batch send the target Windows service file and the target service dependency file to the selected Windows system devices in the list for installation.

[0012] In an alternative embodiment of the first aspect of the present invention, the installation management program for building a Windows service includes:

[0013] Building a Windows service file pulling and downloading function based on a hook function;

[0014] Building a packaging function for Windows service files and dependent files based on Electron tools and NSIS scripts.

[0015] In an alternative embodiment of the first aspect of the present invention, the building of the Windows service file pulling and downloading function based on a hook function includes:

[0016] Performing type matching of hook functions based on the Windows service type to obtain target hook functions;

[0017] Building a Windows service framework and integrating the target hook function and the Windows service framework;

[0018] Using the WinHTTP or WinINet library to implement file transfer of the Windows service framework based on the HTTP / HTTPS protocol;

[0019] Integrating an asynchronous task queue and hash verification encryption in the file transfer of the Windows service framework.

[0020] In an alternative embodiment of the first aspect of the present invention, the building of the packaging function for Windows service files and dependent files based on Electron tools and NSIS scripts includes:

[0021] Defining NSIS parameters in the package.json of the Electron tool and selecting a custom script path;

[0022] Registering the Windows service by calling the sc command through ExecWait in the NSIS script;

[0023] Using the File / r instruction to recursively package Electron front-end and.NET Core back-end service files into a unified directory, separating the app.asar front-end and the Service back-end subdirectories;

[0024] Using the nsDialogs plugin to create an interactive installation wizard to collect service configurations;

[0025] Configuring a digital signature mechanism for the Windows service file packaging.

[0026] In an alternative embodiment of the first aspect of the present invention, downloading the target Windows service file and the target service dependency file to the local of the service management device through the installation management program includes:

[0027] Receiving Windows service information input by the user in the interaction interface of the installation management program;

[0028] Finding the download resources of the Windows service information from at least one recommended address source based on the Windows service information;

[0029] Generating key information of the download resources in the interaction interface of the installation management program;

[0030] Receiving the user's selection of the download resources, and downloading the target Windows service file and the target service dependency file corresponding to the download resources to the local of the service management device.

[0031] In an alternative embodiment of the first aspect of the present invention, batch-sending the target Windows service file and the target service dependency file to the selected Windows system devices in the list for installation includes:

[0032] Receiving the selection by the user in the list of the Windows system devices that need to install the target Windows service file and the target service dependency file;

[0033] Obtaining the communication addresses of each of the selected Windows system devices in the list;

[0034] Obtaining the Windows system version information of each of the Windows system devices;

[0035] Obtaining the target Windows service file and the target service dependency file corresponding to each of the Windows system devices respectively based on the Windows system version information of each of the Windows system devices;

[0036] For each of the Windows system devices with the same Windows system version, synchronously sending the target Windows service file and the target service dependency file;

[0037] For each of the Windows system devices with different Windows system versions, asynchronously sending the target Windows service file and the target service dependency file.

[0038] In an alternative embodiment of the first aspect of the present invention, generating a list of a batch of the Windows system devices in the interaction interface of the installation management program includes:

[0039] Obtaining the device information of each of the Windows system devices;

[0040] Using the device unique identifier in the device information as the identity identifier of the Windows system device;

[0041] Based on the identity identifier, initially arranging each of the Windows system devices into a preset list;

[0042] Grouping each of the Windows system devices in the list based on the system version of each of the Windows system devices.

[0043] The second aspect of the present invention provides a batch installation management system for Windows services, and the batch installation management system for Windows services includes:

[0044] A program construction module, configured to construct an installation management program for Windows services, and the installation management program has functions of downloading Windows services, associating Windows service dependencies, and installing Windows services;

[0045] A program installation module, configured to install the installation management program into a service management device;

[0046] A communication establishment module, configured to establish a communication connection between the service management device and a batch of Windows system devices;

[0047] A list generation module, configured to generate a list of a batch of the Windows system devices in the interaction interface of the installation management program;

[0048] A file download module, configured to download a target Windows service file and a target service dependency file to the local of the service management device through the installation management program;

[0049] A file installation module, configured to batch send the target Windows service file and the target service dependency file to the selected Windows system devices in the list for installation.

[0050] The third aspect of the present invention provides a batch installation management device for Windows services, and the batch installation management device for Windows services includes: a memory and at least one processor, wherein instructions are stored in the memory, and the memory and the at least one processor are interconnected through a line;

[0051] The at least one processor invokes the instructions in the memory to cause the batch installation management device of the Windows service to execute the batch installation management method of the Windows service according to any one of the first aspects of the present invention.

[0052] In a fourth aspect of the present invention, a computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, it implements the batch installation management method of the Windows service according to any one of the first aspects of the present invention.

[0053] Beneficial effects: The present invention provides a batch installation management method, system and related devices for Windows services. The method includes constructing an installation management program for Windows services, where the installation management program has functions of downloading Windows services, dependency association and installation; installing the installation management program into a service management device; establishing a communication connection between the service management device and a batch of Windows system devices; generating a list of batch Windows system devices in the interactive interface of the installation management program; downloading target Windows service files and target service dependency files to the local of the service management device through the installation management program; and batch sending the target Windows service files and target service dependency files to the selected Windows system devices in the list for installation. The present invention provides a method for batch installing Windows services onto a device system without requiring personnel to have professional knowledge, realizing efficient batch management of Windows services. Description of the Drawings

[0054] Figure 1 It is a schematic diagram of an embodiment of the main method steps of a batch installation management method for Windows services according to the present invention;

[0055] Figure 2 It is a schematic diagram of an embodiment of a batch installation management system for Windows services according to the present invention;

[0056] Figure 3 It is a schematic diagram of an embodiment of a batch installation management device for Windows services according to the present invention. Detailed Embodiments

[0057] In the description and claims of the present invention and the above-mentioned drawings, terms such as "first", "second", "third", "fourth", etc. (if any) are used to distinguish similar objects and do not necessarily describe a specific order or sequence. It should be understood that such data can be interchanged under appropriate circumstances so that the embodiments described herein can be implemented in an order other than that illustrated or described herein. In addition, the term "comprising" or "having" and any variations thereof are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or device that comprises a series of steps or units does not necessarily have to be limited to those steps or units clearly listed, but may include other steps or units not clearly listed or inherent to these processes, methods, products, or devices.

[0058] For ease of understanding, the specific process of the embodiments of the present invention will be described below. Please refer to Figure 1 , the first aspect of the present invention provides a method for batch installation and management of Windows services, including:

[0059] S100. Build an installation management program for Windows services. The installation management program has functions of Windows service download, Windows service dependency association, and Windows service installation. The purpose of the technical solution of the present invention is to provide a method that does not require implementers to have relevant professional knowledge to complete the batch installation of services onto user Windows system machines, and to provide functions of service configuration, management, and monitoring. The first aspect of the present invention is to automatically download the required specified version of the service and configuration files through the installation management program for Windows services and then package them into an installation program. The installation management program for Windows services mainly utilizes the Electron packaging tool and hook functions, automatically downloads the dependencies listed in the configuration file from the specified resource path to the local using Nodejs, and then NSIS packages these dependencies and the client software source code into an executable installation file under Windows.

[0060] In an optional implementation manner of step S100 of the present invention, the building of the installation management program for Windows services includes:

[0061] S101. Build the Windows service file pulling and downloading function based on hook functions. Specifically, this step may include performing type matching of hook functions based on the Windows service type to obtain target hook functions; building a Windows service framework and integrating the target hook functions and the Windows service framework; using the WinHTTP or WinINet library to implement file transfer of the Windows service framework based on the HTTP / HTTPS protocol; and integrating an asynchronous task queue and hash verification encryption in the file transfer of the Windows service framework.

[0062] The technical concept of building the Windows service file pulling and downloading function based on hook functions in the present invention is as follows:

[0063] (1) Selection of hook functions and file system monitoring mechanism

[0064] Hook type selection: In the Windows system, real-time monitoring of the file system can be achieved through the ReadDirectoryChangesW API (suitable for asynchronous monitoring of directory changes), rather than traditional message hooks. However, if more low-level interception is required (such as file operation interception), kernel-level hook technologies (such as SSDT Hook or file filter drivers) can be combined, but attention should be paid to the PatchGuard restrictions of the x64 system; for user-mode services, it is recommended to use ReadDirectoryChangesW in combination with the asynchronous I / O model to achieve efficient monitoring by creating overlapped operations (Overlapped I / O).

[0065] Event triggering mechanism: When a file is created, modified, or deleted in the target directory, ReadDirectoryChangesW will return the specific event type (such as FILE_ACTION_ADDED) and the file name. The service can process these events through multi-threaded polling or an event-driven model to trigger the file pulling logic.

[0066] (2) Service architecture design and hook integration

[0067] Windows service framework: It is necessary to implement a standard Windows service structure, including the ServiceMain entry point, service control handling functions (such as SERVICE_CONTROL_STOP), and register the service through StartServiceCtrlDispatcher. The initialization of the hook functions should be completed when the service starts.

[0068] Combination of Hook and Service: Global Hook Injection: If cross-process file operation interception is required (such as monitoring file writing of all applications), the hook function needs to be encapsulated in a DLL and injected into the target process through SetWindowsHookEx (such as WH_SHELL or WH_CBT hook), but permission issues need to be noted; Service Permission Elevation: The service needs to run with the SYSTEM or high-privilege account to ensure access rights to the system directory and avoid UAC pop-up windows from interfering.

[0069] (3) Implementation of File Pulling and Downloading Module

[0070] Network Communication Layer: Use the WinHTTP or WinINet library to implement file transfer of HTTP / HTTPS protocols. For example, when a new file is detected, the service can call WinHttpOpenRequest to initiate a POST request to the specified URL to upload the file content; or download a remote file to the local directory through a GET request.

[0071] Asynchronous Task Queue: To avoid blocking the main service thread, a task queue and a thread pool need to be designed. For example, use CreateThreadpoolWork to submit file transfer tasks and handle the completion status through a callback function.

[0072] (4) Security and Stability Optimization

[0073] Integrity of Hook Chain: CallNextHookEx must be called in the hook function to ensure that the system message chain is not damaged, otherwise it may cause the system to freeze. For file filtering hooks, the original API call needs to be restored after interception (such as the "unhook - execute - rehook" mechanism of InlineHook).

[0074] Data Encryption and Verification: File transfer needs to support TLS encryption (such as OpenSSL integration) and perform hash verification on the file locally (such as SHA-256) to prevent man-in-the-middle attacks or data tampering.

[0075] S101. Packaging function for Windows service files and dependent files built based on Electron tools and NSIS scripts. Specifically, this step may include defining NSIS parameters in the package.json of the Electron tool and selecting a custom script path; calling the sc command in the NSIS script to register the Windows service through ExecWait; using the File / r instruction to recursively package the Electron front-end and.NET Core back-end service files into a unified directory, separating the app.asar front-end and Service back-end subdirectories; using the nsDialogs plugin to create an interactive installation wizard to collect service configurations; and configuring a digital signature mechanism for the Windows service file packaging.

[0076] Electron-builder configuration: Implement the integration of the packaging process through the NSIS plugin of electron-builder. NSIS parameters (such as oneClick, allowElevation, createDesktopShortcut, etc.) need to be defined in the package.json, and a custom script path (include and script fields) needs to be specified to extend the service registration logic.

[0077] Service registration and lifecycle management: Call the nssm (unofficial service manager) or sc command in the NSIS script to register the Windows service through ExecWait. Service dependencies (such as.NET Core runtime) and installation directory permissions (RequestExecutionLevel admin) need to be handled.

[0078] Multi-component packaging strategy: Use the File / r instruction to recursively package the Electron front-end (rendering process) and.NET Core back-end service files into a unified directory, separating the app.asar (front-end) and Service (back-end) subdirectories. Specify the runtime path through SetOutPath to avoid path conflicts

[0079] Dynamic parameter collection: Use the nsDialogs plugin to create an interactive installation wizard to collect service configurations (such as port number, database path). The user input value is obtained through ${NSD_GetText} and written to a configuration file (such as JSON or INI) for the back-end service to read when starting.

[0080] Registry and Shortcut Management: Write uninstall information to Windows\CurrentVersion\Uninstall, and support displaying service version and publisher in the Control Panel. Create shortcuts with parameters via CreateShortCut, such as starting the service debug console.

[0081] Code Signing and Permission Control: Digitally sign the installer (.exe) and service executable file (.exe) to prevent being recognized as malware. Use the!packhdr instruction to compress the installer package header, and combine it with TLS encryption to configure file transfer (such as calling the WinHTTP API).

[0082] S200. Install the installation management program into the service management device; in the present invention, by using the installation management program, the user can batch install specified services onto the Windows system of the target device, and can manage and configure the installed Windows services through the user interface provided by this installation management program. For example, by using the one-key installer, install these application services compressed in the installation package onto the specified Windows system. Through the user interface, the user can perform operations such as starting, stopping, restarting, and editing the service configuration on the specified service. By clicking the refresh button, the current status of each service, such as "Running", "Stopped", "Starting / Stopping", can be intuitively seen.

[0083] S300. Establish a communication connection between the service management device and a batch of Windows system devices; in the present invention, the purpose of establishing a communication connection between the service management device and a batch of Windows system devices is to achieve information communication between the service management device and a batch of Windows system devices, and establish a dedicated data transmission channel, so that the service management device can obtain the device information of a batch of Windows system devices and improve the security of data transmission. The installation management program in the present invention integrates the ability to read the connection information of network devices within the local area network. After the service management device is connected to a batch of Windows system devices, it will trigger the service management device and a batch of Windows system devices to send device information requests.

[0084] S400. Generate a list of a batch of the Windows system devices in the interactive interface of the installation management program; in the present invention, after the service management device obtains the device information of a batch of Windows system devices, it will generate a device list based on the device information of a batch of Windows system devices, and the user can select the devices that need to install Windows services from the list.

[0085] In an alternative embodiment of step S400 of the present invention, generating a list of a batch of the Windows system devices in the interactive interface of the installation management program includes: obtaining the device information of each of the Windows system devices; using the unique device identifier in the device information as the identity identifier of the Windows system device; initially arranging each of the Windows system devices into a pre-set list based on the identity identifier; and grouping each of the Windows system devices in the list based on the system version of each of the Windows system devices. In the list of the present invention, each of the Windows system devices is also grouped based on the system version, which facilitates the unified management of Windows system devices with the same system version. In the present invention, the groups of Windows system devices with different system versions can be distinguished by colors. In the list, the group of Windows system devices with a newer system version is ranked higher.

[0086] S500. Download the target Windows service file and the target service dependency file to the local of the service management device through the installation management program; in the present invention, when the installation management program downloads the target Windows service file, it will download the target service dependency file according to the service dependency relationship. Currently, the dependency relationships between different services need to be manually processed, and intelligent analysis and optimized deployment cannot be achieved. The technical solution of the present invention solves this problem of the prior art.

[0087] In an alternative embodiment of the first aspect of the present invention, downloading the target Windows service file and the target service dependency file to the local of the service management device through the installation management program includes: receiving the Windows service information input by the user in the interactive interface of the installation management program; finding the download resources of the Windows service information from at least one recommended address source based on the Windows service information; generating the key information of the download resources in the interactive interface of the installation management program; receiving the selection of the download resources by the user, and downloading the target Windows service file and the target service dependency file corresponding to the download resources to the local of the service management device. In the present invention, at least one of the recommended address sources includes an official address source. When searching for download resources, the Windows service file with better compatibility is preferentially downloaded. In the present invention, different download resources are downloaded in a breadth-first manner and then distributed to each of the Windows system devices in a depth-first manner. The advantage of doing this is that it can improve the download matching efficiency of the download resources.

[0088] S600. Batch send the target Windows service file and the target service dependency file to the selected Windows system devices in the list for installation. In the present invention, after obtaining the target Windows service file and the target service dependency file, batch distribution and installation can be performed based on the device identifier of the Windows system device.

[0089] In an alternative embodiment of step S600 of the present invention, the batch sending of the target Windows service file and the target service dependency file to the selected Windows system devices in the list for installation includes: receiving the selection by the user of the Windows system devices in the list that need to install the target Windows service file and the target service dependency file; obtaining the communication addresses of each of the selected Windows system devices in the list; obtaining the Windows system version information of each of the Windows system devices; obtaining the corresponding target Windows service file and target service dependency file for each of the Windows system devices based on the Windows system version information of each; for each of the Windows system devices with the same Windows system version, synchronously send the target Windows service file and the target service dependency file; for each of the Windows system devices with different Windows system versions, asynchronously send the target Windows service file and the target service dependency file. In the present invention, the priority of synchronous sending is higher than that of asynchronous sending. That is to say, for each target Windows service file and target service dependency file, first determine whether there is a case of synchronous sending for the target Windows service file and the target service dependency file. If so, first execute the case of synchronous sending. After the case of synchronous sending, then execute the case of asynchronous sending. The technical solution of the present invention performs the sending and installation of the target Windows service file and the target service dependency file according to the above logic, making the file transmission more orderly. In addition, when a file sending exception occurs, it is easier to locate the exception point, so as to better handle it targeted.

[0090] In order to reduce the implementation labor cost, the present invention develops a program for automatic installation, configuration, management and monitoring of database services under Windows. It can automatically download the specified version of the service compressed package from the configured download link, install it as a Windows service, and provide monitoring, management and configuration interfaces. Compared with the manual installation of the specified version by implementation personnel and configuration into a Windows service, it improves the installation and configuration efficiency, reduces human errors, and improves the software controllability. Generally speaking, the main features of the present invention are as follows:

[0091] (1) It can download the service application of the specified version and package it into an installation management program.

[0092] (2) It can install and configure Windows services in batches. The one-key installation package can automatically install the required services and preset the service configuration.

[0093] (3) It can provide service management functions. Users can perform operations such as start, stop, and restart on the specified service in the installation management program.

[0094] (4) It can provide service configuration functions. After the user stops the specified service in the installation management program, by modifying the configuration items in the service configuration interface of the software and then restarting the service, the operation of modifying a service configuration can be completed.

[0095] (5) It reduces the requirements for the professional skills of implementation personnel.

[0096] See Figure 2 , the second aspect of the present invention provides a batch installation management system for Windows services, and the batch installation management system for Windows services includes:

[0097] A program construction module 10 for constructing an installation management program for Windows services, and the installation management program has functions of Windows service download, Windows service dependency association, and Windows service installation;

[0098] A program installation module 20 for installing the installation management program into a service management device;

[0099] A communication establishment module 30 for establishing a communication connection between the service management device and a batch of Windows system devices;

[0100] An inventory generation module 40 for generating an inventory of a batch of the Windows system devices in the interaction interface of the installation management program;

[0101] A file download module 50, configured to download a target Windows service file and a target service dependency file to the local of the service management device through the installation management program;

[0102] A file installation module 60, configured to batch send the target Windows service file and the target service dependency file to the selected Windows system devices in the list for installation.

[0103] In an optional implementation manner of the second aspect of the present invention, the program construction module includes:

[0104] A download function construction unit, configured to construct a Windows service file pulling and downloading function based on a hook function;

[0105] A packaging function construction unit, configured to construct a packaging function for the Windows service file and the dependency file based on the Electron tool and the NSIS script.

[0106] In an optional implementation manner of the second aspect of the present invention, the download function construction unit includes:

[0107] A function type matching subunit, configured to perform type matching of the hook function based on the Windows service type to obtain a target hook function;

[0108] A framework building subunit, configured to build a Windows service framework and integrate the target hook function and the Windows service framework;

[0109] A transmission construction subunit, configured to use the WinHTTP or WinINet library to implement file transmission of the Windows service framework based on the HTTP / HTTPS protocol;

[0110] An anti-blocking / encryption subunit, configured to integrate an asynchronous task queue and hash check encryption in the file transmission of the Windows service framework.

[0111] In an optional implementation manner of the second aspect of the present invention, the packaging function construction unit includes:

[0112] A script path customization subunit, configured to define NSIS parameters and select a custom script path in the package.json of the Electron tool;

[0113] A service registration subunit, configured to register a Windows service by calling the sc command through ExecWait in the NSIS script;

[0114] A directory construction subunit, which is used to recursively package Electron front-end and.NET Core back-end service files into a unified directory using the File / r command, and separate the app.asar front-end and Service back-end subdirectories;

[0115] A service configuration subunit, which is used to create an interactive installation wizard using the nsDialogs plugin and collect service configurations;

[0116] A packaging and encryption subunit, which is used to configure a digital signature mechanism for Windows service files during packaging.

[0117] In an optional implementation manner of the second aspect of the present invention, the file download module includes:

[0118] An input receiving unit, which is used to receive Windows service information input by a user in the interaction interface of the installation management program;

[0119] A resource searching unit, which is used to search for download resources of the Windows service information from at least one recommended address source based on the Windows service information;

[0120] A key information generating unit, which is used to generate key information of the download resources in the interaction interface of the installation management program;

[0121] A selected download unit, which is used to receive the selection of the download resources by the user, and download the target Windows service file and target service dependency file corresponding to the download resources to the local of the service management device.

[0122] In an optional implementation manner of the second aspect of the present invention, the file installation module includes:

[0123] A selected receiving unit, which is used to receive the selection of the Windows system devices that need to install the target Windows service file and the target service dependency file by the user in the list;

[0124] An address obtaining unit, which is used to obtain the communication addresses of each of the selected Windows system devices in the list;

[0125] A system version information obtaining unit, which is used to obtain the Windows system version information of each of the Windows system devices;

[0126] A service file matching unit, which is used to obtain the target Windows service file and the target service dependency file corresponding to each of the Windows system devices respectively based on the Windows system version information of each of the Windows system devices;

[0127] A synchronous sending unit, configured to synchronously send the target Windows service file and the target service dependency file to each of the Windows system devices with the same Windows system version;

[0128] An asynchronous sending unit, configured to asynchronously send the target Windows service file and the target service dependency file to each of the Windows system devices with different Windows system versions.

[0129] In an optional implementation manner of the second aspect of the present invention, the manifest generation module includes:

[0130] A device information acquisition unit, configured to acquire the device information of each of the Windows system devices;

[0131] An identity identification determination unit, configured to use the device unique identifier in the device information as the identity identification of the Windows system device;

[0132] A device arrangement unit, configured to preliminarily arrange each of the Windows system devices into a preset manifest based on the identity identification;

[0133] A manifest grouping unit, configured to group each of the Windows system devices in the manifest based on the system versions of each of the Windows system devices.

[0134] Figure 3 FIG. is a schematic structural diagram of a device for batch installation and management of Windows services provided by an embodiment of the present invention. The device for batch installation and management of Windows services may vary greatly due to configuration or performance differences, and may include one or more processors 70 (central processing units, CPUs) (for example, one or more processors) and a memory 80, and one or more storage media 90 for storing application programs or data (for example, one or more mass storage devices). Among them, the memory and the storage media may be transient storage or persistent storage. The programs stored in the storage media may include one or more modules (not shown in the figure), and each module may include a series of instruction operations on the device for batch installation and management of Windows services. Further, the processor may be configured to communicate with the storage media and execute a series of instruction operations in the storage media on the device for batch installation and management of Windows services.

[0135] The batch installation management device for Windows services of the present invention may further include one or more power supplies 100, one or more wired or wireless network interfaces 110, one or more input / output interfaces 120, and / or, one or more operating systems, such as Windows Serve, Mac OS X, Unix, Linux, FreeBSD, etc. Those skilled in the art can understand that Figure 3 The structure of the batch installation management device for Windows services shown does not limit the batch installation management device for Windows services, and may include more or fewer components than shown, or combine certain components, or have different component arrangements.

[0136] The present invention also provides a computer-readable storage medium. The computer-readable storage medium can be a non-volatile computer-readable storage medium, and the computer-readable storage medium can also be a volatile computer-readable storage medium. Instructions are stored in the computer-readable storage medium. When the instructions run on a computer, the computer is caused to execute the steps of the batch installation management method for Windows services described above.

[0137] Those skilled in the art can clearly understand that for the convenience and brevity of description, the specific working processes of the above-described system or systems and units can refer to the corresponding processes in the foregoing method embodiments, and will not be described herein again.

[0138] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on such an understanding, the technical solution of the present invention, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for causing a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in various embodiments of the present invention. The foregoing storage medium includes: various media such as USB flash drives, mobile hard disks, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical discs that can store program codes.

[0139] As described above, the above embodiments are only used to illustrate the technical solutions of the present invention, rather than to limit it; although the present invention has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand that they can still modify the technical solutions recorded in the foregoing embodiments, or perform equivalent replacements on some of the technical features; and these modifications or replacements do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of the present invention.

Claims

1. A batch installation management method for Windows services, characterized in that: include: Constructing an installation management program for Windows services, wherein the installation management program has Windows service downloading, Windows service dependency association and Windows service installation functions; Installing the installation management program into the service management device; Establishing a communication connection between the service management device and batch Windows system devices; Generating a batch list of the Windows system devices in the interactive interface of the installation management program; Download the target Windows service file and the target service dependency file to the local service management device through the installation management program; The target Windows service files and the target service dependent files are sent in batches to the Windows system devices selected in the list for installation.

2. The batch installation management method for Windows services according to claim 1, characterized in that: The installation management program for building Windows services includes: Based on the hook function, the Windows service file pull and download function is built; Windows service files and dependent file packaging functions built based on Electron tools and NSIS scripts.

3. The batch installation management method for Windows services according to claim 2, characterized in that: The Windows service file pull and download function constructed based on the hook function includes: Match the type of hook function based on the Windows service type to obtain the target hook function; Building a Windows service framework, integrating the target hook function with the Windows service framework; Use WinHTTP or WinINet library to implement file transfer based on HTTP / HTTPS protocol in Windows service framework; Integrate asynchronous task queue and hash check encryption in the file transfer of the Windows service framework.

4. The batch installation management method for Windows services according to claim 2, characterized in that: The Windows service file and dependent file packaging functions built based on the Electron tool and NSIS script include: Define NSIS parameters in the package.json of the Electron tool and select the custom script path; In the NSIS script, call the sc command through ExecWait to register the Windows service; Use the File / r command to recursively package the Electron front-end and .NET Core back-end service files into a unified directory, separating the app.asar front-end and Service back-end sub-directories; Use nsDialogs plugin to create interactive installation wizard and collect service configuration; Configure the digital signature mechanism for Windows service file packaging.

5. The batch installation management method for Windows services according to claim 1, characterized in that: The downloading of the target Windows service file and the target service dependency file to the local of the service management device through the installation management program includes: Receiving Windows service information input by a user in an interactive interface of the installation management program; Based on the Windows service information, searching for a download resource of the Windows service information from at least one recommended address source; Generating key information of the download resource in the interactive interface of the installation management program; Receive a user's selection of the download resource, and download the target Windows service file and the target service dependency file corresponding to the download resource to the local service management device.

6. The batch installation management method for Windows services according to claim 1, characterized in that: The step of sending the target Windows service files and the target service dependent files in batches to the Windows system devices selected in the list for installation includes: Receive a user's selection of the Windows system device on which the target Windows service file and the target service dependent file need to be installed in the list; Obtaining the communication address of each of the Windows system devices selected in the list; Obtaining Windows system version information of each of the Windows system devices; Based on each of the Windows system version information, obtain the target Windows service file and the target service dependency file corresponding to each of the Windows system devices; For each of the Windows system devices with the same Windows system version, synchronously sending the target Windows service file and the target service dependency file; For each of the Windows system devices of different Windows system versions, the target Windows service file and the target service dependency file are sent asynchronously.

7. The batch installation management method for Windows services according to claim 1, characterized in that: Generating a list of batch Windows system devices in the interactive interface of the installation management program includes: Obtain device information of each of the Windows system devices; Using the unique device identifier in the device information as the identity identifier of the Windows system device; Preliminarily arranging each of the Windows system devices into a preset list based on the identity identifier; The Windows system devices are grouped in the list based on the system versions of the Windows system devices.

8. A batch installation management system for Windows services, characterized in that: The batch installation management system of Windows services includes: A program construction module, used to construct an installation management program for Windows services, wherein the installation management program has Windows service download, Windows service dependency association and Windows service installation functions; A program installation module, used to install the installation management program into the service management device; A communication establishment module, used to establish a communication connection between the service management device and batch Windows system devices; A list generation module, used to generate a list of the Windows system devices in batches in the interactive interface of the installation management program; A file download module, used to download the target Windows service file and the target service dependency file to the local of the service management device through the installation management program; The file installation module is used to send the target Windows service files and the target service dependent files in batches to the Windows system devices selected in the list for installation.

9. A batch installation management device for Windows services, characterized in that: The batch installation management device for Windows services comprises: a memory and at least one processor, the memory stores instructions, and the memory and the at least one processor are interconnected via a line; The at least one processor calls the instruction in the memory to enable the batch installation management device of Windows services to execute the batch installation management method of Windows services according to any one of claims 1 to 7.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the batch installation management method for Windows services according to any one of claims 1 to 7 is implemented.

Images