ConfigMgr 2012 Capture media does not run

Question

I am experiencing an issue in more than one customer environments (so far) and in my own VM environment (which is now running the full release version of ConfigMgr 2012), capture media when ran within a functional OS doesn't give me a wizard.   I thought
this might just have been an RC1 issue, but this is also now a problem for me with the full release.  I find the TSMBAutorun.log in the %temp% folder and notice it is saying the following;
TSMBAutoRun started
Unknown system architecture 0
failed to run TSMBootstrap
The running OS is a fully patched Windows 7 Enterprise SP1 32-bit, but have also tried capturing from a 64bit Windows 7 Enterprise SP1 as well. I have tried burning the capture iso to a cdrom and extracting to the root of a USB key. Also tried generating
directly to a USB key and the result is the same.  I have tried adding a dummy SYSPREP folder onto C:.  I'm trying to run as regular and elevated user and as administrator.  I have tried regenerating the boot images and capture media iso file.
 A fully automated build and capture task sequence works fine, but I prefer to perform a manual capture using capture media.
I've done this many, many times before with ConfigMgr 2007 capture media so I'm no noob to this process.
Any ideas? What is TSMBootstrap actually looking for and why does it not recognise the system architecture.
Andy

Answer 1

Hello all. Or you can leave every thing in place in your task sequence and just modify the usb or ISO boot media (if you have daemon tools).
Here are the steps:
1 - Create Capture boot media in SCCM 2012 RTM
2 - After boot media is created browse to this directory <working drive>\SMS\bin\i386
3 - Create a directory called SMS
4 - double click this directory and create a directory called "bin"
5 - double click this directory and create a directory called x64. When you are done your path should look like this: <working drive>\SMS\bin\i386\SMS\bin\X64
6 - Now navigate back to the <working drive>\SMS\bin\x64 directory and copy ALL of the contents to the \SMS\bin\i386\SMS\bin\X64 directory
That's it!! Now you can run the TSMBAutorun.exe file from explorer, cmd, etc successfully.
The reason this works is because now the windows environment has a defined path for the reasons explained above. Now you don't have to circumvent security features like "disabling the GPO Pack" task sequence step.
I validated this fix after reading this post: 
http://jackychuasce.blogspot.com/2012/05/why-click-on-tsmbautorunexe-cannot.html
Thank you Jacky!!
JV
You know, as I was reading through here I thought the short-term fix or workaround was to just prepare the path to what it expects! At least until the fix arrives.