A method for making a cloud desktop software installation package based on user session

Abstract

The present invention discloses a method for producing a cloud desktop software installation package based on a user session. Through the Windows file filtering driver and the registry driver, after the administrator runs the software installation package process, the file release and registry modification process of the software installation package are recorded, the proprietary data operations under the user session are distinguished, and the files and registry entries are redirected, and the circulating data generated by the software is redirected to generate a green software package. The green software package can be directly imported into the same version of Windows system on other computers through a specified tool, without the need to repeatedly run the software installation package. The present invention mainly solves the problem that users need to install the same software multiple times on different computers in a converged virtual desktop environment.

Description

Technical Field

[0001] The present invention relates to the technical field of virtualization, and in particular to a method for producing a cloud desktop software installation package based on user sessions. Background Art

[0002] In a physical machine environment, users typically install software by downloading the installation package and running the installer directly. However, in a virtualized application environment, after virtual desktop deployment is complete, some desktops may require new software installation. In this case, because end users may have different software requirements, system administrators cannot perform a unified upgrade by simply upgrading the master disk image. To install software, desktop users must download the installation package and then install it. This process can lead to inconsistent software package versions, inconsistent sources, and inconsistent installation settings, increasing administrator workload and increasing system security risks. Some software also cannot be silently installed via remote commands, preventing administrators from performing a unified remote installation. This is caused by software installation package creation tools. Summary of the Invention

[0003] In order to overcome the above-mentioned problems existing in the existing software installation process, the present invention uses Windows file filtering driver and registry driver to realize that after the administrator runs the software installation package process, the file release and registry modification process of the software installation package are recorded, and the proprietary data operations under the user session are distinguished. (A session is composed of all processes and system objects representing a single user login session. The objects include all windows, desktops and windowsstations. It can be understood as a memory space unique to the currently logged-in user. The current user's application processes, objects, and windows are all in this memory space. The session spaces of different users are isolated), and the files and registry entries are redirected. The floating data generated by the software is redirected to generate a green software package. The green software package can be directly imported into the same version of Windows system on other computers through a specified tool, without the need to repeatedly run the software installation package. At the same time, the present invention also solves the problem that users need to install the same software multiple times on different computers in a converged virtual desktop environment.

[0004] To achieve the above objectives, the present invention provides the following technical solution: a method for creating a cloud desktop software installation package based on a user session, which is specifically implemented according to the following steps:

[0005] Step 1. The administrator prepares the software installation package to be installed;

[0006] Step 2. The administrator runs the production program;

[0007] Step 3. The production end program will release the file filter driver file and the registry driver file, create a service, and load the file filter driver and the registry driver. The file filter driver and the registry driver will register kernel function callbacks to monitor the system's file and registry operations.

[0008] Step 4. Start the software installation package installation program that needs to be run through the production end program. The production end program will send the software installation package process ID and current user session to the file driver and registry driver. After receiving the software installation package process ID and user session, the file driver and registry driver will perform process ID and user session judgment when filtering file and registry behavior. The current process ID or parent process ID will be judged to contain the software installation package process ID. If the installation package process ID and user session are included, it is considered that the current operation needs to be redirected.

[0009] Step 5. The administrator installs the software according to the prompts in the software installation package and makes the required software installation settings during the installation process;

[0010] Step 6. After the software installation is complete, select End Installation on the production client. The production client will then convert the redirected registry entries and export them to reg format, making them easier to modify and load on the import client. Once the export is complete, the green software installation package is complete.

[0011] Preferably, in step 3, the Windows file filter driver is mounted on the Windows file system device stack, and the file operation behavior during the installation process is obtained through the Windows file driver callback port, user session distinction is performed, and redirection operation is performed. The Windows registry driver obtains the registry operation behavior during the installation process through the registry callback, user session distinction is performed, and redirection operation is performed.

[0012] Preferably, the software installation package in step 5 includes two parts: a software green package production end and a software green package import end. The green package production end is an application running in a Windows environment. The application releases and starts a Windows file filter driver and a Windows registry driver. The installation package is started through the program, and the installation package process information is sent to the file driver and the registry driver. At the same time, the user session of the current installation behavior is sent to the driver, and the redirected registry redirection file is converted into an importable batch file. The generated file and the registry redirection file are made into a software green package.

[0013] The green package importer is an application running in a Windows environment. The application modifies the file directory and registry of the software green package according to the local user session information. After the modification is completed, the software green package files and registry are imported into the local system to automatically complete the software installation.

[0014] Windows file filter driver: The Windows file filter driver is mounted on the Windows file system device stack. It obtains file operation behaviors during the installation process through the Windows file driver callback port, distinguishes user sessions, and performs redirection operations.

[0015] Windows registry driver: The Windows registry driver obtains registry operation behaviors during the installation process through registry callback, distinguishes user sessions, and performs redirection operations.

[0016] Green Package Creator: This is an application running in the Windows environment that releases and activates the Windows file filter driver and the Windows registry driver. This application initiates the installation package and sends installation process information to the file and registry drivers. It also sends the user session of the current installation to the drivers and converts the redirected registry redirection file into an importable batch file. The generated file and registry redirection file are then created as a software green package.

[0017] Green package importer: The green package importer is an application running in the Windows environment. This application modifies the file directory and registry of the software green package based on the local user session information. After the modification is completed, the software green package files and registry are imported into the local system to automatically complete the software installation.

[0018] Compared with the prior art, the present invention has the following beneficial effects:

[0019] The present invention implements file redirection, registry redirection, process ID and user session determination, file import, and registry import operations in the Windows operating system. Through these operations, the green software installation package can be green-installed in the same version of the Windows operating system, eliminating the need for administrators to perform separate installation operations for multiple virtual desktops. Instead, unified deployment can be performed through remote commands, ensuring uniformity and security of software installation. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] Figure 1 Create a flow chart for the green package of the software of the present invention;

[0021] Figure 2 This is a flowchart for importing the green package of the software of the present invention. DETAILED DESCRIPTION

[0022] The following will clearly and completely describe the technical solutions of the present invention in the embodiments of the present invention in conjunction with the drawings of the present invention in the embodiments of the present invention. Obviously, the embodiments described are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of the present invention.

[0023] The present invention provides a method for preparing a cloud desktop software installation package based on a user session, which is specifically implemented according to the following steps:

[0024] Step 1. The administrator prepares the software installation package to be installed;

[0025] Step 2. The administrator runs the production program;

[0026] Step 3. The production end program will release the file filter driver file and the registry driver file, create a service, and load the file filter driver and the registry driver. The file filter driver and the registry driver will register kernel function callbacks to monitor the system's file and registry operations.

[0027] Step 4. Start the software installation package installation program that needs to be run through the production end program. The production end program will send the software installation package process ID and current user session to the file driver and registry driver. After receiving the software installation package process ID and user session, the file driver and registry driver will perform process ID and user session judgment when filtering file and registry behavior. The current process ID or parent process ID will be judged to contain the software installation package process ID. If the installation package process ID and user session are included, it is considered that the current operation needs to be redirected.

[0028] Step 5. The administrator installs the software according to the prompts in the software installation package and makes the required software installation settings during the installation process;

[0029] Step 6. After the software installation is complete, select End Installation on the production client. The production client will then convert the redirected registry entries and export them to reg format, making them easier to modify and load on the import client. Once the export is complete, the green software installation package is complete.

[0030] Furthermore, in step 3, the Windows file filter driver is mounted on the Windows file system device stack, and the file operation behavior during the installation process is obtained through the Windows file driver callback port, user session distinction is performed, and redirection operation is performed. The Windows registry driver obtains the registry operation behavior during the installation process through the registry callback, user session distinction is performed, and redirection operation is performed.

[0031] Furthermore, the software installation package in step 5 includes two parts: a software green package production end and a software green package import end. The green package production end is an application running in a Windows environment. The application releases and starts a Windows file filter driver and a Windows registry driver. The installation package is started through the program, and the installation package process information is sent to the file driver and the registry driver. At the same time, the user session of the current installation behavior is sent to the driver, and the redirected registry redirection file is converted into an importable batch file. The generated file and the registry redirection file are made into a software green package.

