Domestic substitution-oriented Windows application and data automatic migration method and system

Abstract

The invention discloses a Windows application and data automatic migration method and system oriented to localization substitution, and the method comprises the steps: deploying a migration management platform on a target system virtual machine, and storing a universal software installation package supported by a target system; uploading the customized software installation package of the enterprise to a migration management platform, and analyzing the customized software installation package by using a dpkg tool; deploying an agent in the source Windows system to read a personalized software configuration file, and sending the personalized software configuration file to the migration management platform for analysis and replacement; deploying an agent which is packaged into a deb package in a target system so as to synchronize software composition information from a migration management platform, and silently executing an installation command of a dpkg tool to install customized software; and comparing, installing and updating the installed software in the two systems through the migration management platform, and migrating software configuration files and user data. According to the invention, the problems of low manual migration efficiency, long service interruption time and split user experience are solved.

Description

Technical Field

[0001] This invention belongs to the field of automated migration technology, and specifically relates to a method and system for automated migration of Windows applications and data for domestic substitution. Background Technology

[0002] Currently, domestic substitution often adopts a complete machine replacement model: enterprises distribute terminals pre-installed with domestic systems and basic software to users, but internal business systems (such as security desktop management and internal communications) need to be installed and configured by the users themselves, and data needs to be copied from the old equipment. Due to insufficient compatibility of the domestic ecosystem, users often face problems such as missing software dependencies, driver anomalies, and configuration failures, resulting in migration cycles of up to several weeks. Many non-technical employees develop resistance due to the complexity of the operation, further amplifying the obstacles to implementation caused by the imperfect ecosystem.

[0003] Existing domestic alternatives mainly fall into the following categories: manual migration, cloud tools, and app store software. Manual migration requires manually searching for and installing domestic alternative software one by one, while simultaneously copying user data and adjusting configuration files. It cannot be performed in batches, resulting in low efficiency, high error rates, and long downtime. Existing automatic synchronization tools (such as rsync and FreeFileSync) and cloud synchronization solutions are unusable in intranet environments and only support file-level or limited data synchronization, failing to address application adaptation and configuration migration issues. They also lack automated permission conversion mechanisms, have limited functionality, and experience long downtime. Domestic desktop operating systems come with app stores, but these app stores have incomplete software coverage and lack offline installation packages. In intranet environments, the installation and deployment of enterprise-customized software and the resolution of dependency libraries still require manual intervention. Furthermore, because intranets cannot access the internet, users cannot download the necessary software and its dependencies from the app store, making the migration process complex and difficult to scale.

[0004] Chinese patent CN108614869A discloses a method for synchronously migrating historical data across different automated system platforms. It generates a result file containing key information by identifying the source system ID, domain name, and table names. Using SQL commands such as SELECT, WHERE, INSERT, and UPDATA, it obtains sampling definition information from the old and new systems, exports it as database insertion statements, and automatically generates a data migration script. Based on a clear understanding of the start and end points of the historical data migration, it uses a pre-existing mapping relationship text between the source and destination systems to migrate all data seamlessly to the destination system. However, this invention does not address how to handle errors and anomalies during the data migration process, which may lead to data loss or inconsistency during the migration. Summary of the Invention

[0005] To address the problems existing in the prior art, this invention provides a method and system for automated migration of Windows applications and data for domestic substitution, which solves the technical problems of low efficiency, long business interruption time, and fragmented user experience caused by manual migration. It supports batch migration of Windows applications, configurations, and user data to domestic desktop operating systems in an enterprise intranet environment.

