Operating System Deployment in SCCM 2012

Operating System Deployment in SCCM 2012

Operating system deployment with SCCM 2012 provides a tool for creating operating system images so that we can deploy it to computers that are managed by Configuration Manager and deploying unmanaged computers by using bootable media such as a CD set, DVD, or USB flash drives. The operating system image, in a Windows Imaging Format (WIM) format file, contains the required version of a Windows operating system and any line-of-business applications that have to be installed on the computer.

Operating system deployment provides the following functionality:
We can capture an image of the operating system that you want to deploy.
We can capture and restore user state by using the User State Migration Tool (USMT).
We can deploy the operating system image to a collection of computers.

         We can create task sequences that perform multiple actions on a computer at the command-line level that do not require user intervention.

What’s new in SCCM 2012 for Operating System Deployment?

·         Now we can apply Windows Updates by using Component-Based Servicing (CBS) to update the Windows Imaging (.wim) file format images that are stored in the image node of the Software Library.

·         The Task Sequence Media Wizard includes steps to add prestart command files (formerly pre-execution hooks) to pre-staged media, bootable media, and stand-alone media.

·         Configuring  the Task Sequence Media Wizard to suppress the Configuration Manager Boot Media wizard during operating system installation. This configuration enables us  to deploy operating systems without end user intervention.

·         Defining  a deployment in a prestart command which will override the existing deployments to the target computer. Use the SMSTSPreferredAdvertID task sequence variable to configure the task sequence to use the specific Offer ID that defines the conditions for the deployment.

·         Same task sequence media can be used to deploy operating systems to computers anywhere in the hierarchy.

·         The Capture User State task sequence action and the Restore User State task sequence action supports new features from the User State Migration Tool (USMT) version 4.

·         Install Application task sequence action can be used to deploy applications from the Software Library when you deploy an operating system.

·         User device affinity can be defined for a client computer during operating system deployment.

·         The functionality of the PXE service point and its configuration is moved to the distribution point to increase scalability.

·         SCCM 2012 uses the Windows Assessment and Deployment Kit (Windows ADK) instead of Windows Automated Installation Kit (Windows AIK) to deploy an operating system. Before installing SCCM server, Windows ADK need to be installed on the site server and the provider computer.

·         The USMT for Windows 8 is installed while installing Windows ADK. At the top-level site, SCCM setup automatically creates the package for this new version of USMT at the site.

• While installing SCCM it automatically updates default boot images at the site. You must manually update any custom boot images.

The Operating System Deployment Process

SCCM 2012 provides several methods that you can use to deploy an operating system.  In spite of the deployment method that we use, there are several actions that needs to be considered and requires attention. These actions include the following:

·         Considering and taking care of any Windows device drivers that are required to run the boot image or the operating system image that you have to deploy.

·         Implementing the boot image that requires to start the destination computer. SCCM 2012 comes with two default boot images.

·         Capturing an image of the operating system to deploy by using a task sequence.

·         Distributing the boot image, operating system image, and any related content to a distribution point.

·         Creating a task sequence to deploy the boot image and the operating system image.

·         Deploying the task sequence to the collection that contains the destination computer. If there are multiple computers in the collection, the task sequence is deployed to each computer in the collection.

Types of Operating System Deployment

Through SCCM 2012 we can deploy Operating syetem in five different ways

·         PXE initiated deployments

·         Multicast deployments

·         Bootable Media Deployments

·         Stand-alone Media Deployments

·         Pre-staged Media deployments

Pxe Initiated Deployments.

In this method of deployment the operating system image and Windows PE boot image are distributed to the distribution point which is configured to accept PXE boot request. This process permits client computers request for deployment over the network.

Multicast deployments.

This type of deployment conserves  network bandwidth by concurrently sending data to multiple clients instead of sending a copy of the data to each client over a separate connection. In this method of deployment, the operating system image is sent to a distribution point. This in turn deploys the image when client computers request the deployment.

Bootable Media Deployments

Through Bootable media deployments we can deploy  operating system when the destination computer starts. When the destination computer starts, it retrieves the task sequence, the operating system image, and any other required content from the network. Because that content is not included on the media, you can update the content without having to re-create the media

Stand-alone Media Deployments

Through Stand-alone media deployments we can deploy operating systems in two different conditions

1.        In site locations where we cannot copy an operating system image or other large packages over the network.

2.        There is no network connectivity or low bandwidth network connectivity.

Pre-staged Media deployments

Pre-staged media deployments let us to deploy an operating system to a computer that is not fully provisioned. The pre-staged media is a Windows Imaging Format (WIM) file that can be installed on a bare-metal computer by the manufacturer or at an enterprise staging center that is not connected to the Configuration Manager environment.

Later, when the computer starts in the System Center 2012 Configuration Manager environment, the computer starts by using the boot image provided by the media, and then connects to the site management point for available task sequences that complete the download process. This method of deployment can reduce network traffic because the boot image and operating system image are already on the destination computer. Starting at Configuration Manager SP1, you can specify applications, packages, and driver packages to include in the pre-staged media.