Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. Information about the User State Migration Tool (USMT) 4.0 update

Information about the User State Migration Tool (USMT) 4.0 update

INTRODUCTION

This article describes the User State Migration Tool (USMT) software update. The update includes fixes and support for migration scenarios for when the source or destination computer has Microsoft Office 2010 installed. You can download the USMT 4.0 update from the Microsoft Windows Download Center.

This update is required if the source or destination computers in a USMT migration have Microsoft Office 2010 installed.

If you are using USMT to migrate from a computer that has Microsoft Office Outlook 2003 installed, also make sure that you have the following update (or a later update that includes this update), installed on the Office 2010 client: 
2405793 Description of the Outlook 2010 hotfix package (outlook-x-none.msp): October 26, 2010

About USMT

USMT is included in the Windows Automated Installation Kit (Windows AIK). Administrators can use USMT to migrate user data and user settings. The tool supports several operating systems, application settings, and user data migration scenarios that include the following scenarios:
  • Migrating operating system settings, application data, or user data from a Windows installation that is running on an older computer to a Windows installation that is running on a newer computer.
  • Migrating operating system settings, application data, or user data from an older Windows installation to a newer Windows installation that are running on the same computer in a "refresh" scenario.
USMT migrates user data, operating system settings, and application settings for applications such as Microsoft Office. For more information about data that USMT migrates, visit the following Microsoft TechNet website:
Introduction to the data that USMT migrates
You can customize USMT for enterprise environments. To customize a migration, modify or create XML files that specify the migration rules for the utility.

For more information about how to customize migrations, view the following Microsoft TechNet website:
General information about USMT 4.0
To download the Windows AIK tools, visit the following Microsoft website:
Download Windows AIK

Contents of this update

The USMT update includes the following changes:
  • The XML rules included in the default Migapp.xml file are updated to include new rules that support migrating Office 2010 application settings.
  • Changes that resolve an issue that creates many temporary files, that does not correctly remove the temporary files in a hard-link migration, and that causes poor LoadState performance.
  • An issue that prevents migration in certain time zones is corrected. When this issue occurs, the user receives the following error message in a log file:
    Unhandled exception, abnormal termination.
Additional Information about the Time Zone issue:

Consider the following scenario:
  • You change the time zone to a time zone that has a negative value in Coordinated Universal Time (UTC) on a computer that is running Windows 7. For example, you change the time zone to (UTC -04:30) Caracas.
  • You run the scanstate command by using the /progress option. For example, you run the following command:
    scanstate.exe c:\statestore /o /all /c /localonly /v:13 /progress:USMTCaptureProgress.prg
    Note The scanstate command is part of Windows User State Migration Tool (USMT) 4.0. USMT 4.0 is included in Windows 7.
In this scenario, an exception occurs, and you receive an error message that resembles the following:
Error [0x000000] Unhandled exception: OutOfMemoryException: (no exception message provided) class UnBCL::String *__stdcall Mig::pGetDateAndTime(void)[gle=0x00000091]
<Date><Time>, Error [0x000000] Unhandled exception, abnormal termination[gle=0x00000091]
Note This issue also occurs when you use the loadstate command in USMT 4.0.

Cause

This issue occurs because of an error in the code for the progress log in USMT 4.0.

Office setup and migration considerations

This update is required in a USMT migration if the source or destination computer has Microsoft Office 2010 installed.

Because of the way that user settings are stored in the registry, USMT can migrate Office settings from the following installations:
  • From an x64-based installation of Office to only an x64-based installation of Office
  • From an x86-based installation of Office to only an x86-based installation of Office
Therefore, settings and customizations that you try to migrate from an x86-based installation of Office to an x64-based installation of Office might not take effect on the new installation.

Additionally, USMT cannot migrate the Microsoft Word settings in the following registry key from an x86-based installation of Office:
HKEY_CURRENT_USER\software\Microsoft\Office\<OfficeVersion>\Word\Data
USMT does not support migrating settings to a version of Office that is earlier than the version that is currently installed on the source computer. For example, USMT cannot migrate settings from a 2007 Microsoft Office installation to an Office 2003 installation.

Note To migrate application settings, you must install applications on the destination computer before you run the loadstate command. For Office installations, you must run the LoadState tool to apply settings before you start Office on the destination computer for the first time by using a migrated user. If you start Office for a user before you run the LoadState tool, many settings of Office will not migrate correctly. For more information, visit the following Microsoft TechNet website:
Best practices for USMT

↑ Back to the top

Resolution

You must install this hotfix to support Office 2010 migrations.

Note Not all Office customizations can be migrated because of the design of the Office products themselves. Additionally, you may have to customize your migration in order to achieve the results that you want if you use nonstandard configurations of Office or of Windows in your environment. Some configurations are officially not supported by Microsoft. For example, hosting .pst files on a network share or on a mapped drive are officially not supported by Microsoft. In order to achieve all goals of a migration, you may have to contact Microsoft Customer Service and Support for more help to customize your XML rules.

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft website:
http://support.microsoft.com/contactus/?ws=support
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

To apply this hotfix, you must have USMT 4.0 installed.

Registry information

You do not have to make any changes to the registry to use this hotfix.

Installation instructions

