Just a quick “Learn from my Mistakes” post here.
Let me first say that the Task Sequence Debugger is an excellent tool and can and will make troubleshooting task sequences so much easier. BUT, there is a catch….
We’ve amassed a very large number of task sequences since migrating to Configuration Manager 2012 and it got me thinking about ways to archive off older sequences so that we can clean house. So I came up with this script.
The script will first collect all of the task sequences in your site. Next it will enumerate through them, write the sequence to an XML named after the task sequence ID and finally create a CSV index of the TSID, task sequence name, the last modified date of the sequence and when the sequence was backed up.
I’ve been looking for a simple way to identify and map out the nested task sequences. This is the first part of a project that I’m working on. The goal of the overall project is to duplicate an entire task sequence “suite” of the parent and all nested sequences, and then update all the nested references.