[0006] The technical solution of the present invention is as follows: On the one hand, this invention provides a method for automated migration of Windows applications and data for domestic substitution, comprising the following steps: Deploy a migration management platform on the target system virtual machine and store the common software installation packages supported by the target system in a fixed directory on the migration management platform; Upload the enterprise's customized software installation package to the designated directory of the migration management platform, and use the dpkg tool to parse the customized software installation package to extract software composition information and configuration files; Deploy an agent on the source Windows system. The agent reads the personalized software configuration files of the source Windows system using the Windows API or by reading the registry, and sends them to the migration management platform for analysis and replacement of the software configuration files. Deploy an agent packaged as a deb file on the target system. The agent synchronizes software composition information from the migration management platform and silently executes the installation commands of the dpkg tool to install the customized software based on the software composition information. The migration management platform compares, installs, and updates the software already installed on the source Windows system and the target system, and migrates the software configuration files and user data between the source Windows system and the target system.

[0007] Preferably, the migration management platform performs software configuration file analysis and replacement as follows: First, by comparing the default configuration items of the software in the source Windows system that are pre-recorded in the migration management platform with the actual configuration items received, the migration management platform identifies the personalized or custom configuration items of the source Windows system. For the personalized or custom configuration items of the source Windows system, the migration management platform uses a keyword recognition machine configuration replacement method to generate corresponding configuration information according to the specifications and requirements of the target system; The migration management platform extracts the converted and adapted configuration information and applies it to the target system during the migration process, ensuring that the software runs correctly in the domestic system according to the user's personalized needs.

[0008] Preferably, the agent deployed in the source Windows system is also used to listen for sharing requests from the target system. Upon receiving a sharing request, the agent calls the VSS of the source Windows system to create a snapshot volume for the shared disk or directory. The snapshot volume is a read-only copy. The agent points the shared disk or directory to the snapshot volume, and the target system accesses the data in the snapshot volume through the CIFS protocol.

[0009] Preferably, the migration management platform is used to compare, install, and update the software already installed on the source Windows system and the target system. Specifically: The migration management platform compares the source Windows system with the target system, including the installed software, to determine whether the source Windows system contains software that is not installed on the target system; if so, the migration management platform further determines whether the target system can match the version of the uninstalled software. If a match is found, the migration management platform generates a differentiated migration report and allows users to select migration strategies, including full coverage, incremental synchronization, or custom filtering, through a graphical interface. The platform then performs a silent installation of the software on the target system using the dpkg command chain. Otherwise, the migration management platform performs a version rollback using the dpkg command chain to achieve software version matching.

[0010] Preferably, the software configuration file migration includes general configuration migration and non-general configuration migration; The general configuration migration specifically involves: directly reading the software configuration file of a general file in the source Windows system, parsing the software configuration file into key-value pairs or structured data, extracting the software configuration items supported by the target system through regular expression matching, XPath positioning, or JSON Schema verification, and automatically generating a software configuration file compatible with domestic systems; The non-generic file configuration specifically refers to: for software configuration files that are not directly compatible, dynamic mapping is performed based on a predefined conversion rule base or logical equivalence is achieved through environment variable redirection, so as to generate software configuration files compatible with domestic systems.

[0011] Preferably, the software configuration file migration also includes environment variable synchronization, which specifically involves: extracting environment variables from the source Windows system, detecting conflicts with the target system, automatically generating an adapted environment variable script based on the target system's environment specifications, and escaping path separators and special symbols.

[0012] Preferably, the synchronized user data specifically includes: Install the Samba service on the target system via an agent, create a dedicated user without login privileges, and configure a shared directory between the target system and the source Windows system. On the source Windows system, use PowerShell to map the Samba service shared directory as a mount point. Use VSS snapshots to lock the folder on the Windows system where the user data that needs to be synchronized to the target system is located. Generate a read-only snapshot volume to ensure file consistency. Use the Robocopy command to copy the snapshot data in the snapshot volume to the mount point and record the operation log. The target system recursively modifies the owner of all user data files synchronized from the source Windows system to the target system and resets file permissions, and repairs file tags according to the target system's security policy.

[0013] Preferably, the method further includes uninstalling the Samba service of the target system, specifically: On the target system, first stop the Samba service, then use a package manager to uninstall the Samba service, and delete the files, related configuration files and dedicated users from the migration process. Finally, clean up the firewall rules to ensure that the normal operation of other services on the target system is not interfered with by the firewall rules.