This download provides updated versions of the USMT files that replace the USMT 4.0 files. By default, USMT is installed in the following folder:
C:\Program Files\Windows AIK\Tools\USMT\<architecture>
Note<architecture> is x86 or amd64.

To install the USMT 4.0 update, follow these steps:
  1. Download the USMT release .cab file for both architectures to a folder on your computer.
  2. In Windows Explorer, locate the x86 .cab file on your computer.
  3. In Windows Explorer, double-click the .cab file to view the contents of the file.
  4. Press CTRL+A to select all the files.
  5. Right-click the selection, and then click Extract.
  6. In the Select a Destination window, select the folder that contains the .cab file.
  7. Click Make New Folder, and then type x86 for the folder name.
  8. Click Extract to extract the files.
  9. In Windows Explorer, locate the folder where you extracted the files in the previous steps.
  10. Press CTRL+A to select all the files in the folder.
  11. Right-click the selection, and then click Copy.
  12. Locate the folder where the x86 USMT files are installed on your computer. For example, the x86 USMT files may be installed in the C:\Program Files\Windows AIK\Tools\USMT\x86 folder.
  13. Right-click anywhere in the folder, and then click Paste.
  14. When you are prompted, click Copy and Replace to replace the USMT 4.0 file with the newer version that this release includes.
  15. If a window prompts you for administrator permissions, click Continue. If other File Operation windows prompt you, click Yes in those windows.
  16. Repeat steps 2-15 by using the amd64 USMT .cab file, by typing amd64 for the folder name, and by selecting this folder as the destination for the extracted amd64 USMT files. For example, the amd64 USMT files may be installed in the C:\Program Files\Windows AIK\Tools\USMT\amd64 folder.
How to add the update to Microsoft Deployment Toolkit (MDT) deployment shares

To add the USMT 4.0 update into some existing MDT deployment shares, follow these steps:
  1. Update both the x86 folder and the amd64 folder in C:\Program Files\Windows AIK\Tools\USMT as described in the "Download Information" section.
  2. Open MDT Deployment Workbench.
  3. Update each deployment share by following the instructions in MDT.
How to add the update to Configuration Manager packages

To add the USMT 4.0 update into some existing MDT deployment shares, follow these steps:
  1. Download the USMT release .cab file for both architectures to a folder on your computer.
  2. In Windows Explorer, locate the x86 .cab file on your computer.
  3. In Windows Explorer, double-click the .cab file to view the contents of the file.
  4. Press CTRL+A to select all the files.
  5. Right-click the selection, and then click Extract.
  6. In the Select a Destination window, select the folder that contains the .cab file.
  7. Click Make New Folder, and then type x86 for the folder name.
  8. Click Extract to extract the files.
  9. In Windows Explorer, locate the folder where you extracted the files in the previous steps.
  10. Press CTRL+A to select all the files in the folder.
  11. Right-click the selection, and then click Copy.
  12. Locate the package source for the USMT files package, select the x86 subfolder.
  13. Right-click anywhere in the folder, and then click Paste.
  14. When you are prompted, click Copy and Replace to replace the USMT 4.0 file with the newer version that this release includes.
  15. If a window prompts you for administrator permissions, click Continue. If other File Operation windows prompt you, click Yes in those windows.
  16. Repeat steps 2-15 by using the amd64 USMT .cab file, by typing amd64 for the folder name, and by selecting this folder as the destination for the extracted amd64 subfolder of the USMT files package.
  17. In the Configuration Manager console, select the package that has the USMT files, and then update all distribution points.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

File information

The global version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.
For USMT 4.0 on all supported x86-based versions of a Windows operating system
File nameFile versionFile sizeDateTimePlatform
Loadstate.exeNot applicable1,019,39219-Jan-201112:32x86
Migapp.xmlNot applicable622,96819-Jan-201107:31Not applicable
Migcore.dllNot applicable5,766,65619-Jan-201114:35x86
Scanstate.exeNot applicable1,019,39219-Jan-201112:32x86
For USMT 4.0 on all supported x64-based versions of a Windows operating system
File nameFile versionFile sizeDateTimePlatform
Loadstate.exeNot applicable1,378,81619-Jan-201112:50x64
Migapp.xmlNot applicable622,96819-Jan-201107:31Not applicable
Migcore.dllNot applicable8,033,28019-Jan-201115:38x64
Scanstate.exeNot applicable1,382,40019-Jan-201112:50x64

↑ Back to the top

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top

More Information

For more information about how to upgrade and migrate Windows 7, visit the following Microsoft TechNet website: 
How to upgrade and migrate Windows 7
For more information about MDT, visit the following Microsoft TechNet website: 
Introduction to MDT
For more information about System Center Configuration Manager, visit the following Microsoft TechNet website:
General information about System Center Configuration Manager
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:

824684

Description of the standard terminology that is used to describe Microsoft software updates

↑ Back to the top

Keywords: kbautohotfix, kbhotfixserver, kbfix, kbqfe, kbsurveynew, kbexpertiseinter, kb

↑ Back to the top

Article Info
Article ID : 2023591
Revision : 1
Created on : 1/7/2017
Published on : 2/26/2011
Exists online : False
Views : 131