A domain control-based device activation method, system and readable storage medium

Abstract

The application discloses a device activation method and system based on a domain control and a readable storage medium, relates to the technical field of batch activation of applications, and aims to solve the problem that existing batch activation services cannot finely control the activation of terminal devices. The device activation method based on the domain control comprises the following steps: a user logs in a terminal device through a domain account and a password, a domain management client arranged in the terminal device pushes a login request to a domain control platform server arranged in a first server, the domain control platform server pushes a domain account login notification to a batch activation server of a second server after successfully verifying the login request, the batch activation server updates the association between the terminal device and the domain account after successfully verifying the domain account login notification, and pushes a script creation task notification to the domain control platform server; the domain control platform server creates a script and pushes the script to the domain management client; and the domain management client executes the script to complete the activation of the terminal device.

Description

Technical Field

[0001] This invention relates to the field of batch activation technology, and in particular to a domain controller-based device activation method, system, and readable storage medium. Background Technology

[0002] Modern operating systems and commercial software typically use activation control to manage their functionality. Common activation methods include serial number activation, activation file activation, online activation, and batch activation tools.

[0003] Serial number activation, also known as activation code, requires users to manually enter the serial number, which poses a risk of the serial number being copied and spread, resulting in poor security.

[0004] Activation via activation file is similar to activation via serial number; users must manually import the activation file, which also carries the risk of being copied and distributed, making it difficult to control.

[0005] Online activation requires prior account registration. Activation is automatic after logging in. This option is not suitable for locations that cannot connect to a wide area network or require a high level of network security.

[0006] Batch activation tools are services that provide batch activation. Devices connected to a specific network can take turns using serial numbers imported from the server. This activation method requires deploying a batch activation service (Key Management Service, KMS) and importing a batch of serial numbers into the batch activation tool at once. Devices / software to be activated only need to enter the KMS's IP address, port number, and password to log in to the batch activation service and complete automatic activation. Compared to serial number activation and activation file activation, batch activation tools have the following advantages: 1. They avoid users touching serial numbers that can be directly used for activation, enhancing data security; 2. Batch activation services can be deployed on public or local area networks depending on the user scenario, making them more widely applicable than online activation; 3. For large-scale activation needs, there is no need to manually enter different activation codes or import different activation files for each device, greatly simplifying the activation process and improving the user experience; 4. Serial numbers are recyclable and shareable. Devices only consume the service's serial number when connected to KMS. When a device disconnects from KMS, the server reclaims the serial number for use by other devices.

[0007] For bulk activation servers, all devices connected via IP port and correct password are treated the same. However, some organizations need to implement more granular control over the activation of terminal devices at different levels and departments. For example, companies with high confidentiality requirements may only allow activation of certain terminal devices. In such cases, traditional bulk activation services obviously cannot meet the needs.

[0008] In summary, existing bulk activation services have the problem of not being able to finely control the activation of terminal devices. Summary of the Invention

[0009] Therefore, the present invention provides a domain-controlled device activation method, system, and readable storage medium in an attempt to solve or at least alleviate at least one of the problems mentioned above.

[0010] According to one aspect of the present invention, a domain-based device activation method applicable to a domain controller platform server is provided, comprising: responding to receiving a login request pushed by a domain management client, verifying the domain account and password carried in the login request, and after successful verification, pushing a domain account login notification to a batch activation server, so that the batch activation server verifies the batch activation server address and password carried in the domain account login notification, and after successful verification and when there is remaining quota for domain account activation, pushing a script creation task notification to the domain controller platform server; and responding to receiving the script creation task notification pushed by the batch activation server, creating a script according to the script creation task notification, and pushing the created script to the domain management client corresponding to the script, wherein the domain management client is deployed on a terminal device, so that the domain management client executes the script to complete the activation of the terminal device.

[0011] Optionally, in the domain-based device activation method according to the present invention, the method further includes: in response to receiving the domain entry request pushed by the domain management client, pushing a domain entry event notification to the batch activation server, so that the batch activation server adds a new terminal device hardware information record in the database.

[0012] Optionally, in the domain controller-based device activation method according to the present invention, the step of creating a script according to the script creation task notification includes: creating an activation script according to the batch activation server address, the password, and the domain identification code of the terminal device carried in the script creation task notification.

[0013] According to another aspect of the present invention, a domain controller-based device activation method suitable for batch activation servers is provided, comprising: in response to receiving a domain account login notification pushed by a domain controller platform server, verifying the batch activation server address and password carried in the domain account login notification, and updating the association between the terminal device and the domain account after successful verification; and when there is a remaining quota for the number of domain account activations, pushing a script creation task notification to the domain controller platform server, so that the domain controller platform server creates a script and pushes the script to the domain management client corresponding to the script, the domain management client being deployed on the terminal device, so that the domain management client executes the script to complete the activation of the terminal device.

