| title | Create a task sequence for non-OS deployments |
|---|---|
| description | Create task sequences that aren't for deploying an OS, such as distributing software or automating tasks |
| ms.date | 11/30/2020 |
| ms.subservice | osd |
| ms.topic | install-set-up-deploy |
| ms.collection | tier3 |
Applies to: Configuration Manager (current branch)
Task sequences in Configuration Manager are used to automate different kinds of tasks within your environment. These tasks are primarily designed and tested for deploying operating systems. Configuration Manager has many other features that should be the primary technology that you use for the following scenarios:
-
[!NOTE] Starting in version 2002, install complex applications using task sequences via the application model. Add a deployment type to an app that's a task sequence, either to install or uninstall the app. For more information, see Create Windows applications.
Starting in version 2010, use the task sequence deployment type of an application to deploy a task sequence to a user-based collection.
Also consider other Microsoft System Center automation technologies, such as Orchestrator and Service Management Automation.
The power of task sequences lies in their flexibility and how you use them. They can configure client settings, distribute software, update drivers, edit user states, and do other tasks independent of OS deployment. You can create a custom task sequence to add any number of tasks. The use of custom task sequences for non-OS deployment is supported in Configuration Manager. However, if a task sequence results in unwanted or inconsistent results, look at ways to simplify the operation:
- Use simpler steps
- Divide the actions across multiple task sequences
- Take a phased approach to creating and testing the task sequence
The following steps are supported for use in a non-OS deployment custom task sequence: