WO2019119850A1

WO2019119850A1 - Application software deployment method and device, and virtual machine

Info

Publication number: WO2019119850A1
Application number: PCT/CN2018/102285
Authority: WO
Inventors: 于涛; 秦延涛; 侯春华; 陆剑峰; 吴小明
Original assignee: 中兴通讯股份有限公司
Priority date: 2017-12-21
Filing date: 2018-08-24
Publication date: 2019-06-27
Also published as: CN107992355B; CN107992355A

Abstract

An application software deployment method and device, and a virtual machine. The application software deployment method comprises: mounting a target disk in a read-write manner, intercepting a file operation and a registry operation by means of a file system filter driver, redirecting an actual installation path of an application to a partition of the target disk, and saving a registry operation record of the application by means of a registry file created on the target disk (S110); and mounting, in a read-only manner, the target disk carrying an application installation file and the registry operation record, and intercepting an access operation on the application by means of the file system filter driver and carrying out redirection processing (S120). The application deployment process can be simplified and the deployment efficiency is improved.

Description

Method, device and virtual machine for deploying application software

Technical field

The present invention relates to the field of computer technologies, and in particular, to a method, an apparatus, and a virtual machine for deploying application software.

Background technique

Virtual Desktop Infrastructure (VDI) has been widely used. Instead of configuring a desktop PC running Windows operating system for each user, VDI creates a Windows desktop image for each user. Different users can get a unified experience using a unified Windows desktop image. Through the network, you can quickly deploy a common desktop environment. A single server can support many virtual desktops and deliver the desktop operating system to end users through various protocols.

But the desktop is not the purpose, the end user needs the application on the desktop (Application, referred to as APP). In related art, an administrator embeds necessary software in the template when creating an operating system template. The virtual machine user installs the necessary software while installing the operating system template. However, this method binds the application to the operating system, and after the operating system template is distributed to each virtual machine, it is very inconvenient for each user to maintain the upgrade application by himself.

Summary of the invention

The invention provides a method, a device and a virtual machine for deploying application software, which are used for streamlining an application deployment process and improving deployment efficiency.

The embodiment of the invention provides a method for deploying application software, including:

Mounting the target disk in read-write mode, intercepting file operations and registry operations through the file system filter driver, redirecting the actual installation path of the application to the partition of the target disk, and creating on the target disk The registry file saves the registry operation record of the application;

The target disk hosting the application installation file and the registry operation record is mounted in a read-only mode, and the access operation of the application is intercepted and redirected by the file system filtering driver.

The embodiment of the invention further provides an apparatus for deploying application software, including:

The disk package template creation module is configured to mount the target disk in a read-write manner, and the file system filter driver intercepts the file operation and the registry operation, and redirects the actual installation path of the application to the partition of the target disk, and Saving the registry operation record of the application by using a registry file created on the target disk;

The disk package template uses a module that is configured to mount a target disk that hosts the application installation files and registry operation records in a read-only manner, and intercepts and redirects access operations to the application through the file system filter driver.

The embodiment of the invention further provides a virtual machine, including:

a memory, a processor, and a program for deploying application software stored on the processor and operable on the processor, the step of implementing the method of deploying the application software when the program deploying the application software is executed by the processor .

The embodiment of the present invention further provides a computer readable storage medium, wherein the computer readable storage medium stores a program for deploying application software, where the program for deploying the application software is executed by the processor to implement the deployment application software. The steps of the method.

Compared with the related art, the embodiment of the present invention provides a method, an apparatus, and a virtual machine for deploying application software, and a disk package template is generated by uniformly installing (updating) all applications on an independent disk, and the virtual machine is read-only. Mount the target disk (the independent disk where the disk package template is located) that carries the application installation file and the registry operation record. The file system filter driver intercepts the access operation of the application and performs redirection processing. The application does not actually need to be one by one. Installed on a virtual machine, it only shows through redirection that it has been installed, so it can achieve a second-level deployment installation, which can streamline the application deployment process and improve deployment efficiency.

DRAWINGS

The drawings described herein are intended to provide a further understanding of the invention, and are intended to be a part of the invention. In the drawing:

1 is a flowchart of a method for deploying application software according to Embodiment 1 of the present invention;

2 is a schematic diagram of an apparatus for deploying application software according to Embodiment 2 of the present invention;

3 is a schematic diagram of a virtual desktop infrastructure in Example 1 of the present invention.

Detailed ways

The embodiments of the present invention will be described in detail below with reference to the accompanying drawings. It should be noted that, in the case of no conflict, the features in the embodiments and the embodiments in the present application may be arbitrarily combined with each other.

Example 1