[0014] Optionally, in the domain-based device activation method according to the present invention, in response to a change in the address and / or password of the batch activation server, the changed address and / or password of the batch activation server is pushed to the domain management client.

[0015] Optionally, in the domain-based device activation method according to the present invention, in response to receiving an activation request pushed by the domain management client, the batch activation server address and password carried in the activation request are verified; and after successful verification, a serial number is returned to the domain management client, and the serial number is bound to the hardware information of the terminal device.

[0016] Optionally, in the domain controller-based device activation method according to the present invention, the method further includes: in response to receiving an entry event notification pushed by the domain controller platform server, adding a terminal device hardware information record to the database.

[0017] Optionally, in the domain controller-based device activation method according to the present invention, the method further includes: in response to the administrator's operation to activate a specified device, pushing a script creation task notification to the domain controller platform server, so that the domain controller platform server creates a script according to the script creation task notification, and pushes the created script to the domain management client of the specified device, so that the domain management client executes the script to complete the activation of the specified device.

[0018] According to another aspect of the present invention, a domain controller-based device activation system is also provided, comprising: a domain management client and a batch activation client deployed on a terminal device, a domain controller platform server deployed on a first server, and a batch activation server deployed on a second server; the domain management client is adapted to send a login request to the domain controller platform server and execute a script sent by the domain controller platform server, so that the batch activation client deployed on the same terminal device as the domain management client connects to the batch activation server and completes activation; the domain controller platform server is adapted to verify the legality of the domain account login information sent by the domain management client, push a domain account login event notification to the batch activation server, create a script according to the script creation task notification sent by the batch activation server, and distribute the created script to the corresponding domain management client; the batch activation server is adapted to verify the batch activation server address and password carried in the domain account login event notification, update the association between the terminal device and the domain account after successful verification, and push a script creation task notification to the domain controller platform server when there is a remaining quota for the domain account activation.

[0019] According to another aspect of the present invention, a readable storage medium storing program instructions is also provided, which, when read and executed by a computing device, causes the computing device to perform the domain controller-based device activation method applicable to a domain controller platform server or the domain controller-based device activation method applicable to a batch activation server, as described above.

[0020] The device activation method, system, and readable storage medium based on domain controller according to the present invention can achieve at least one of the following beneficial effects: Based on the batch distribution of serial numbers in traditional KMS batch activation schemes, the device management capabilities of the domain controller platform are added. Terminal devices are added to the domain through the domain controller platform, and the domain account and password of the requesting terminal device are verified, achieving finer-grained control over terminal device activation, making it more secure and reliable. Automatic activation triggered by domain account login and activation of designated devices are both implemented through script distribution, so users are unaware of the existence of the KMS service. Even if the batch activation server modifies the IP address and connection password, it does not affect the activation of the terminal device, shielding the impact of the batch activation server connection configuration on the terminal device, simplifying the user's operation process, and increasing the usability and reliability of the above method and system. Attached Figure Description

[0021] To achieve the foregoing and related objectives, certain illustrative aspects are described herein in conjunction with the following description and accompanying drawings. These aspects indicate various ways in which the principles disclosed herein may be practiced, and all aspects and their equivalents are intended to fall within the scope of the claimed subject matter. The foregoing and other objectives, features, and advantages of this disclosure will become more apparent from the following detailed description, taken in conjunction with the accompanying drawings. Throughout this disclosure, the same reference numerals generally refer to the same parts or elements.

[0022] Figure 1 A schematic diagram of a domain controller-based device activation system 100 according to an embodiment of the present invention is shown;

[0023] Figure 2 This diagram illustrates the data synchronization principle between a domain controller platform server and a batch activation server according to an embodiment of the present invention.

[0024] Figure 3 A schematic diagram of a computing device 300 according to an embodiment of the present invention is shown;

[0025] Figure 4 A flowchart of a domain controller-based device activation method 400 according to an embodiment of the present invention is shown;

[0026] Figure 5 A flowchart of a domain controller-based device activation method 500 according to an embodiment of the present invention is shown;

[0027] Figure 6 A schematic diagram illustrating the principles of method 400 and method 500 according to an embodiment of the present invention is shown;

[0028] Figure 7 A flowchart illustrating the reactivation request according to an embodiment of the present invention is shown. Detailed Implementation

[0029] Exemplary embodiments of the present disclosure will now be described in more detail with reference to the accompanying drawings. While exemplary embodiments of the present disclosure are shown in the drawings, it should be understood that the present disclosure may be implemented in various forms and should not be 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 scope of the disclosure to those skilled in the art.

