In BDD 2007, we provide a task sequence that is preconfigured to do all of the activities needed to perform a deployment end-to-end (for Lite Touch, Zero Touch, refresh, upgrade, new computer, Windows XP, Windows Vista, etc.). However, that doesn't mean that it does everything you need. Depending on your particular requirements, you may need to add your own custom steps to the task sequence. That's one of the benefits of having the task sequencer and task sequence editor available: you can make whatever adjustments you require.
Now, that doesn't mean that making those adjustments is always a simple process. For example, let's assume you want to add batch files or simple Command Shell commands into the task sequence. Some things to keep in mind to help assure that these run successfully:
What if you want to test out a new task sequence action without running an entire deployment to do it? Well, you can create your own stand-alone task sequencer XML file, then tell it to run that. (Note that the typical environment variables, e.g. DEPLOYROOT or SCRIPTROOT, won't be defined in this case.) Here's the process that you need for that:
Any other suggestions? If so, please submit comments below and I'll continue to integrate them into this posting.