[0032] The green package import end is an application running in the Windows environment. The application modifies the file directory and registry of the software green package according to the local user session information. After the modification is completed, the software green package file and registry are imported into the local system to automatically complete the software installation.

[0033] The software green package import process is as follows:

[0034] A. The administrator sends the green installation package of the software to be imported to the virtual desktop where it needs to be installed.

[0035] B. The administrator runs the import end through remote commands and passes the location of the software green package to the import end program.

[0036] C. The importer imports the green package files by copying them. If files with the same path and name exist, the newer version will be used. If a file path is a user path, the current user path will be obtained and replaced with the user path in the green package. For example, if the green package user path is C:\Users\test1 and the current user name is test2, the green package user path will be replaced with C:\Users\test2.

[0037] D. The import-side program imports the registry of the software green package using the reg file import method. If there are registry entries with the same path, an overwrite operation will be performed, and the key value of the software green package will prevail. Before importing, the user name of the reg file will be traversed. If the session ID is different, the current session ID will prevail. The key value of the user path contained in the reg file will be replaced with the current user path. For example, if the user path in the software green package is C:\Users\test1 and the current user name is test2, the user path in the reg file of the software green package will be replaced with C:\Users\test2.

[0038] E. While traversing the reg file path, check whether any new services are created. If new services are created, the user will be prompted to restart to complete the software import.

[0039] F. After the file import and registry import are completed, the user is prompted that the software import is complete. The software can be used normally after logging out or restarting.

[0040] While embodiments of the present invention have been shown and described, it will be appreciated by those skilled in the art that various changes, modifications, substitutions, and variations may be made to these embodiments without departing from the principles and spirit of the invention, and that the scope of the invention is defined by the appended claims and their equivalents.

Claims

1. A method for making a cloud desktop software installation package based on user session, characterized in that: Please follow the steps below to implement: Step 1. The administrator prepares the software installation package to be installed; Step 2. The administrator runs the production program; Step 3. The production end program will release the file filter driver file and the registry driver file, create a service, and load the file filter driver and the registry driver. The file filter driver and the registry driver will register kernel function callbacks to monitor the system's file operations and registry operations. Step 4. Start the software installation package installation program that needs to be run through the production end program. The production end program will send the software installation package process ID and current user session to the file driver and registry driver. After receiving the software installation package process ID and user session, the file driver and registry driver will judge the process ID and user session when filtering file and registry behaviors. Check whether the current process ID or parent process ID contains the software installation package process ID. If the installation package process ID and user session are included, it is considered that the current operation needs to be redirected. Step 5. The administrator installs the software according to the prompts in the software installation package and makes the required software installation settings during the installation process; Step 6. After the software installation is complete, select End Installation on the production end. At this time, the production end will convert the redirected registry entries into reg format, making it easier for the import end to modify and load them. After the export is complete, the green production of the software installation package is completed. In step 3, the Windows file filter driver is mounted on the Windows file system device stack, and the file operation behavior during the installation process is obtained through the Windows file driver callback port, user session distinction is performed, and redirection operation is performed. The Windows registry driver obtains the registry operation behavior during the installation process through the registry callback, user session distinction is performed, and redirection operation is performed.

2. A method for making a cloud desktop software installation package based on user session according to claim 1, characterized in that: The software installation package in step 5 includes two parts: a software green package production end and a software green package import end. The green package production end is an application running in the Windows environment. The application releases and starts the Windows file filter driver and the Windows registry driver. The installation package is started through the program, and the installation package process information is sent to the file driver and the registry driver. At the same time, the user session where the current installation behavior is located is sent to the driver, and the redirected registry redirection file is converted into an importable batch file, and the generated file and the registry redirection file are made into a software green package.

3. A method for making a cloud desktop software installation package based on user session according to claim 2, characterized in that: The green package import end is an application running in the Windows environment. The application modifies the file directory and registry of the software green package according to the local user session information. After the modification is completed, the software green package file and registry are imported into the local system to automatically complete the software installation.

Images