I can’t stress enough how invaluable log files can be in tracking down deployment issues.
In many cases IT Administrators will troubleshoot a problem with a trial and error methodology.
ZTI is a fully automated deployment scheme in which installation requires no user interaction whatsoever. An LTI deployment needs very little infrastructure, so it can be installed from a network share, or media using either a USB flash drive or an optical disc.
As a computer and mobile device administrator and enterprise IT Professional, you can use this solution guide to understand the Microsoft recommended processes for creating and deploying Windows operating systems.
However, in many cases, those administrators are not familiar with Microsoft best practices recommendations or the operating system deployment tools and capabilities available to them.
Instead, they typically use manual methods that include combinations of answer files, scripts, the Windows Automated Installation Kit (Windows AIK), and so on to perform operating system deployments.
This is an updated version of the skipping deployment wizard pages table.
This is one of the most popular articles on Scriptimus Ex Machina as it covers most of what is required to automate Lite Touch deployments.
Zero Touch Installation (ZTI), Lite Touch Installation (LTI), and User Driven Installation (UDI).A lot of time and effort can typically be saved if you troubleshoot MDT deployments with log files.:%WINDIR%\TEMP\Deployment Logs I have also found the Windows Setup logs to be very beneficial in troubleshooting MDT deployment issues so I’ll add a fourth location: X:$WINDOWS.~BT\Sources\Panther (prior to partition creation) C:\Windows\Panther (after partition creation)*consult the Troubleshooting Windows Deployments 2012-09-11 guide for additional log locations There are a lot of logs generated during the deployment process.In fact, pretty much every script that runs has a corresponding log file.Change a setting, re-attempt, research, try another setting.This type of approach doesn’t serve an Administrator that well with deployment troubleshooting for two reasons: A deployment admin can quickly find themselves wasting a lot of valuable time testing if they aren’t quickly identifying the real cause of the problem.Readers use it as a jumping off point to find other articles written here.