Before you can troubleshoot BDD 2007 you need to clearly understand the many logs used during an OS deployment.
If you understand what log to refer to and at what time you will find things that where once mysterious become understandable.
With this in mind I thought I would provide this quick guide to BDD logs.
BDD scripts automatically create log files. Each script creates a log file that matches the name of the script, for example ZTIGather.wsf creates a log file named ZTIGather.log. Each script also updates a common log file (BDD.log) that aggregates the contents of logs created by the BDD scripts. BDD logs are located in the C:\MININT\SMSOSD\OSDLOGS folder during the deployment process. They are then moved at the completion of a deployment, their destination is dependent on the deployment type:
- Lite Touch – C:\WINDOWS\TEMP\BDDLogs unless the /debug:true option has been specified.
- Zero Touch – C:\TEMP\SMSOSD or C:\SMSOSD unless the C:\MININT\Archive_OSD.SMS file is found.
The BDD.log file is also copied to a network location at the end of the deployment if the SLShare value is specified in the Customsettings.ini.
The BDD log format is designed to be read by TRACE32, part of the SMS 2003 Toolkit 2 – download here. I would strongly recommend that you use this tool whenever possible to read the logs as it makes finding errors much easier.
The rest of this blog details the log files that are created during the deployment and examples of when they can be used when troubleshooting.
Bdd.log – The aggreated BDD log file.
<Scriptname>.log – A log file created by each BDD script.
Wizard.log – Updated by BDD wizards.
DeployUpdates_platform.log – Created when deployment points are updated. Also used when updating Windows PE. Useful when troubleshooting Windows PE driver integration issues. This log is located in the %temp% folder.
SMSTS.log – Logs all of the transactions for the Task Sequencer. This will be located in %TEMP%, C:\Windows\System32\ccm\logs, or C:\SMSTSLog, depending on the situation.
WPEinit.log – Logs the Windows PE intialisation process – Useful for troubleshooting error starting windows PE
BDD 2007 automatically adds the logging switches to save the USMT logs to the BDD log file location
USMTEstimate.log – Log created when estimating the USMT requirements
USMTCapture.log – Log created when capturing data
USMTRestore.log – Log created when restoring data
Windows setup logs
This is a subset of the log files that are most useful for troubleshooting deployment issues, for more detailed information about Vista setup log files refer to this KB – http://support.microsoft.com/kb/927521.
setupapi.dev.log – Windows setup log, located in C:\Windows\inf – Useful for investigating failed Driver installations.
setupact.log – Windows setup log, located in C:\Windows\panther – Useful for investigating failed installations.
setuperr.log – Windows setup log, located in C:\Windows\panther – contains a list of errors that occurred during installation.
netsetup.log – Windows setup log, located in C:\Windows\Debug – useful for troubleshooting domain join issues.
setupapi.log – Windows setup log, located in C:\Windows – record inf installation actions – useful for investigating failed driver installations.
setupact.log – Windows setup log, located in C:\Windows – Lists installation actions.
setuperr.log – Windows setup log, located in C:\Windows – Details installation errors.
netsetup.log – Windows setup log, located in C:\Windows\Debug, useful for troubleshooting domain join issues.
The following logs are created during the deployment phases, these logs are located in the C:\MININT\SMSOSD\OSDLOGS folder:
OSDAgent.log – This is the primary log and should be the first place you look to determine what step failed
OSDEnv.log – Indicates which OSD environment variables are set
OSDInstallWIM.log – Logs image installation options
IDUser.log – User notification log
IDUserNotification.log – User notification log
MachineState.log – Logs computer state migration information (computer name, IP Address, Registered Owner/Org
WinPEInstall.log – WinPE installation information
Exec.log – Logs ‘Run SWD Program’ actions
scanstate.log – USMT scanstate log
OSDLaunch.log – OSD Bootstrap – May contain errors if the Advanced Client Network Access account is not configured correctly.
SMSCMT.log – Logs SMS Client migration information (site code, client GUIID)
WinPEInstall.log -Windows PE installation information.
OSDInstallWizard.log – Logs start-up operations.
OSDShell.log – Launches the OSD Install Wizard.
OSDSWDProgramExec.log – Logs Run SWD Program Actions.
OSDUsmtScanstate.log – Logs Capture User State operations
OSDUsmtLoadstate.log – Logs Restore User State operations
OSDBootstrap.log – May contain errors if the Advanced Client Network Access account is not configured correctly.
Note: The C:\minint folder is lost during the disk partitioning process. If you need to trobleshoot issues that occur before this point then disable the disk partitioning task in the task sequencer.