I’ve been asked a few times, which task sequence template to use? Well, when planning your deployments, you should first consider the usage of your task sequences. There are 4 task sequence usage scenarios in MDT 2010, they are New Computer, Refresh, Replace and Upgrade. When choosing which task sequence template to use, consider the deployment scenarios.
NEW COMPUTER
The target computer is a new computer that has never been a member of the network. The Standard Client Task Sequence should be used in this situation. PXE booting and running this task sequence will wipe any out of box image.
- Bare metal deployment
- Pre-Boot Execution Environment (PXE) boot using Windows Deployment Services or Boot image CD
- No user state capture
REFRESH
The target computer is an existing computer on the network that needs the desktop environment standard to be redeployed. The Standard Client Task Sequence is designed to handle care of this scenario.
- Task Sequence deployment, started from within Operating System
- Existing OS needs to be refreshed.
- Requires capture and retention of user state.
- Applications need to be re-applied, if compatible.
REPLACE
An existing computer on the network is being replaced with a new computer. The user state migration data is transferred from the existing computer to share then back to the new computer. Within MDT this means running 2 task sequences, Replace Client Task Sequence then a task based on the Standard Client Task Sequence template. The Replace Task Sequence will only back up your data and wipe the disk in preparation for disposal/reuse.
- Task Sequence deployment from within Operating System or Bare Metal
- Task Sequence run on Source machine captures user state
- New machine begins using PXE boot or boot image media
- User state must be stored on a share or state migration point
- User state and compatible applications re-applied on new machine
UPGRADE
An existing computer on the network is running an earlier version of the Windows operating system and needs to be upgraded to the most current desktop environment standard. The Standard Client Task Sequence template can be used for this scenario.
- Task Sequence deployment from within Operating System
- Old OS is stored under a folder named windows.old
- User state is handled as part of the upgrade
- Applications do not need to be re-installed
Scriptimus Ex Machina 
Thank you, this was very helpful.
LikeLike
Is there a task sequence or a process that automatically re-installs the applications in a refresh/replace scenario? Or do you need to have all the necessary applications re-applied manually, i.e. your SKIPAPPLICATIONS=YES followed by the AppId’s in your custom settings examples.
LikeLike
Yes for each application you want installing, you will have to create an application in MDT and select it during deployment or use the list as you said.
LikeLike
As always, great, useful information Andrew. Hope you continue to write more articles like this with the upcoming release of MDT 2013
LikeLike
Thanks mate. I’ll try to get some new content posted soon.
LikeLike
Thanks Andrew. So for the Replace scenario we need 2 TSs, the 1st TS to run in the OS and capture the data, the 2nd TS to image the new computer? If so, do we need a State Migration Point? If so, do we need to create computer associations to restore the data to the correct machines? Is there an alternative way of capturing/restoring data, perhaps using UDI instead?
Best regards
Scott
LikeLike
Yes to all of the above. UDI and state migration points are SCCM though, not just MDT. Some people dont use the state migration point but configure a share.
LikeLike