[0030] To address the issue that existing batch activation services cannot achieve activation control only for devices that meet specific conditions, a domain controller-based device activation method, system, and readable storage medium are provided.

[0031] Figure 1 A schematic diagram of a domain controller-based device activation system 100 according to an embodiment of the present invention is shown.

[0032] like Figure 1As shown, the domain controller-based device activation system 100 includes a domain management client 111 and a batch activation client 112 deployed in a terminal device 110, a domain controller platform server 121 deployed in a first server 120, and a batch activation server 131 deployed in a second server 130. Domain management client 111 is adapted to send login requests to domain control platform server 121 and execute scripts sent by domain control platform server 121, enabling batch activation client 121, which is deployed on the same terminal device as domain management client 111, to connect to batch activation server 131 and complete activation. Domain control platform server 121 is adapted to verify the legitimacy of domain account login information sent by domain management client 111, push domain account login event notifications to batch activation server 131, create scripts according to script creation task notifications sent by batch activation server 131, and distribute the created scripts to the corresponding domain management client 111. Batch activation server 131 is adapted to verify the batch activation server address and password carried in the domain account login event notification, update the terminal device-domain account association after successful verification, and push script creation task notifications to domain control platform server 121 when there are remaining quotas for domain account activation. The first server 120 and the second server 130 can be two servers or a single server. When the first server 120 and the second server 130 are two servers, they synchronize information via an HTTP POST interface. The batch activation server 131 and the batch activation client 112 communicate via TLS-encrypted TCP packets.

[0033] System 100 adds the following activation access checks to the traditional KMS batch activation: 1. Whether the terminal device has joined the domain; 2. Whether the domain account used by the terminal device has exhausted its allocated activation codes. These checks enable more granular control over terminal devices.

[0034] This embodiment adds a KMS domain management module to the conventional batch activation server 131 program for interfacing with the domain controller platform server 121. The domain account information and terminal device information of the batch activation server 131 and the domain controller platform server 121 are synchronized. If the data on the domain controller platform server 121 changes, the changed data is synchronized to the batch activation server 131. For example... Figure 2As shown, data synchronization includes, but is not limited to, events such as: deactivating a domain account, deleting a domain account, deleting a terminal / leaving the domain, deactivating a terminal, and enabling a terminal. For deactivating and deleting domain accounts, the batch activation server 131 needs to set the serial number quota of the deactivated or deleted domain account to 0, meaning there are no available serial numbers under the deactivated or deleted domain account. For deleting / leaving the domain and deactivating a terminal, the batch activation server 131 needs to record the hardware information of the deleted terminal, the terminal that left the domain, and the deactivated terminal. For enabling a terminal, the batch activation server 131 needs to add the hardware information record of the enabled terminal device.

[0035] The administrator creates the organizational structure and domain accounts in the domain control platform according to actual needs, imports a batch of serial numbers into the platform, and assigns these serial numbers to various domain accounts, with each domain account containing several serial numbers. Taking an enterprise as an example, the organizational structure includes different levels and departments, and each department contains several terminal devices. A domain account can be assigned to each department, and the number of serial numbers assigned to each domain account is determined based on the number of terminal devices in each department.

[0036] In one embodiment, a user can also apply for domain entry on terminal device 110. The user issues a domain entry request on terminal device 110; the domain management client 111 pushes the domain entry request to the domain controller platform server 121, and the domain entry request carries the hardware device information of terminal device 110 (such as motherboard serial number, hard drive serial number, etc.); the domain controller platform server 121 pushes a domain entry event notification to the batch activation server 131, and the domain entry event notification carries the aforementioned hardware device information; the batch activation server 131 adds the aforementioned hardware device information to the domain management hardware information record, completing the domain entry of terminal device 110.

[0037] After terminal device 110 joins the domain, the bulk activation server 131 automatically returns the IP address and password of the second server 130 to terminal device 110. The user enters their domain username and password on the terminal device. The domain management client 111 generates a login request based on the domain username and password, as well as the IP address and password of the second server 130, and pushes the login request to the domain control platform server 121. The domain control platform server 121 verifies the validity of the domain username and password. Upon successful verification, it pushes a domain username login event notification to the bulk activation server 131. The bulk activation server 131 updates the association between the terminal device and the domain account in the database. The specific update method is as follows: the domain username login event notification carries the domain username and password of terminal device 110. The association between hardware information and domain account is updated. After the update, it checks whether there is a free serial number for the domain account. If there is a free serial number, it assigns a free serial number to the terminal device 110 and pushes a script creation task notification to the domain controller platform server 121. The script creation task notification carries the above serial number information. The domain controller platform server 121 creates a script according to the script creation task notification. The function of the script is to connect the batch activation client 112 to the batch activation server 131 and complete the activation. Then, it calls the application programming interface (API) of the domain controller platform server 121 to send the script content to the domain management client 111. The domain management client 111 executes the script and completes the activation.

