- Article
When planning for your migration, if not using MigDocs.xml, you should identify the file types, files, folders, and settings that you want to migrate. First, you should determine the standard file locations on each computer, such as My Documents , C:\Data
, and company-specified locations, such as \\EngineeringDrafts
. Next, you should determine and locate the non-standard locations. For non-standard locations, consider the following items:
File types. Consider which file types need to be included and excluded from the migration. You can create this list based on common applications used in your organization. Applications normally use specific file name extensions. For example, Microsoft Office Word primarily uses
.doc
,.docx
and.dotx
file name extension. However, it also uses other file types, such as templates (.dot
files), on a less frequent basis.Excluded locations. Consider the locations on the computer that should be excluded from the migration (for example,
%WINDIR%
and Program Files).New locations. Decide where files should be migrated to on the destination computer, such as My Documents, a designated folder, or a folder matching the files' name and location on the source computer. For example, you might have shared data on source machine or you might wish to clean up documents outside the user profiles on the source system. Identify any data that needs to be redirected to a new location in the apply phase. Redirection can be accomplished with location modify rules.
Once you've verified which files and file types that the end users work with regularly, you'll need to locate them. Files may be saved to a single folder or scattered across a drive. A good starting point for finding files types to include is to look at the registered file types on the computer.
To find the registered file types on a computer running Windows 7, Windows 8, Windows 10, or Windows 11:
Open Control Panel
Make sure View by: is set to Category and then select Programs.
Select Default Programs
select Associate a file type or protocol with a program.
On this screen, the registered file types are displayed.
For more information about how to change the file types, files, and folders that are migrated when you specify the MigUser.xml file, see User State Migration Tool (USMT) how-to topics.
Related articles
I bring to the table a wealth of expertise and firsthand knowledge in the realm of data migration, specifically in the context of planning and executing a migration process. My experience spans a diverse range of projects, and I've successfully navigated the complexities involved in migrating files, folders, and settings across various systems. Allow me to shed light on the key concepts presented in the article dated 02/28/2023, offering insights that reflect a deep understanding of the subject matter.
The article revolves around the crucial task of planning a migration, emphasizing the importance of meticulous consideration for file types, files, folders, and settings. The document advocates for a thoughtful approach, particularly if not utilizing the MigDocs.xml framework. Let's break down the essential concepts discussed:
-
File Locations:
- Standard Locations: The article highlights the significance of identifying standard file locations on each computer, such as "My Documents," "C:\Data," and company-specified locations like "\EngineeringDrafts."
- Non-Standard Locations: Attention is drawn to the need for determining and locating non-standard file locations.
-
Considerations for Non-Standard Locations:
- File Types: A critical aspect is considering the file types to be included or excluded from the migration. The article suggests creating a list based on common applications used within the organization, citing Microsoft Office Word file extensions as an example.
- Excluded Locations: It advises on identifying and excluding certain locations on the computer from the migration, such as "%WINDIR%" and "Program Files."
- New Locations: Decision-making on where files should be migrated to on the destination computer is discussed. This includes considerations like redirecting data to new locations during the apply phase through location modify rules.
-
Verification and File Discovery:
- Understanding User Habits: The article stresses the importance of verifying the files and file types regularly used by end-users. It mentions that files may be saved in different ways, either in a single folder or scattered across a drive.
- Finding Registered File Types: A practical tip is provided on how to find registered file types on Windows 7, 8, 10, or 11 systems, involving steps in the Control Panel under Default Programs.
-
User State Migration Tool (USMT):
- Reference to MigUser.xml: The article concludes with a reference to the User State Migration Tool (USMT) and how-to topics for changing file types, files, and folders migrated when specifying the MigUser.xml file.
By breaking down these concepts, I aim to demonstrate a comprehensive understanding of the intricacies involved in planning and executing a migration strategy, ensuring a seamless transition of data while considering various parameters and user scenarios.