[0014] On the other hand, the present invention provides a Windows application and data automated migration system for domestic substitution, including a target system and a source Windows system; The target system is used to deploy a migration management platform, with a pre-configured execution agent that automatically triggers silent installation and configuration replacement upon receiving migration instructions, provides Samba service to synchronize user data, and verifies the consistency of permissions and configuration. The source Windows system is used to deploy the agent and call VSS to achieve hot backup of user data.

[0015] In another aspect, the present invention also provides a computer-readable storage medium having a computer program stored thereon, wherein the computer program, when executed by a processor, implements the Windows application and data automated migration method for domestic substitution as described in any embodiment of the present invention.

[0016] Compared with the prior art, the present invention has the following technical effects: 1. This invention automatically collects Windows application configuration and user data (including registry, INI / XML configuration, document library, etc.) through a source-end proxy, builds a unified migration list, and automatically completes the system and software related configurations after migration.

[0017] 2. This invention addresses the issue of the inability to install or update general software due to physical isolation between enterprise intranets and official software repositories of domestic operating systems. It designs an intranet general software repository synchronization mechanism that automatically synchronizes standard components from the Internet through a secure proxy channel. It also performs dependency adaptation and silent push based on the characteristics of domestic OS versions, ensuring that intranet terminals can complete the installation of basic software without manual intervention.

[0018] 3. This invention addresses the complex dependency configuration issues that exist when enterprise-developed or customized software is adapted to domestic operating systems. By building a private software library for the enterprise and using a sandbox environment to perform dependency pre-parsing and silent installation template generation for software installation packages, it achieves "zero configuration" one-click deployment on the user side, reducing the difficulty of use for users.

[0019] 4. This invention addresses the business interruption caused by the need for several hours of downtime for data copying in traditional migration solutions by employing background incremental synchronization technology to achieve seamless data migration during user operations. Attached Figure Description

[0020] Figure 1 This is an overall flowchart of the Windows application and data automated migration method for domestic substitution described in this invention. Figure 2 This is the overall architecture diagram of the Windows application and data automated migration system for domestic substitution described in this invention. Detailed Implementation

[0021] To make the objectives, technical solutions, and advantages of the present invention clearer, the technical solutions of the present invention will be clearly and completely described below in conjunction with specific embodiments of the present application and with reference to the accompanying drawings.

[0022] Example 1 This embodiment provides a method for automated migration of Windows applications and data for domestic substitution. The method utilizes silent installation of domestic alternative software, automated configuration mapping conversion, and background incremental data synchronization technology to achieve a migration process without user intervention. System switching can be completed with only a minute-level business interruption, ensuring user continuity of work. (See also...) Figure 1 As shown, the core of the method described in this embodiment lies in: pre-building a general and customized software library applicable to the domestic target system on the migration management platform; then, the migration management platform silently pushes and installs the required software to the target system, while automatically converting and updating configuration data. Seamless migration of user data is achieved through background incremental synchronization technology, ultimately ensuring a seamless switch from the source Windows system to the domestic target system desktop, without affecting normal office work on the source Windows system. Specifically, the applicable Windows systems in this embodiment include Win7, Win10, and Win11, and the applicable domestic target systems include Kylin and UOS.

[0023] The method described in this embodiment includes the following steps: Deploy a migration management platform on the target system virtual machine. Create a fixed directory on the migration management platform and store the universal software installation packages supported by the target system as files in the fixed directory. Furthermore, the migration management platform can be deployed using a UOS / Kylin desktop virtual machine. This allows for direct installation verification on the virtual machine when parsing customized installation packages is blocked. After verification, the packages can be deleted, which is both convenient and efficient. Write scripts to periodically retrieve the latest universal software installation packages from the internet and save them to the fixed directory, enabling synchronization and updates of universal software in the fixed directory with the internet. Even in an intranet-isolated environment, the software repository can be pre-updated with a single click.

