Select the product you need help with
USMT 4.0 migration from x86 to x64 results in corrupted COM+ componentsArticle ID: 2481190 - View products that this article applies to. SymptomsUsing the User State Migration Tool (USMT) 4.0 to migrate from an x86 platform to an x64 platform, COM+ component settings will be corrupt. Note The issue does not happen when migrating from x86 to x86 or x64 to x64 platforms. Opening COMEXP.MSC or DCOMCNFG.EXE and navigating to Component Services\Computers\My Computer will result in the following on-screen error: You do not have permission to perform the requested action. Additionally you may see Event ID 4434 logged in the Application log:Log Name: Application Source: Complus Event ID: 4434 Level: Warning User: N/A Task Category: Security Keywords: Classic Computer: win7-1.contoso.com A method call to an object in a COM+ application was rejected because the caller is not properly authorized to make this call. The COM+ application is configured to use Application and Compoinent level access checks, and enforcement of these checks is currently enabled. The remainder of this message provides information about the component method that the caller attempted to invoke and the identity of the caller.SVC/Lvl/Imp = 10/6/3, Identity=<<DOMAIN\Username>> CauseThis is a known issue with USMT when migrating from x86 to x64. ResolutionSolution This issue is fixed in USMT 5.0. The recommended solution is to use USMT 5.0 for migrations instead of USMT 4.0. USMT 5.0 is part of the Windows Assessment and Deployment Kit (ADK): http://www.microsoft.com/en-us/download/details.aspx?id=30652
(http://www.microsoft.com/en-us/download/details.aspx?id=30652)
Workaround To workaround the issue in USMT 4.0, you must specify a config.xml file and set the “Microsoft-Windows-COM-ComPlus-Setup” to not migrate. If you are not already using a config.xml file for USMT, you can generate one automatically by specifying the /genconfig switch to scanstate.exe syntax. For example: scanstate.exe /genconfig:config.xml /i:migdocs.xml /i:migapp.xml For more information about USMT and config.xml files, see the following Microsoft TechNet Article: http://technet.microsoft.com/en-us/library/cc766203(WS.10).aspx#Config
(http://technet.microsoft.com/en-us/library/cc766203(WS.10).aspx#Config)
Once you have generated the config.xml file, you must edit the following section, depending on source operating system (OS): Windows XP - <component displayname="Microsoft-Windows-COM-ComPlus-Setup-DL" migrate="no" Windows Vista or Windows 7 - <component displayname="Microsoft-Windows-COM-ComPlus-Setup" migrate="no" Save your changes to config.xml. Include the updated config.xml when using scanstate.exe to work around the issue. For example:scanstate.exe c:\mystore /i:migdocs.xml /i:migapp.xml /config:config.xml /v:5 This will execute scanstate.exe, using c:\mystore as the migration store, and include MigDocs.XML, MigApp.xml, and Config.XML for the migration with verbose logging enabled.More informationIf you are in a scenario where you have already migrated and have corrupted COM+, you can use the following as a script to restore the original COM+ repository. Copy the following indented text into notepad, and save as COM_Restore.vbs: Dim objComCatalog Set objComCatalog = CreateObject("COMAdmin.COMAdminCatalog") objComCatalog.RestoreREGDB "C:\windows\winsxs\amd64_microsoft-windows-com-complus-runtime_31bf3856ad364e35_6.1.7600.16385_none_b5bfb0b8ee629431\R000000000001.clb" MsgBox "Backup Restored!" Set objComCatalog = Nothing Once you have saved the script, launch an elevated command prompt and navigate to the directory where COM_Restore.vbs was saved. Type the following command: cscript COM_Restore.vbs Once you see a window pop-up with "Backup Restored!", you can close the command prompt, and restart the client machine. Note This is a "FAST PUBLISH" article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use
(http://go.microsoft.com/fwlink/?LinkId=151500)
for other considerations.PropertiesArticle ID: 2481190 - Last Review: February 28, 2013 - Revision: 6.0
|  |
Back to the top
