The following steps create a task sequence intended to install an operating system and applications on a computer, then capture the result as a reference image. The wizard creates a number of required packages and other components if they did not exist previously. When specifying the source folder for these components, think of them as application packages. OS Deployment packages are, in fact, created as Software Deployment packages.
- Expand Operating System Deployment in the ConfigMgr console
- Right click Import Microsoft Deployment Task Sequence
- select Client Task Sequence
- Enter name for task sequence, such as "Build XPSP2 Reference"
- Details page
- Join a workgroup, select name
- Enter desired user name and Organization name
- Enter Product Key if desired
- Enter capture destination as UNC path with desired wim file name. Do NOT use a local path
- Enter account and password used to capture the image. This must have write permissions to the capture destination
- Boot image page
- Choose existing boot image or create new
- Michael Niehaus says new image is only needed if you need one of the features specified on that page, such as ADO, unknown computer support, custom background image, etc.
- If you specify an existing image, click Browse and select standard x86 or x64 image
- Or select to create new image and specify UNC path, then specify image name
- Then specify desired details
- Create new Deployment Toolkit package or select existing one
- OS Image page, choose one of the following
- Select existing WIM image (image must be created with WinPE 2.0)
- Specify existing OS install package (uses OS source files)
- Create new OS install package (point to OS source files and desired package source location)
- ConfigMgr Client Package
- Select existing ConfigMgr install package or create new one (no options used)
- Select existing USMT package or create new
- Note, required files are installed with MS Deployment
