<div>
Hi, 
 
The only reason that folder get's left behind and not removed is if the task-sequence ends early, i.e. it crashes. The folder is needed for your deployment to work, as that's where software is downloaded. In normal operation, the whole folder will be deleted, 
 
Your Helix clients have a problem running the task-sequence. Unfortunately if you have ticked the option &quot;continue or error&quot; you will not realise anything failed, as the task-sequence will carry on as if nothing happened. It will gracelessly end, &nbsp;not delete the folder and may well not exit provisioning mode. If you *ever* see that directory it is a sure sign something is wrong. 
 
Therefore you need to track down the cause. For this you need to read and understand the logs, in c:\windows\cccm\logs. There are several: 
 
smsts.log - the first to check 
execmgr.log - contains the exact command line of packages 
AppDeploy.log - the command line of applications 
 
Check the smsts logs first and use CMTrace to read them. When you open both files, tick &quot;merge&quot;. 
Look for red fail lines. You can attach (don't paste) the logs here. 
 
Mike 
PS: just deleting that folder is easy enough, but not the solution at all.
</div>

<div>
Hi Mike, 
I have updated the SCCM 2012 R2 to CU5. &nbsp;One thing which I have found about this task Sequence, once I click on it the compliance for All unknown computers is 0.0% where as other task sequence which are working fine(cleaning after them) are 100% compliance. &nbsp;How and where can I make this TS compliance to all unknown computers? &nbsp;Also 
Same results even I uncheck the 'continue on error' which was checked on updates. &nbsp;Under SMSTS.log 
Still working on finding the cause. &nbsp;Need help 
I have these Errors in RED 
************************************************************************************** 
Failed to read filesystem from OSDPartitions2FileSystem, not formatting &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;OSDDiskPart &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;11/30/2015 10:17:51 AM &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;1136 (0x0470) 
*********************************************************** 
 
 
I had these errors in yellow: 
********************************************************************************** 
Unable to fixup reparse points in C:\programdata\Microsoft\Windows\LocationProvider (0x80070005) &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;ApplyOperatingSystem &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;11/30/2015 10:34:38 AM &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;1364 (0x0554) 
 
Unsuccessful in finding a suitable device driver for device 'Generic volume'. &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;OSDDriverClient &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;11/30/2015 10:36:46 AM &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;1108 (0x0454) 
Unsuccessful in finding a suitable device driver for device 'Generic volume'. &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;OSDDriverClient &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;11/30/2015 10:36:46 AM &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;1108 (0x0454) 
Unsuccessful in finding a suitable device driver for device 'HID-compliant vendor-defined device'. &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;OSDDriverClient &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;11/30/2015 10:36:46 AM &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;1108 (0x0454) 
Unsuccessful in finding a suitable device driver for device 'PCI Express Root Complex'. &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;OSDDriverClient &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;11/30/2015 10:36:46 AM &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;1108 (0x0454) 
Unsuccessful in finding a suitable device driver for device 'Microsoft Basic Display Driver'. &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;OSDDriverClient &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;11/30/2015 10:36:46 AM &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;1108 (0x0454) 
Unsuccessful in finding a suitable device driver for device 'Motherboard resources'. &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;OSDDriverClient &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;11/30/2015 10:36:11 AM &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;1108 (0x0454) 
Unsuccessful in finding a suitable device driver for device 'Microsoft AC Adapter'. &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;OSDDriverClient &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;11/30/2015 10:36:11 AM &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;1108 (0x0454) 
Unsuccessful in finding a suitable device driver for device 'Numeric data processor'. &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;OSDDriverClient &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;11/30/2015 10:36:11 AM &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;1108 (0x0454) 
Unsuccessful in finding a suitable device driver for device 'Microsoft ACPI-Compliant Embedded Controller'. &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;OSDDriverClient &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;11/30/2015 10:36:11 AM &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;1108 (0x0454) 
Unsuccessful in finding a suitable device driver for device 'Microsoft ACPI-Compliant Control Method Battery'. &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;OSDDriverClient &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;11/30/2015 10:36:11 AM &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;1108 (0x0454) 
Unsuccessful in finding a suitable device driver for device 'Microsoft ACPI-Compliant Control Method Battery'. &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;OSDDriverClient &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;11/30/2015 10:36:11 AM &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;1108 (0x0454) 
Unsuccessful in finding a suitable device driver for device 'Volume Manager'. &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;OSDDriverClient &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;11/30/2015 10:36:11 AM &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;1108 (0x0454) 
Unsuccessful in finding a suitable device driver for device 'Generic SuperSpeed USB Hub'. &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;OSDDriverClient &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;11/30/2015 10:36:11 AM &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;1108 (0x0454) 
 
************************************************************************************ 
 
 
There were just instructions, I guess have no significance where _SMSTasksequence is set not to be wiped 
***********************************************************************************: 
Starting to apply image 1 from HelixC2.wim to C:\ &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;ApplyOperatingSystem &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;11/30/2015 10:28:46 AM &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;1364 (0x0554) 
Wiping C:\ &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;ApplyOperatingSystem &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;11/30/2015 10:28:46 AM &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;1364 (0x0554) 
Set &quot;C:\_SMSTaskSequence&quot; to not be wiped &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;ApplyOperatingSystem &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;11/30/2015 10:28:46 AM &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;1364 (0x0554) 
Set &quot;%OSDStateStorePath%&quot; to not be wiped &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;ApplyOperatingSystem &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;11/30/2015 10:28:46 AM &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;1364 (0x0554) 
Set &quot;%_SMSTSClientCache%&quot; to not be wiped &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;ApplyOperatingSystem &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;11/30/2015 10:28:46 AM &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;1364 (0x0554) 
Set &quot;%_SMSTSNewClientCachePathToCleanup%&quot; to not be wiped &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;ApplyOperatingSystem &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;11/30/2015 10:28:46 AM &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;1364 (0x0554) 
Skipping C:\_SMSTaskSequence for wipe &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;ApplyOperatingSystem &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;11/30/2015 10:28:46 AM &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;1364 (0x0554) 
Calculating expected free space. &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;ApplyOperatingSystem &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;11/30/2015 10:28:47 AM &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;1756 (0x06DC) 
Reporting deletion progress. &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;ApplyOperatingSystem &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;11/30/2015 10:28:47 AM &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;1756 (0x06DC) 
Successfully wiped C:\ &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;ApplyOperatingSystem &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;11/30/2015 10:28:47 AM &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;1364 (0x0554) 
Applying image to C:\ &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;ApplyOperatingSystem &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;11/30/2015 10:28:47 AM &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;1364 (0x0554) 
Applying image 1 to volume C: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;ApplyOperatingSystem &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;11/30/2015 10:28:47 AM &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;1364 (0x0554) 
Successfully applied image to C:\ &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;ApplyOperatingSystem &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;11/30/2015 10:34:30 AM &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;1364 (0x0554) 
OfflineRegistry::Init(&quot;C:\WINDOWS&quot;) &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;ApplyOperatingSystem &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;11/30/2015 10:34:30 AM &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;1364 (0x0554) 
Loading offline registry hive &quot;C:\WINDOWS\system32\config\software&quot; into HKLM\OfflineRegistry1 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;ApplyOperatingSystem &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;11/30/2015 10:34:30 AM &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;1364 (0x0554) 
Loading offline registry hive &quot;C:\WINDOWS\system32\config\system&quot; into HKLM\OfflineRegistry2 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;ApplyOperatingSystem &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;11/30/2015 10:34:32 AM &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;1364 (0x0554) 
CurrentControlSet is mapped to ControlSet001 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;ApplyOperatingSystem &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;11/30/2015 10:34:32 AM &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;1364 (0x0554) 
System root for target OS is C:\WINDOWS, System drive is C: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;ApplyOperatingSystem &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;11/30/2015 10:34:32 AM &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;1364 (0x0554) 
OS Version is 6.3 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;ApplyOperatingSystem &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;11/30/2015 10:34:32 AM &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;1364 (0x0554) 
*****************************************************************************
</div>

<div>
Hi again, 
 
That's a lot of errors and a lot of work to fix. I'll help where I can but you really need to read up on things yourself I think. Remember we're volunteers and SCCM is a very advanced product and can take lots of effort to get right which is way beyond a post here. 
 
That said you need to concentrate on the following: 
 
Errors: Unsuccessful in finding a suitable device driver for device 
Point to your machine not installing the right drivers for most of the hardware. 
What make and model is the hardware? Thinkpad X200? (guessing!) 
What drivers are you applying? 
How are you applying them? 
What drivers do you have in the boot WIM, WinPE? 
 
You need to fix those before going any further at all. Without drivers nothing much will work. Drivers need identifying, downloading, organising, pruning, testing, importing and targeting. They are the biggest piece of work for OSD and the most important. 
 
The 3rd error you pasted: 
Set &quot;C:\_SMSTaskSequence&quot; to not be wiped &nbsp; &nbsp; &nbsp;ApplyOperatingSystem &nbsp; &nbsp; &nbsp; 
 
is completely normal. The process is: 
boot into WinPE 
wipe the disk 
format at NTFS 
create a new DIR called _SMSTasksequence 
start copying files SCCM needs to _SMS... 
install things from that path 
run through all steps of the TS 
finish and clean up _SMS as last few steps 
display logon screen 
 
Your build is way off that. Check the monitoring section to see how far the deployment got. 
 
Mike
</div>

<div>
Mike, 
I am using the Lenovo drivers package for SCCM 2012 R2 for this Helix tablet make 3698-4LU. &nbsp;No idea why SCCM logs are complaining about. &nbsp;Anyways, my image for Helix has all the drivers already, in the TS if I uncheck the option of install of drivers, SCCM logs still complain. &nbsp; 
-In the boot image I have some generic drivers for NIC cards, should I remove them and try? 
- I tried making new TS the _SMSTasksequence folder is still not deleted at the end of TS. 
Still struggling to get this _SMStasksequence deleted at the end of TS. 
Thanks
</div>

<div>
Mike, 
I removed all the drivers from the Boot image, downloaded the SCCM driver package as you linked above. &nbsp;Downloaded the image onto the Helix and No luck. 
I am closing this case considering I have to make a new image and then check. &nbsp;For making the new image I need some extra time. &nbsp;Thanks for the help. &nbsp;I really appreciate it.
</div>

<div>
<div class="content wysiwyg-content">
Hi there, 
I have SCCM2012 R2 CU3, I use to deploy windows 8.1 image on my Helix clients. &nbsp;For some reason SCCM2012 is not cleaning the _SMSTasksequence folder (it has other folders as Applybootsystem, contentcache, drivers, logs, osd, packages,sms and TSEnv) once the image deployment is complete, since the folder is big, the users come back to me after a week with a big red bar on C drive to free some space. &nbsp;What can be done to prevent this huge folder left behind after deployment. &nbsp;I just deployed a new image on X200 machine and on C drive _SMSTasksequence is cleaned by SCCM2012. &nbsp;I need help on why Helix clients get this folder left by sccm. 
Thanks
</div>
</div>

Hi there,
I have SCCM2012 R2 CU3, I use to deploy windows 8.1 image on my Helix clients.  For some reason SCCM2012 is not cleaning the _SMSTasksequence folder (it has other folders as Applybootsystem, contentcache, drivers, logs, osd, packages,sms and TSEnv) once the image deployment is complete, since the folder is big, the users come back to me after a week with a big red bar on C drive to free some space.  What can be done to prevent this huge folder left behind after deployment.  I just deployed a new image on X200 machine and on C drive _SMSTasksequence is cleaned by SCCM2012.  I need help on why Helix clients get this folder left by sccm.
Thanks

SCCM2012 R2 CU3 deploying windows 8.1 image on clients leaves a folder SMSTasksequence

Systems Center Configuration Manager (SCCM, formerly known as Systems Management Server) is Microsoft’s system software for managing large groups of not only Microsoft computers, but those running other operating systems, such as Linux, OS-X, and various mobile technologies.

SCCM

The Microsoft Legacy Operating System topic includes legacy versions of Microsoft operating systems prior to Windows 2000: All versions of MS-DOS and other versions developed for specific manufacturers and Windows 3/3.1, Windows 95 and Windows 98, plus any other Windows-related versions, and Windows Mobile.

Microsoft Legacy OS

The Microsoft Server topic includes all of the legacy versions of the operating system, including the Windows NT 3.1, NT 3.5, NT 4.0 and Windows 2000 and Windows Home Server versions.

Microsoft Server OS

This topic area includes legacy versions of Windows prior to Windows 2000: Windows 3/3.1, Windows 95 and Windows 98, plus any other Windows-related versions including Windows Mobile.

Windows OS

Microsoft applications include a variety of software programs, including development and digital authoring programs (Expression and Media Center), educational programs, Internet software, including Essentials, Skype and the Live family, anti-virus, productivity applications and suites like Office, Excel, Word, Outlook, Access and PowerPoint, video games and server applications such as Exchange, SharePoint, IIS and Virtual Server.