[0038] In one embodiment, when a terminal device 110 is in an activated state, if the IP address and / or password of the batch activation server 131 change, the batch activation server 131 will automatically send the changed IP address and / or password to the domain management client 111 through the domain control platform server 121. The domain management client 111 will then send the information to the batch activation client 112, and the batch activation client 112 will re-initiate an activation request to the batch activation server 131 based on the new IP address and password.

[0039] In one embodiment, the batch activation server 131 is embedded with a domain management module. The domain management module interface displays a list of online terminal devices. Administrators can issue activation scripts to selected terminal devices on this interface to activate the specified devices.

[0040] It should be noted that the present invention does not limit the specific types of terminal device 110, first server 120, and second server 130. For example, the first server 120 and second server 130 can be implemented as computing devices such as desktop computers, laptops, processor chips, mobile phones, and tablet computers.

[0041] In one embodiment, the terminal device 110, the first server 120, and the second server 130 of the present invention can be implemented as a computing device, enabling the domain controller-based device activation method of the present invention to be executed in the computing device. The computing device can be any device with storage and computing capabilities, such as a server, workstation, or a personal computer like a desktop computer or laptop computer, or a terminal device like a mobile phone, tablet computer, smart wearable device, or IoT device, but is not limited thereto.

[0042] Figure 3 A schematic diagram of a computing device 300 according to an embodiment of the present invention is shown. It should be noted that... Figure 3 The computing device 300 shown is merely an example. In practice, the computing device used to implement the domain controller-based device activation method of the present invention can be any type of device, and its hardware configuration can be similar to... Figure 3 The computing device 300 shown is the same as, and can also be with Figure 3 The computing device 300 shown is different. In practice, the computing device used to implement the domain-controller-based device activation method of the present invention can... Figure 3 The hardware components of the computing device 300 shown can be added or removed. This invention does not limit the specific hardware configuration of the computing device.

[0043] It should be noted that the domain controller-based device activation method of the present invention requires multiple computing devices 300 to implement together, and each computing device 300 is responsible for implementing a part of the domain controller-based device activation method of the present invention.

[0044] like Figure 3 As shown, computing device 300 typically includes memory 310 and processor 320, which communicate via bus 330. Depending on the desired configuration, processor 320 can be any type of processor, including but not limited to: microprocessor (μP), microcontroller (μC), digital information processor (DSP), or any combination thereof. Depending on the desired configuration, memory 310 can be any type of memory, including but not limited to: volatile memory (such as RAM), non-volatile memory (such as ROM, flash memory, etc.), or any combination thereof. Memory 310 may include operating system 311, program instructions 312 executing a domain controller-based device activation method, and program data 313. Program data 313 may include files for recording the association between terminal devices and domain accounts, and terminal device hardware information recording files.

[0045] The computing device 300 can be implemented as a server, such as a file server, database server, application server, and web server, or as a personal computer with configurations including desktop and laptop computers. Of course, the computing device 300 can also be implemented as part of a small, portable (or mobile) electronic device.

[0046] According to an embodiment of the present invention, a device activation method 400 based on a domain controller is applicable to a domain controller platform server. The method 400 includes: in response to receiving a login request pushed by a domain management client, verifying the domain account and password carried in the login request, and after successful verification, pushing a domain account login notification to a batch activation server, so that the batch activation server verifies the batch activation server address and password carried in the domain account login notification, and after successful verification and when there is a remaining quota for domain account activation, pushing a script creation task notification to the domain controller platform server; and in response to receiving the script creation task notification pushed by the batch activation server, creating a script according to the script creation task notification, and pushing the created script to the domain management client corresponding to the script, wherein the domain management client is deployed on the terminal device, so that the domain management client executes the script to complete the activation of the terminal device.

[0047] Figure 4 A flowchart of a domain controller-based device activation method 400 according to an embodiment of the present invention is shown. Method 400 is executed in a computing device (e.g., the aforementioned computing device 300) and is used for fine-grained control over the activation of terminal devices. Figure 4 As shown, method 400 begins with 410.

[0048] In 410, in response to receiving a login request pushed by the domain management client 111, the domain account and password carried in the login request are verified, and after successful verification, a domain account login notification is pushed to the batch activation server 131, so that the batch activation server 131 verifies the batch activation server address and password carried in the domain account login notification, and after successful verification and when there is a remaining quota for the number of domain account activations, a script creation task notification is pushed to the domain control platform server 121.