[0024] Upload the enterprise's customized software installation package to the designated directory of the migration management platform, and use the dpkg tool to parse the customized software installation package to extract software composition information and configuration files, providing data support and reference for the subsequent migration of customized software in the source Windows environment.

[0025] Specifically, the deb package uses the ar archive format and contains three core files, which can be represented as follows: debian-binary: declares the package format version (e.g., "2.0"); control.tar.gz: Stores information about software components (dependencies, software components, configuration scripts, etc.): data.tar.gz: The actual installation files (binary files, configuration files, etc.).

[0026] The specific logic flow of the dpkg tool for parsing is as follows: Dependency extraction: Resolve dependencies from the Depends field of the control file (e.g., libc6 (>= 2.34)). Configuration trigger: Execute hook scripts such as postinst (post-installation script) to complete dynamic configuration; File deployment: Extract data.tar.gz to the target system path (e.g., / usr / bin).

[0027] Deploy an agent on the source Windows system. The agent reads the personalized software configuration files of the source Windows system using the Windows API or by reading the registry, and sends them to the migration management platform for analysis and replacement of the software configuration files. Furthermore, the agent uses the Windows API or the registry to read personalized software configuration files from the source Windows system. Specifically, the agent uses the Windows API or the registry to accurately capture key information such as the software version, installation path, and environment variables of the personalized software installed on the source Windows system. It then delves into the corresponding directories to read the software configuration files.

[0028] As a preferred embodiment of this practice, the migration management platform performs software configuration file analysis and replacement as follows: First, by comparing the default configuration items of the software in the source Windows system that are pre-recorded in the migration management platform with the actual configuration items received, the migration management platform identifies the personalized or custom configuration items of the source Windows system. For the personalized or custom configuration items of the source Windows system, the migration management platform uses a keyword recognition machine configuration replacement method to generate corresponding configuration information according to the specifications and requirements of the target system; Specifically, the core implementation of the keyword recognition machine configuration replacement method can be divided into three stages: 1. Configuration item extraction and parsing: Key configurations such as registry entries and group policy settings in the source Windows system are identified through regular expressions and a syntax analyzer, and a mapping relationship library between configuration items and target system parameters is established.

[0029] 2. Rule Engine Conversion: Converts Windows-specific policy settings (such as account policies and security options) into equivalent configurations for the target system, during which compatibility verification is called to perform semantic checks.

[0030] 3. Atomic Deployment: An executable configuration script for the target system is generated using a declarative configuration language. A transaction mechanism ensures the atomicity of the configuration application, with automatic rollback in case of failure. Finally, a configuration drift detection report is generated to verify migration consistency.

[0031] The migration management platform extracts the converted and adapted configuration information and applies it to the target system during the migration process, ensuring that the software runs correctly in the domestic system according to the user's personalized needs.

[0032] In a preferred embodiment, the agent deployed in the source Windows system also listens for sharing requests from the target system. Upon receiving a sharing request, the agent calls the source Windows system's VSS to create a snapshot volume for the shared disk or directory. This snapshot volume is a read-only copy. The agent points the shared disk or directory to the snapshot volume, and the target system accesses the data in the snapshot volume via the CIFS protocol, ensuring secure and unrestricted data reading from the snapshot. This process not only guarantees the integrity of data transmission but also ensures the continued stable operation of the original services on the source Windows system, achieving seamless data migration and sharing.

[0033] An agent packaged as a deb file is deployed on the target system. This agent synchronizes software composition information (including the software and all its dependencies) from the migration management platform and silently executes the dpkg tool's installation commands to install the customized software based on this information. For different software, the agent receives pushed customized configuration files and content to ensure accurate software configuration. Before data transfer, the agent builds a shared directory via Samba for data migration. After the migration task is completed, this shared directory is promptly reclaimed to ensure efficient use of system resources and security.

