gmoney_99

In windows explorer go to the root of your deployment share and make a folder called Logs. Share the Logs folder. In MDT go to your Rules (customsettings) and add the following code in. You will need to change the server name and path. SLShare=\\mdtserver\mdtshare$\Logs Refresh your Deployment share. After each deployment occurs a new folder in the LOGS is created with the computer name of the client PC and ALL MDT logs are copied from the client to the server for later review. Also for best viewing results you will probably want to use the TRACE32.exe file. It even highlights the errors for you! This tool is free and located in the file ConfigMgrToolsVersion 2 Toolkit!. Google search it. Good Luck G

To help with troubleshooting you can do the following: In windows explorer go to the root of your deployment share and make a folder called Logs. Share the Logs folder. In MDT go to your Rules (customsettings) and add the following code in. You will need to change the server name and path. SLShareDynamicLogging=\\mdtserver\mdtsharename$\Logs Refresh your Deployment share. Now go to your LOGS folder and watch for a file that gets created in real time called BBD.log. You will need to keep the log open while your deployment is in action. This may help you see where exactly it is failing and why. Also for best viewing results you will probably want to use the TRACE32.exe file. It even highlights the errors for you! This tool is free and located in the file ConfigMgrToolsVersion 2 Toolkit!. Google search it. Good Luck G

You can attempt to mount the ISO file using a iso mounter then point MDT to look at the iso for the files it needs to try and "import" and OS. As far as the drivers you can build the scructure needed to inject drivers as needed for the models. G