What Does USMT 3.0 Migrate?

In this topic

• User data
• Operating system components
• Supported applications
• What USMT does not migrate

User data

• Folders from each user profile. When you specify MigUser.xml, USMT migrates everything in a user’s profiles including the following:
  My Documents, My Video, My Music, My Pictures, Desktop files, Start Menu, Quick launch settings, and Favorites.
• Folders from the "All users" and Public profile. When you specify MigUser.xml, USMT also migrates the following which are from the "All users" profile (in Windows XP) or the Public profile (in Windows Vista):
  Shared Documents, Shared Video, Shared Music, Shared Desktop files, Shared Pictures, Shared Start Menu, and Shared Favorites.
• File types. When you specify MigUser.xml, USMT migrates the following file types. ScanState searches the fixed drives and collects the files with any of these extensions. The asterisk (*) stands for zero or more letters. For example, .xla, .xlb, .xls, and so on.
  .qdf, .qsd, .qel, .qph, .doc, .dot, .rtf, .mcw, .wps, .scd, .wri, .wpd, .xl*, .csv, .iqy, .dqy, .oqy, .rqy, .wk*, .wq1, .slk, .dif, .ppt*, .pps*, .pot*, .sh3, .ch3, .pre, .ppa, .txt, .pst, .one*, .mpp, .vsd, .vl*, .or6, .accdb, .mdb, .pub
• Access control lists. USMT 3.0 migrates access control lists (ACLs) for files and folders from computers running both Windows XP and Windows Vista. For example, if you migrate a file named File1.txt that was read-only for User1 and “full control” for User2, these settings will still apply after the migration on the destination computer.

Operating system components

USMT 3.0 migrates the following operating system components.

Note

Some settings like fonts, wallpaper, and screensaver settings are not applied by LoadState until after the destination computer has been restarted. For this reason, you should log off after you run LoadState.

When the destination computer is running Windows XP, the following components are migrated when you specify MigSys.xml.

When the destination computer is running Windows Vista, the following components are migrated by default using the manifests.

Accessibility settings Classic desktop Command prompt settings Dial-up connections Favorites Folder options Fonts Group membership. For example, right click My Computer and click Manage. USMT migrates the groups under Local Users and Groups (for the users that are included in the migration). Microsoft Internet Explorer settings (all versions through version 6.0) Microsoft Open Database Connectivity settings Microsoft Outlook Express mail (.dbx) files Mouse and keyboard settings Multimedia settings Phone and modem options RAS connection phone book(.pbk) files Regional options Remote Access Screen saver selection Taskbar settings Wallpaper settings

Important This list may not be complete. There may be additional components that are migrated. Accessibility settings Command prompt Custom wallpaper Dial-up connections FAX settings Folder options Group membership. For example, right click My Computer and click Manage. USMT migrates the groups under Local Users and Groups (for the users that are included in the migration). Mouse and keyboard settings Media player settings Microsoft Internet Explorer settings (all versions through version 7.0) Microsoft Outlook Express mail (.dbx) files Network printers RAS connection phone book(.pbk) files and settings Regional options Remote Access Scheduled jobs Screensaver Sound Settings Taskbar settings

Supported applications

Though it is not always essential, it is good practice to install all applications on the destination computer before restoring the user state. This ensures that migrated settings are preserved. Specifically, if the following applications are installed on the source computer, they must be installed on the destination computer prior to running LoadState: Lotus SmartSuite, RealPlayer Basic, and Quicken 2004 Home and Business.

Note

The versions of these applications must match on the source and destination computers. This is because USMT does not support migrating the settings of an older version of an application to a newer version — except with Microsoft Office which USMT can migrate from an older version to a newer version.

Note

USMT only migrates settings that have been used and/or modified by the user. If there is an application setting that was not touched by the user on the source computer, the setting may not migrate.

When you specify MigApp.xml, USMT 3.0 migrates the settings for the following applications:

