This is because MDT adds another layer of tools and scripts on top of the core setup engine and the Windows AIK tools.
Luckily MDT also provides additional error handling and log files that can help us figure out what's going on so, in the end, we are better suited for troubleshooting.
The logs are stored in X:\MININT\SMSOSD\OSDLOGS, C:\MININT\SMSOSD\OSDLOGS, or C:\Windows\Temp\Deployment Logs depending on when the deployment fails.is the master log file, but the file may also yield additional clues as to why a Lite Touch deployment breaks.While VA awards compensation more quickly under BDD than through its traditional process, VA's efforts to manage the BDD program provide limited accountability for achieving optimal results.For example, the agency does not measure the time local VA personnel are developing BDD claims and thus has limited information on potential problems during claim development.Finally, VA has not evaluated initiatives to improve the program, such as its effort to achieve paperless processing of BDD claims.
As a result of these gaps in oversight, VA has limited information on how well the program is working or whether further improvements are warranted.In the scenario depicted below, we are deploying Windows 7 with a file, but it fails in the middle of the setup with a strange error code: Solution: Do not click OK.Instead, press Shift-F10 to locate the file (this file will be in different locations depending on when setup fails).In this case, the real error is that we typed an incorrect computer name into our which showed. On purpose I had assigned a computer name with more than 16 characters to my file (which I have seen customers do), and that is what caused setup to choke. For a list of possible locations for the file, refer to this article.Back to top When using MDT 2010 Lite Touch to deploy Windows, issues are more complex to troubleshoot.That being said, when compared with Windows XP and Windows Server 2003 deployment, deploying the new Windows platform is quite different.