I am currently setting up our Task Sequence so that It checks error logs on itself throughout the build and if it runs into an error it will jump out to an error section upload the logs to the server so that someone can check them. This has been done with the Guidance of Steve Rachui's blog: http://blogs.msdn.com/b/steverac/archive/2008/07/15/capturing-logs-during-failed-task-sequence-execution.aspx The function itself for a single domain works great!!! However here is my dilemm, The step 'Connect to network folder' - If you have one domain then you can hardcode the path to the folder, but we have 3 seperate domains and as I have one Task Sequence i need to somehow create some sort of variable. I have tried setting it on the collection and also creating a TS variable in the Task Sequence itself but as yet to no avail. Wondered if anyone has run into a similar issue or has any thoughts how to work around the issue. Thank-you in advanceLee Martin

Just create 3 steps to connect to the log folder, and put conditions (check for variables) on each step. Tip: These log gathering steps are default included in the MDT. Ronni Pedersen | Configuration Manager MVP | Blog: http://ronnipedersen.com/ | Twitter @ronnipedersen

How you currently specify in your task sequences which domain to join the computer to? Do each of your domains have their own Site Servers(including Primary, Secondary and/or Distribution Points)? Are your domains fully trusted? Somehow, we need to programatically gather from the environment what domain you are supposed to be in as a condition to specifying a network path to map to. If you've already solved the "what domain to join" problem somehow, you can probably use the task sequence variable OSDDomainName as a condition.

Until I can find a nicer way I have created 3 TS vairalbes with the server names added to this. Thanks for your helpLee Martin

Until I can find a nicer way I have created 3 TS vairalbes with the server names added to this. That IS a "nice way"... no need to change it, if it works... :o)Ronni Pedersen | Configuration Manager MVP | Blog: http://ronnipedersen.com/ | Twitter @ronnipedersen

Having thought I had this working it appears it is now not. I have three steps configured and assumed it was going to the be a task sequence varialbe on OSDDomainName as specified above but the TS skops both steps as they result in false. what am i missing :S ThanksLee Martin