Sounds like I need to do a side by side comparison of my task sequence with the MDT template to see if any are out of position.
From: [email protected] [mailto:[email protected]] On Behalf Of Michael Niehaus Sent: Wednesday, January 08, 2014 7:21 PM To: [email protected] Subject: RE: [MDT-OSD] Use Toolkit Location The MDT task sequences are also designed to handle the changing drive letters, updating %SCRIPTROOT%, %TOOLROOT%, etc. as the task sequence progresses. This is handled by the multiple "Use Toolkit Package" steps in the task sequence, strategically positioned at various points where reboots that change drive letters could occur. Since these variables point to folders that aren't on the USB key, and since deploying from the USB can only result in one extra reboot (taken into account in MDT 2012 Update 1), this should "just work". By any chance did you remove or disable any of the "Use Toolkit Package" steps? Thanks, -Michael From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Keith Garner Sent: Wednesday, January 8, 2014 4:00 PM To: [email protected]<mailto:[email protected]> Subject: RE: [MDT-OSD] Use Toolkit Location >From what I recall, the SCCM Task Sequencer will place the _SMSTaskSequence >folder on the *largest* fixed disk partition (or is it the partition with the >most free space). Can you move over to a "removable" USB Flash Drive instead? Otherwise taking a look at the bdd.log and smsts.log file would be helpful. Can you copy them to a public share like SkyDrive and copy the link here? From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Giroux, Eric J Sent: Wednesday, January 8, 2014 2:35 PM To: [email protected]<mailto:[email protected]> Subject: [MDT-OSD] Use Toolkit Location I've started seeing an issue crop up since moving to SCCM 2012 with MDT 2012 integrated task sequences. Occasionally it looks like the Use Toolkit action is resulting in the %SCRIPTROOT%, %TOOLROOT%, etc. variables referencing a drive letter other than C:. The problem this is causing is when trying to run things at certain points in the task sequence, getting results such as this: The system cannot find the file D:\_SMSTaskSequence\WDPackage\Scripts\ZTIConf.hta. This only seems to be happening when building from USB media. Sometimes it works fine, sometimes it does not. Sometimes it's E: or D:. Is there a way to force the Use Toolkit action to always copy to C:
