Task Sequence Steps – Set Task Sequence Variable
This post is part of our Task Sequence – Beyond the Docs series.
Use this step to set a single task sequence variable. This step allows you assign additional attributes to the variable that the dynamic variable step does not allow.
You can have the value visable or hidden to keep it more secure in the console.
While the variable might be hidden in the console, it is not hidden to the Task Sequence, and someone with access to the machine during deployment, if F8 console access is allowed could still dump the variables and find the information.
To use these variables, you can use powershell to pull them into your scripts via the com object, or using the command line step, you can call a varable much line in Windows. %TaskSequenceVariable%
The Variables will also be shown in the SMSTS log when being used in a command line, so if you don’t want some steps to record what is going on, you can use the variable OSDDoNotLogCommand to prevent it from being recorded.
I typically never see issues when running this step, as it’s only setting a variable, and the Task Sequence really doesn’t care what variable you’re making or what you’re setting it to. The problem comes in when you’re setting a variable to trigger something later on in the process, and it never triggers. When that happens you’ll have to confirm that the step ran to create the variable and that it set it to what you’re expecting. The most common reason it doesn’t get set is due to a condition on the step itself, or in a higher-level group that the step is in. If I run into problems with not having a variable set to what I’m expecting, I’ll dump variables via a script after the step, use a pause, or enable a task sequence debugger.
More Task Sequence Steps – Beyond the Docs
Find all of our Task Sequence – Beyond the Docs series posts here.