Jump to content


Sign in to follow this  
anyweb

USMT x86 to x64 migration– Do not migrate COM+ setup manifest

Recommended Posts

via Ned Pyle, Microsoft.

 

Ned here. We rarely release USMT KB articles, so this post is to spread the word on a scenario that is easy to run into: do not allow calling of the Microsoft-Windows-COM-ComPlus-Setup-DL or Windows-COM-ComPlus-Setup manifests if migrating from x86 to x64. Bad things will happen otherwise, and while fixing it is easy on one machine, fixing it on 10,000 is not. For steps on preventing the issue and remediation, see:

 

USMT 4.0 migration from x86 to x64 results in corrupted COM+ components -

http://support.microsoft.com/kb/2481190

 

 

This effectively means that CONFIG.XML is now a required option for SCANSTATE, if you are moving from 32-bit to 64-bit OS. If going from 32-bit to 32-bit, or 64-bit to 64-bit, you have nothing to worry about.

 

Until next time.

 

Ned “Com Minus” Pyle

 

via > http://blogs.technet.com/b/askds/archive/2011/08/03/usmt-x86-to-x64-migration-do-not-migrate-com-setup-manifest.aspx

Share this post


Link to post
Share on other sites


Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
Sign in to follow this  

×
×
  • Create New...