Nesting Task Sequences
Review the nested DeployR task-sequence example that separates shared imaging steps from school-specific computer names and Autopilot group tags.
Source-derived reference
These notes were recovered from OneNote. Configuration, permissions and operating results have not been freshly verified. Confirm the applicable authority and environment before acting.
Sometimes it is necessary to have different task sequences where it isn't possible to have variables dynamically set. The source uses Cornerstone and Dunsborough as examples with different device-name prefixes and Autopilot group tags.
Rather than having task sequences the duplicate identical steps, it is useful to break out the task sequences into different functions.
The example uses a Base Task Sequence that contains all the steps that MUST be done on EVERY device, regardless. This includes things like deploying the Microsoft Connected Cache registry settings or applying BIOS updates, Clearing the TPM and diskpart cleaning the disk before imaging.
Separate task sequences are then used for Cornerstone and Dunsborough.
Each school-specific sequence contains three steps:
- Set the ComputerName variable as per standard for the school.
- Run the Base Task Sequence, which contains all the tasks required for EVERY device.
- Register with Autopilot with the school appropriate Group Tag.
Screenshot retained for review
Screenshot retained for review
The source illustrates its Base Task Sequence in the held screenshot below.
Screenshot retained for review