[0034] The migration management platform compares, installs, and updates the software already installed on the source Windows system and the target system, and migrates the software configuration files and user data between the source Windows system and the target system.

[0035] In a preferred embodiment, the comparison, installation, and update of software already installed on the source Windows system and the target system through the migration management platform specifically involves: The migration management platform performs in-depth comparative analysis on the source Windows system and the target system, including information such as the software list, version number, and dependency tree of installed software, to determine whether the source Windows system contains software that is not installed on the target system. If all the software is already installed on the target system and the existing software versions match, no installation or update is required; only software configuration files and user data migration need to be synchronized. If such software exists, the migration management platform further determines whether the target system can match the versions of the missing software.

[0036] If a match is found, the migration management platform generates a differentiated migration report and provides a graphical interface for users to select migration strategies, including full coverage, incremental synchronization, or custom filtering. A silent installation of the software is then performed on the target system via the dpkg command chain (which can be integrated with the expect tool for non-interactive automation). Otherwise, the migration management platform performs a version rollback via the dpkg command chain to achieve software version matching. Specifically, the differentiated migration report provides a visual overview, guiding users to intuitively identify which software needs to be migrated from the source Windows system, which software is already present on the target system, which needs updating, and which needs a clean install. Users can also select specific software not to be synchronized. Furthermore, for dependency conflict scenarios, the migration management platform has a built-in pre-check mechanism that dynamically generates a compatibility whitelist based on the apt dependency resolution algorithm, automatically filtering out irrelevant or potentially conflicting packages.

[0037] As a preferred implementation method in this embodiment, after the software is installed, the configuration file customization information of this software in the source Windows system will be updated through the migration management platform (backup before updating). If the update fails, it can be ignored (the configuration file does not affect the use of the software). At this time, the data can also be synchronized, but the user needs to make some personalized configurations for the software.

[0038] In Windows systems, configuration files for commonly used software (such as .cfg, .xml, .json, .html, .ini, .conf, etc.) are mostly in text format, which can be automatically parsed and adapted through a migration management platform. As a preferred embodiment of this practice, the software configuration file migration includes both general configuration migration and non-general configuration migration. The general configuration migration specifically involves: directly reading the software configuration file of a general file in the source Windows system, parsing the software configuration file into key-value pairs or structured data (such as XML nodes and JSON fields), extracting the software configuration items supported by the target system through regular expression matching, XPath positioning, or JSON Schema verification, and automatically generating a software configuration file compatible with domestic systems (such as replacing path separators \→ / , adjusting the encoding to UTF-8, etc.). The non-generic file configuration specifically refers to: for software configuration files that are not directly compatible (such as Windows-specific registry parameters and hardware driver paths), dynamic mapping is performed based on a predefined conversion rule base (for example, replacing %APPDATA% with the ~ / .config directory of the domestic system) or logical equivalence is achieved through environment variable redirection, so as to generate software configuration files compatible with the domestic system.

[0039] As a preferred embodiment of this practice, the software configuration file migration also includes environment variable synchronization. Specifically, environment variable synchronization involves: extracting environment variables from the source Windows system (such as JAVA_HOME, PATH, PYTHONPATH), detecting conflicts with the target system (such as path format and dependency versions), and automatically generating an adapted environment variable script (such as .bashrc or / etc / profile.d / ) based on the target system's environment specifications, and escaping path separators and special characters. Table 1 shows an example table of configuration file conversion.

[0040] Table 1. Example of Configuration File Conversion

