In Johan’s presentation on Troubleshooting MDT 2010 LTI (go to 55:16) Johan shows how to troubleshoot your CustomSettings.ini file

He creates a folder called MDT, copy the files ZTIDataAccess.vbs, ZTIGather.wsf, ZTIGather.xml, ZTIUtility.vbs, CustomSettings.ini and Microsoft.BDD.Utility.dll to the folder and then creates a batch (Gather.cmd) that run cscript.exe ZTIGather.wsf /debug:true

This is a great trick for troubleshooting your CustomSettings.ini file without actual doing an OS deployment

I added the following bits to the trick:

I’ve copied Trace32.exe (from the SMS 2003/ConfigMgr 2007 Toolkit) to the MDT folder
Created a .reg file called Trace32.reg that set Trace32.exe as the default logfile viewer and placed it in the same folder

Then I’ve added these 4 lines of code to Johan’s batch
—
mkdir C:\MININT\SMSOSD\OSDLOGS\ & echo. 2>C:\MININT\SMSOSD\OSDLOGS\BDD.log
regedit /s “%~dp0Trace32.reg”
start /max “%~dp0Trace32.exe” C:\MININT\SMSOSD\OSDLOGS\BDD.log
start “ZTIGather” /min cscript.exe “%~dp0ZTIGather.wsf” /debug:true
—

You can download Trace32.reg and Gather.cmd here

Now SMS Trace (Trace32.exe) will start maximized and show BDD.log will it’s being written to