How to Deploy Operating Systems by Using Media in Configuration Manager
Updated: May 14, 2015
Applies To: System Center 2012 Configuration Manager, System Center 2012 Configuration Manager SP1, System Center 2012 Configuration Manager SP2, System Center 2012 R2 Configuration Manager, System Center 2012 R2 Configuration Manager SP1
Use the procedures in this topic to create capture, bootable, prestaged, and stand-alone media in your System Center 2012 Configuration Manager environment.
Important
If you use a Configuration Manager console that is not on the site server and your operating system is earlier than Windows 7, your computer must have the Configuration Manager client and Windows AIK installed. If these are not installed, the Create Task Sequence Media Wizard fails.
Use the following sections to help you capture an operating system image or deploy an operating system by using the different types of media:
How to Create Capture Media
How to Create Bootable Media
How to Create Prestaged Media
How to Create Stand-alone Media
For planning information, see Planning for Media Operating System Deployments in Configuration Manager.
How to Create Capture Media
Use capture media to capture an operating system image from a reference computer. Capture media contains the boot image that starts the reference computer and the task sequence that captures the operating system image. For more information about capture media, see the Capture Media for Operating System Images section in the Planning for Media Operating System Deployments in Configuration Manager topic.
You create capture media by using the Create Task Sequence Media Wizard. Before you run the wizard, be sure that all the following conditions are met:
The boot image used to start the reference computer must be distributed to a distribution point. In addition, the architecture of the boot image that is distributed must be appropriate for the architecture of the reference computer. For example, an x64 reference computer can boot and run an x86 or x64 boot image. However, an x86 reference computer can boot and run only an x86 boot image.
To run the Create Task Sequence Media Wizard, you must have read access rights to the content library on the distribution point where the boot image is located. The wizard retrieves the boot image from the distribution point when it creates the media.
When you create capture media for a USB flash drive, the flash drive must be connected to the computer where the wizard is run, and the USB flash drive must be detectable by Windows as a removal device. The wizard writes directly to the flash drive when it creates the media.
Important
If the administrative user needs to start the USB flash drive media from within an existing Windows Vista and later operating system, they need to manually run the TSMBAutorun.exe program.
The TSMBAutorun.exe program is located in the following folder:
\sms\bin\<architecture folder>\TSMBAutorun.exe
Before you run the Create Task Sequence Media Wizard to create media for a CD or DVD set, you must create a folder for the output files created by the wizard. Media that is created for a CD or DVD set is written as .iso files directly to the folder. If multiple media is needed the wizard adds a sequence number to the name of each output file that is created.
Use the following procedure to create capture media.
To create capture media
-
In the Configuration Manager console, click Software Library.
-
In the Software Library workspace, expand Operating Systems, and then click Task Sequences.
-
On the Home tab, in the Create group, click Create Task Sequence Media to start the Create Task Sequence Media Wizard.
-
On the Select Media Type page, select Capture media, and then click Next.
-
On the Media Type page, specify the following options, and then click Next.
- Select whether the media is a flash drive or a CD/DVD set. - If you select **USB flash drive**, you must also specify the drive where you want the content stored. - If you select **CD/DVD set**, specify the capacity of the media and the name and path of the output files. The wizard writes the output files to this location. For example: **\\\\servername\\folder\\outputfile.iso** If the capacity of the media is too small to store the entire content, you must store the content on multiple CDs or DVDs. When multiple media is required, Configuration Manager automatically adds a sequence number to the name of each output file that it creates. <div class="alert"> > [!NOTE] > <P>If you select an existing .iso image, the Task Sequence Media Wizard deletes that image from the drive or share as soon as you proceed to the next page of the wizard. The existing image is deleted even if you then cancel the wizard.</P> </div> -
On the Boot image page, specify the following information, and then click Next.
Important
The architecture of the boot image that you specify must be appropriate for the architecture of the reference computer. For example, an x64 reference computer can boot and run an x86 or x64 boot image. However, an x86 reference computer can boot and run only an x86 boot image.
- In the **Boot image** box, specify the boot image to start the reference computer. - In the **Distribution point** box, specify the distribution point where the boot image resides. The wizard retrieves the boot image from the distribution point and writes it to the media. <div class="alert"> > [!NOTE] > <P>You must have Read access rights to the content library on the distribution point.</P> </div> -
Complete the wizard.
How to Create Bootable Media
Bootable media contains only the boot image, optional prestart commands and their required files, and Configuration Manager binaries. For more information about bootable media, see the Bootable Media Operating System Deployments section in the Planning for Media Operating System Deployments in Configuration Manager topic.
You create bootable media by using the Create Task Sequence Media Wizard. Before you run the wizard, be sure that all the following conditions are met:
The boot image used to start the destination computer must be distributed to a distribution point. In addition, the architecture of the boot image that is distributed must be appropriate for the architecture of the destination computer. For example, an x64 destination computer can boot and run an x86 or x64 boot image. However, an x86 destination computer can boot and run only an x86 boot image.
To run the Create Task Sequence Media Wizard, you must have read access rights to the content library on the distribution point where the boot image is located. The wizard retrieves the boot image from the distribution point when it creates the media.
When you create bootable media for a USB flash drive, the flash drive must be connected to the computer where the wizard is run, and the USB flash drive must be detectable by Windows as a removal device. The wizard writes directly to the flash drive when it creates the media.
Important
If the administrative user needs to start the USB flash drive media from within an existing Windows Vista and later operating system, they need to manually run the TSMBAutorun.exe program.
The TSMBAutorun.exe program is located in the following folder:
\sms\bin\<architecture folder>\TSMBAutorun.exe
Before you run the Create Task Sequence Media Wizard to create media for a CD or DVD set, you must create a folder for the output files created by the wizard. Media that is created for a CD or DVD set is written as .iso files directly to the folder. If multiple media is needed the wizard adds a sequence number to the name of each output file that is created.
Use the following procedure to create bootable media.
To create bootable media
-
In the Configuration Manager console, click Software Library.
-
In the Software Library workspace, expand Operating Systems, and then click Task Sequences.
-
On the Home tab, in the Create group, click Create Task Sequence Media to start the Create Task Sequence Media Wizard.
-
On the Select Media Type page, specify the following options, and then click Next.
- Select **Bootable media**. - Optionally, if you want to only allow the operating system to be deployed without requiring user input, select **Allow unattended operating system deployment**. <div class="alert"> > [!IMPORTANT] > <P>When you select this option, the user is not prompted for network configuration information or for optional task sequences. However, the user is still prompted for a password if the media is configured for password protection.</P> </div> -
On the Media Management page, specify one of the following options, and then click Next.
- Select **Dynamic media** if you want to allow a management point to redirect the media to another management point, based on the client location in the site boundaries. - Select **Site-based media** if you want the media to contact only the specified management point. -
On the Media Type page, specify the following options, and then click Next.
- Select whether the media is a flash drive or a CD/DVD set. - If you select **USB flash drive**, you must also specify the drive where you want the content stored. - If you select **CD/DVD set**, specify the capacity of the media and the name and path of the output files. The wizard writes the output files to this location. For example: **\\\\servername\\folder\\outputfile.iso** If the capacity of the media is too small to store the entire content, you must store the content on multiple CDs or DVDs. When multiple media is required, Configuration Manager adds a sequence number to the name of each output file that it creates. <div class="alert"> > [!NOTE] > <P>If you select an existing .iso image, the Task Sequence Media Wizard deletes that image from the drive or share as soon as you proceed to the next page of the wizard. The existing image is deleted even if you then cancel the wizard.</P> </div> -
On the Security page, specify the following options, and then click Next.
- Select the **Enable unknown computer support** check box to allow the media to deploy an operating system to a computer that is not managed by Configuration Manager. There is no record of these computers in the Configuration Manager database. Unknown computers include the following: - A computer where the Configuration Manager client is not installed - A computer that is not imported into Configuration Manager - A computer that is not discovered by Configuration Manager - Select the **Protect the media with a password** check box and enter a strong password to help protect the media from unauthorized access. When you specify a password, the user must provide that password to use the bootable media. <div class="alert"> > [!IMPORTANT] > <P>As a security best practice, always assign a password to help protect the bootable media.</P> </div> - For HTTP communications, select **Create self-signed media certificate**, and then specify the start and expiration date for the certificate. - For HTTPS communications, select **Import PKI certificate**, and then specify the certificate to import and its password. For more information about this client certificate that is used for boot images, see [PKI Certificate Requirements for Configuration Manager](gg699362\(v=technet.10\).md). - **User Device Affinity**: To support user-centric management in Configuration Manager, specify how you want the media to associate users with the destination computer. For more information about how operating system deployment supports user device affinity, see [How to Associate Users with a Destination Computer](hh846243\(v=technet.10\).md). - Specify **Allow user device affinity with auto-approval** if you want the media to automatically associate users with the destination computer. This functionality is based on the actions of the task sequence that deploys the operating system. In this scenario, the task sequence creates a relationship between the specified users and destination computer when it deploys the operating system to the destination computer. - Specify **Allow user device affinity pending administrator approval** if you want the media to associate users with the destination computer after approval is granted. This functionality is based on the scope of the task sequence that deploys the operating system. In this scenario, the task sequence creates a relationship between the specified users and the destination computer, but waits for approval from an administrative user before the operating system is deployed. - Specify **Do not allow user device affinity** if you do not want the media to associate users with the destination computer. In this scenario, the task sequence does not associate users with the destination computer when it deploys the operating system. -
On the Boot image page, specify the following options, and then click Next.
Important
The architecture of the boot image that is distributed must be appropriate for the architecture of the destination computer. For example, an x64 destination computer can boot and run an x86 or x64 boot image. However, an x86 destination computer can boot and run only an x86 boot image.
- In the **Boot image** box, specify the boot image to start the destination computer. - In the **Distribution point** box, specify the distribution point where the boot image resides. The wizard retrieves the boot image from the distribution point and writes it to the media. <div class="alert"> > [!NOTE] > <P>You must have Read access rights to the content library on the distribution point.</P> </div> - If you create site-based bootable media (you selected **Site-based media** on the **Media Management** page of the wizard), in the **Management point** box, specify a management point from a primary site. - If you create dynamic bootable media (you selected **Dynamic media** on the **Media Management** page of the wizard), in the **Associated management points** box, specify the primary site management points to use, and a priority order for the initial communications. -
On the Customization page, specify the following options, and then click Next.
- Specify the variables that the task sequence uses to deploy the operating system. - Specify any prestart commands that you want to run before the task sequence runs. Prestart commands are a script or an executable that can interact with the user in Windows PE before the task sequence runs to install the operating system. For more information about prestart commands for media, see the [Prestart Commands for Task Sequence Media in Configuration Manager](jj651034\(v=technet.10\).md) topic. <div class="alert"> > [!TIP] > <P>During task sequence media creation, the task sequence writes the package ID and prestart command-line, including the value for any task sequence variables, to the CreateTSMedia.log log file on the computer that runs the Configuration Manager console. You can review this log file to verify the value for the task sequence variables.</P> </div> Optionally, select the **Files for the prestart command** check box to include any required files for the prestart command. -
Complete the wizard.
How to Create Prestaged Media
Prestaged media contains the boot image and operating system image that you can use to provision a computer. However prestaged media does not contain the task sequence that is used in the deployment process. For more information about prestaged media, see the Prestaged Media Operating System Deployments section in the Planning for Media Operating System Deployments in Configuration Manager topic.
You create prestaged media by using the Create Task Sequence Media Wizard. Before you run the wizard, be sure that all the following conditions are met:
The boot image used to start the destination computer must be distributed to a distribution point. In addition, the architecture of the boot image that is distributed must be appropriate for the architecture of the destination computer. For example, an x64 destination computer can boot and run an x86 or x64 boot image. However, an x86 destination computer can boot and run only an x86 boot image.
To run the Create Task Sequence Media Wizard, you must have read access rights to the content library on the distribution point where the boot image and operating system image are located. The wizard retrieves the boot images from the distribution points when it creates the media.
Ensure that the boot image contains the network and mass storage drivers that are required to provision the destination computer.
The package that contains the operating system image that is deployed to the destination computer must be distributed to a distribution point.
In the task sequence used by the media, do not set a condition for the Apply Operating System action.
The hard drive of the destination computer must be formatted before the prestaged media is staged onto the hard drive of the computer. If the hard drive is not formatted when the media is applied, the task sequence that deploys the operating system will fail when it attempts to start the destination computer.
Note
The Create Task Sequence Media Wizard sets the following task sequence variable condition on the media: _SMSTSMedia = OEMMedia. You can use this condition throughout your task sequence.
Use the following procedure to create prestaged media.
To create prestaged media
-
In the Configuration Manager console, click Software Library.
-
In the Software Library workspace, expand Operating Systems, and then click Task Sequences.
-
On the Home tab, in the Create group, click Create Task Sequence Media to start the Create Task Sequence Media Wizard.
-
On the Select Media Type page, specify the following information, and then click Next.
- Select **Prestaged media**. - Optionally, if you want to allow the operating system to be deployed without requiring user input, select **Allow unattended operating system deployment**. When you select this option the user is not prompted for network configuration information or for optional task sequences. However, the user is still prompted for a password if the media is configured for password protection. -
On the Media Management page, specify the following information, and then click Next.
- Select **Dynamic media** if you want to allow a management point to redirect the media to another management point, based on the client location in the site boundaries. - Select **Site-based media** if you want the media to contact only the specified management point. -
On the Media Properties page, specify the following information, and then click Next.
- **Created by**: Specify who created the media. - **Version**: Specify the version number of the media. - **Comment**: Specify a unique description of what the media is used for. - **Media file**: Specify the name and path of the output files. The wizard writes the output files to this location. For example: **\\\\servername\\folder\\outputfile.wim** -
On the Security page, specify the following information, and then click Next.
- Select the **Enable unknown computer support** check box to allow the media to deploy an operating system to a computer that is not managed by Configuration Manager. There is no record of these computers in the Configuration Manager database. Unknown computers include the following: - A computer where the Configuration Manager client is not installed - A computer that is not imported into Configuration Manager - A computer that is not discovered by Configuration Manager - Select the **Protect the media with a password** check box and enter a strong password to help protect the media from unauthorized access. When you specify a password, the user must provide that password to use the prestaged media. <div class="alert"> > [!IMPORTANT] > <P>As a security best practice, always assign a password to help protect the prestaged media.</P> </div> - For HTTP communications, select **Create self-signed media certificate**, and then specify the start and expiration date for the certificate. - For HTTPS communications, select **Import PKI certificate**, and then specify the certificate to import and its password. For more information about this client certificate that is used for boot images, see [PKI Certificate Requirements for Configuration Manager](gg699362\(v=technet.10\).md). - **User Device Affinity**: To support user-centric management in Configuration Manager, specify how you want the media to associate users with the destination computer. For more information about how operating system deployment supports user device affinity, see [How to Associate Users with a Destination Computer](hh846243\(v=technet.10\).md). - Specify **Allow user device affinity with auto-approval** if you want the media to automatically associate users with the destination computer. This functionality is based on the actions of the task sequence that deploys the operating system. In this scenario, the task sequence creates a relationship between the specified users and destination computer when it deploys the operating system to the destination computer. - Specify **Allow user device affinity pending administrator approval** if you want the media to associate users with the destination computer after approval is granted. This functionality is based on the scope of the task sequence that deploys the operating system. In this scenario, the task sequence creates a relationship between the specified users and the destination computer, but waits for approval from an administrative user before the operating system is deployed. - Specify **Do not allow user device affinity** if you do not want the media to associate users with the destination computer. In this scenario, the task sequence does not associate users with the destination computer when it deploys the operating system. -
On the Boot image page, specify the following information, and then click Next.
Important
The architecture of the boot image that is distributed must be appropriate for the architecture of the destination computer. For example, an x64 destination computer can boot and run an x86 or x64 boot image. However, an x86 destination computer can boot and run only an x86 boot image.
- In the **Boot image** box, specify the boot image to start the destination computer. - In the **Distribution point** box, specify the distribution point where the boot image resides. The wizard retrieves the boot image from the distribution point and writes it to the media. <div class="alert"> > [!NOTE] > <P>You must have Read access rights to the content library on the distribution point.</P> </div> - If you create site-based bootable media (you selected **Site-based media** on the **Media Management** page of the wizard), in the **Management point** box, specify a management point from a primary site. - If you create dynamic bootable media (you selected **Dynamic media** on the **Media Management** page of the wizard), in the **Associated management points** box, specify the primary site management points to use and a priority order for the initial communications. -
On the Images page, specify the following information, and then click Next.
- In the **Image package** box, specify the package that contains the operating system image. - If the package contains multiple operating system images, in the **Image index** box, specify the image to deploy. - In the **Distribution point** box, specify the distribution point where the operating system image package resides. The wizard retrieves the operating system image from the distribution point and writes it to the media. <div class="alert"> > [!NOTE] > <P>You must have Read access rights to the content library on the distribution point.</P> </div> -
On the Customization page, specify the following information, and then click Next.
Specify the variables that the task sequence uses to deploy the operating system.
Specify any prestart commands that you want to run before the task sequence runs. Prestart commands are a script or an executable that can interact with the user in Windows PE before the task sequence runs to install the operating system. For more information about prestart commands for media, see the Prestart Commands for Task Sequence Media in Configuration Manager topic.
Tip
During task sequence media creation, the task sequence writes the package ID and prestart command-line, including the value for any task sequence variables, to the CreateTSMedia.log log file on the computer that runs the Configuration Manager console. You can review this log file to verify the value for the task sequence variables.
-
Complete the wizard.
How to Create Stand-alone Media
Stand-alone media contains all the necessary information to deploy the operating system without requiring a connection to a Configuration Manager site. For more information about stand-alone media, see the Stand-Alone Media Operating System Deployments section in the Planning for Media Operating System Deployments in Configuration Manager topic.
You create stand-alone media by using the Create Task Sequence Media Wizard. Before you run the wizard, be sure that all the following conditions are met:
You must have a task sequence that is associated with a boot image.
Content that is required by the task sequence must be distributed to a distribution point and you must have Read access rights to the content library of that distribution point. The wizard gathers the information from the distribution point when it creates the stand-alone media.
When you create stand-alone media for a USB flash drive, the flash drive must be connected to the computer where the wizard is run, and the USB flash drive must be detectable by Windows as a removal device. The wizard writes directly to the flash drive when it creates the media.
Important
If the administrative user needs to start the USB flash drive media from within an existing Windows Vista and later operating system, they need to manually run the TSMBAutorun.exe program.
The TSMBAutorun.exe program is located in the following folder:
\sms\bin\<architecture folder>\TSMBAutorun.exe
Before you run the Create Task Sequence Media Wizard to create media for a CD or DVD set, you must create a folder for the output files created by the wizard. Media that is created for a CD or DVD set is written as .iso files directly to the folder. If multiple media is needed the wizard adds a sequence number to the name of each output file that is created.
Configuration Manager does not support the following actions for stand-alone media:
Automatic application of device drivers from the driver catalog.
Installing software updates.
Installing software before an operating system deployment.
Associating users with the destination computer to support user device affinity.
With System Center 2012 Configuration Manager SP1 or earlier: Installing dependencies for applications that are specified as part of the task sequence is not supported. Beginning with System Center 2012 R2 Configuration Manager this is supported.
Dynamic package installs via the Install Packages task.
Dynamic application installs via the Install Application task.
Use the following procedure to create stand-alone media for a USB flash drive or a CD/DVD set.
To create stand-alone media
-
In the Configuration Manager console, click Software Library.
-
In the Software Library workspace, expand Operating Systems, and then click Task Sequences.
-
On the Home tab, in the Create group, click Create Task Sequence Media to start the Create Task Sequence Media Wizard.
-
On the Select Media Type page, specify the following options, and then click Next.
- Select **Stand-alone media**. - Optionally, if you want to allow the operating system to be deployed without requiring user input, select **Allow unattended operating system deployment**. When you select this option the user is not prompted for network configuration information or for optional task sequences. However, the user is still prompted for a password if the media is configured for password protection. -
On the Media Type page, specify the following options, and then click Next.
Important
Stand-alone media uses a FAT32 file system. You cannot create stand-alone media on a USB flash drive whose content contains a file over 4 GB in size.
- Select whether the media is a flash drive or a CD/DVD set. - If you select **USB flash drive**, you must also specify the drive where you want to store the content. - If you select CD/DVD set, specify the capacity of the media and the name and path of the output files. The wizard writes the output files to this location. For example: **\\\\servername\\folder\\outputfile.iso** If the capacity of the media is too small to store the entire content, you must store the content on multiple CDs or DVDs. When multiple media is required, Configuration Manager adds a sequence number to the name of each output file that it creates. In addition, if you deploy an application along with the operating system and the application cannot fit on a single media, Configuration Manager stores the application across multiple media. When the stand-alone media is run, Configuration Manager prompts the user for the next media where the application is stored. <div class="alert"> > [!NOTE] > <P>If you select an existing .iso image, the Task Sequence Media Wizard deletes that image from the drive or share as soon as you proceed to the next page of the wizard. The existing image is deleted, even if you then cancel the wizard.</P> </div> -
On the Security page, enter a strong password to help protect the media, and then click Next. If you specify a password, the password is required to use the media.
Important
On stand-alone media, only the task sequence steps and their variables are encrypted. The remaining content of the media is not encrypted, so do not include any sensitive information in task sequence scripts. Store and implement all sensitive information by using task sequence variables.
-
On the Stand-Alone CD/DVD page, specify the task sequence that deploys the operating system, and then click Next. The wizard lets you select only those task sequences that are associated with a boot image.
-
On the Distribution Points page, specify the distribution points that contain packages that are required by the task sequence, and then click Next.
Note
You must have Read access rights to the content library on the distribution points.
-
On the Customization page, specify the following information, and then click Next.
- Specify the variables that the task sequence uses to deploy the operating system. - Specify any prestart commands that you want to run before the task sequence. Prestart commands are a script or an executable that can interact with the user in Windows PE before the task sequence runs to install the operating system. For more information about prestart commands for media, see the [Prestart Commands for Task Sequence Media in Configuration Manager](jj651034\(v=technet.10\).md) topic. Optionally, select the **Files for the prestart command** check box to include any required files for the prestart command. <div class="alert"> > [!TIP] > <P>During task sequence media creation, the task sequence writes the package ID and prestart command-line, including the value for any task sequence variables, to the CreateTSMedia.log log file on the computer that runs the Configuration Manager console. You can review this log file to verify the value for the task sequence variables.</P> </div> -
Complete the wizard.