Where are the MDT 2010 log files located?

MDT 2010 creates the following log files: • BDD.log. This is the aggregated MDT 2010 log file that is copied to a network location at the end of the deployment if you specify the SLShare property in the Customsettings.ini file. • DeployUpdates_Platform.log.

How to troubleshoot Microsoft Deployment Toolkit ( MDT )?

Before effective troubleshooting of MDT can begin, you must have a clear understanding of the many .log files used during an operating system deployment. When you know which log files to research for what failure condition and at what time, issues that were once mysterious and difficult to understand may become clear and understandable.

Where are the MDT scripts located in smsosd?

Each script also updates a common master log file (BDD.log) that aggregates the contents of the log files that MDT scripts create. MDT log files reside in C:\\MININT\\SMSOSD\\OSDLOGS during the deployment process.

Where to find bdd.log file in MDT?

It will create a file named BDD.log in the specified directory which means if you set SLShareDynamicLogging it to \\\\MDTServer\\Logs you’ll find a file named BDD.log in that directory.

How is the XMLHttpRequest object used in web development?

The XMLHttpRequest Object. The XMLHttpRequest object can be used to request data from a web server. The XMLHttpRequest object is a developer’s dream, because you can: Update a web page without reloading the page. Request data from a server – after the page has loaded.

How to use MDT to solve deployment problems?

Provides scenario-based samples of how to solve common deployment issues using MDT. Most samples include example configuration files and step-by-step processes for implementing the solution. Use this document to help solve difficult deployment problems. Toolkit Reference

How to check the status of an XMLHttpRequest?

Once the server has responded, we can receive the result in the following xhr properties: status HTTP status code (a number): 200, 404, 403 and so on, can be 0 in case of a non-HTTP failure. statusText HTTP status message (a string): usually OK for 200, Not Found for 404, Forbidden for 403 and so on. response (old scripts may use responseText)