Note |
The information in this topic applies only to System Center
2012 Configuration Manager SP1. |
Operating system deployment provides
System Center 2012 Configuration Manager
administrative users with a tool for creating operating system
images that they can deploy to computers that are managed by
Configuration Manager. This topic shows how you can create a
reference operating system image, partition computers differently
based on whether the computer starts in UEFI mode or BIOS mode, and
deploy Windows 8 to computers that are managed by
Configuration Manager
Scenario Overview
This scenario represents one way to deploy
Windows 8 to computers based on specific assumptions and
business requirements. The following table provides an outline of
the sections that make up this scenario.
Technical Requirements
This scenario requires the following technical
requirements:
- All sites in the Configuration Manager
hierarchy are running Configuration Manager SP1 and are fully
functional.
- PXE-enabled distribution points are
configured and available to select as the content location for task
sequence content. For more information about how to configure the
distribution point to support PXE, see the Planning for
PXE-Initiated Operating System Deployments in Configuration
Manager topic.
- Windows Assessment and Deployment Kit
(Windows ADK) for Windows 8 is installed on all site servers
and computers that have the SMS Provider site system role. For more
information about Windows ADK, see Windows Deployment with the Windows
ADK.
- All computers that are managed by
Configuration Manager have x64 system architecture.
- The computers that are managed by
Configuration Manager have either firmware that meets the Unified
Extensible Firmware Interface (UEFI) 2.3.1 specifications or a BIOS
firmware interface. For more information about UEFI, see the
Unified EFI Forum website.
- All computers that are managed by
Configuration Manager have Trusted Platform Module (TPM) enabled.
The task sequence steps that support BitLocker require TPM.
Business Requirements
This scenario accommodates the following business
requirements:
- Create a single task sequence to deploy
Windows 8 to computers that have firmware that meets the UEFI
specifications or a BIOS firmware interface.
- The deployment for Windows 8 will be
PXE-initiated only.
- Install all mandatory software updates with
the Windows 8 deployment.
- Enable BitLocker on all computers that
install Windows 8.
Pre-Deployment Considerations
Before you deploy Windows 8 to Configuration
Manager clients, consider the following pre-deployment steps
- Windows 8 upgrade assessment: The
Microsoft System Center 2012
Configuration Manager Upgrade Assessment Tool gives you
information that you can use to determine whether the hardware and
software on computers that are managed by Configuration Manager are
compatible with Windows 8. The Upgrade Assessment Tool provides the
following functionality:
- Retrieves device driver compatibility for
installed peripheral devices and creates reports that you can use
to determine which device drivers have to be upgraded to support
the Windows operating system.
- Lets you see which computers meet the
recommended system requirements for Windows operating systems and
to customize these requirements for your environments.
- Creates summary reports that you can use to
see an enterprise wide view of operating system upgrade
readiness.
- Lets you create dynamic collections for an
operating system deployment. The collection query rules can be
based on system requirements, application compatibility status, and
device driver status.
Download the Upgrade Assessment Tool from the Microsoft Download Center site.
For more information, see Configuration Manager Upgrade Assessment
Tool.
- UEFI-based computers: Before you
install Windows 8 on a UEFI-based computer, note the
following.
- All computers that are certified for
Windows 8 use firmware that meets the UEFI specifications.
- For some computers, you might have to perform
additional steps to make sure that Windows is installed in UEFI
mode, and not in legacy BIOS-compatibility mode. It is not
supported to switch from legacy BIOS-compatibility mode to UEFI
mode by using a task sequence. For more information, see How to Switch from BIOS-Compatibility Mode
to UEFI Mode.
- Some computers might support UEFI. However,
they do not support a PXE-initiated boot when in UEFI mode. To
provision these computers in UEFI mode, you must start them from
boot media instead of using PXE. If the computer performs a
PXE-initiated boot, Configuration Manager detects that the computer
is in BIOS mode and therefore provisions the computer as such. For
more information about how to create boot media, see the
How to Create Bootable Media section in the How to Deploy Operating
Systems by Using Media in Configuration Manager topic.
- UEFI and BIOS have different disk
partitioning requirements. UEFI hard disks require the GUID
partition table (GPT) partition structure, instead of the master
boot record (MBR) partition structure that is used in BIOS. When
you use a task sequence to deploy Windows 8, the task sequence
detects whether the computer was started in UEFI mode or
BIOS-compatibility mode, and the task sequence configures the
partitions on the hard disk to accommodate the associated
requirements.
Step 1: Prepare and Deploy the Boot
Image
A boot image contains a version of Windows PE that
provides a boot environment for a computer. Windows PE is a minimal
operating system with limited components and services that prepare
the destination computer for Windows installation. In this
scenario, after a computer starts in Windows PE, Configuration
Manager begins the Windows 8 installation. You can use the steps in
this section to prepare and deploy the boot image that you will use
in your Windows 8 deployment task sequence. This section
consists of the following steps:
For more information about how to manage boot images,
see the How to
Manage Boot Images in Configuration Manager topic.
Step 1a: Prepare the Boot Image
Configuration Manager provides two boot images: One to
support the x86 architecture and one to support the x64
architecture. For computers that start in UEFI mode, you must use a
boot image that matches the architecture of the computer; that is,
x86 for x86-based computers or x64-based computers. You cannot use
an x86 boot image for both architectures for computers that boot in
UEFI mode in the same manner that you can for computers that boot
in BIOS. For this scenario, only x64-based computers are in the
environment. Therefore, this scenario uses the default x64 boot
image (Boot image (x64)).
Important |
Configuration Manager does not support a PXE-initiated startup
for computers that have the IA-32 architecture. |
The default boot image contains standard device drivers
and might be sufficient for your deployment. However, you can
customize the boot image with one or more of the following
configurations:
- Image properties
- Drivers
- Prestart command settings
- Windows PE background image
- Command shell support
- Windows PE scratch space
- Optional components to use in Windows PE
For more information about how to change the boot
image, see the
How to Modify a Boot Image section in the topic, How to Manage Boot
Images in Configuration Manager.
Step 1b: Distribute the Boot
Image
After you prepare the boot image, you must distribute
the image to all PXE-enabled distribution points. When the task
sequence is run by a client, the client downloads the boot image
from the distribution point. You distribute boot images to
distribution points in the same way that you distribute other
content. You can specify single distribution points, distribution
point groups, or collections that are associated with distribution
point groups. For more information about distributing content in
Configuration Manager, see the Distribute
Content on Distribution Points section in the Operations and
Maintenance for Content Management in Configuration Manager
topic.
Follow these steps to distribute the boot image to
distribution points.
To distribute the boot image to
distribution points
-
In the Configuration Manager console, click Software
Library.
-
In the Software Library workspace, expand
Operating Systems, and then click Boot Images.
-
In the Boot Images node, select the boot image
objects that you want to deploy.
-
On the Home tab, in the Deployment group,
click Distribute Content to start the Distribute Content
Wizard.
-
On the General page, verify that the content
listed is the content that you want to distribute, and then click
Next.
-
On the Content Destination page, click
Add, choose one of the following, and then follow the
associated step:
- Collections: Select User
Collections or Device Collections, click the collection
associated with one or more distribution point groups, and then
click OK.
- Distribution Point: Select an existing
distribution point, and then click OK. Distribution points
that have previously received the content are not displayed.
- Distribution Point Group: Select an
existing distribution point group, and then click OK.
Distribution point groups that have previously received the content
are not displayed.
When you finish adding content destinations, click
Next.
-
On the Summary page, review the settings for the
distribution before you continue. To distribute the content to the
selected destinations, click Next.
-
The Progress page displays the progress of the
distribution.
-
The Confirmation page displays whether the
content was successfully assigned to the points. For more
information about how to monitor the content distribution, see the
Monitor
Content section in the Operations and
Maintenance for Content Management in Configuration Manager
topic.
Step 2: Build and Capture a
Reference Operating System Image
Operating system images are WIM files and represent a
compressed collection of reference files and folders that are
required to successfully install and configure an operating system
on a computer. You can use the steps in this section to import the
base operating system image (install.wim) located on the
Windows 8 installation media. Then, you create a task sequence
that installs Windows 8, mandatory software updates, and
applications to a reference computer. You deploy the task sequence
to a reference computer and the task sequence captures a new
reference operating system image and stores it on a network shared
folder. Finally, you can configure Configuration Manager to apply
mandatory software updates to the operating system image on a
schedule that you specify. This section consists of the following
steps:
For more information about how to build and capture a
reference operating system image, see the How
to Create Task Sequences section in the How to Manage Task
Sequences in Configuration Manager topic.
Step 2a: Add the Windows 8 Operating
System Image
You must add a Windows 8 operating system image to
the Configuration Manager console before you can build the
reference operating system image.
Follow these steps to add the Windows 8 operating
system image to the Configuration Manager console.
To add the Windows 8 operating
system image
-
In the Configuration Manager console, click Software
Library.
-
In the Software Library workspace, expand
Operating Systems, and then click Operating System
Images.
-
On the Home tab, in the Create group,
click Add Operating System Image to start the Add Operating
System Image Wizard.
-
On the Data Source page, specify the network
path to the Windows 8 operating system image. For example,
specify
\\MyServer\MyShare\Window8InstallationFiles\sources\install.wim.
-
On the General page, specify the following
information, and then click Next.
- Name: Specify the name of the image.
By default, the name of the image is taken from the WIM file.
- Version: Specify the version of the
image.
- Comment: Specify a brief description
of the image.
-
Complete the wizard.
Step 2b: Create a Build and Capture
Task Sequence
The build and capture task sequence is run on a
reference computer where the task sequence creates an operating
system image that is based on a set of operating system source
files. The task sequence uses the Windows 8 operating system
image that you added in Step 2a: Add the
Windows 8 Operating System Image to install Windows 8 on
the reference computer. Then, the task sequence adds software
updates, applications, and custom settings to the reference
computer. Finally, the task sequence captures a new Windows 8
image from the reference computer and stores it on a network shared
folder.
Follow these steps to create the build and capture task
sequence.
To create a task sequence that builds
and captures an operating system image
-
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 to start the Create Task Sequence
Wizard.
-
On the Create a New Task Sequence page, select
Build and capture a reference operating system image, and
then click Next.
-
On the Task Sequence Information page, specify
the following settings, and then click Next.
- Task sequence name: Specify a name
that identifies the task sequence.
- Description: Specify a description of
the task that is performed by the task sequence, such as a
description of the operating system that is created by the task
sequence.
- Boot image: Specify the default x64
boot image (Boot image (x64)).
-
On the Install Windows page, specify the
following settings, and then click Next.
- Image package: Click Browse,
select the Windows 8 operating system image that you added in
Step 2a: Add the Windows 8 Operating System
Image, and then click OK.
- Product key: Specify the product key
for the Windows operating system to install. You can specify
encoded volume license keys or standard product keys. If you use a
non-encoded product key, each group of 5 characters must be
separated by a dash (-). For example:
XXXXX-XXXXX-XXXXX-XXXXX-XXXXX
- Server licensing mode: Specify that
the server license is Per seat, Per server, or that
no license is specified. If the server license is Per
server, you must also specify the maximum number of server
connections.
- Specify how to handle the administrator
account that is used when the operating system is deployed.
- Disable local administrator account:
Specify whether the local administrator account is disabled when
the operating system is deployed.
- Always use the same administrator
password: Specify whether the same password is used for the
local administrator account on all computers where the operating
system is deployed.
-
On the Configure Network page, specify the
following settings, and then click Next.
- Join a workgroup: Specify whether to
add the destination computer to a workgroup when the operating
system is deployed.
- Join a domain: Specify whether to add
the destination computer to a domain when the operating system is
deployed. In Domain, specify the name of the domain.
Important |
You can browse to locate domains in the local forest. However,
you must specify the domain name for a remote forest. |
You can also specify an organizational unit (OU). This is an
optional setting that specifies the LDAP X.500-distinguished name
of the OU in which to create the computer account if it does not
already exist.
- Account: Specify the user name and
password for the account that has permissions to join the specified
domain. For example: domain\user or %variable%.
Important |
You must enter the appropriate domain credentials if you plan
to migrate either the domain settings or the workgroup
settings. |
-
On the Install Configuration Manager page,
verify that the Configuration Manager client package is selected,
add any additional properties to use for client installation, and
then click Next.
For more information about properties that can be used
to install a client, see About Client
Installation Properties in Configuration Manager.
-
On the Include Updates page, specify
Mandatory software updates. Configuration Manager installs
only the software updates that target the collections for which the
destination computer is a member.
-
On the Install Applications page, specify the
applications to install on the destination computer, and then click
Next. If you specify multiple applications, you can also
specify that the task sequence continues if the installation of a
specific application fails.
-
On the System Preparation page, click
Next. Sysprep is automatically available on Windows 8
and you do not have to specify a package.
-
On the Images Properties page, specify the
following settings for the operating system image, and then click
Next.
- Created by: Specify the name of the
user who created the operating system image.
- Version: Specify a user-defined
version number that is associated with the operating system
image.
- Description: Specify a user-defined
description of the operating system computer image.
-
On the Capture Image page, specify the following
settings, and then click Next.
- Path: Specify a shared network folder
where the output .WIM file is stored. This file contains the
operating system image that is based on the settings that you
specify in the wizard. Configuration Manager overwrites a .WIM file
with the same name, if it exists.
- Use the following account to access the
output folder: Specify the Windows account that has Read
and Write permissions to the output shared network
folder.
-
Complete the wizard.
Step 2c: Distribute the Task
Sequence Content
Before the reference computer can run the task sequence
to build and capture the reference operating system task sequence,
you must distribute that content to distribution points.
Follow these steps to distribute the content that is
referenced by a task sequence.
To distribute the task sequence
content to distribution points
-
In the Configuration Manager console, click Software
Library.
-
In the Software Library workspace, expand
Operating Systems, and then click Task Sequences.
-
In the Task Sequences node, select the task
sequence that you created in step 2b.
-
On the Home tab, in the Deployment group,
click Distribute Content to start the Distribute Content
Wizard.
-
On the General page, verify that the content
listed is the content that you want to distribute, and then click
Next.
-
On the Content Destination page, click
Add, choose one of the following, and then follow the
associated step:
- Collections: Select User
Collections or Device Collections, click the collection
associated with one or more distribution point groups, and then
click OK.
- Distribution Point: Select an existing
distribution point, and then click OK. Distribution points
that have previously received the content are not displayed.
- Distribution Point Group: Select an
existing distribution point group, and then click OK.
Distribution point groups that have previously received the content
are not displayed.
When you finish adding content destinations, click
Next.
-
On the Summary page, review the settings for the
distribution before you continue. To distribute the content to the
selected destinations, click Next.
-
The Progress page displays the progress of the
distribution.
-
The Confirmation page displays whether the
content was successfully assigned to the distribution points. For
more information about how to monitor the content distribution, see
the Monitor
Content section in the Operations and
Maintenance for Content Management in Configuration Manager
topic.
Step 2d: Deploy the Build and
Capture Task Sequence
Now that you created the task sequence to build and
capture the reference operating system and the content is available
on a distribution point, you must deploy it to the reference
computer. When the task sequence runs on the reference computer,
the computer starts in Windows PE. Then, the task sequence
partitions and formats the hard disk on the reference computer,
installs Windows 8, installs software updates and
applications, and then creates a new reference Windows 8 operating
system image that you will use to deploy Windows 8.
Follow these steps to deploy the task sequence to the
reference computer.
To deploy the task sequence to build
and capture the reference operating system image
-
In the Configuration Manager console, click Software
Library.
-
In the Software Library workspace, expand
Operating Systems, and then click Task Sequences.
-
In the Task Sequence list, select the task
sequence that you created in Step 2b: Create
a Build and Capture Task Sequence.
-
On the Home tab, in the Deployment group,
click Deploy.
-
On the General page, specify the following
information, and then click Next.
- Task sequence: Verify that the correct
task sequence is selected.
- Collection: Specify the collection
that contains the reference computer.
Important |
Verify that the collection you select contains only the
reference computer that will run the task sequence. |
- Comments (optional): Specify
additional information that describes this deployment of the task
sequence.
-
On the Deployment Settings page, specify the
following information, and then click Next.
- Purpose: Choose Available from
the drop-down list.
- Specify when to make this task sequence
available. For this scenario, choose Only media and PXE to
have the task sequence available when you use the pre-execution
environment (PXE) to initiate the task sequence deployment.
-
On the Scheduling page, specify the following
information, and then click Next.
Specify the current date and time for Schedule when
this deployment will become available, and then click
Next.
- Schedule when this deployment will become
available: Specify the current date and time to make the task
sequence available on the reference computer.
- Schedule when this deployment will
expire: Specify the date and time when the task sequence
expires on the destination computer.
-
On the User Experience page, review the default
settings, and then click Next. For this scenario, the
default settings are likely sufficient.
-
On the Alerts page, specify whether to generate
an alert for a failed deployment, and then click Next.
-
On the Distribution Points page, click
Next. For this scenario, the default settings are likely
sufficient.
-
Complete the wizard.
Step 2e: Run the Task Sequence from
the Reference Computer
You have deployed the build and capture task sequence
to a collection that contains the reference computer. Now, you must
start the reference computer to PXE and run the task sequence to
create the new Windows 8 reference operating system image.
When you start in PXE, the task sequence that you created in
Step 2b: Create a Build and Capture Task
Sequence should be available to run. Start the task sequence to
restart the computer to Windows PE, partition and format the hard
disk drive, and install Windows 8. When the operating system
installation is complete, the task sequence begins a capture and
stores the new operating system image on a network shared
folder.
Step 2f: Add the Reference Operating
System Image
After the task sequence creates the Windows 8
reference operating system image, you must add the image to the
Configuration Manager console before it will be available to use in
the task sequence to deploy Windows 8 to clients.
Follow these steps to add the Windows 8 reference
operating system image to the Configuration Manager console.
To add the Windows 8 operating
system image
-
In the Configuration Manager console, click Software
Library.
-
In the Software Library workspace, expand
Operating Systems, and then click Operating System
Images.
-
On the Home tab, in the Create group,
click Add Operating System Image to start the Add Operating
System Image Wizard.
-
On the Data Source page, specify the path to the
Windows 8 reference operating system image. This is the same
path that you specified on the Capture Image page in step
2b.
-
On the General page, specify the following
information, and then click Next.
- Name: Specify the name of the image.
By default, the name of the image is taken from the WIM file.
- Version: Specify the version of the
image.
- Comment: Specify a brief description
of the image.
-
Complete the wizard.
Step 2g: Schedule Operating System
Image Updates
Periodically, new software updates are released that
apply to the operating system in your operating system image. You
can apply applicable software updates to an image on a specified
schedule to reduce the number of required software updates to
install after the operating system is installed. This process
reduces your vulnerability footprint on the image. On the schedule
that you specify, Configuration Manager applies the software
updates that you select to the operating system image, and then
optionally distributes the updated image to distribution points.
For more information about scheduling operating system image
updates, see the How to Manage Operating
System Images and Installers in Configuration Manager
topic.
Follow these steps to apply software updates to an
operating system image.
To apply software updates to an
operating system image
-
In the Configuration Manager console, click Software
Library.
-
In the Software Library workspace, expand
Operating Systems, and then click Operating System
Images.
-
Select the operating system image to which to apply
software updates.
-
On the Home tab, in the Operating System
Image group, click Schedule Updates to start the
wizard.
-
On the Choose Updates page, select the software
updates to apply to the operating system image, and then click
Next.
-
On the Set Schedule page, specify the following
settings, and then click Next.
- Schedule: Specify the schedule for when the software
updates are applied to the operating system image.
- Continue on error: Select this option to continue to
apply software updates to the image even when there is an
error.
- Distribute the image to distribution points: Select this
option to update the operating system image on distribution points
after the software updates are applied.
-
On the Summary page, verify the information, and
then click Next.
-
On the Completion page, verify that the software
updates were successfully applied to the operating system
image.
Step 3: Create a Task Sequence to
Deploy the Operating System
The task sequence performs multiple steps on a client
computer at the command-line level without requiring user
intervention. In this section, you will create a task sequence to
install Windows 8 on computers. The task sequence uses the
default x64 boot image, Boot image (x64), to start the
computer in Windows PE, partition the hard disk, pre-provision
BitLocker, install Windows 8, enable BitLocker, and restore
user files and settings. This section consists of the following
steps:
For more information about how to create and deploy a
task sequence, see the How to Manage Task
Sequences in Configuration Manager topic.
Step 3a: Create the Task Sequence to
Deploy Windows 8
The task sequence to deploy Windows 8 provides the
steps to format and partition the computer, install Windows 8,
enable BitLocker, and install mandatory software updates.
Follow these steps to create the task sequence to
deploy Windows 8.
To create a task sequence to deploy
Windows 8
-
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 to start the Create Task Sequence
Wizard.
-
On the Create a New Task Sequence page, select
Install an existing image package, and then click
Next.
-
On the Task Sequence Information page, specify
the following settings, and then click Next.
- Task sequence name: Specify a name
that identifies the task sequence.
- Description: Specify a description of
the task that is performed by the task sequence.
- Boot image: Specify the default x64
boot image (Boot image (x64)).
-
On the Install Windows page, specify the
following settings, and then click Next.
- Image package: Click Browse,
select the Windows 8 operating system image that you captured
and then added in Step 2f: Add the Reference
Operating System Image, and then click OK.
- Partition and format the target computer
before installing the operating system:
- Configure task sequence for use with
BitLocker: Select this setting to use
- Product key: Specify the product key
for the Windows operating system to install. You can specify
encoded volume license keys or standard product keys. If you use a
non-encoded product key, each group of 5 characters must be
separated by a dash (-). For example:
XXXXX-XXXXX-XXXXX-XXXXX-XXXXX
- Server licensing mode: Specify that
the server license is Per seat, Per server, or that
no license is specified. If the server license is Per
server, also specify the maximum number of server
connections.
- Specify how to handle the administrator
account that is used when the operating system is deployed.
- Randomly generate the local administrator
password and disable the account on all supported platforms
(recommended): Specify whether the local administrator account
is disabled when the operating system is deployed.
- Enable the account and specify the local
administrator password: Specify whether to enable the local
administrator account. When enabled, specify the password to use
for this account.
-
On the Configure Network page, specify the
following settings, and then click Next.
- Join a workgroup: Specify whether to
add the destination computer to a workgroup when the operating
system is deployed.
- Join a domain: Specify whether to add
the destination computer to a domain when the operating system is
deployed. In Domain, specify the name of the domain.
Important |
You can browse to locate domains in the local forest. However,
you must specify the domain name for a remote forest. |
You can also specify an organizational unit (OU). This is an
optional setting that specifies the LDAP X.500-distinguished name
of the OU in which to create the computer account if it does not
already exist.
- Account: Specify the user name and
password for the account that has permissions to join the specified
domain. For example: domain\user or %variable%.
Important |
You must enter the appropriate domain credentials if you plan
to migrate either the domain settings or the workgroup
settings. |
-
On the Install Configuration Manager page,
verify that the Configuration Manager client package is selected,
add any additional properties to use for client installation, and
then click Next.
For more information about properties that can be used
to install a client, see About Client
Installation Properties in Configuration Manager.
-
On the State Migration page, clear the following
settings, and then click Next. The user settings are not
captured in this scenario.
- Capture user settings: The task
sequence captures the user state. For more information about how to
capture and restore the user state, see How to Manage the User
State in Configuration Manager.
- Capture network settings: The task
sequence captures network settings from the computer. You can
capture the membership of the domain or workgroup in addition to
the network adapter settings.
- Capture Microsoft Windows settings:
The task sequence captures Windows settings from the computer
before the operating system image is installed. You can capture the
computer name, registered user and organization name, and the time
zone settings.
-
On the Include Updates page, specify
Mandatory software updates. Configuration Manager installs
only applicable software updates that are deployed to a collection
for which the computer is a member.
-
On the Install Applications page, specify the
applications to install on the destination computer, and then click
Next. If you specify multiple applications, you can also
specify that the task sequence continues if the installation of a
specific application fails.
-
Complete the wizard.
Step 3b: Review the Task Sequence
Settings
The Create Task Sequence creates the steps that you
must follow to deploy Windows 8. However, before you deploy
the task sequence review the settings to make sure that they meet
your business requirements.
Follow these steps to review the task sequence:
To review the task sequence
-
In the Configuration Manager console, click Software
Library.
-
In the Software Library workspace, expand
Operating Systems, and then click Task Sequences.
-
In the Task Sequence list, select the task
sequence that you created in Step 3a: Create
the Task Sequence to Deploy Windows 8.
-
On the Home tab, in the Task Sequence
group, click Edit.
-
Verify each step in the task sequence, including the
following steps:
- Partition Disk 0 – BIOS: Verify that
the volume disk space is sufficient for the boot partition. Notice
on the Options tab that there several conditions specified
to so this step is not run if the task sequence detects that the
computer starts in UEFI mode.
- Partition Disk 0 – UEFI: Verify that
the volume disk space is sufficient for the various partitions.
Notice on the Options tab that there several conditions
specified to so this step is not run if the task sequence detects
that the computer does not boot in UEFI mode.
- Pre-provision BitLocker: Verify that
BitLocker will be applied to the appropriate destination drive and
that the Skip this step for computers that do not have a TPM or
when TPM is not enabled setting is enabled. This step enables
BitLocker on a drive while in Windows PE. Only the used drive space
is encrypted, and therefore, encryption times are much faster. The
step can only be run on computers that have TPM enabled.
Pre-provision BitLocker section of the Task Sequence Steps in
Configuration Manager topic.
- Enable BitLocker: Verify that the
Current operating system drive is selected and the encryption type
is TPM only. For more information about the Enable BitLocker task
sequence step, see the Enable
BitLocker section of the Task Sequence Steps in
Configuration Manager topic.
-
Add additional steps to the task sequence to support
the business requirements in your environment.
-
Click OK to save the changes.
Step 3c: Distribute the Task
Sequence Content
Before you deploy the task sequence to computers,
distribute the content to distribution points to make sure that the
content is available.
Follow these steps to distribute the content that is
referenced by a task sequence.
To distribute the task sequence
content to distribution points
-
In the Configuration Manager console, click Software
Library.
-
In the Software Library workspace, expand
Operating Systems, and then click Task Sequences.
-
In the Task Sequences node, select the task
sequence that you created in Step 3a: Create
the Task Sequence to Deploy Windows 8.
-
On the Home tab, in the Deployment group,
click Distribute Content to start the Distribute Content
Wizard.
-
On the General page, verify that the content
listed is the content that you want to distribute, and then click
Next.
-
On the Content Destination page, click
Add, choose one of the following, and then follow the
associated step:
- Collections: Select User
Collections or Device Collections, click the collection
associated with one or more distribution point groups, and then
click OK.
- Distribution Point: Select an existing
distribution point, and then click OK. Distribution points
that have previously received the content are not displayed.
- Distribution Point Group: Select an
existing distribution point group, and then click OK.
Distribution point groups that have previously received the content
are not displayed.
When you finish adding content destinations, click
Next.
-
On the Summary page, review the settings for the
distribution before you continue. To distribute the content to the
selected destinations, click Next.
-
The Progress page displays the progress of the
distribution.
-
The Confirmation page displays whether the
content was successfully assigned to the distribution points. For
more information about how to monitor the content distribution, see
the Monitor
Content section in the Operations and
Maintenance for Content Management in Configuration Manager
topic.
Step 3d: Deploy the Task Sequence to
Install Windows 8
As soon as you create the task sequence to install
Windows 8 and the content is available on your distribution
points, you can deploy the task sequence to Configuration Manager
clients. Before you deploy the task sequence, make sure that you
have a deployment strategy that includes the collections for which
you will deploy the task sequence. If you used the Upgrade
Assessment Tool in the Pre-Deployment
Considerations section, you likely created collections with
clients that are ready to upgrade to Windows 8.
Follow these steps to deploy the task sequence to
deploy Windows 8.
To deploy the task sequence to install
Windows 8
-
In the Configuration Manager console, click Software
Library.
-
In the Software Library workspace, expand
Operating Systems, and then click Task Sequences.
-
In the Task Sequence list, select the task
sequence that you created in Step 3a: Create
the Task Sequence to Deploy Windows 8.
-
On the Home tab, in the Deployment group,
click Deploy.
-
On the General page, specify the following
information, and then click Next.
- Task sequence: Verify that the correct
task sequence is selected.
- Collection: Specify the collection for
this deployment. Members of this collection will receive the task
sequence to install Windows 8 when they boot to PXE.
Important |
To install Windows 8 to computers that are not managed by
Configuration Manager, you must use a collection that includes All
Unknown Computers. |
- Comments (optional): Specify
additional information that describes this deployment.
-
On the Deployment Settings page, specify the
following information, and then click Next.
- Purpose: Choose Available from
the drop-down list.
- Specify when to make this task sequence
available. For this scenario, choose Only media and PXE to
have the task sequence available when the destination computer
boots to PXE.
-
On the Scheduling page, specify the following
information, and then click Next.
- Schedule when this deployment will become
available: Specify the current date and time to make the task
sequence available to destination computers.
- Schedule when this deployment will
expire: Specify the date and time when the task sequence
expires on the destination computer.
-
On the User Experience page, review the default
settings, and then click Next. For this scenario, the
default settings are likely sufficient.
-
On the Alerts page, specify whether to generate
an alert for a failed deployment, and then click Next.
-
On the Distribution Points page, click
Next. For this scenario, the default settings are likely
sufficient.
-
Complete the wizard.