User status migration of Windows XP 1/6: Introduction
Release Date: June 29, 2001
In the Windows XP operating system, there are two system tools that make the files and settings make easier and apply to different types of users and environments, respectively.
Files and Settings Transfer Wizard: Designed for users and small businesses, it also applies to the company's network environment. Employees can migrate their files and settings to the new computer with technical support with IT departments or help. User State Migration Tool (USMT): Designed for corporate IT administrators that need to perform large-scale Windows XP Professional deployment. Although the functionality of USMT is the same as "File and Set Transfer Wizard", it is a large-scale multi-user migration. USMT provides an administrator with a command line that can accurately define special settings, such as specific modifications to the registry. This article is divided into two parts: Part 1 briefly outlines the "Document and Set Transfer Wizard" and provides users with relevant entry knowledge; Part 2 provides a deep-level technical summary for USMT, and introduces the method of modifying the INF file to the administrator.
2/6: File and Set Transfer Wizard Overview
Release Date: June 29, 2001
This section outlines the "File and Set Transfer Wizard". The system tool helps them for files and settings for personal users in a home or a small enterprise environment. The Benefits Migration Wizard with File and Set Transfer Wizard provide users with fast and direct solutions that copies the required files and settings to new computers or newly installed Windows operating systems, continue its best effect. By shortening the time required to perform the following operations, the guide is easier to migrate to Windows XP.
Resetting the downtime to find the downtime to find the downtime to find the downtime to reset the personalized desktop, you need to call the technical support for a large amount of time-migrated settings that consume during the new operating system. These settings include the following four major categories:
Appearance: including the position of wallpapers, colors, sounds, and taskbars. Operation: Including the repeating speed of the button, double-click whether the folder expands the new window or displayed in the original window, is you open by double-clicking or click to open an object. Internet: Internet Settings Helps you connect to the Internet and control the action of your browser. These settings include: URL addresses, favorites, or bookmarks, cookies, security settings, dial-up and proxy settings. Email: Includes the information necessary to connect the mail server, your signature file, view, email rules, local emails, and contacts. Supportable mail agents include Outlook and Outlook Express. Migrated Application Settings Currently, Migration Wizard supports the migration of the specified application settings: Access, Excel, Outlook?, PowerPoint? And Word in Microsoft Office. After Windows XP is released, you can support more applications. Note: Migration is just the settings of the application without including the entire application. You need to reinstall the appropriate application on the new computer. Migrated Settings List Migrable Settings Groups include:
Internet Explorer Sets Outlook Express Settings and Save Outlook Settings and Save Dial Connection Telephone and Modem Option Auxiliary Options Selected Screen Sword Font Folder Selection Task Bar Settings Mouse and Keyboard Settings Sound Settings Setting Office Settings Network Drives and Printer Desktop Folder My Document Folder My Image Folder Favorites Cookies Folder Office Shared File Type Migrable file file Press file type (such as: .doc), folder (such as: c: / my documents) or specified File names (such as C: /Important/money.mny) migrate. Migration Wizard Default Migrating Most Shared File Types and Folders, and you can also choose the corresponding folder, file type, or specified file to add or delete. Start Migration Wizard: Click "Start" to point to "Programs", "Accessories", System Tools, click "File and Set Transfer Wizard". For the operation steps of the Migration Wizard in different applications, see the File and Settings Migration Guide. 3/6: User Status Migration Tool (USMT) Overview
Release Date: June 29, 2001
"User Status Migration Tool" not only has all the functionality of the File and Set Transfer Wizard, but also helps administrators fully customize specific settings, such as specific modifications to the registry. USMT is designed for administrators, and personal users do not need to use this tool. In addition, using USMT requires a client computer connected to the Windows Server domain controller. The benefits of using USMT will improve the following aspects, USMT reduces the cost required to deploy the operating system.
The cost employees who hire migration technicians to reset the downtime employee consumed by the personalized desktop to find the downtime call helper to lose the work file to assist employees to reset the time employee consumed by the personalized desktop in using the new operating system. A large amount of time employee spent on the process is controlled by a group of shared INF files, IT professionals or OIS can be modified by a group of shared INF files. During the actual process of performing automatic migration using USMT, IT professionals tend to modify the INF file to better deal with specific environments and meet special needs. The following sections will describe the details to help IT professionals use USMT and modify the INF file.
4/6: Composition of USMT
Release Date: June 29, 2001
The user status migration tool consists of two executables (ScanState.exe and LoadState.exe), and four migration rule information files (Migapp.inf, Migsys.inf, Miguser.inf, and sysfiles.inf). ScanState.exe executables can collect user data and settings based on the information contained in migapp.inf, migsys.inf, miguser.inf, and sysfiles.inf files. LoadState.exe executable The user status data is stored in a clean installation (cannot be an upgrade installation) to install Windows XP Professional's computer. These two files can be found in the folder in the "/ ValueAdd / MSFT / USMT /" directory of the Windows XP installation CD. For other migration requirements, you can create additional INF files. Under the premise that the default setting is not modified, the file and settings of the USMT migration include:
Internet Explorer Sets Outlook Express Settings and Save Outlook Settings and Save Dial Connection Telephone and Modem Options Auxiliary Options Standard Desktop Selected Screen Sword Font Folder Selection Task Bar Setting Mouse and Keyboard Settings Sound Settings Office Settings Network Drives and Printer My Document Folder My Image Folder Favorites The cookies folder is easy to modify the user status of the ScanState.exe collected. The program will guide you or delete the specified file, folder, registry item, or registry subtree. Regarding the rules of modifying scripts, see "Modify INF Migration Rule File". Table 1: Application of User Status Migration Tool Requirements System Type Requirements Source System Windows 95, Windows 98, Windows NT Workstation 4.0, or Windows 2000 Professional. Accessible Intermediate Storage Media Storage requires migration data (for general users, There is usually a 50 megabyte storage space. The specific storage space is dependent on the situation.) Target system Windows XP Professional Access to the intermediate storage medium There is enough hard disk space to receive user status data The simplest method is , Perform migration using the default migration file - ISfiles.inf). But usually, the administrator must create a script for running on the customer workstation. The creation steps of the script are as follows:
Run the ScanState.exe file on the customer workstation to copy the user status data to a middle storage medium. You can send this script shortcut to each user to remind them to run the program before participating in the evening. You can also perform the automatic deployment of the script or in a predetermined schedule; format the hard drive, and install Windows XP Professional and the required applications. You can use disk image software to automatically complete the entire process; run the loadState.exe file, and local administrators on the customer workstation start save user settings. (This process can be executed by the local administrator as a planned task.) When the user logs in to the system again, their final user status is reset. If you want to modify the default parameters in the sysfiles.inf file, follow these steps:
Confirm the settings for applications to migrate; confirm that you want to migrate file types, folders, or specified files; position these settings and files, and create a migration rule file (extension INF); run scanstate.exe Document, copy the user status data to a middle storage medium. You can send this script shortcut to each user to remind them to run the program before participating in the evening. You can also perform the automatic deployment of the script or completed by a predetermined schedule; format your hard drive, and install Windows XP Professional and the required applications. You can use disk image software to automatically complete the entire process; run the loadState.exe file, and local administrators on the customer workstation start save user settings. (This process can be executed by the local administrator as a planned task.) When the user logs in to the system again, their final user status is reset. The remainder of this section will introduce the syntax and how to use the User Status Migration Tool. ScanState.exe Syntax This section describes the syntax and usage of ScanState.exe executable.
ScanState [/ c / I infut.inf] * [/ l scanstate.log] [/ v verbosit_level] [/ f] [/ u] [/ x] migureration_path
Table 2: Apply ScanState.exe flag Perform operation / C to retain the past "filename_ TOO_LONG (file name too long)" error, the error record file is saved in the longfile.log file. / i Specifies a INF file that contains the definition of the migration status rule, you can specify multiple INF files. / 1 Specify a file for recording an error occurred. / v Enable lengthy output, syntax: / v # where # IS 1 to 7 (1 is minimum; 7 is the maximum). / u Specifies the user settings to be migrated, just a fault diagnostic variable. / f Specify that the file will be migrated, just a fault diagnostic variable. / x Specify that there is no file and settings to be migrated. Note: "Migration_Path" means the path to read the migration file. Example: scanstate // fileserver / migration / elizabeth / i ./migapp.inf / i ./migsys.inf / i ./miguser.inf /i./sysfiles.inf / i ./files.inf user settings, system settings And the file is migrated by default. "/ U", "/ f" and "/ x" flag are only used for troubleshooting. You can specify multiple INF migration rules files. If the specified INF file is more than one, there must be a sysfiles.inf migration rule file. LoadState.exe Syntax This section describes the syntax and usage of loadState.exe executable.
LoadState [/ i Iinput.inf] * [/ l loadingstate.log] [/ v #] [/ f] [/ u] [/ x] migration_path
Table 3: Apply loadState.exe flag Perform operation / C preserved past "filename_ TOO_LONG (file name too long)" error, the error record file is saved in the longfile.log file. / i Specifies a INF file that contains the definition of the migration status rule, you can specify multiple INF files. / 1 Specify a file for recording an error occurred. / v Enable lengthy output, syntax: / v # where # IS 1 to 7 (1 is minimum; 7 is the maximum). / x Specifies no file or setting to migrate, just a fault diagnosis variable. / u Specifies the user settings to be migrated, just a fault diagnostic variable. / f Specify that the file will be migrated, just a fault diagnostic variable. Note: "Migration_Path" means the path to read the migration file. Example:
LoadState // FileServer / migration / Elizabeth / i ./miguser.inf user settings, system settings, and files are migrated by default. "/ U", "/ f" and "/ x" logo are only used for troubleshooting. You can specify multiple INF migration rules files.
5/6: Modify the INF Migration Rule File
Release Date: June 29, 2001
This section describes the rules and syntax in the INF migration rule file (including Migapp.inf, Miguser.inf, Migsys.inf, and sysfiles.inf). Only the administrators who are familiar with the scripts and registry can try to modify the default INF migration rule file. After any changes are completed, it should be fully tested for the corresponding INF file. Special Folders and Environment Variables Support INF Migration Rule File Support for special folder paths defined by CSIDL value collections. Simply insert the name of the CSIDL into two percentage symbols (for example, "% csidl_systi%" or "% csidl_personal%"), USMT can apply it. For other environment variables, as long as the user and the administrator are the same, USMT can support. Example:% csidl_personal% / *. TXT Would Match C: / Documents and settings The rules of additional files can be added to the [Copy this State] statement in the INF migration rule file can be added to the flag of "copyfiles" Additional files and folders join the migration of the file. The "CopyFiles" flag is followed by a statement segment name. This statement section contains the location where the file and folder that will migrate to the target computer. Example:
[Copy This State] CopyFiles = Copy Trip Reports [Copy Trip Reports]; The next line copies the TripRpts folder non-recursingDIR = C: / TripRpts; The next line copies everything in the TrpRpts folder-recursing ONLYDIR = C: / TripRpts / *; The next line copies All Files on the user's desktop in a folder caled triprpts; matching the 99 * .doc Wildcard search.% Csidl_desktop% / Triprpts / 99 * .doc Excluded the file rules if you don't want to migrate some files or files The clip is added to the "Delfiles" in the [Copy this State] statement in the INF migration rule file to exclude the migration of the file and folder. The "DELFILES" flag is followed by a statement segment name. This statement section contains the location where you do not want to migrate to the target computer. Originally, ScanState.exe defaults to replication specified items, will not be copied now. Note: The files and folders specified here, no matter whether it is on the original computer or on the target computer, it will not be truly deleted. Example:
[COPY THIS STATE] DELFILES = Trip Reports Delfiles [Trip Reports Delfiles]; We don't want to migrate the july '99 Trip report% CSIDL_DEKSTOP% / TRIPRPTS / 9907 * .DOC write instead of reading different locations, The migrated file will be transferred to a more perfect desktop environment. Therefore, both administrators want to transfer the user's documents to "My Documents" (statement: csidl_personal). This process can be done by adding the destination folder on the target computer to the end of the "CopyFiles" statement. The new folder becomes the root directory of the migration file. You can also re-set the root directory to the destination folder, copy the migration file to a folder other than My Document. You can naming the location of the folder (such as: C: / DATA). More information about mobile files, see below: "Mobile and Replication Rules for Registry". Example: [Copy This State] CopyFiles = Copy Trip Reports [Copy Trip Reports]; The next line copies the TripRpts folderDIR = C: / TripRpts,% CSIDL_PERSONAL%; The next line copies everything in the TrpRpts folderDIR = C: / TripRpts / *,% CSIDL_PERSONAL%; the next line copies all files on the user's desktop in a folder called; TripRpts;. matching the 99 * .DOC wildcard search% CSIDL_DESKTOP% / TripRpts / 99 * .DOC,% CSIDL_PERSONAL% in the example above In all files are moved to the "CSIDL_Personal" statement, in the "My Document" folder of the user. The "C: / Triprpts" folder is repositioned under the "My Document" folder (where: c: / documents and settings /
/ My Documents / Triprpts.
The wildcard INF migration rule file supports the Microsoft (MSDoS) style, a searcheon for a part of the extension. For example, an asterisk (*) matches zero or more characters, question mark (?) Matches individual characters. If the original string contains a backslash, the path name that meets the specification target file matches the original string. Otherwise, the part of the match includes only the file name and extension. A plurality of wildcards are allowed in the original string. If the original string matches only to a directory, you need to add a "DIR = TAG" statement at the beginning of the row statement. E.g:
"C: /Triprpts/2000/AUGUST.*" matches "C: / Triprpts/2000/August.doc" and "C: /Triprpts/2000/August.xls"; with "C: / Triprpts / August. DOC "does not match;" August. * "matches" C: /Triprpts/2000/august.doc "," c: /trpts/2000/august.txt "and" C: /Triprpts/august.doc " "* .Doc" matches "C: / Triprpts/2000/August.doc" and "C: /Triprpts/august.doc"; "C: / * / 2000 /*." And "C: / Triprpts / 2000 / August.doc "," c: /trpts/2000/august.txt "and" c: /expenserpts/2000/morefiles.ext "match;" C: / Triprpts "with" C: / Triprpts "file matches, and the directory named" C: / Triprpts "does not match;" DIR = C: / Triprpts "matches the directory named" Triprpts ", and is called" Triprpts " "The file does not match; use the" * .doc "string to get all the files in the system in DOC-extension; use" C: /. DOC "or" C: / * / *. DOC "string to get the drive All files in the C drive are expanded in DOC. Settings /% Username% / My Documents / August.txt Registry Additional Rule You can add an additional registry key by adding a flag named "AddReg" in the [Copy this State] statement segment in the INF migration rule file. Or the migration of the entire registration form tree to the document. The "AddReg" flag is followed by a statement segment name. This statement segment contains the location of the registry key and subtree that will migrate to the destination computer. These registry entries will overwrite the various items corresponding to it. Example:
[COPY THIS STATE] AddREG = SPACECADET AddREG [SPACECADET AddReg] HKR / Software / Microsoft / Plus! / Pinball / SpaceCadet / * = Rule of Rubber Registry If you do not want to migrate some registry entries, you can in the INF migration rule file. [COPY THIS STATE] The function segment is added to the flag named "DELREG", and these registry keys exclude the migration of the file. The "DELREG" flag is followed by a statement segment name. This statement segment contains the location where you do not want to migrate to the registry key of the destination computer. Note: The registry key specified here is not truly deleted on the destination computer. Example:
[COPY THIS STATE] DELREG = SPACECADET DELREG [SPACECADET DELREG] HKR / Software / Microsoft / Plus! / Pinball / SpaceCadet [Table EXE] = Registry Move and Replication Rules Typically, a registry key must be included in the information of migration. So, if it is upgraded from Windows 95 or Windows 98 to the Windows XP Professional operating system, you need to modify, move, delete, or add most of the sub-keys and items in the registry. This process can be implemented by adding a flag called "renreg" in the [Copy this State] statement in the INF migration rule file. The "renreg" flag is followed by a statement segment name. This statement segment contains the location where the registry key to migrate to the destination computer, and the location where the registry key that needs to be renamed or moved. Example:
[Copy This State] RenReg = Outlook98 & 97 RenReg [Outlook98 & 97 RenReg] HKR / Software / Microsoft / Windows Messaging Subsystem / Profiles / * = / HKR / Software / Microsoft / Windows NT / CurrentVersion / Windows Messaging Subsystem / Profiles Note: If the Migration Rule INF The statement line in the file is ended in a backslash (/), indicating that the statement line is connected. If the file pointed to by a registry key also needs to be migrated, then the flag named "regfile" is added in the [Copy this State] statement segment, you can copy the file pointed to the value of the registry key. . The "regfile" flag is followed by a statement segment name. This statement segment contains the location where the relevant registry key is located, and each registry key listed must contain a file name. All listed file names will be copied to the destination computer. In the destination computer, the file paths are set to the actual location of the file (unless the file is moved). A registry key can be listed in "renreg" and "regfile" segment. "Regfile" statement can also be used for mobile files. Example: [Copy This State] RegFile = Desktop RegFile [Desktop RegFile] HKR / Control Panel / Desktop [Wallpaper] =; This next line would move the wallpaper image to My Documents .; You would NOT have both of these in the same file .Hkr / control panel / desktop [Wallpaper] =,% CSIDL_PERSONAL% Priority rule When the same file or folder applies multiple migration rules, there will be an algorithm to find the best match rules. Typically, the most appropriate rules for file or folder will win priority. If there are two rules that are equally accurate for files or folders, the "Include" rule is preferred. Find the scope of the best matching rule includes the full name path and file name. Even if the degree of matching is exactly the same, unexpected results have often occurred. The application order of the registry migration rules is as follows:
"DELREG" statement can be specified to ScanState.exe or LoadState.exe; "AddReg", "Renreg", and "regfile" statements can be assigned to any one in ScanState.exe and LoADState.exe. However, if you specify to LoadState.exe instead of scanstate.exe, you will not copy the specified registry key. For the "regfile" statement, the specified file is not copied; any item listed in the "DELREG" statement will not be copied to the destination computer; any items listed in the "renreg" statement will be renamed . If the same item appears multiple times, only one rename rule will be applied; any item listed in the "regfile" statement must contain the path to the specified value. There is no difference between the same number of occurrences. Any item listed in the "AddReg" statement overwrites the appropriate items on your computer. There is no difference between the same number of occurrences. This item is not overwritten (unless you are listed in the "AddReg" statement unless you are listed in the "AddReg" statement. Each registry key to any of the "renreg", "regfile", and "addReg" rules. Therefore, all designated rules can be applied simultaneously. However, the rules of the application must have the same path. For example, you can apply a "addReg" and a "renreg" rule for the "HKEY_LOCAL_MACHINE / SOFTWARE / Microsoft / Exchange / * Subkey" path, respectively. If the "addReg" rule pointed to the application is "HKEY_LOCAL_MACHINE / SOFTWARE / Microsoft / Exchange / * Subkey", and the path "hkey_local_machine / software / microsoft / exchang/cly subkey", then "renreg" Rules will get priority. The reason is that the path described is more specific. 6/6: Summary and related links
Release Date: June 29, 2001
This article describes two migration tools in Windows XP: File and Set Transfer Wizards, and User Status Migration Tool (USMT). "File and Setup Wizard" is designed for families and small business users. At the same time, it also applies to the company's network environment. Employees can migrate their files and settings into the new computer with technical support with IT departments or help. For detailed guidance on using this wizard, see text: File and Set Transfer Wizard. "User Status Migration Tool" is designed for corporate IT administrators who need to perform large-scale Windows XP Professional deployment. Although the functionality of USMT is the same as "File and Set Transfer Wizard", it is a large-scale multi-user migration. USMT provides an administrator with a command line that can accurately customize special settings, such as specific modifications to the registry. In addition, this paper also introduces the modification of the INF file for IT professionals.
For more information, please see the following related links:
File and Setup Migration Guide Planning Windows XP Deployment Implementation Windows XP Deployment
