Select the product you need help with
Information about the User State Migration Tool (USMT) 4.0 updateArticle ID: 2023591 - View products that this article applies to. On This PageINTRODUCTIONThis 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
(http://support.microsoft.com/kb/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:
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.
(http://go.microsoft.com/fwlink/?LinkId=207216)
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:
(http://technet.microsoft.com/en-us/library/dd560801(WS.10).aspx)
Download Windows AIK
(http://go.microsoft.com/fwlink/?LinkId=136976)
Contents of this updateThe USMT update includes the following changes:
Consider the following scenario:
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] Cause This issue occurs because of an error in the code for the progress log in USMT 4.0. Office setup and migration considerationsThis 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:
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 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
(http://go.microsoft.com/fwlink/?LinkID=207111)
RESOLUTIONYou 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 informationA 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.
(http://support.microsoft.com/contactus/?ws=support)
PrerequisitesTo apply this hotfix, you must have USMT 4.0 installed.Registry informationYou do not have to make any changes to the registry to use this hotfix.Installation instructionsThis 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:
To add the USMT 4.0 update into some existing MDT deployment shares, follow these steps:
To add the USMT 4.0 update into some existing MDT deployment shares, follow these steps:
Hotfix replacement informationThis hotfix does not replace a previously released hotfix.File informationThe 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 systemCollapse this table
For USMT 4.0 on all supported x64-based versions of a Windows operating systemCollapse this table
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. MORE INFORMATIONFor 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:
(http://go.microsoft.com/fwlink/?LinkID=186886)
Introduction to MDT For more information about System Center Configuration Manager, visit the following Microsoft TechNet website:
(http://go.microsoft.com/fwlink/?LinkId=207036)
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:
(http://go.microsoft.com/fwlink/?LinkId=207037)
824684
(http://support.microsoft.com/kb/824684/
)
Description of the standard terminology that is used to describe Microsoft software updates
PropertiesArticle ID: 2023591 - Last Review: February 26, 2011 - Revision: 2.0
|



Back to the top








