In this chapter, we've discussed the task sequence and how variables are utilized by the stock scripts; we also discussed how to create our own variables for different hardware configurations.
We've also looked at the structure of the
variables.dat files and
Unattend.xml file. More importantly, we've discussed the interconnectedness of
CustomSettings.ini and how it is used to variable-ize
Unattend.xml dynamically. On top of this, the task sequence itself can make
Unattend.xml values into variables as well for our deployment purposes.
We've also walked through the deployment task sequence structure and covered the gotchas, frequently used areas, and best practices.
Lastly, we've gone over monitoring, from its roots to its current incarnation of PowerShell-enabled cmdlets.
In the next chapter, we'll cover driver concepts, when drivers are applications and when they are drivers, how to handle both scenarios, and mandatory driver profiles.