nullpoynter Posted July 2, 2015 Report post Posted July 2, 2015 I have what seems like a stupid question. After running a build and capture task sequence, the C:\SMSTSLog directory and C:\smsbootsect.bak are left behind on the image captured? I don't ever remember seeing these on the previous (and first) image I built. Do the existence of these on the root C: drive signify that an error has occurred? Thanks... Quote Share this post Link to post Share on other sites More sharing options...
Rocket Man Posted July 2, 2015 Report post Posted July 2, 2015 It generally means that the task sequence did not finish with a successful code. I get this sometimes when I deploy an OSD TS and it fails at a certain stage, so I guess it is the same for the B&C Task Sequence. Do you have continue on error selected on any tasks of the sequence? This may cause it in particular if the last task in the sequence has it selected. Quote Share this post Link to post Share on other sites More sharing options...
nullpoynter Posted July 5, 2015 Report post Posted July 5, 2015 It generally means that the task sequence did not finish with a successful code. I get this sometimes when I deploy an OSD TS and it fails at a certain stage, so I guess it is the same for the B&C Task Sequence. Do you have continue on error selected on any tasks of the sequence? This may cause it in particular if the last task in the sequence has it selected. Well, if I disable the last three steps of my task sequence (Prepare Configuration Manager Client, Prepare OS, and Capture the Reference Machine) the task sequence doesn't leave the C:\SMSTSLog directory or the smsbootsect.bak file behind. I've also tried running the task sequence with these three steps disabled again and using ISO capture media. The ISO capture leaves this folder and file behind as well. What about these three steps would cause this issue to happen? Quote Share this post Link to post Share on other sites More sharing options...
Rocket Man Posted July 14, 2015 Report post Posted July 14, 2015 The ISO capture leaves this folder and file behind as well How are you preparing your OS before the manual capture using the ISO capture media? TBH I have only used ISO capture media for my images as I have no need for FAT images(which I assume is why you are using automated build and capture) so that it installs OS, software, updates and any other custom tasks before capturing to a wim file. BTW are you targeting a virtual machine or physical machine with the B&C task sequence? Quote Share this post Link to post Share on other sites More sharing options...