As shown in FIG. 1 , an embodiment of the present invention provides a method for deploying application software, including:

Step S110, mounting the target disk in a read-write manner, and intercepting the file operation and the registry operation by the file system filtering driver, redirecting the actual installation path of the application to the partition of the target disk, and passing the target disk The registry file created on the saves the registry operation record of the application;

In step S120, the target disk carrying the application installation file and the registry operation record is mounted in a read-only mode, and the access operation of the application is intercepted and redirected by the file system filtering driver.

The method also includes the following features:

In one embodiment, when the target disk is mounted in a read-write manner, the target disk is allocated to the virtual machine for use alone; when the target disk carrying the application installation file and the registry operation record is mounted in a read-only manner, The target disk is allocated to one or more virtual machines for common use;

In an embodiment, the target disk is a mobile hard disk;

In an embodiment, after the target disk is mounted in a read-write manner, the method further includes:

Sending a notification message to the file system filter driver through the auxiliary tool before installing or updating the application, triggering the file system filter driver to work in the disk package template creation mode;

After all the applications are installed or updated, the auxiliary tool sends a notification message to the file system filter driver, triggering the file system filter driver to exit the disk package template creation mode and enter the idle mode;

In an embodiment, the method further includes:

After all the applications are installed or updated, the application installation information is collected by the auxiliary tool, and the application installation information is saved in the configuration file created on the target disk;

In an embodiment, after the target disk carrying the application installation file and the registry operation record is mounted in a read-only manner, the method further includes:

Sending a notification message to the file system filter driver through the auxiliary tool, triggering the file system filter driver to work in the disk package template usage mode;

In an implementation manner, the file system filtering driver intercepts an access operation to the application and performs a redirection process, including:

Reading the registry operation record saved on the partition of the target disk, and copying it to the registry backup file created in the system cache;

When the file system filter driver intercepts the registry operation, the operation is redirected to the registry record in the registry backup file created in the system cache;

When the file system filter driver intercepts to write the file generated by the application during the installation process, copy the original file saved on the target disk to the system cache, and redirect the write operation to the The corresponding file in the system cache;

When the file system filter driver intercepts the read operation of the file generated by the application during the installation process, if a corresponding file exists in the system cache, the corresponding file in the system cache is read, if the system caches If the corresponding file does not exist, the corresponding file on the target disk is read;

Example 2

As shown in FIG. 2, an embodiment of the present invention provides an apparatus for deploying application software, including:

The disk package template creation module 201 is configured to mount the target disk in a read-write manner, and the file system filtering driver intercepts the file operation and the registry operation, and redirects the actual installation path of the application to the partition of the target disk. And saving the registry operation record of the application by using a registry file created on the target disk;

The disk package template uses module 202, which is configured to mount the target disk carrying the application installation file and the registry operation record in a read-only manner, and intercept the access operation to the application through the file system filtering driver and perform redirection processing.

In one embodiment, the disk package template uses a module that is configured to intercept and redirect access to the application through the file system filtering driver in the following manner:

When the file system filter driver intercepts the registry operation, the operation is redirected to the registry record in the registry backup file created in the system cache.

When the file system filter driver intercepts to write the file generated by the application during the installation process, copy the original file saved on the target disk to the system cache, and redirect the write operation to the The corresponding file in the system cache.

When the file system filter driver intercepts the read operation of the file generated by the application during the installation process, if a corresponding file exists in the system cache, the corresponding file in the system cache is read, if the system caches If the corresponding file does not exist, a read operation is performed on the corresponding file on the target disk.

In one embodiment, when the target disk is mounted in a read-write manner, the target disk is allocated to the virtual machine for use alone; when the target disk carrying the application installation file and the registry operation record is mounted in a read-only manner, The target disk is allocated for use by one or more virtual machines.

Example 3

The embodiment of the invention provides a virtual machine, including:

a memory, a processor, and a program for deploying application software stored on the memory and operable on the processor, the program deploying the application software being executed by the processor to implement the method described in Embodiment 1 above Steps to deploy the application's approach.

Example 4

An embodiment of the present invention provides a computer readable storage medium, where the program for deploying application software is stored on a computer readable storage medium, and the program for deploying the application software is executed by the processor to implement the method described in Embodiment 1 above. Steps to deploy the application's approach.

The method of deploying application software of the present application is illustrated by a plurality of examples below.

Example 1

As shown in FIG. 3, the example provides a virtual desktop infrastructure VDI system, which includes at least a virtual machine resource pool and a virtual desktop management platform.