[0041] In a preferred embodiment of this practice, the synchronization of user data specifically includes: Install the Samba service on the target system via an agent, create a dedicated user without login privileges, and configure a shared directory (such as / data / sync) between the target system and the source Windows system. On the source Windows system, use PowerShell to map the Samba service shared directory as a mount point (New-PSDrive). Use VSS snapshot to lock the folder (Win32_ShadowCopy) where the user data to be synchronized to the target system is located on the Windows system. Generate a read-only snapshot volume to ensure file consistency. Use the Robocopy command ( / MIR / ZB) to copy the snapshot data in the snapshot volume to the mount point and record the operation log. The target system recursively modifies the owner of all user data files synchronized from the source Windows system to the target system (e.g., chown -R kylinuser:kylingroup) and resets file permissions (chmod 660 file, 2770 directory), and repairs file tags (e.g., SELinux / AppArmor tags) according to the target system's security policy.

[0042] In a preferred embodiment of this invention, the method further includes uninstalling the Samba service of the target system, specifically: On the target system, first stop the Samba service, then use a package manager to uninstall the Samba service, and delete the files, related configuration files and dedicated users from the migration process. Finally, clean up the firewall rules to ensure that the normal operation of other services on the target system is not interfered with by the firewall rules.

[0043] In summary, the method described in this embodiment integrates multiple technologies, including agent software, migration management platform, and data transmission protocols within a local area network. These technologies work together to achieve automated cross-platform migration while preserving the integrity of user data, application configurations, and other data. Therefore, the method described in this embodiment is a unique and effective solution that can meet the actual needs of enterprises and improve migration efficiency and security.

[0044] To verify the effectiveness and superiority of the method provided in this embodiment, some specific examples are provided: Taking the migration of Google Chrome from Windows to the UOS desktop system as an example, the specific implementation steps are as follows: Set up a migration management platform: Deploy the migration management platform on the enterprise intranet server, and pre-install the deb package of Chrome or its domestic alternative software and its dependency libraries.

[0045] Source system data collection: Deploy an agent on the source Windows system to collect Google Chrome's installation path, version information, and configuration files (such as bookmarks, history, and settings files) via Windows API or by reading the registry.

[0046] Target system preparation: Deploy the agent on the UOS system, configure the Samba service, and create a shared directory for data migration.

[0047] Software installation: The migration management platform silently pushes and installs Chrome or its domestically produced alternative software to the UOS system.