[0049] Users log in on terminal device 110 using their domain username and password. Domain management client 111, deployed on terminal device 110, pushes a login request to domain control platform server 121, deployed on the first server 120. Domain control platform server 121 verifies the domain username and password carried in the login request and, upon successful verification, pushes a domain username login notification to batch activation server 131. Batch activation server 131 verifies the batch activation server address and password carried in the domain username login notification and, upon successful verification and if there are remaining domain username activation quotas, pushes a script creation task notification to domain control platform server 121.

[0050] Next, in step 420, after receiving the script creation task notification pushed by the batch activation server 131, the domain control platform server 121 creates a script according to the script creation task notification. For example, it can create an activation script according to the address and password of the batch activation server and the domain identification code of the terminal device carried in the script creation task notification. Then, the created script is pushed to the domain management client 111 corresponding to the script. The domain management client 111 executes the script to complete the activation of the terminal device.

[0051] Domain management client 111 can also push domain entry requests to domain control platform server 121. After receiving the domain entry request, domain control platform server 121 pushes a domain entry event notification to batch activation server 131. After receiving the domain entry event notification, batch activation server 131 adds a record of terminal device hardware information in the database, thus completing the domain entry of terminal device 110.

[0052] According to an embodiment of the present invention, a device activation method 500 based on a domain controller is applicable to a batch activation server 131, comprising: responding to receiving a domain account login notification pushed by a domain controller platform server 121, verifying the batch activation server address and password carried in the domain account login notification, and updating the association between the terminal device 110 and the domain account after successful verification; and pushing a script creation task notification to the domain controller platform server 121 when there is a remaining quota for domain account activation, so that the domain controller platform server 121 creates a script and pushes the script to the domain management client 111 corresponding to the script, the domain management client 111 is deployed on the terminal device 110, so that the domain management client 111 executes the script to complete the activation of the terminal device 110.

[0053] Figure 5 A flowchart of a domain controller-based device activation method 500 according to an embodiment of the present invention is shown. Method 500 is executed in a computing device (e.g., the aforementioned computing device 300) and is used for fine-grained control over the activation of terminal devices. Figure 5 As shown, method 500 begins with 510.

[0054] In 510, in response to receiving a domain account login notification pushed by the domain controller platform server 121, the system verifies the batch activation server address and password carried in the domain account login notification, and updates the association between the terminal device 110 and the domain account after successful verification.

[0055] A user logs in on terminal device 110 using a domain username and password. Domain management client 111, deployed on terminal device 110, pushes a login request to domain control platform server 121, deployed on the first server 120. Domain control platform server 121 verifies the domain username and password carried in the login request and, upon successful verification, pushes a domain username login notification to batch activation server 131. Batch activation server 131 verifies the batch activation server address and password carried in the domain username login notification and, upon successful verification, updates the association between terminal device 110 and the domain username in the database.

[0056] Next, in step 520, when there is a remaining quota for domain account activation, a script creation task notification is pushed to the domain controller platform server 121, so that the domain controller platform server 121 creates a script and pushes the script to the corresponding domain management client 111. The domain management client 111 is deployed on the terminal device 110, so that the domain management client 111 executes the script and completes the activation of the terminal device 110.

[0057] First, determine if there are any remaining domain account activation slots. If so, push a script creation task notification to the domain controller platform server 121. After receiving the script creation task notification, the domain controller platform server 121 starts creating the script and then pushes the created script to the corresponding domain management client 111. The domain management client 111 executes the script to complete the activation of the terminal device 110.

[0058] Based on methods 400 and 500, embodiments of this application provide a complete schematic diagram of the principle of a domain controller-based device activation method, such as... Figure 6 As shown.

[0059] Users log in on terminal device 110 using their domain username and password, and the domain management client 111 pushes a login request to the domain controller platform server 121. Terminal devices 111 that have already joined the domain are called domain-connected devices, and only domain-connected devices that send the correct IP address and password to the bulk activation server 131 can be activated.

[0060] In one embodiment, the administrator allocates a certain number of activation codes (i.e., domain account activation code quota) to each domain account on the bulk activation server 131. Users can apply to join the domain on terminal device 110. After a user submits a domain joining request on terminal device 110, the domain management client 111 pushes the domain joining request to the domain controller platform server 121. The domain joining request carries the hardware device information of the requesting terminal device 110. The domain controller platform server 121 generates a digest using SHA based on the aforementioned hardware device information and uses the generated digest as the domain ID of the requesting terminal device 110. Next, the domain controller platform server 121 pushes a domain joining event notification to the bulk activation server 131. The domain joining notification carries the hardware device information and domain ID of the requesting terminal device 110. After receiving the domain joining event notification, the bulk activation server 131 adds the domain ID and hardware device information record of the requesting terminal device 110 to the file recording domain device hardware information in the database.

