ZTIDrivers.log – When troubleshooting MDT Driver injection.ZTIApplications.log – When troubleshooting application installs.Other log files you may want to look for: I’d even say this is practically useless CMTrace allows you easily read MDT log files, it highlights warnings, errors and points out problems for you. The first place to look when troubleshooting MDT is the BDD.log file in the windows temp. There’s lots of logs for each script that runs as part of the task sequence and you can even specify to log MSI installs during the deployment as well. It will let you dump logs back to MDT at the end of the deployment. If you don’t have server logging set up in your share, set that up. MDT will dump that to the Windows temp folder on the system being imaged. MDT will move everything there at the end. If the task sequence has finished, or at least been wrapped up cleanly, look in %WINDIR%\TEMP\DeploymentLogs. If the task sequence has started and that PC has at least imaged, look in C:\MININT\SMSOSD\OSDLOGS. If the imaging hasn’t started and you’re still in WinPE, look in X:\MININT\SMSOSD\OSDLOGS. Yes, sometimes knowing if half the battle, and with MDT that battle is knowing where to look for log files. CMTrace should ask you this right away – Select yes The hard part is knowing which log files to check. Open CMTrace once and it’ll ask to be the default.
Once that’s installed you may need to set CMTrace as your default viewer for logfiles. Pass on the ServerTools and Select Client Tools When installing the SCCM2012R2 Toolkit, just select client tools. It’s part of the SCCMTooklit downloads available here: This is a free tool you can download from Microsoft. These logs will contain lots of information, and while it can seem overwhelming at first, they’re only hard to read when you’re not using CMTrace. They certainly are verbose (which is in fact a good thing). I was on the TechNet MDT forums the other day and I read somebody claiming that the MDT logfiles were too verbose and too hard to read.
0 kommentar(er)
