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 -
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.
We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.
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