Product	Version
Adobe Acrobat Reader	4.0, 6.0, 7.x
Adobe PhotoShop CS	8, 9
AOL Instant Messenger	5.9
Apple iTunes	6.0
Apple QuickTime Player	7
Corel Paint Shop Professional	9.0
CuteFTP Professional	6.0, 7.0
Eudora	5,6,7
ICQ Pro	2003b
IBM Lotus Notes	6.x, 7.0
IBM Lotus SmartSuite Lotus 1-2-3 Organizer WordPro	9, 9.8
MusicMatch JukeBox Basic	7.x, 8.x, 10.x
Microsoft Windows Media Player	7-9, 11
Microsoft Office Microsoft Access Microsoft Excel Microsoft FrontPage* Microsoft Outlook Microsoft PowerPoint Microsoft Publisher Microsoft Word	2000, XP, 2003, 2007* Note Microsoft FrontPage is not available in Office 2007.
MSN Messenger	6.1, 7.0, 7.5
Microsoft OneNote	2003, 2007
Microsoft Project	2003, 2007
Microsoft Visio	2003, 2007
Microsoft Windows Live Messenger	8.0
Microsoft Windows Moviemaker	2.1
Microsoft Works	7.0, 8.0
Mozilla Firefox	1.8
Odigo Messenger	4.0
Quicken	2001-2006 Home and Business
RealPlayer Basic	6.x, 10
SpyBot - Search & Destroy	1.4
WinAmp	5
WinZip	8.0, 9.0, 10.0
WordPerfect Office	11, 12, X3
WS_FTP Pro	8, 9, 10
Yahoo Messenger	5.x,6.x, 7.x

What USMT does not migrate

The following is a list of the settings that USMT does not migrate. For a list of the components that are migrated, see What Does USMT 3.0 Migrate?. If you are having a problem that is not listed here, see Common Issues.

Application settings

USMT 3.0 does not migrate the following application settings.

• Settings from older versions of an application. The versions of each application must match on the source and destination computers. This is because USMT does not support migrating the settings of an older version of an application to a newer version — except with Microsoft Office, which USMT can migrate from an older version to a newer version.
• Application settings and some operating system settings (for example, wallpaper and screensaver settings) when a local account is created. For example, if you run /lac to create a local account on the destination computer, USMT will migrate the user data, but all application settings and some operating system settings will not migrate.
• Microsoft Project settings, when migrating from Office 2003 to 2007 Microsoft Office system.
• ICQ Pro settings if ICQ Pro is installed in a different location on the destination computer. In order to successfully migrate the settings of ICQ Pro, you will need to install ICQ Pro in the same location on the destination computer as it was installed on the source computer. Otherwise, after you run LoadState, the application will not start. You may encounter problems when:
  • You change the default installation location on 32-bit destination computers.
  • Migrating from a 32-bit computer to a 64-bit computer. This is because the ICQ Pro default installation directory is different — when you install ICQ Pro on a 32-bit computer, the default location is "C:\Program Files\..." and the default directory on a x64-based computer is “C:\Program Files (x86)\...”.

Operating system settings

USMT 3.0 does not migrate the following operating system settings.

• Mapped network drives, local printers, hardware-related settings, drivers, passwords, application binary files, synchronization files, .dll files, or other executable files.
• Permissions for shared folders. After migration, you will have to manually re-share any folders that they were shared on the source computer.
• Files and settings between operating systems with different languages. That is, the operating system of the source computer must match the language of the operating system on the destination computer.
• Customized icons for shortcuts (may not migrate). For example, if user right-clicks a shortcut, clicks Properties, and changes the icon for the shortcut, then the customized icon may not migrate to the destination computer.
• Taskbar settings, when the source computer is running Windows XP.
• Network printers and the following firewall settings when the destination computer is running Windows XP.
  • Only the Internet Connection Firewall check box and setting is migrated. USMT supports Windows Management Instrumentation (WMI)–based settings and the Windows XP Service Pack 2 registry setting.
  • The Internet Connection Sharing setting is not migrated because it can make the network less secure if it is migrated to the destination computer.
  • The firewall advanced configuration settings are not migrated due to security risks.
  • The network connections user interface will not completely refresh until you log off or press F5.
  • Bridge settings are not migrated (for example, bridging a virtual private network to a second network adapter).

You should also note the following:

• You should run USMT from an account with administrative credentials, or some data will not migrate. When running ScanState and LoadState on Windows Vista, you need to run the tools in “Administrator” mode from an account with administrative credentials. If you do not run USMT in “Administrator” mode, only the user profile that is logged on will be included in the migration. In addition, you must run ScanState on Windows XP from an account with administrative credentials, or some operating system settings will not migrate. To run in “Administrator” mode, click the start button, click All Programs, click Accessories, right-click Command Prompt, and click Run as administrator.
• The data located on external universal serial bus (USB) hard disks will be migrated even when you specify /localonly. However, this issue will not occur with USB flash drives (that is, the data on USB flash drives will not be included when you specify /localonly).