[0061] Devices within the domain can log in to the domain control platform using their domain username and password. When a user enters their domain username and password on their device and initiates a login, the domain management client 111 generates a login request based on the domain username, password, bulk activation server IP address, and password, and pushes the login request to the domain control platform server 121. The domain username and password information carried in the login request are the same as those entered by the user. The IP address and password of the bulk activation server 131 carried in the login request are automatically fed back to the terminal device 110 by the bulk activation server 131 after the terminal device 110 joins the domain and are stored on the terminal device 110. The user cannot access these IP address and password information.

[0062] Upon receiving a login request from the domain management client 111, the domain controller platform server 121 verifies the domain account and password carried in the login request. If the verification is successful, it sends a domain account login notification to the batch activation server 131. The domain account login notification is generated by the domain controller platform server 121 based on the domain account, the IP address and password of the batch activation server 131, and the hardware device information of the terminal device 110.

[0063] After receiving the domain account login notification pushed by the domain controller platform server 121, the batch activation server 131 verifies the IP address and password of the batch activation server 131 carried in the domain account login notification. After successful verification, it updates the association between the terminal device and the domain account. When the remaining quota of the domain account activation quantity is greater than 0 (that is, the number of activation codes in use under the domain account is less than the activation code quota of the domain account), it pushes a script creation task notification to the domain controller platform server 121.

[0064] If the IP address and password carried in the domain account login notification are correct, the batch activation server 131 updates the file recording the association between terminal devices and domain accounts. The update method is as follows: based on the hardware device information of terminal device 110 and the domain account carried in the domain account login notification, the hardware device information is added to the domain account to establish the association between the hardware device information and the domain account. Simultaneously, the association between the hardware device information and other domain accounts is removed. Then, the remaining activation quota of the domain account associated with the aforementioned terminal device 110 hardware device information is queried. Each domain account is pre-allocated a certain number of activation codes. Activation codes are recyclable and shareable. Each time terminal device 110 connects to the batch activation server 131, it consumes one activation code. The consumed activation code is in use. When terminal device 110 logs out of the batch activation server 131, the activation code is reclaimed. The remaining activation quota of a domain account refers to the number of activation codes that are not in use. A remaining activation quota of a domain account greater than 0 indicates that a usable activation code can be allocated to a domain device logged in using that domain account. The script creation task notification includes the activation code assigned to the currently logged-in terminal device 110, the IP address and password of the batch activation server 131, and the terminal device ID.

[0065] Upon receiving the script creation task notification pushed by the batch activation server 131, the domain controller platform server 121 creates the script according to the script creation task notification and pushes the created script to the corresponding domain management client 111. The function of the script is to point the activation address of the terminal device 110 to the KMS service, thereby triggering the activation request and automatically completing the activation.

[0066] After receiving the script pushed by the domain controller platform server 121, the domain management client 111 executes the script. After the script is executed, the batch activation client 112 of the terminal device 110 connects to the batch activation server 131 and completes the activation. The activation of the terminal device 110 is thus completed.

[0067] Methods 400 and 500 add domain entry verification to the traditional KMS batch activation. Specifically, they verify whether the currently logged-in terminal device 110 has joined a domain. Even if the IP address, port, and password of the batch activation server 131 are leaked, activation cannot be completed if the device hosting the batch activation client 112 is not joined to a domain. This enhances the security of the KMS service and provides more granular control over terminal device activation. Furthermore, methods 400 and 500 simplify the activation process. Users no longer need to worry about the IP address and password of the batch activation server 131; they only need to enter their domain username and password to automatically connect to the batch activation server and achieve automatic activation. Changes to the IP address and password of the batch activation server 131 do not affect the user's normal use of terminal device 110.

[0068] For an already activated terminal device 110, if the IP address of the batch activation server 131 changes (for example, the second server 130 is migrated from one device to another), or the password changes, the existing KMS batch activation scheme requires the user to manually modify the IP address and password on the terminal device 110 and re-initiate the activation request. This is not only cumbersome, but also poses a risk of IP address and password leakage. This embodiment of the application, however, uses an automatic activation request initiation method to avoid manual operation by the user, and also avoids the leakage of IP address and password.

