Download Managing Operating System Deployment

Managing Operating
System Deployment
Module Overview
• Overview of Operating System Deployment
• Preparing the Site for Operating System Deployment
• Capturing an Operating System Image
• Deploying an Operating System
Lesson 1: Overview of Operating System Deployment
• What Is Operating System Deployment?
• Operating System Deployment Terminology
• Overview of Operating System Deployment Scenarios
• Server Roles Used in Operating System Deployment
Processes
What Is Operating System Deployment?
Operating system deployment refers to the combined
technologies used to install a complete operating system to
workstations and servers. You can include additional hardware
drivers and software packages in an operating system
deployment task sequence.
Operating system deployment includes the following:
• Operating system image capture
• Windows® Automated Installation Kit (Windows AIK)
• Task sequences
• Operating system image deployment
• User state migration
Operating System Deployment Terminology
Category
Term
Category Term
• Boot image
Image
• Reference computer
• Operating system
image
• Windows Image File
Computer
Format (.wim)
• Source computer
• Target computer
• Unknown computer
• Task sequence step
Task
• Task sequence group
• Operating system
installer
• Task sequence
• Windows device
driver (or driver)
Driver
• Preboot Execution
Other
Environment (PXE)
Boot
• Drivers node
• Windows PE
• Driver package
• Sysprep
Overview of Operating System Deployment Scenarios
The operating system deployment scenarios include:
• Bare-metal installation
• Operating system refresh
• In-place upgrade
• Side-by-side migration
The various methods that initiate an operating system
deployment include:
• Configuration Manager software distribution
• PXE
• Bootable media
• Stand-alone media
• Prestaged media
Server Roles Used in Operating System
Deployment Processes
Systems
Used
for
aSide-by-side
Bare-Metal
Installation
Systems
Used
for
an
In-place
Upgrade
Systems
Used
forfor
an
System
Refresh
Systems
Used
aOperating
Migration
Createimage
imagefor
for
Create
installationand
and
installation
installation
and
distributeto
to
distribute
distribute
to
distributionpoint
point
distribution
Createdeployment
deploymentfor
for
Create
Create
deployment
for
clients
Primary
clients
Primary Site
Site clients
Primary Site
Management point
Management point Client downloads policy from
Management point
management
point and
uploads
Client downloads
policy
from state
information
to state
migration point
management
point
Client
downloads
policy from
Client
performs
a PXE boot
fromfrom
New
computer
perform
PXE boot
management
point
Client
uploads
state
information
to
distributionpoint
point
distribution
state migration
point
Client
installs operating
system
Distribution point Client
readsinstructions
instructionsfrom
from
reads
Distribution point Client
from
point system
Clientdistribution
installs
operating
management
point
management
point
and installs
from
distribution
point
State
Results reported
to
management
operating
system
from
distribution
Distribution
Client installs
operating
system
Migration
point
point
Client
downloads
state
information
point
from distribution point
point
from downloads
state migration
Client
state point
information
Results reported to management
from
statereported
migration
Results
to point
management
point
State migration
point reported to management
Results
point
point
Import computer
information
Uses
existing Client
Uses
existing clients
or
Creates
an association
Enable unknown
with
a newsupport
computer
computer
Primary Site
Prerequisites for Operating System Deployment
The prerequisites for operating system deployment are :
Prerequisite
Description
• Install the Windows AIK for Windows 7 to:
Primary site server
• Install WinPE boot Images
• Install the Windows User State Migration
Tool (USMT) 4.0
Distribution point
• Enabling PXE and/or Multicast support install
the Windows Deployment Services (WDS) role
State migration point
• Supports User State Migration
DHCP
• Supports PXE and multicast
Firewalls need to allow PXE traffic
Configuration Manager Settings and
Component Requirements
Drivers
and
The Network
Access
Driver
Packages
account:

You can import any
 Allows drivers
site-wide setting
Windows
 Is must
used add
to access
 You
a driver
todistribution
a driver package
pointto
use
it
during
operating

system deployment
You can enable or
operations
disable
drivers
 Must
read
 You
can have
categorize

access
to shares containing
drivers
the images and the
You
can add
drivers to
drivers
node
boot images
Preparing the Boot Images
The boot image
properties include:
• Enable prestart
command


Specify commands to
run before the task
sequence; for example,
set a Task Sequence
variable
Use to add files to boot
image; for example,
CMTrace
Default x64 and x86
boot images based
on Windows PE
• Set custom background
• Enable command
support to view logs
You can import additional
boot images
Operating System Images and Operating
System Installers
There are two methods to store the operating system
files that will be used for operating system deployment
Image file:
• Is typically used to deploy
to target computers
Installer package:
• Is typically used to build a
reference computer
• Is created from a reference
• Copies the installation
• Stores as a single .wim file,
• Does not compress the
• Can contain captured
• Does not preinstall
computer
a compressed file format
operating system images
that include installed
applications and patches
media
files
applications and patches in
the operating system
image
Additional Packages Used by Operating
System Deployment
• The Configuration Manager client software

