This is to announce new NCSU-level base and in-place upgrade OSD task sequences that will replace the existing Windows 10 and 11 OSD task sequences.
The Windows Server and Windows LTSC OSD task sequences have not been changed at this time.
Why the change?
Previously, a base OSD task sequence template was created for college and departmental OU admins (IT admins) to copy the steps from the template to their custom OSD task sequence. This works well to get up and running quickly but when we need to make changes to task sequence properties or steps that affect everyone, making those changes to all OSD task sequences can be a cumbersome process.
Since we have the ability to run a task sequence from a task sequence, and we noticed that most departmental OSD task sequences do not modify the steps that were copied from the template, we decided to provide NCSU-level OSD task sequences that handle all the OSD steps, allowing IT admins to run the base OSD task sequence from their custom OSD task sequence and then install applications, run scripts, etc.
Also, the old OSD task sequences did not adhere to our naming convention and now they do, being prefixed with “NCSU-“.
Who’s Affected
All IT admins need to switch to the new NCSU-level OSD task sequences before Friday, June 10.
If you do not have a custom OSD task sequence the only modification needed to your SOP is to use the new OSD task sequences.
For example, if you have been using Windows 10 Education 21H2, use NCSU-Windows 10 Education 21H2 instead.
We will audit and make any necessary changes to existing custom OSD task sequences, which will likely just involve changing the OSD content package used for the OSD deployment content files.
What’s New
For unknown computers (i.e those that are not in the Config Manager database), use one of the NCSU- OSD task sequences instead of the old Windows 10|11 ones.
For known computers (i.e. computers that are in the Config Manager database), if you are using the OS Deployment groups in Active Directory, no changes are necessary. Just use the new NCSU- OSD task sequences when they are deployed.
If you are not using the OS Deployment groups in Active Directory and have deployed an old OSD task sequence to one of your collections, delete the deployment and deploy one of the new OSD task sequences.
IT admins that have a custom OSD task sequence and would like to run the new NCSU-level OSD task sequences from their task sequence can:
- Delete the steps related to OSD that were copied from the old template.
- Add a Run Task Sequence step, selecting which NCSU-level OSD task sequence to run.
The Plan
The new OSD task sequences have already been deployed to the All Unknown Computers collection and are available to use now. Which you should since they use the latest version of the driver install script that has support for Windows 11.
On Friday, May 27, 2022 the old base and upgrade OSD task sequence deployments to the NCSU-OS-Windows 10|11-* collections will be deleted and the new OSD task sequences deployed. This ensures that members of departmental OS deployment groups in Active Directory, primarily used for OSD with known computers, will get the new OSD task sequence.
On Friday, June 10, 2022 the old OSD task sequences will be deleted. If you currently have one or more deployed to a departmental collection, please delete the deployment and deploy one of the new OSD task sequences.
On Friday, June 24, 2022 the old OSD packages, and any associated content on a network share, will be deleted, along with the old template task sequences.
New Task Sequences
Base OSD
- NCSU-Windows 10 Education 20H2 OSD
- NCSU-Windows 10 Education 21H1 OSD
- NCSU-Windows 10 Education 21H2 OSD
- NCSU-Windows 11 Education 21H2 OSD
These have all the steps for OSD. i.e. disk partitioning, setting the computer name, installing the OS, etc. If you are running an NCSU-level OSD task sequence from your custom OSD task sequence, one of these is what you would choose.
They are located in Config Manager Console at Software Library > Operating Systems > Task Sequences > NCSU OSD.
Base in-place upgrade
- NCSU-Windows 10 Education 20H2 in-place upgrade
- NCSU-Windows 10 Education 21H1 in-place upgrade
- NCSU-Windows 10 Education 21H2 in-place upgrade
- NCSU-Windows 11 Education 21H2 in-place upgrade
These have all the steps for performing an in-place upgrade to a new build of Windows. They can also be ran from a custom in-place upgrade task sequence.
They are located in Config Manager Console at Software Library > Operating Systems > Task Sequences > NCSU OSD.
OSD deployments
- NCSU-Windows 10 Education 20H2
- NCSU-Windows 10 Education 21H1
- NCSU-Windows 10 Education 21H2
- NCSU-Windows 11 Education 21H2
These are the deployed OSD task sequences which have one Run Task Sequence step that runs the base OSD task sequence. They are also the task sequences you see when booted into WinPE after PXE booting, at the Select a task sequence to run dialog.
They are located in Config Manager Console at Software Library > Operating Systems > Task Sequences > NCSU OSD Deployments.
In-place upgrade deployments
- NCSU-Windows 10 Education 20H2 Upgrade
- NCSU-Windows 10 Education 21H1 Upgrade
- NCSU-Windows 10 Education 21H2 Upgrade
- NCSU-Windows 11 Education 21H2 Upgrade
These are the deployed in-place upgrade task sequences which have one Run Task Sequence step that runs the base in-place upgrade task sequence. The in-place upgrade task sequences have been updated to use the new package content. Namely, the new driver install script. These will be deployed to the same collections the old upgrade OSD task sequences are deployed to and the old ones will be deleted.
They are located in Config Manager Console at Software Library > Operating Systems > Task Sequences > NCSU OSD Deployments.
New OSD Content Packages
Packages contain the files that are downloaded during OSD. For example, the script that downloads and installs drivers and the unattend file used to customize Windows. Previously there were several packages used during OSD. Those have been consolidated to two packages, one for production and one for pre-production. This allows us to better formalize testing in pre-production before going to production.
We will update existing task sequences to use the new packages before the old ones are deleted.
More information about OSD at NC State University can be found on the Active Directory website. If you have questions, comments or would like assistance with getting your departmental OSD task sequence to use one of the new NCSU-level OSD task sequences, please email activedirectory_imaging@ncsu.edu.