Task Sequence Steps – Set Dynamic Variables
This post is part of our Task Sequence – Beyond the Docs series.
This step allows you to set several variables all at the same time. You can set several static variables, or use rules inside the step to set variables based on other criteria.
Example 1: Static
I will typically use one of these steps at the start of a task sequenced to get several things setup that will be used throughout the process. Here is an example below from my in place upgrade task sequence of items that I set in the beginning.
Some of the Variables are built in ConfigMgr variables to control the task sequence behavior, and several are custom ones I created to make rest of the process more dynamic. Like in this step below, I’m using two variables to set where the information will be written to in the registry.
Throughout the Task Sequence, I’ll leverage those variables in different steps or scripts used in the process so then when we move from 1809 to 1909 to 2009, etc, all I have to do is come in here to this SMSTS_Build variable and change it, and all of my steps and scripts are updated automatically without a need to check out the code.
Example 2: Rule Based
In this example, I have 4 unique variables that will be set to different things based on attributes of the machine it is running on. The steps themselves have conditions to run based on the manufacturer of the machine, then based on the model of the machine, it will set additional variables.
Nice to Know
This step, by just running it, will also activate several other variables that aren’t lit by default in the task sequence, including the make & model variables. This is another reason I’ll run this step at the start of the TS, to enable additional variables that can be leveraged later.
More Task Sequence Steps – Beyond the Docs
Find all of our Task Sequence – Beyond the Docs series posts here.