Create a task sequence for non-operating system deployments with System Center Configuration Manager
Applies to: System Center Configuration Manager (Current Branch)
Task sequences in System Center Configuration Manager are used to automate a variety 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 scenarios such as application installation, software updates installation, setting configuration, or custom automation. There are other Microsoft System Center automation technologies, such as Orchestrator and Service Management Automation that you should also consider.
The power of task sequences lies in their flexibility and how you can use them to configure client settings, distribute software, update drivers, edit user states, and perform other tasks independent of operating system deployment. You can create a custom task sequence to add any number of tasks. The use of custom task sequences for non-operating system deployment is supported in Configuration Manager. However, if a task sequence results in unwanted or inconsistent results, look at ways to simplify the operation. You can accomplish this by using simpler steps, dividing the actions across multiple task sequences, or by taking a phased approach to creating and testing the task sequence.
The following steps are supported for use in a non-operating system deployment custom task sequence:
We'd love to hear your thoughts. Choose the type you'd like to provide:
Our feedback system is built on GitHub Issues. Read more on our blog.