[0048] Configuration file and user data synchronization includes bookmark synchronization, history and tag synchronization: Bookmarks sync: The Windows agent collects bookmark files (usually located in the Bookmarks file or a similar file in the user's directory). The bookmark files are then converted to JSON format and transferred to the UOS system via the migration management platform.

[0049] The UOS agent receives bookmark files and imports them into Chrome's bookmark management.

[0050] History and tags sync: Windows-based proxies retrieve history and currently open tab information via browser APIs or by accessing a history database (such as an SQLite database).

[0051] Historical records and tab information are converted into structured data and then transferred to the UOS system via the migration management platform.

[0052] The UOS-side proxy parses the received data and simulates user actions to reopen these history records and tabs in Chrome.

[0053] Configuration Update: Update Chrome's configuration files (such as the Preferences file) as needed to adapt to the environmental differences of the UOS system.

[0054] Migration Completed and Verified: Verify that Chrome is installed and configured correctly on the UOS system.

[0055] Check that your bookmarks, history, and tabs are synced.

[0056] Overview of the above technical implementation steps: 1. Environment data collection (source: Windows system): The agent collects information about the installation path, version, and configuration file location of Google Chrome.

[0057] Extract bookmarks, history database, and current tab information.

[0058] Data conversion and transmission Convert bookmark files to JSON format, and convert history and tab information into structured data.

[0059] These data are transferred to the UOS system through the migration management platform.

[0060] 2. Target Deployment and Configuration (Target UOS System): Silently install Chrome or its domestically developed alternatives.

[0061] Import bookmarks files into Chrome Bookmarks Manager.

[0062] Parse history and tab data, and reopen those tabs in Chrome.

[0063] Example 2 Accordingly, this embodiment provides an automated migration system for Windows applications and data oriented towards domestic substitution, including a target system and a source Windows system. The system is used to implement the automated migration method for Windows applications and data oriented towards domestic substitution as described in Embodiment 1 of this invention.

[0064] The target system is used to deploy a migration management platform, pre-configure an agent, automatically trigger silent installation and configuration replacement upon receiving migration instructions, provide Samba service to synchronize user data, and verify the consistency of permissions and configurations.

[0065] Furthermore, such as Figure 2 As shown, the migration management platform includes a software resource pool, a configuration conversion engine, and a data synchronization engine; The software resource pool is used to pre-configure domestic alternative software libraries and dependency libraries (including general software .deb packages and enterprise-customized software), and supports intelligent version dependency matching; A configuration conversion engine is used to automatically map and convert source Windows system configurations to Linux configuration files based on regular expressions and syntax tree parsing. The data synchronization engine is used to achieve seamless full / incremental transmission of user data based on VSS technology and CIFS protocol.

[0066] The source Windows system is used to deploy the agent and call VSS to perform hot backup of user data, ensuring uninterrupted service during the migration process.

[0067] Example 3 This embodiment provides a computer-readable storage medium storing a computer program thereon. When the computer program is executed by a processor, it implements the Windows application and data automated migration method for domestic substitution as described in Embodiment 1 of this invention.

[0068] In this application embodiment, "at least one" refers to one or more, and "more than one" refers to two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent the existence of A alone, A and B simultaneously, or B alone. A and B can be singular or plural. The character " / " generally indicates that the preceding and following related objects are in an "or" relationship. "At least one of the following" and similar expressions refer to any combination of these items, including any combination of singular or plural items. For example, at least one of a, b, and c can represent: a, b, c, a and b, a and c, b and c, or a and b and c, where a, b, and c can be single or multiple.

[0069] Those skilled in the art will recognize that the units and algorithm steps described in the embodiments disclosed herein can be implemented using electronic hardware, computer software, or a combination of electronic hardware and software. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0070] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0071] In the several embodiments provided in this application, any function, if implemented as a software functional unit and sold or used as an independent product, can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0072] The above description is merely an embodiment of the present invention and does not limit the patent scope of the present invention. Any equivalent structural or procedural transformations made based on the content of the present invention's specification and drawings, or direct or indirect applications in other related technical fields, are similarly included within the patent protection scope of the present invention.

Claims

1. A method for automated migration of Windows applications and data for domestic substitution, characterized in that, Includes the following steps: Deploy a migration management platform on the target system virtual machine and store the common software installation packages supported by the target system in a fixed directory on the migration management platform; Upload the enterprise's customized software installation package to the designated directory of the migration management platform, and use the dpkg tool to parse the customized software installation package to extract software composition information and configuration files; Deploy an agent on the source Windows system. The agent reads the personalized software configuration files of the source Windows system using the Windows API or by reading the registry, and sends them to the migration management platform for analysis and replacement of the software configuration files. Deploy an agent packaged as a deb file on the target system. The agent synchronizes software composition information from the migration management platform and silently executes the installation commands of the dpkg tool to install the customized software based on the software composition information. The migration management platform compares, installs, and updates the software already installed on the source Windows system and the target system, and migrates the software configuration files and user data between the source Windows system and the target system.

2. The method for automated migration of Windows applications and data for domestic substitution as described in claim 1, characterized in that, The migration management platform performs software configuration file analysis and replacement as follows: First, by comparing the default configuration items of the software in the source Windows system that are pre-recorded in the migration management platform with the actual configuration items received, the migration management platform identifies the personalized or custom configuration items of the source Windows system. For the personalized or custom configuration items of the source Windows system, the migration management platform uses a keyword recognition machine configuration replacement method to generate corresponding configuration information according to the specifications and requirements of the target system; The migration management platform extracts the converted and adapted configuration information and applies it to the target system during the migration process, ensuring that the software runs correctly in the domestic system according to the user's personalized needs.