The virtual machine resource pool is a logical entity composed of multiple physical machines in the data center. Running the virtualization layer application hypervisor on each physical machine, the hypervisor is an intermediate software layer running between the physical server and the operating system, allowing multiple operating systems and applications to share a set of basic physical hardware, virtualizing hardware through Hypervisor , generating multiple CPUs (Central Processing Units), GPUs (Graphics Processing Units), disks, buses, and the like.

The virtual machine operating system template is an operating system that can be directly started and run on virtual hardware (no need to install), such as windowsXP, windows7, and so on. One of the advantages of VDI is the rapid allocation of new virtual machines based on operating system templates. The operating system template here is based on the operating system installed by the virtual hardware and is saved in the file on the physical machine. When you create a new virtual machine, by specifying an allocation template, the new virtual machine gets a template-based copy of the operating system that can be started directly. In this example, the file system filter driver is pre-installed in the operating system template. The file system filter driver runs in the background of the operating system after being installed in the operating system (windows operating system) template, and executes different processing logic through three modes (idle mode, production mode, and operation mode). In idle mode, the file filter driver neither intercepts file system calls nor modifies the received path. In production mode, the template machine's file filter driver is used to make disk package templates. For example, intercept messages and registry messages sent to the file system layer. During the installation of the application, the files with the original path in the first path (the default installation path of the application) are automatically redirected to the second path (the application installation path of the partition where the disk package template is located). The record in the original path in the third path (the default registry save path) is automatically redirected to the fourth path (the registry save path of the partition where the disk package template is located). In the running mode, the user machine mounts the disk package template in read-only mode. The priority of the file read/write or registry record read/write path is as follows: the path of the system cache is higher than the path of the partition where the disk package template is located. Priority, the path of the partition where the disk package template is located has a higher priority than the application's default installation path (or default registry save path).

The disk package template is used to store new files, modify files, new registry records, and registry record modification information involved in the application installation process (installed by the administrator on the production machine). After the disk package template is created, the assignment is assigned to the virtual machine. Unlike the operating system template, no copy is generated, but multiple virtual machines are mounted in a read-only manner.

System cache (optional), when the user machine mounts the disk package template in read-only mode, when the data in the disk package template needs to be modified, the file system filter driver copies a copy of the data into the system cache, and then Then perform read and write operations.

The virtual desktop management platform includes a virtual desktop management center and a virtual desktop background control entity. The virtual desktop management center provides a human-computer interaction management page, including viewing, creating, assigning, modifying, and updating operations. When making a disk package template, the virtual desktop management center controls the virtual desktop background control entity to create a new independent disk, and then assigns the independent disk to a virtual machine. The virtual machine role is changed to the production machine and then enters the operating system. Package production.

Example 2

This example provides a method for creating a disk package template. Assume that APP1 and APP2 are installed on a disk package template. The template machine performs the following processing:

Step S101: Install a virtual machine operating system template on a virtual machine that creates a disk package template and start it.

The operating system template includes a file system filtering driver.

The operating system template further includes an auxiliary tool, wherein the auxiliary tool is configured to communicate with the file system filter driver, and set a mode of the file filter driver (idle mode, production mode, and operation mode)

Step S102, performing partition formatting on the mounted disk.

For example, formatted as NTFS (New Technology File System), set the disk drive letter to F:.

In step S103, the auxiliary tool runs to create a root directory FILE (F:\FILE) on the mounted disk partition (for example, F:), and the root directory is used to redirect the application's default installation directory (for example, C: \). Create a registry file (for example, reg) that records the modified key value of the registry record during the installation process. Create a configuration file (for example, vpack.ini).

The configuration file vpack.ini may contain information describing each application in the disk package template, such as a version number, a GUID (Globally Unique Identifier).

The auxiliary tool sends a control message to the file system filter driver, triggering the file system filter driver to enter a production mode, in which the file system filter driver intercepts all the default installation directory (C:\) in the application. File system call.

In step S104, two applications APP1 and APP2 are installed.

The functions, file operations, and registry operations executed by the installer are intercepted by the file system filter driver. After interception, the query merges the directory operation and the target path is modified to be redirected.

The following uses the APP1 installer (app1_install) as an example to explain the interception and redirection of file operations:

(1) The installer (app1_install) initiates a read-only query to the underlying path, path c:\program files\app1;

The file system filter driver performs 2 query actions. The first path is c:\program files\app1, and the second path is F:\FILE\program files\app1. At this point, neither path exists and immediately returns a failure.

(2) The installer (app1_install) initiates the create directory operation of the write mode, and the creation path is c:\program files\app1.