[0069] In one embodiment, the method for automatically initiating an activation request includes the following process: After the IP address and / or password of the batch activation server 131 changes, the batch activation server 131 pushes the changed batch activation server address IP and / or password to the domain management client 111, and the domain management client 111 initiates an activation request to the batch activation server 131 according to the new IP address and password; Figure 7 As shown, the activation request is sent to the batch activation server 131 in the form of a connection password. The batch activation server 131 verifies the IP address and password in the connection password. After successful verification, the batch activation client 112 sends the hardware device information of the terminal device 110 to the batch activation server 131. The batch activation server 131 allocates a free serial number to the terminal device 110, binds the serial number to the hardware device information of the terminal device 110, and feeds back the serial number information to the batch activation client 112. It should be noted that although the terminal device 110 receives the serial number information, and the serial number information corresponds one-to-one with the serial number, the serial number information cannot be used directly, so there is no risk of it being copied and leaked. Next, The operating system of terminal device 110 verifies the serial number and sends a verification status to the batch activation server 131. If the verification status is successful, the batch activation server 131 sends activation confirmation information to the batch activation client 112. Subsequently, the batch activation client 112 periodically sends heartbeat packets to the batch activation server 131. If the batch activation server 131 does not receive a heartbeat packet from a terminal device 110 for an extended period, it considers the connection between the terminal device 110 and the batch activation server 131 to be broken. When the batch activation server 131 actively deactivates the serial number or detects that the connection between the batch activation client 112 and the batch activation server 131 is broken, it releases the binding relationship between the serial number and the terminal device 110 and reclaims the serial number. When the batch activation server 131 actively deactivates the serial number, the batch activation client 112 is forced to disconnect from the batch activation server 131. Afterward, the batch activation client 112 sends activation requests to the batch activation server 131 at fixed time intervals.

[0070] In one embodiment, methods 400 and 500 also support administrators to activate designated terminal devices 110. The administrator selects terminal device 110 and initiates the activation operation on the interface of the domain management module embedded in the batch activation server 131. The batch activation server 131 will push a script creation task notification to the domain controller platform server 121 for the selected terminal device 110.

[0071] The various techniques described herein can be implemented in combination with hardware or software, or a combination thereof. Thus, the methods and apparatus of the present invention, or certain aspects or portions thereof, can take the form of program code (i.e., instructions) embedded in a tangible medium, such as a removable hard disk, USB flash drive, floppy disk, CD-ROM, or any other machine-readable storage medium, wherein when the program is loaded into and executed by a machine such as a computer, the machine becomes an apparatus for practicing the present invention.

[0072] When the program code is executed on a programmable computer, the computing device generally includes a processor, a processor-readable storage medium (including volatile and non-volatile memory and / or storage elements), at least one input device, and at least one output device. The memory is configured to store program code; the processor is configured to execute the domain-controlled device activation method of the present invention according to instructions in the program code stored in the memory.

[0073] By way of example, and not limitation, readable media include readable storage media and communication media. Readable storage media stores information such as computer-readable instructions, data structures, program modules, or other data. Communication media generally embodies computer-readable instructions, data structures, program modules, or other data in the form of modulated data signals such as carrier waves or other transmission mechanisms, and includes any information delivery medium. Any combination of the above is also included within the scope of readable media.

[0074] In the specification provided herein, the algorithms and displays are not inherently related to any particular computer, virtual system, or other device. Various general-purpose systems can also be used with the examples of this invention. The required structure for constructing such systems is apparent from the above description. Furthermore, this invention is not directed to any particular programming language. It should be understood that the contents of the invention described herein can be implemented using various programming languages, and the above description of specific languages ​​is for the purpose of disclosing preferred embodiments of the invention.

[0075] Numerous specific details are set forth in the specification provided herein. However, it will be understood that embodiments of the invention may be practiced without these specific details. In some instances, well-known methods, structures, and techniques have not been shown in detail so as not to obscure the understanding of this specification.

[0076] Similarly, it should be understood that, in order to simplify this disclosure and aid in understanding one or more aspects of the invention, various features of the invention are sometimes grouped together in a single embodiment, figure, or description thereof in the above description of exemplary embodiments of the invention. However, this method of disclosure should not be construed as reflecting an intention that the claimed invention requires more features than are expressly recited in each claim. Those skilled in the art will understand that modules, units, or components of the devices in the examples disclosed herein can be arranged in the devices described in this embodiment, or alternatively, can be located in one or more devices different from the devices in this example. The modules in the foregoing examples can be combined into a single module or further divided into multiple sub-modules.

[0077] Those skilled in the art will understand that modules in the device of the embodiments can be adaptively changed and placed in one or more devices different from that embodiment. Modules, units, or components in the embodiments can be combined into a single module, unit, or component, and further, they can be divided into multiple sub-modules, sub-units, or sub-components. Except where at least some of such features and / or processes or units are mutually exclusive, any combination can be used to combine all features disclosed in this specification (including the accompanying claims, abstract, and drawings) and all processes or units of any method or device so disclosed. Unless expressly stated otherwise, each feature disclosed in this specification (including the accompanying claims, abstract, and drawings) may be replaced by an alternative feature that serves the same, equivalent, or similar purpose.

