[tweetmeme source=”jojitsoriano” only_single=false]
When I first ran DCOMCNFG.EXE in my Windows 7 64-bit operating system, I could not find my 32-bit automation servers in the list as compared to when I did it in any 32-bit operating systems. The legacy application that was using the automation servers were running well so there must be no problem with the installation of the legacy application nor with the automation servers themselves.
Run this from the command line: MMC comexp.msc /32
Thanks to this thread from the MSDN forum where I got the answer.
For more info, see: Running 32-Bit and 64-Bit Snap-ins on 64-Bit Windows Operating Systems
After running it from the command line, I noticed that succeeding calls to DCOMCNFG.EXE would always show my 32-bit components. This must be what the Technet article meant by “bypassing the MMC decision-making process”. This may not be an issue at all since you can switch back to the 64-bit version when you need to.