The file system filter driver still performs 2 queries after receiving it. The first path is c:\program files\app1, and the second path is F:\FILE\program files\app1. At this time, it is a write mode operation. And the parent directory c:\program files of the first path exists. The file system filter driver first creates the directory F:\FILE\program files, and then changes the execution path to the second path F:\FILE\program files\app1. The actual creation work is handed to the lower layer of the file system. After the lower layer is created, the handle is returned, and the redirection is completed. After returning, app1_install receives the redirected second path handle.

(3) The installer app1_install initiates the create file operation, and the file to be created is c:\program files\app1\file1.

The installer app1_install queries the path c:\program files\app1. The file system filter driver receives 2 queries after receiving it. The first path is c:\program files\app1, and the second path is F:\FILE\program files\app1. At this time, it is a write mode operation. And F:\FILE\program files\app1 exists, and the second path F:\FILE\program files\app1 is preferred. The file system filter driver then executes the path modification F:\FILE\program files\app1\file1, and the actual work is given to the lower layer of the file system for execution. After the lower layer execution returns, app1_install receives the redirected second path handle. The redirection creation file is completed.

(4) The installer app1_install initiates enumeration of the specified directory file operation, and the specified directory is c:\program files.

The installer app1_install opens the directory c:\program files. The file system filter driver sequentially queries the first path c:\program files, and the second path F:\FILE\program files. Since the second path already exists, according to the priority principle, the path is modified to the second path F:\FILE\program files, and the lower layer of the file system returns the second path handle, and the redirection is completed. Next app1_install initiates the enumeration directory file. The file system filter driver receives the path to the handle path F:\FILE\program files that was just opened. At this point, the enumeration directory operation is performed twice.

First c:\program files\return

Second F:\FILE\program files\return

2017/07/11 10:35 <DIR> app1

The two results are merged. If there is the same item, the file information under the F: path is used first.

Finally return:

The app1_install program gets a list of merged files.

The following uses the APP1 installer (app1_install) as an example to explain the interception and redirection of registry information:

When the auxiliary tool triggers the file system filter driver to enter the production mode, the registry file (F:\reg) on the partition where the disk package template is located is mounted by the file system filter driver to the system registry path HLM\SYSTEM\Setup\VPACK. At the beginning, the content is empty. This path (HLM\SYSTEM\Setup\VPACK) corresponds to the default root path of the registry (C:\).

(1) The installer (for example, app1_install) initiates a read-only query with the path HCU\Software.

The file system filter driver performs 2 query actions. The first path is HCU\Software, and the second path is HLM\SYSTEM\Setup\VPACK\HCU\Software. At this point, neither path exists and immediately returns a failure.

(2) The installer (for example, app1_install) initiates the creation of the write mode. Create a path of HCU\Software\app1.

The file system filter driver still performs 2 queries after receiving it.

The first path HCU\Software\app1;

The second path is HLM\SYSTEM\Setup\VPACK\HCU\Software\app1;

At this time, it is a write mode operation. And the parent path HCU\Software\ of the first path exists. The file system filter driver creates the path entry HLM\SYSTEM\Setup\VPACK\HCU\Software\ at this time. Then modify the execution path to the second path HLM\SYSTEM\Setup\VPACK\HCU\Software\app1. After the system is executed, the second path handle is returned. After returning, app1_install receives the redirected second path handle. The redirect is complete.

(3) The installer app1_install initiates the creation of a key value and operates on HCU\Software\app1\key1.

First open the path HCU\Software\app1. At this time, it is a write mode operation. HLM\SYSTEM\Setup\VPACK\HCU\Software\app1 exists. The path HLM\SYSTEM\Setup\VPACK\HCU\Software\app1 is preferred. After the path is modified, the actual creation work is submitted to the lower layer of the system for execution. After the lower layer execution returns, app1_install receives the redirected path handle. The redirection is created.

(4) The installer app1_install initiates the enumeration of the specified path sub-record operation.

First app1_install opens the registry key HCU\Software\. File system filter driver query in turn

The first path HCU\Software\;

The second path is HLM\SYSTEM\Setup\VPACK\HCU\Software\;

Since the second path already exists, according to the priority principle, the path is modified to the second path HLM\SYSTEM\Setup\VPACK\HCU\Software, and the lower layer of the file system returns the second path handle, and the redirection is completed. Next app1_install initiates an enumeration child record. The file system filter driver receives the path to the handle path that was just opened.

HLM\SYSTEM\Setup\VPACK\HCU\Software\

At this point, the enumeration operation is performed twice.

First HCU\Software\Back

7zip

Adobe

Second HLM\SYSTEM\Setup\VPACK\HCU\Software\Back

App1

Combine the two results, if there is the same item, use the second path first.

Information under HLM\SYSTEM\Setup\VPACK\HCU\Software\.