[0078] Furthermore, those skilled in the art will understand that although some embodiments described herein include certain features included in other embodiments but not others, combinations of features from different embodiments are meant to be within the scope of the invention and form different embodiments. Additionally, some of the embodiments described herein are described as methods or combinations of method elements that can be implemented by a processor of a computer system or by other means of performing the functions. Therefore, a processor having the necessary instructions for implementing the method or method elements forms means for implementing the method or method elements. Furthermore, the elements described herein in the device embodiments are examples of means for implementing the functions performed by elements for the purposes of carrying out the invention.

[0079] As used herein, unless otherwise specified, the use of ordinal numbers such as “first,” “second,” “third,” etc., to describe ordinary objects merely indicates different instances of similar objects and is not intended to imply that the objects being described must have a given order in time, space, ordering, or any other manner.

[0080] Although the invention has been described with respect to a limited number of embodiments, those skilled in the art will understand from the foregoing description that other embodiments are conceivable within the scope of the invention described herein. Furthermore, it should be noted that the language used in this specification has been chosen primarily for readability and edibility purposes, and not for the purpose of explaining or limiting the subject matter of the invention.

Claims

1. A device activation method based on a domain controller, applicable to a domain controller platform server, comprising: In response to receiving a login request pushed by the domain management client, the domain account and password carried in the login request are verified, and after successful verification, a domain account login notification is pushed to the batch activation server, so that the batch activation server verifies the batch activation server address and password carried in the domain account login notification. After successful verification and when there is a remaining quota for domain account activation, the batch activation server pushes a script creation task notification to the domain control platform server. as well as In response to receiving the script creation task notification pushed by the batch activation server, a script is created according to the script creation task notification, and the created script is pushed to the domain management client corresponding to the script. The domain management client is deployed on the terminal device so that the domain management client executes the script to complete the activation of the terminal device.

2. The domain controller-based device activation method as described in claim 1 further includes: In response to receiving the domain entry request pushed by the domain management client, a domain entry event notification is pushed to the batch activation server so that the batch activation server adds a new record of terminal device hardware information in the database.

3. The domain controller-based device activation method as described in claim 1 or 2, wherein, The step of creating a script based on the script creation task notification includes: An activation script is created based on the batch activation server address, the password, and the domain identification code of the terminal device carried in the script creation task notification.

4. A device activation method based on a domain controller, suitable for batch activation of server-side applications, comprising: In response to receiving a domain account login notification pushed by the domain control platform server, the system verifies the batch activation server address and password carried in the domain account login notification, and updates the association between the terminal device and the domain account after successful verification. as well as When there is remaining quota for activating domain accounts, a script creation task notification is pushed to the domain controller platform server, so that the domain controller platform server creates a script and pushes the script to the domain management client corresponding to the script. The domain management client is deployed on the terminal device, so that the domain management client executes the script to complete the activation of the terminal device.

5. The domain controller-based device activation method as described in claim 4 further includes: In response to a change in the address and / or password of the bulk activation server, the changed address and / or password of the bulk activation server are pushed to the domain management client.

6. The domain controller-based device activation method as described in claim 4 or 5, further comprising: In response to receiving the activation request pushed by the domain management client, the batch activation server address and password carried in the activation request are verified. as well as After successful verification, a serial number is returned to the domain management client, and the serial number is bound to the hardware information of the terminal device.

7. The domain controller-based device activation method as described in claim 4 or 5, further comprising: In response to receiving the domain entry event notification pushed by the domain control platform server, a new record of terminal device hardware information is added to the database.

8. The domain controller-based device activation method as described in claim 4 or 5, further comprising: In response to the administrator's activation of a specified device, a script creation task notification is pushed to the domain controller platform server. The domain controller platform server then creates a script based on the script creation task notification and pushes the created script to the domain management client of the specified device. The domain management client then executes the script to complete the activation of the specified device.

9. A domain controller-based device activation system, comprising a domain management client and a batch activation client deployed on terminal devices, a domain controller platform server deployed on a first server, and a batch activation server deployed on a second server; The domain management client is adapted to send a login request to the domain control platform server and execute the script sent by the domain control platform server, so that the batch activation client deployed on the same terminal device as the domain management client can connect to the batch activation server and complete the activation. The domain control platform server is adapted to verify the legitimacy of the domain account login information sent by the domain management client, push domain account login event notifications to the batch activation server, create scripts according to the script creation task notification sent by the batch activation server, and distribute the created scripts to the corresponding domain management clients. The batch activation server is adapted to verify the batch activation server address and password carried in the domain account login event notification, and update the association between the terminal device and the domain account after successful verification, and push a creation script task notification to the domain control platform server when there is a remaining quota for the domain account activation.

10. A readable storage medium storing program instructions, which, when read and executed by a computing device, cause the computing device to perform a domain-controller-based device activation method as claimed in any one of claims 1-3 or any one of claims 4-8.

Images