Created capture media ISO in SCCM R2 and have tried it on a virtual machine and a physical machine. When you insert the cd and it autoruns nothing happens. If I go to the\SMS\BIN\I386 and double click tsmbautorun.exe i get an hourglass for a second or 2 and nothing happens.Any ideas on why it won't run?Mark Koenig

Verify that you have minimum 512 MB RAM, and that you included the nic drivers in the boot image... Also add the command shell to your boot image, so you can press F8 for a command prompt, and then review the log files

Ram is not the problem. Since you insert this cd into a machine running the OS to be captured and it autoruns to start the capture wizard I don't think that any of what you suggested would apply. I am in a functional operating system already so the log files would be accesable. Don't need command shell, drivers, etc. on the cd to see anything at this point in the process. The wizard will not run on any machine I have tried.Mark Koenig

Hi, The F8 option or drivers in the boot image will not help you with this. As I understand the wizard running in the OS you want to capture won't start. I faced the same problems onces. We mounted the ISO file instead of burning the ISO to disk. The solution for me was recreating the capture ISO file and burned it to a physical disk.Regards, Jannes Alink | Please mark posts as Answered if appropriate.

Do you have a smsts.log?Anything enlightening in there?"Everyone is an expert at something" Kim Oppalfens Configmgr expert for lack of any other expertise. http://www.scug.be/blogs/sccm

It could be that:1. Sysprep could not be found.2. You have the SMS client installed.Please look at the SMSTS.LOG file. That will tell you what the real reason is.If you can't find the SMSTS.LOG file, then it means that TSMBAutorun.exe could not launch TSMBootstrap.exe. You should then look for the TSMBAutorun.log file (in the TEMP folder).

Yes there is a smstslog and it looks like it fails to copy file from the d:\sms\bin to _tasksequence... something to that effect. I have a password on the Administrator account and the sccm client installed, please advise if the password would pose as a problem.

Are you capturing XP or Vista?Is sysprep in place for XP?Are you running this as an Administrator? I guess this is the issue.If you are admin, does Admin have permissions to the root of the folder?John | Program Manager | System Center Configuration Manager

I just ran into this, and believe it or not, the problem was that the files for the boot media were not at the root of the flash drive I was using. I moved the SMS, autorun, and volumeID files to the root and it then ran fine. Strange...http://blog.concurrency.com/author/nlasnoski/

If you are using VMware as the capture machine, ensure you built it using IDE drive instead of SCSI. If you built it on SCSI there is no way I know of to convert it, I had to just delete the drive and create anew one, this time specifying IDE instead of SCSI. I am sure it was a driver issue but I could not find anything concrete in the logs. Hope that tip helps someone. My symptoms: I launched tsmbautorun.exe as administrator, filled out all the info, when I click finish, nothing happens.