Finally return:

7zip

Adobe

App1

The installer app1_install got the merged list.

In step S105, after all the applications are installed, the auxiliary tool runs, and the auxiliary operations after the installation is completed are performed.

The auxiliary tool sends a message to the file system filter driver to notify the application that the installation is completed, the file system filter driver detaches the node previously mounted on the registry branch, and the registry modification content is written to the disk partition where the disk package template is located. In the table file (F:\reg), then the file system filter driver enters the idle state.

The auxiliary tool can also clean up unnecessary files (such as temporary files) in the disk partition where the disk package template is located, scan the registry file (F:\reg) to get the path of the installed application, extract the icon of the application, version number, Vendor information, etc., is reported to the virtual desktop management platform for storage. At this point, the disk package template is created. The template machine can unmount the disk where the disk package template is located.

Example 3

This example provides a method for using a disk package template. Assume that the application package APP1 and APP2 are installed on the disk package template. The user machine uses an application (for example, APP1) by mounting the disk where the disk package template is located. The user machine performs the following processing:

Step S101, identifying a disk package template;

When the operating system starts, the disk package template mount message is intercepted by the file system filter driver, scans the partition volume, and looks for configuration files (for example, vpack.ini), FILE folder, and registry files (for example, reg). By analyzing the contents of the configuration file, the contents of the registry file determine whether it is a disk package template. If it is a disk package template, the file system filter driver triggers into run mode.

Step S102, the file content of the registry file (F:\reg) is merged into the system cache registry file (for example, G:\REG) in a read-only manner, and an empty file is created if there is no such file in the system cache. . If the system cache registry file has been merged according to a version number and GUID match, then this step is ignored. The merge record is also recorded in the system cache registry file (G:\REG). Then mount the system cache registry file (G:\REG) to the system registry HLM\SYSTEM\Setup\VPACK\ path. Then start intercepting file system messages and registry messages.

The following describes the file system and file directory related operations in the file system filter driver.

(1) The user clicks on the start menu.

For example, the windows desktop program explorer.exe initiates an enumeration directory query. Directory path C:\ProgramData\Microsoft\Windows\Start Menu\Programs. The file system filter driver performs 3 query actions.

The first path C:\ProgramData\Microsoft\Windows\Start Menu\Programs returns:

The second path F:\FILE\ProgramData\Microsoft\Windows\Start Menu\Programs returns:

2017/07/03 16:30 <DIR> app1

2017/07/03 15:52 <DIR> app2

The third path G:\FILE\ProgramData\Microsoft\Windows\Start Menu\Programs returns null; where G:\FILE\ is the system cache path;

At this point 2 paths exist and the results are merged into:

The explorer.exe program gets a list of merged files. Users can find out more app1 and app2 program menus.

(B) The user mouse clicks app1/app1.exe to start the program.

The windows desktop program explorer.exe initiates a read-only mode to open the app1.exe file flow. The file system filter driver performs 3 query actions. The first path is C:\Program files\app1. The second path is F:\FILE\Program files\app1. The third path G:\FILE\Program files\app1;

The second path already exists, and the path is used preferentially. The file system filter driver modifies the path to this path. The actual work is performed by the lower layer of the file system, and the path handle is returned after the lower layer is executed. Explorer.exe gets the redirected handle and starts the subsequent operations.

(3) app1.exe program to modify C:\Program files\app1\file1

The file system filter driver performs 3 query actions.

The first path is C:\Program files\app1\file1. The return failure does not exist.

The second path is F:\FILE\Program files\app1\file1. The return succeeds.

The third path is G:\FILE\Program files\app1\file1. The return failure does not exist.

The second path already exists, but since it is a modification action, it cannot be directly modified. Copy the file file1 to the system cache directory. First create the directory G:\FILE\Program files, G:\FILE\Program files\app1\, and then execute the copy file to G:\FILE\Program files\app1\file1. Modify the path to this path, the actual work is performed by the lower layer of the file system, and the path handle is returned after the lower layer is executed. App1.exe gets the redirected handle and starts the subsequent write operation.

(4) The app1.exe program deletes C:\Program files\app1\file1

The file system filter driver performs 3 query actions.

The second path is F:\FILE\Program files\app1\file1. The return succeeds.

The third path is G:\FILE\Program files\app1\file1. The return succeeds.

Delete one that belongs to the modification operation. Since the third path exists, the modified path is the third path, but since it is a delete operation. And the second path disk package path exists. Special handling is required. Mark this file with a delete. For example, modify the creation time of the third path file to a certain second of a specific date. Return immediately to the success without letting the underlying file system actually delete. After the file is encountered after this special date, it takes over the operation of the lower layer system and judges that it has been deleted and returns a failure.

