Documented on TechNet. People often simply use it to shutdown or reboot the system after build. It can however run a script to perform actions
> On 21 Nov 2014, at 01:03, Giroux, Eric J <[email protected]> wrote: > > No, never heard of SMSTSPostAction. Is there a blog post explaining this? > > From: [email protected] [mailto:[email protected]] > On Behalf Of Niall Brady > Sent: Thursday, November 20, 2014 4:43 PM > To: [email protected] > Subject: Re: [mssms] Remnants after non-OSD task sequence > > have you tried running a script to clean them up as a SMSTSPostAction ? > > On Thu, Nov 20, 2014 at 8:27 PM, Giroux, Eric J <[email protected]> wrote: > I’m pre-caching content using a task sequence (a few packages) to be later > used during another installation. During the caching task sequence I’m doing > an MDT Use Toolkit and Gather to key off some of the gathered variables. The > problem I’m seeing is C:\_SMSTaskSequence and C:\MININT being left on the C: > drive. I thought these should be cleaned up. Clues in smsts.log below. > This is with SCCM 2012 SP1 and MDT2012U1 integrated. Manually restarting the > machine does not clear the folders. I also have a couple values under > HKLM\SOFTWARE\Microsoft\SMS\Task Sequence that seem to be related: > > <image001.png> > > Execution engine result code: 0 (Success=0, Failure=1, RebootInitiated=2) > Cleaning Up. > Removing Authenticator > Cleaning up task sequence folder > Unable to delete file C:\_SMSTaskSequence\TSEnv.dat (0x80070005). Continuing. > Failed to delete directory 'C:\_SMSTaskSequence' > SetNamedSecurityInfo() failed. > SetObjectOwner() failed. 0x80070005. > RemoveFile() failed for C:\_SMSTaskSequence\TSEnv.dat. 0x80070005. > RemoveDirectoryW failed (0x80070091) for C:\_SMSTaskSequence > Deleting volume ID file > C:\_SMSTSVolumeID.7159644d-f741-45d5-ab29-0ad8aa4771ca ... > Deleting volume ID file > D:\_SMSTSVolumeID.7159644d-f741-45d5-ab29-0ad8aa4771ca ... > Deleting volume ID file > G:\_SMSTSVolumeID.7159644d-f741-45d5-ab29-0ad8aa4771ca ... > Successfully unregistered Task Sequencing Environment COM Interface. > Executing command line: "C:\Windows\CCM\TsProgressUI.exe" /Unregister > > ==========[ TsProgressUI started in process 4628 ]========== > Unregistering COM classes > Shutdown complete. > Process completed with exit code 0 > Successfully unregistered TS Progress UI. > Start to cleanup TS policy > End TS policy cleanup > Task Sequence Manager ServiceMain finished execution. > Task Sequence Manager service will be reconfigured > Task Sequence Manager service reconfigured successfully > Sending success status message > Set authenticator in transport > RegQueryValueExW failed for Software\Microsoft\SMS\Task Sequence, > SMSTSEndProgram > GetTsRegValue() failed. 0x80070002. > End program: > Successfully finalized logs to SMS client log directory from > C:\Windows\CCM\Logs > > > Any ideas of what else needs to be done to allow these lingering folders to > be cleaned up? > > Thank You, > > Eric Giroux > Senior Infrastructure Engineer > Unum End User Computing > E-mail: [email protected] | Office: (207) 575-2482 > Mobile: (207) 239-5190 | Fax: (207) 575-2158 > > > > >