3. The method for automated migration of Windows applications and data for domestic substitution as described in claim 1, characterized in that, The agent deployed in the source Windows system is also used to listen for sharing requests from the target system. Upon receiving a sharing request, the agent calls the VSS of the source Windows system to create a snapshot volume for the shared disk or directory. The snapshot volume is a read-only copy. The agent points the shared disk or directory to the snapshot volume, and the target system accesses the data in the snapshot volume through the CIFS protocol.

4. The method for automated migration of Windows applications and data for domestic substitution as described in claim 1, characterized in that, The migration management platform compares, installs, and updates software between the source Windows system and the target system. Specifically, this involves: The migration management platform compares the source Windows system with the target system, including the installed software, to determine whether the source Windows system contains software that is not installed on the target system; if so, the migration management platform further determines whether the target system can match the version of the uninstalled software. If a match is found, the migration management platform generates a differentiated migration report and allows users to select migration strategies, including full coverage, incremental synchronization, or custom filtering, through a graphical interface. The platform then performs a silent installation of the software on the target system using the dpkg command chain. Otherwise, the migration management platform performs a version rollback using the dpkg command chain to achieve software version matching.

5. The method for automated migration of Windows applications and data for domestic substitution according to claim 1, characterized in that, The software configuration file migration includes general configuration migration and non-general configuration migration; The general configuration migration specifically involves: directly reading the software configuration file of a general file in the source Windows system, parsing the software configuration file into key-value pairs or structured data, extracting the software configuration items supported by the target system through regular expression matching, XPath positioning, or JSONSchema verification, and automatically generating a software configuration file compatible with domestic systems. The non-generic file configuration specifically refers to: for software configuration files that are not directly compatible, dynamic mapping is performed based on a predefined conversion rule base or logical equivalence is achieved through environment variable redirection, so as to generate software configuration files compatible with domestic systems.

6. The method for automated migration of Windows applications and data for domestic substitution as described in claim 1, characterized in that, The software configuration file migration also includes environment variable synchronization. Specifically, the environment variable synchronization involves: extracting environment variables from the source Windows system, detecting conflicts with the target system, automatically generating an adapted environment variable script based on the target system's environment specifications, and escaping path separators and special characters.

7. The method for automated migration of Windows applications and data for domestic substitution as described in claim 1, characterized in that, The synchronized user data specifically refers to: Install the Samba service on the target system via an agent, create a dedicated user without login privileges, and configure a shared directory between the target system and the source Windows system. On the source Windows system, use PowerShell to map the Samba service shared directory as a mount point. Use VSS snapshots to lock the folder on the Windows system where the user data that needs to be synchronized to the target system is located. Generate a read-only snapshot volume to ensure file consistency. Use the Robocopy command to copy the snapshot data in the snapshot volume to the mount point and record the operation log. The target system recursively modifies the owner of all user data files synchronized from the source Windows system to the target system and resets file permissions, and repairs file tags according to the target system's security policy.

8. The method for automated migration of Windows applications and data for domestic substitution according to claim 7, characterized in that, The method also includes uninstalling the Samba service on the target system, specifically: On the target system, first stop the Samba service, then use a package manager to uninstall the Samba service, and delete the files, related configuration files and dedicated users from the migration process. Finally, clean up the firewall rules to ensure that the normal operation of other services on the target system is not interfered with by the firewall rules.

9. A Windows application and data automated migration system for domestic substitution, characterized in that, Includes a target system and a source Windows system, wherein the system is used to implement the automated migration method for Windows applications and data oriented towards domestic substitution as described in any one of claims 1-8; The target system is used to deploy a migration management platform, with a pre-configured execution agent that automatically triggers silent installation and configuration replacement upon receiving migration instructions, provides Samba service to synchronize user data, and verifies the consistency of permissions and configuration. The source Windows system is used to deploy the agent and call VSS to achieve hot backup of user data.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by the processor, it implements the Windows application and data automated migration method for domestic substitution as described in any one of claims 1-8.

Images