The following describes the file system filter driver's operations on the registry in run mode.

(1) The application (for example, app1) initiates a read-only query with the path HCU\Software.

The file system filter driver performs 2 query actions.

First path HCU\Software

Second path HLM\SYSTEM\Setup\VPACK\HCU\Software

The second path exists, and is a read-only mode. The modified path is the second path. The actual work is completed by the lower layer system, and the second path handle is obtained after the return, and the redirection is completed. App1 gets the second path handle.

(2) app1 initiates the modification of the key value, the path HCU\Software\app1\key1.

The file system filter driver performs 2 query actions.

The first path HCU\Software\app1\key1 return failure does not exist;

The second path HLM\SYSTEM\Setup\VPACK\HCU\Software\app1\key1 returns successfully;

The second path exists, although it is a write operation, but since the system used caches the registry file, it can be modified directly. The modified path is the second path, and the actual work is completed by the lower layer system. After returning, the second path handle is obtained, and the redirection is completed. App1 gets the second path handle.

(3) app1 initiates the creation of a key value and operates on HCU\Software\app1\key1.

First query the path HCU\Software\app1.

The file system filter driver will perform 2 query actions.

First path HCU\Software\app1

Second path HLM\SYSTEM\Setup\VPACK\HCU\Software\app1

At this time, it is a write mode operation. And the second path exists, the second path is preferentially selected, and the path is modified to be HLM\SYSTEM\Setup\VPACK\HCU\Software\app1\key1 in the second path, and the actual creation work is performed to the lower layer of the system for execution. After the lower layer performs the return, what app1 receives is the redirected path handle. The redirection is created.

(4) app1 initiates enumeration of the specified path sub-recording operation.

App1 opens the registry key HCU\Software\.

File system filter driver query in turn

First path HCU\Software\

Second path HLM\SYSTEM\Setup\VPACK\HCU\Software\

Since the second path already exists, the path is modified to the second path according to the priority principle. The lower layer of the system returns the second path handle, and the redirection is completed. Next, enumerate the child records. The file system filter driver receives the path to the second path that was just opened. At this point, the enumeration operation is performed twice.

First HCU\Software\Back

7zip

Adobe

Second HLM\SYSTEM\Setup\VPACK\HCU\Software\Back

App1

App2

2 results merge, if there is the same item, the system cache is used first, then the disk package template, and finally the system default original path;

Finally return:

7zip

Adobe

App1

App2

Therefore, the app1 program gets a merged list.

(5) app1 deletes the specified path sub-record operation.

App1 opens the registry key HCU\Software\.

File system filter driver query in turn

First path HCU\Software\app1\key1

Second path HLM\SYSTEM\Setup\VPACK\HCU\Software\app1\key1

Since the second path already exists, the path is modified to the second path according to the priority principle. The lower layer of the system returns the second path handle, and the redirection is completed. The system then performs subsequent delete operations. Here is the system cache registry file, you can delete it directly.

Example 4

This example provides an update method for a disk package template. Suppose the administrator wants to update the disk package template including APP1 and APP2 on the template machine. The update involves: upgrading APP1, deleting APP2, and adding APP3. Perform the following processing on the template machine:

Step S101, assigning a disk package template to a virtual machine. This disk is automatically mounted by the operating system after the virtual machine is powered on. Suppose this drive letter is F:.

Step S102, installing a file system filter driver on the virtual machine that creates the disk package template. Install the accessibility tools. At this point, the file system filter driver works in idle mode, neither intercepting file system calls nor modifying the received path. If the file system filter driver has been installed on this machine, it will automatically trigger into the usage mode.

In step S103, the auxiliary tool runs. At this time, the directory FILE, the registry file reg, and the configuration file vpack.ini already exist. Accessibility tools are no longer created. The auxiliary tool sends a control message to the file system filter driver, triggering the entry into production mode. At this point, all file system calls on C: are intercepted.

In step S104, the installer starts to update app1, deletes app2, and installs app3. The functions, file operations, and registry operations executed by the installer during the installation process are intercepted by the file system filter driver, query the merge directory operation, and modify the target path to reach the redirect.

(1) Update app1:

App1's installer app1_install initiates a modification file (c:\program files\app1\file1) operation.

App1_install queries the path c:\program files\app1\file1. The file system filter driver receives 2 queries after receiving it. The first path is c:\program files\app1, and the second path is F:\FILE\program files\app1. At this time, it is a write mode operation. And F:\FILE\program files\app1 exists, and the second path F:\FILE\program files\app1 is preferred. The file system filter driver then executes the path modification F:\FILE\program files\app1\file1, and the actual work is given to the lower layer of the file system for execution. After the lower layer execution returns, app1_install receives the redirected second path handle. The redirect file is complete. Subsequent modification writes are also done on this path file.