Is created by default during the Configuration Manager site
installation; the name of the software is Configuration Manager
Client Package

Is used in the Setup Windows and ConfigMgr task
• USMT package (optional package)

Is created by using the Create Package wizard

Can be used with a state migration point
• Application packages (optional)

Can be included in an operating system deployment task
sequence

Must run in the local system context without user intervention
Lesson 3: Capturing an Operating System Image
• Configuring a Reference Computer
• Task Sequence Overview
• Creating a Build and Capture Task Sequence
• Demonstration: Creating a Build and Capture Task
Sequence
• Deploying a Build and Capture Task Sequence
• Capturing a Reference Computer by Using Task Sequence
Media
Configuring a Reference Computer
Build Method
Advantages
Disadvantages
• Unattended
• Time required to validate
Automated
automated build
configuration • Reusable task sequence
• Changes often require
• Task sequence can be
revalidation of entire build
modified
• Effort involved in building
packages such as the
operating system install
package
• Does not need to create • Depends on the
Manual
a task sequence
administrator for accuracy
configuration
• Can install directly from • Requires a test and
removable media
verification method
• Cannot reuse the
configuration method
• Requires active user
involvement
Regardless of the method used, the reference computer cannot be a
member of a domain
Task Sequence Overview
A series of steps or tasks that are performed
automatically
The following terms are used when
describing task sequences:
• Action
• Built-in action
• Custom action
• Condition
• Step
• Group
Creating a Build and Capture Task Sequence
Some steps in the task sequence are
not exposed in the wizard
Deploying a Build and Capture Task Sequence
When deploying a build and capture task sequence:
1.
2.
3.
Determine whether you plan to use PXE boot or boot
media; if using PXE boot, determine how PXE will
respond by using the following options:

Enable unknown computer support

Import computer information
Determine the collection to use; options include:

All Unknown Computers

Administrator created collection
Use the Deploy Software Wizard to deploy the task
sequence:

Select the Make available to boot media and PXE check
box
Capturing a Reference Computer by Using Task
Sequence Media
• Use capture media from within the reference computer to start
the capture process
Lesson 4: Deploying an Operating System
• The Process for Deploying an Operating System Image
• Adding an Operating System Image to Configuration
Manager
• Demonstration: Importing and Distributing an Operating
System Image
• Creating and Deploying a Task Sequence to Install an
Existing Image
• Methods for Running the Installation Task Sequence
• Maintaining Updates for System Images
• Troubleshooting Operating System Deployment
The Process for Deploying an Operating System Image
To deploy an operating system image, perform the following
steps:
1.
Import the operating system image metadata to
Configuration Manager:

2.
Distribute the operating system image content to
distribution points:

3.
The content must be on a distribution point to be usable
Create the task sequence to install the operating
system:

4.
Import the information about the captured .wim file
Select a deployment scenario
Deploy the task sequence:

Select an initiation method that is congruent with the
chosen scenario
Adding an Operating System Image to
Configuration Manager
• Before you can use an
operating system
image, the metadata
must be imported into
Configuration
Manager

Includes information
about the source
location
• After the operating
system metadata is
imported, the
operating system
content can be
distributed to a
distribution point

Site database stores
operating system
image metadata
Is copied from the
source location to the
distribution point
Operating
system
.wim file
Content stored on a
distribution point
Creating and Deploying a Task Sequence to
Install an Existing Image
• Start the Create Task
• Start
the Deploy
Sequence
Wizard, and
Software
and
select theWizard
Install
an
select
the image
collection to
existing
deploy
to option
package
••Configure
or more
Complete one
the wizard
distribution
points for
with the appropriate
the
task sequence
information
••Configure
Modify thethe
task
deployment
sequence assettings
necessary
Methods for Running the Installation Task Sequence
The methods for running the installation task sequence are:
• Configuration Manager deployment

Deploy to collection with existing clients
• PXE boot

Start the system and press the F12 key to start the PXE boot process
• Boot media

Create the boot media; CD/DVD set or USB flash drive with the files
needed to start a system and connect to Configuration Manager
• Stand-alone media

Create the boot media, CD/DVD set, with all the files needed for
operating system installation
• Prestaged media

Used by original equipment manufacturers (OEM) to prestage hard
drives for new systems
Maintaining Updates for System Images
• Use the Update Operating System Image wizard to
schedule updates to keep the images in your .wim file
patched and current
Troubleshooting Operating System Deployment
Method
Log files
Description
• SMSTS.log
• If task sequence completes while in WinPE, log is
located in <largest fixed partition>\SMSTSLOG
• If task sequence completes while in the deployed OS,
log is located in <CCM Install Dir>\logs
• CCMSetup.log
• After client setup is completed, log is located in
%windir%\system32\ccmsetup
• Report categories include:
Configuration
• Task Sequence – Deployment Status
Manager reports
• Task Sequence – Deployments
• Task Sequence – Progress
• Task Sequence – References
During the WinPE phase of the installation, the SMSTS.log file is in RAM and
will be lost with a reboot. Enable command-line support on the boot
image, and use the F8 key to launch a command prompt to access
the smsts.log file