(2) Delete app2:

App2's installer app2_install initiates the delete file (c:\program files\app2\file1) operation.

App2_install queries the path c:\program files\app2\file1. The file system filter driver receives 2 queries after receiving it. The first path is c:\program files\app2, and the second path is F:\FILE\program files\app2. At this time, it is a write mode operation. And the second path exists, and the second path is preferentially selected. The file system filter driver then changes the execution path to F:\FILE\program files\app2\file1, and the actual work is given to the lower layer of the file system for execution. After the lower layer executes the return, app2_install receives the redirected second path handle. The redirect file is complete. Subsequent deletions are also done on this path file.

(3) Install app3:

App3's installer app3_install initiates the create file (c:\program files\app3\file1) operation.

App3_install queries the path c:\program files\app3. The file system filter driver receives 2 queries after receiving it. The first path is c:\program files\app3, and the second path is F:\FILE\program files\app3. At this time, it is a write mode operation. And the second path exists, and the second path is preferentially selected. The file system filter driver then changes the execution path to F:\FILE\program files\app3\file1, and the actual work is given to the lower layer of the file system for execution. After the lower layer execution returns, app3_install receives the redirected second path handle. The redirect file is complete.

Step S104, after all the application installations are updated, the auxiliary tool runs, and the auxiliary operation after the update is completed is performed. The accessibility tool sends a message to the file system filter driver. The file system filter driver detaches the node previously mounted on the registry branch. The registry modification content is written to the F:\reg file, and then the file system filter driver enters the idle state. Subsequent operations are performed by the auxiliary tools and are processed in the disk partition F: to clean up useless files, scan the registry file reg to get the path of the installed application, extract the application's icon, version number, and vendor information. Reported to the virtual desktop management platform storage. At this point, the disk package template update is complete. The template machine can unmount this disk.

Example 5

This example provides the creation and use of a disk package on a physical mobile disk that is off the VDI system.

First, make a disk package.

1. Install the file system filter driver and auxiliary tools on the physical machine that makes the disk package. At this point, the file system filter driver works in idle mode, neither intercepting file system calls nor modifying the received path.

2. Insert the mobile hard disk, the operating system automatically mounts the hard disk, and the user formats the mounted disk (for example, NTFS, assuming that the drive letter is F:).

3. The auxiliary tool runs. Create an empty directory FILE on this partition. This directory corresponds to the C:\ root directory. Create an empty registry file reg to record the modified key value of the registry record during the installation process. Create a configuration file vpack.ini that contains information describing the package, such as the version number and the guid unique identification value. The auxiliary tool sends a control message to the file system filter driver, triggering into the production mode, and the file system filter driver intercepts all file system calls on C: in production mode.

4. Start installing app1, app2. Functions, file operations, and registry operations performed by the installer (for example, app1_install and app2_install) during the installation process are intercepted by the file system filter driver. The file system filter driver queries the merge directory operation and modifies the target path to reach the redirect.

5. End the installation of app1, app2. The accessibility tool sends a message informing the file system that the filter driver is entering idle mode. The auxiliary tool scans the F: unused files in the disc. The disk package is created.

Second, use the disk package.

1. Install the file system filter driver on a physical machine. At this point the file system filter runs in an idle state.

2. After inserting the mobile hard disk, the file system filter driver intercepts the volume mount message, scans the partition volume, and finds the configuration file (vpack.ini), FILE folder, and registry file (reg). Determine whether it is a disk package by analyzing the contents of the configuration file and the contents of the registry file. If it is a disk package, the file system filter driver triggers into the run mode.

3. The file system filter driver merges the contents of the registry file (F:\reg) on the mobile hard disk into the system cache registry file (C:\VPACK\REG) in read-only mode, if there is no such file in the system cache. Then create an empty file. If the system cache registry file has been merged according to a version number and guid match, the merge record is also recorded in the system cache registry file. Then mount the system cache registry file to the system registry path (HLM\SYSTEM\Setup\VPACK\). Then start intercepting file system messages and registry messages.

Third, update the disk package.

1. Install the file system filter driver and auxiliary tools on a physical machine. If it is already installed, you do not need to install it again. At this point the file system filter driver works in idle mode. Neither intercept file system calls nor modify received paths.

2. Insert the mobile hard disk. This disk is automatically mounted by the operating system. Suppose this drive letter is F:. The file system filter driver will automatically trigger into the usage mode.

3, the auxiliary tool runs, at this time the directory FILE, the registry file reg, the configuration file vpack.ini already exists. Accessibility tools are no longer created. Execute the setting mode to the production mode, send a control message to the file system filter driver, trigger into the production mode, and intercept all file system calls on C: in production mode.

4. Start updating app1, delete app2, and install app3. The functions, file operations, and registry operations performed by the installer during the installation process are intercepted by the file system filter driver. The file system filter driver queries the merge directory operation and modifies the target path to reach the redirect.

5. End the installation of app1, app2. The accessibility tool sends a message informing the file system that the filter driver is entering idle mode. The auxiliary tool scans the F: unused files in the disc. The disk package update is complete.

It is to be understood that the invention may be susceptible to various other modifications and changes in the embodiments of the present invention without departing from the spirit and scope of the invention. Corresponding changes and modifications are intended to be included within the scope of the appended claims.

Claims

A method of deploying application software, including:

Mounting the target disk in read-write mode, intercepting file operations and registry operations through the file system filter driver, redirecting the actual installation path of the application to the partition of the target disk, and creating on the target disk The registry file saves the registry operation record of the application;

The target disk hosting the application installation file and the registry operation record is mounted in a read-only mode, and the access operation of the application is intercepted and redirected by the file system filtering driver.
The method of claim 1 wherein

The file system filtering driver intercepts access operations of the application and performs redirection processing, including:

Reading the registry operation record saved on the partition of the target disk, and copying it to the registry backup file created in the system cache;

When the file system filter driver intercepts the registry operation, the operation is redirected to the registry record in the registry backup file created in the system cache.
The method of claim 1 wherein

The file system filtering driver intercepts access operations of the application and performs redirection processing, including:

When the file system filter driver intercepts to write the file generated by the application during the installation process, copy the original file saved on the target disk to the system cache, and redirect the write operation to the The corresponding file in the system cache.
The method of claim 3, wherein

The file system filtering driver intercepts access operations of the application and performs redirection processing, including:

When the file system filter driver intercepts the read operation of the file generated by the application during the installation process, if a corresponding file exists in the system cache, the corresponding file in the system cache is read, if the system caches If the corresponding file does not exist, a read operation is performed on the corresponding file on the target disk.
A method according to any one of claims 1 to 4, wherein

When the target disk is mounted in read/write mode, the target disk is allocated to the virtual machine for use alone;

When a target disk hosting an application installation file and a registry operation record is mounted read-only, the target disk is allocated for use by one or more virtual machines.
A device for deploying application software, comprising:

The disk package template creation module is configured to mount the target disk in a read-write manner, and the file system filter driver intercepts the file operation and the registry operation, and redirects the actual installation path of the application to the partition of the target disk, and Saving the registry operation record of the application by using a registry file created on the target disk;

The disk package template uses a module that is configured to mount a target disk that hosts the application installation files and registry operation records in a read-only manner, and intercepts and redirects access operations to the application through the file system filter driver.
The apparatus of claim 6 wherein

The disk package template uses a module that is set to intercept and redirect access to the application through the file system filter driver in the following manner:

Reading the registry operation record saved on the partition of the target disk, and copying it to the registry backup file created in the system cache;

When the file system filter driver intercepts the registry operation, the operation is redirected to the registry record in the registry backup file created in the system cache.
The apparatus of claim 6 wherein

The disk package template uses a module that is set to intercept and redirect access to the application through the file system filter driver in the following manner:

When the file system filter driver intercepts to write the file generated by the application during the installation process, copy the original file saved on the target disk to the system cache, and redirect the write operation to the The corresponding file in the system cache.
The device of claim 8 wherein

The disk package template uses a module that is set to intercept and redirect access to the application through the file system filter driver in the following manner:

When the file system filter driver intercepts the read operation of the file generated by the application during the installation process, if a corresponding file exists in the system cache, the corresponding file in the system cache is read, if the system caches If the corresponding file does not exist, a read operation is performed on the corresponding file on the target disk.
The apparatus according to any one of claims 6 to 9, wherein

When the target disk is mounted in read/write mode, the target disk is allocated to the virtual machine for use alone;

When a target disk hosting an application installation file and a registry operation record is mounted read-only, the target disk is allocated for use by one or more virtual machines.
A virtual machine that includes:

a memory, a processor, and a program for deploying application software stored on the memory and operable on the processor, the program deploying the application software being executed by the processor to implement any of claims 1-5 A step of the method of deploying an application software as described.
A computer readable storage medium, wherein the computer readable storage medium stores a program for deploying application software, and the program for deploying the application software is executed by a processor to implement any one of claims 1-5 The steps of the method of deploying the application software.