windows accelerate it pro bootcamp: platform delivery (module 2 of 8)

Module 2:

Platform Delivery ServiceLite-TouchZero-TouchWindows To Go

NameTitle

The CA Accelerate 1:M IT Pro Boot Camp

2̀

<Delivery Org> & Customer DetailsIdentify Participants

<Delivery Org>

Consultant Details

Consultant DetailsThe consultant’s details will need to be completed as it will then be processed as part of the completed printout. If later, the group decides to research when the work was done and by whom, this information will then be made available.Fields Required:Contacts full nameContacts email addressNote: If there is a need for a secondary consultant please be sure to complete their details as well.

Customer Info

Customer DetailsThe customer’s details will need to be completed including a reference to the TPID. If later, it is decided to research the work that was done and by whom, this information will then be made available.Fields Required:Company NamePoint of Contact DetailsAddress Phone NumberDetails

Image Creation Service OverviewIntroduction to Image Creation Service Strategy

Review available options

Identify common questions and answers about the options

Determine criteria to help support the decision making process

Define an overarching Image Creation Service strategy

4̀

OS & Device OptionsOptions

Device Target

DriversOperating System

Service ConfigurationArchitecture

Drivers

5̀

OS & Device OptionsDevice Target

Typical Concerns Typical concerns include determining the size of the image (thick vs. thin),

the disk usage profile, the amount of idle CPU load, and memory requirements. There is also an interest in increasing performance.

Purpose Determine the target device where the Windows 8 image will be deployed

Importance Gain the ability to take advantage of image optimization, streaming

capabilities, smaller resource footprints, rapid image testing & reuse, and ease of provisioning options.

Overview

6̀

OS & Device OptionsOperating System

Windows 8 “N” The Windows 8 "N" version is an edition which does not include a bundled

copy of Windows Media Player.

Windows 8 Unlike Windows 7 and Windows Vista, there are no Starter, Ultimate, Home

Premium, or Home Basic editions.

Windows 8 Pro Windows 8 Pro is targeted towards enthusiasts and business users which

includes all the features. Additional features include operating as a Remote Desktop server, the ability to participate in a Windows Server domain, Encrypting File System, Hyper-V, and Virtual Hard Disk Booting, Group Policy as well as BitLocker and BitLocker To Go.

Overview

Windows 8 Enterprise Windows 8 Enterprise provides all the features in Windows 8 Pro (except

the Windows Media Center add-on), with additional features to assist with IT organizations.

7̀

OS & Device Options32-bit vs. 64-Bit Operating System ArchitectureOverview

Typical Concerns Hardware purchased within the past 2 to 3 years is likely be compatible with

Windows 8 64-bit. Use the Microsoft Assessment and Planning (MAP) toolkit to validate

Most hardware manufacturers produce both 32 and 64-bit versions of device drivers Special attention should be directed to printer drivers and support for 64-bit

operating systems Memory configurations greater than 4Gb are only addressable when a 64-bit

operating system is used “Windows on Windows” technology in 64-bit Windows 8 provides support for 32-bit

applications

Purpose This option identifies the architecture of Windows 8 to be used in the creation of

your image

Importance Choosing one architecture will likely reduce the amount of testing required to

prepare applications for a Windows 8 deployment 16-bit applications are not compatible with a 64-bit version of Windows 8

8̀

OS & Device OptionsHardware Model ListOverview

Typical Concerns Additional drivers may be added to the deployment point once the WIM is received

from the factory Determine the maintenance cycle to be used to update manufacturer driver

packages

Purpose Determine which selection of drivers to include in the deployment point, as well as

specific mass-storage or network drivers to include in Windows PE

Importance Selecting the right set of drivers will help in determining the correct machine

make/model list that will be supported by the factory built image.

9̀

OS & Device OptionsHardware Model ListDetermine the hardware model

Patching OverviewRecommendation:If there is a defined list of machine models that require support, expressly identify those.

Alternatives Benefits Disadvantages

Shared Driver Library(Select Make/Model)

Includes drivers for only those machine make/model that you specify.

Will not support hardware beyond those specified

Additional Model List Allows you to identify additional machine make/models for those not listed by the factory.

Will not be feature/function tested to confirm correct installation

Include Generic Drivers Includes drivers for many popular machine models.

May not include drivers for some models required.

May cause conflict b/w machine models from the same vendor, thereby requiring additional testing to validate

10̀

OS & Device OptionsService ConfigurationOverview

Typical configuration changes to consider for Virtual client targets

• Unused services to disable Configuration changes to increase performance Graphical modifications Consider reducing the frequency regularly scheduled activities/events

(i.e. Hardware/software inventory)

11̀

FeaturesOverview: Service Configuration

Purpose Evaluate the available categories of features to be included in the

Windows 8 default image

Importance Defines the default Windows features to be installed during the

deployment of Windows 8 to client machines

Typical Concerns By defining the default features installed on client machines, access to

included components and other features may be controlled, based on other requirements or security mandates.

12̀

Office Professional Plus 2013Overview

Purpose Specify the version and configuration of the Microsoft Office Suite

Installation for the Windows 8 image

Importance Because of the variety of configuration options available for the Microsoft

Office Suite it is important to clarify the major decision points to configure the Office installation behavior

In addition to reviewing x86 (32-bit) vs. x64 (64-bit) editions, you also need to validate of Microsoft Office Professional Plus 2013 or the Office 365 are to be installed

Typical Concerns While you may still have some users that require an older version of Office

for compatibility, the default Office Suite installed into the Windows 8 image will be Microsoft Office Professional Plus 2013

The versions of Office Language Packs to be installed can be identified separately from the Operating System Language Packs

13̀

Office Professional Plus 2013Office Installation Options

First launch is up and running in about 2 minutes

Is primary installation type in the new Office

Is linked to Office 365 for managed customers

User-based activation Also highly customizable per

device Also allows local apps to interact

with it Does not require App-V

infrastructure or MDOP

Click-to-Run Installs can easily take 30

minutes or more Basis of Office deployments

since Office 2000 Offered as VL media in new

Office Device-based activation Highly customizable per

device Allows local apps to interact

with it

MSI

14̀

DemoImage Creation Service Demo Guide

Go to the Platform Delivery Demo Guide and perform the Image Creation Demo lab.

Platform Delivery Service Overview

Introduction to Platform Delivery Service Strategy

Review available options

Identify common questions and answers about the options

Determine criteria to help support the decision making process

Define an overarching Platform Delivery Service strategy

Deployment

Platform Delivery Service – Content Overview

Microsoft Deployment Toolkit 2013

Platform Delivery Service

Customer Agreement

Region & Language

MDT Integration

Internet Based Client Management

Remote Control


Lite TouchInstallation (LTI)

MDT Database

BitLockerUDI Wizard

Diagnostics and Recovery Toolset

Deployment

Monitoring & Reporting

Security

System Center 2012 Configuration Manager Toolkit

Zero Touch Installation (ZTI)

Recommended Practice

Windows To Go

Drivers

Boot ImagesNotes and Summary

Support

Power Management

Multicast Deployment

MBAMDeployment Methods

Deployment Capabilities Compliance

Deployment

Overview


Deployment Capabilities

Support

Deployment Methods

User State MigrationNotes & Summary

DeploymentOverview

Typical Concerns Deployment technologies can support a range of deployment scenarios

and deployment types within each scenario. End-users can be provided with varying levels of choice during

deployment, ranging from no user input to choosing which applications will be installed on their client machine.

Hardware manufacturers are starting to release ‘driver packs’ tailored for Systems Management technologies such as System Center 2012 Configuration Manager.

Support for multiple Microsoft Client and Server Operating Systems.

Purpose Define a deployment method to deploy the reference image to client

devices. This decision may require optimizations to the image creation service e.g. (VDI).

Importance Defining a deployment method will ensure a consistent approach to

Operating System Deployment, reduce support calls and can reduce the Total Cost of Ownership (TCO) for each device.

Deployment Tools

Deployment Components

DeploymentOverviewPlatform Delivery Components

Deployment Capabilities (User Scenarios)

Deployment Methods

New Device

Deployment Types


Windows ADK

System Center 2012 Configuration Manager

StandardOEM Pre-

install

Windows Reference Image(s)

Image Answer File(s)

VHD Native Boot

System Center 2012 Configuration Manager & Microsoft Deployment Toolkit 2013

User Driven Install

Zero Touch Installatio

n

Windows to Go

Installation

Windows to Go

Windows Pre-installation

Environment (Windows PE)

User State Migration Tool

(USMT)

Windows System Image Manager (Windows SIM)

Deployment Imaging Servicing & Management

(DISM)

Lite Touch Installatio

n

Light Touch Installation

Zero Touch Installation

Windows To Go

Efficient Mobile Workforce

Bring Your Own Device (BYOD)

My Data & Apps Follow Me

Windows 8.1 Companion Devices Ready for Business

Contractors Using Shared PC’s / BYOD

Windows 8.1 Applications In The Enterprise

The Effective Developer / Administrator

Better Together

The Secure Workplace

DeploymentOverviewWindows 8.1 Enterprise Scenarios vs. Platform Deployment Methods

Windows 7Windows

8.1

System Center Configuration Manager 2007 SP2


System Center 2012 Configuration Manager R2

Microsoft Deployment Toolkit 2010 Update 1

Microsoft Deployment Toolkit 2012 Update 1


Windows Automated Installation Kit

Windows Assessment and Deployment Kit (for Windows 8.1)

DeploymentOverviewDeployment Tool Support for Windows 7 and Windows 8.1

DeploymentDeployment Methods

Definition Deployment Methods determine which technology will be used to deploy

the Operating System and chosen applications to the client device. Multiple deployment methods are often used to meet customer requirements.

Requirements Each deployment method has specific user and connectivity requirements, and provides a different level of administrative control: Lite Touch Installation (LTI) requires user interaction to deployment to any device. Zero Touch Installation (ZTI) allows centrally-managed deployment targeting

administrator-defined logical computer groups., whilst User Driven Installation (UDI) requires user-provided information, which is closer to the interaction of LTI whilst maintaining the administrative control of ZTI.

Windows to Go installation provides a corporate desktop through a removable drive.

Overview

DeploymentDeployment Methods

Deployment Methods

Technology Requirements

MDT 2013

System Center 2012

Configuration Manager


and MDT 2013

User Interacti

on

Administrative

Control

Lite Touch Installation (LTI) Yes Lower

Zero Touch Installation (ZTI)

& User Driven

Installation (UDI)

ZTI = No

HigherUDI =

Yes

Windows to Go Yes Higher

Overview

Typical Concerns Highly customized user state migration strategies can be created with new

user state migration tools. User state migration tools are easily integrated with Microsoft Deployment

Toolkit 2013 or System Center 2012 Configuration Manager deployment technologies.

User state can be stored on a network share, removable drive or retained on the source computer in client refresh deployments.

DeploymentUser State Migration

Purpose User state migration preserves user generated content, the user’s

customized experience of Windows, and application settings within the constraints of operating system and application compatibility.

Importance A well defined user state migration strategy will benefit from increased

user satisfaction and reduce objection to future deployment projects. When a user performs the process of manually re-applying application

settings and finding documents, support requests can increase and productivity can reduce.

Overview

DeploymentDeployment Capabilities

Description Deployment Capabilities identify the user scenarios available to transition

the user to a new or refreshed client device.

User Scenar

ioDescription

Migrates User State

Uses Existing Target

Computer

Preserves Selected File

Content & Partition

Configuration

New Device

The user requires a new installation of Windows, deployed to a new client device.

No No No

Refresh Device

The user requires the operating system to be re-installed on the same device. This scenario may also be required by an administrator for image standardization or to address a problem.

Yes Yes Yes

Replace Device

The user needs to move from their current device to a new client device. User data is saved from their current device, and a new installation of Windows is deployed to a new client device. Finally, saved user data is restored to the new client device.

Yes No No

Overview

What deployment scenarios are in scope? New device Replace device Refresh device

DeploymentDeployment Capabilities

What Operating Systems are currently in the environment? Windows XP Service Pack 3 Windows Vista Windows 7

Define Deployment Capabilities

What level of automation is required for deployment? Partial automation Full automation

What infrastructure already exists? Microsoft Deployment Toolkit 2008, 2010 Update 1. System Center Configuration Manager 2007, Systems Management Server

2003. 3rd party deployment infrastructure.

Mac OS Unix Linux

iOS Android

DeploymentRecommended Practice

Map Windows 8.1 Enterprise scenarios to platform deployment methods Use only the required Deployment Types, Capabilities and Methods needed to

implement a solution tailored to the Windows 8.1 Enterprise scenarios of the business.

This approach reduces complexity and increases efficiency. Review features of selected deployment tools to determine additional

benefits to the business Security, Compliance, Reporting and Management benefits of System Center

2012 Configuration Manager. Monitoring and troubleshooting improvements in Microsoft Deployment Toolkit

2013.

Take advantage of improved features and deployment components using Windows 8.1

Security Client Device Provisioning Offline migration

Utilize the Platform Delivery service content information to: Identify technologies that complement or improve corporate infrastructure

deployment and management practices. Understand how the technologies will provide benefit for users.

Platform Delivery service content: Deployment Security Network System Center 2012 Configuration Manager Microsoft Deployment Toolkit 2013 Client Management Deployment add-ons

DeploymentSummary

Use the Platform Delivery service to determine your deployment tools and overall deployment strategy against chosen Windows 8.1 Enterprise Scenarios:

Deployment Methods (Lite Touch, Zero Touch, User Driven, Offline) Deployment Capabilities (New Device, Replace Device, Refresh Device) Deployment Types (Standard, OEM, User Driven, Windows to Go, VHD Native

Boot)

ApplicationsOptions

Customer Applications Applications

Base Applications Custom ApplicationsWindows 8 Modern Apps

Typical Applications

Typical Concerns For applications that are not included in the reference image, task

sequence steps may be used to install these during the deployment window.

The packages that are specified will utilize default configuration options for installation – if customization is required, consider deploying that application using MDT or ConfigMgr separately or providing the customized installation source.

ApplicationsCustomer ApplicationsOverview

Purpose Specify the applications that will be included in your Windows 8 image

beyond the default applications.

Importance Applications installed in the reference image will reduce the deployment

duration. Applications with frequent updates should be excluded from the reference image.

Consideration for deployment duration Should it be part of an engineered image or installed as part of the

deployment task sequence? Should the application source be cached rather than installed? (App-V

and/or LIS) Are there any licensing restrictions/limitations that would prevent the

application from being installed on all client machines?

ApplicationsBase Applications

The approach many customers use is to include only applications which will be used by a majority (greater than 80 or 90%) of the end user machines

Typical Applications included in the base image PDF reader applications Runtimes & Frameworks Common web browser plug-ins Microsoft Office

ApplicationsCustom ApplicationsRecommendations

Choose the "lowest common denominator", applications that every single user in your enterprise will need. The image should be the baseline for the organization.

Review the list of applications included in the existing core image (if available) to determine the typical applications that may be included in the Windows 8 image

Consider including those applications that a large percentage of users have installed today.

34̀

Office Professional Plus 2013Options

Installation Requirements Overview

Changes Architecture Decision Matrix

Versions

35̀

Office Professional Plus 2013Overview

Purpose Specify the version and configuration of the Microsoft Office Suite

Installation for the Windows 8 image

Importance Because of the variety of configuration options available for the Microsoft

Office Suite it is important to clarify the major decision points to configure the Office installation behavior

In addition to reviewing x86 (32-bit) vs. x64 (64-bit) editions, you also need to validate of Microsoft Office Professional Plus 2013 or the Office 365 are to be installed

Typical Concerns While you may still have some users that require an older version of Office

for compatibility, the default Office Suite installed into the Windows 8 image will be Microsoft Office Professional Plus 2013

The versions of Office Language Packs to be installed can be identified separately from the Operating System Language Packs

36̀

Office Professional Plus 2013Office Installation Options

First launch is up and running in about 2 minutes

Is primary installation type in the new Office

Is linked to Office 365 for managed customers

User-based activation Also highly customizable per

device Also allows local apps to interact

with it Does not require App-V

infrastructure or MDOP

Click-to-Run Installs can easily take 30

minutes or more Basis of Office deployments

since Office 2000 Offered as VL media in new

Office Device-based activation Highly customizable per

device Allows local apps to interact

with it

MSI

37̀

Office Professional Plus 2013Office Delivery Options

Office desktop apps delivery in the new Office 365

Traditional Office

Click-to-Run Office on Demand Experience carried over from Office 2010

Software as a Service Software as a Service Packaged Software

Works without SkyDrive Pro Requires SkyDrive Pro Incremental Office 15 investments

Always up-to-date or update controlled by admin

Always up-to date Service Pack Updates

Streamlined install-time controls NA Granular install-time controls (OCT)

Subscription upgrade rights Subscription upgrade rights Software Assurance

Offline is the key feature Roaming is the key feature Classic control is the key feature

Fully installed to the machine Transient state Fully installed to the machine

Fast product streaming Fast product streaming No CTR support; App-V & TS

Full featured Office Excludes some Office features Full functionality

Full Add-in support No Outlook, OneNote, or Lync support (Just Web Apps)

No add-in support, loads what is already there though

Full Add-in support

Available for use offline Not intended for offline use Available for use offline

Licensed per user (Fixed number of installs) Licensed per user (Unlimited uses) Licensed per device

Subscription only Subscription only Device-based

Sign-in required Sign-in required Sign-in optional

Requires admin rights to install No admin rights required Requires admin rights to install

Start Screen shortcuts No Start Screen shortcuts Start Screen shortcuts

Added to Add/Remove Programs (ARP) Not in ARP In ARP

Customizations via config.xml, Group Policy and add-ins

No customizations Customizations via Office Customization Tool, GP, config.xml and add-ins

38̀

Office Professional Plus 2013new Office 365 Version Options

new Office 365 Home Premium. The home version of the new Office 365 includes 20GB of additional SkyDrive storage, full Word, Excel, PowerPoint, Outlook, OneNote, Publisher, and Access 2013 applications, and can be installed on up to five PCs or tablets.

new Office 365 Small Business. Available to small businesses with up to 10 users, this version includes a more traditional Office 365 experience with hosted Exchange, SharePoint and Lync, full Word, PowerPoint, Excel, Outlook, OneNote, Access, Publisher, and Lync 2013 applications, and can be installed on up to five PCs or tablets per user.new Office 365 Professional Plus. This new offering provides the same features as Small Business but supports up to 25 users.

new Office 365 Enterprise. (Recommended)The Enterprise new Office 365 offering adds archiving and legal compliance features to Exchange Online and provides support for any number of users.

39̀


What’s New

Deployment Types UDI Designer Wizard

MDT Database

Monitoring

Deployment Methods

40̀

Typical Concerns MDT is the Microsoft recommended process and toolset for

automating client and server deployment. MDT is available in x86 and x64 versions. Both versions of MDT

2013 support deployment of x86 and x64 Windows operating systems.

MDT does not require a license.

Overview


Purpose Microsoft Deployment Toolkit 2013 (MDT) is a Microsoft Solution

Accelerator that allows you to automate the deployment of Operating Systems and applications in your organization.

Importance Only MDT is used in LTI deployments, while ZTI and UDI

deployments are performed using MDT with Microsoft System Center 2012 Configuration Manager.

41̀

Integration with Security Compliance Manager (SCM) Apply security templates to clients during deployment.

What’s New?


Integration with System Center 2012 Configuration Manager Extend the functionality of OS deployment in Configuration

Manager 2012.Integration with Diagnostic and Recovery Toolkit (DaRT) Diagnostic and remote control support added during deployment,

available to organizations with access to the Microsoft Desktop Optimization Pack (MDOP).

Deployment Monitoring Functionality View all LTI deployments performed from a specific deployment

share.

Support for Windows 8.1 and Windows Server 2012 deployment

Integration with Windows Assessment and Deployment Kit (Windows ADK) A collection of tools to customize and automate the deployment of

Windows 8.1.

42̀

What’s New? (Continued)


Improved functionality for Disk Partitioning Support unique partitioning requirements for operating system

and hardware configuration.

Support for UEFI Boot UEFI is a more secure replacement for the older BIOS firmware

interface, which is vulnerable to malware that performs attacks during start-up or power on self-test (POST) processes.

Enhanced User Driven Installation (UDI) functionality with System Center 2012 Configuration Manager Allows IT Professionals to customise a set of wizards that are

presented to a user and/or technician to select operating system deployment options.

43̀

Disadvantages of LTI deployment method User initiation is a minimum requirement for LTI. Requires users or deployment technicians to have credentials with

elevated permissions. Increases the risk of configuration errors – users or deployment

technicians need to know some configuration settings prior to deployment.

Deployment Methods


Advantages of Lite Touch Installation Deployment Method Less up-front configuration time when compared with ZTI or UDI

deployments. Same environment shared with Image Creation. Requires less infrastructure to support deployments. Level of automation for the deployment can be selected.

MDT 2013 supports the Lite Touch Installation (LTI) deployment method when used as a standalone product. To support ZTI & UDI deployments, integration with System Center 2012

Configuration Manager is required.

Lite Touch Installation

44̀

Integrate MDT 2013 with System Center 2012 Configuration Manager to use a combination of deployment methods.

Deployment Methods


Decision Matrix

Option

Less up-front configuration time when compared with ZTI or UDI deployments.

Requires less infrastructure to support deployments.

Level of automation for the deployment can be selected.

Combine the benefits of Lite Touch Installation with additional functionality of Windows to Go.

Increase administrative control and security for users on non-corporate devices.

Description

Use Lite Touch Installation with MDT 2013.

Use a combination of deployment methods (Recommended).

45̀

Select only the required migration types to reduce up front configuration effort.

Deployment Types


Recommendations

Use client Hyper-V on Windows 8.1 instead of Native VHD boot to provide similar functionality without security and management limitations. User productivity is increased by having multiple systems active simultaneously.

Understand the configuration effort required in order to customize a solution by using Microsoft Deployment Toolkit 2013.

Limit access to the Microsoft Deployment Toolkit administrative console where possible. For example, if multiple administrative users will update the MDT database with client device information, consider providing a customized web based front end to achieve this task.

Use Windows Server Update Services to provide software updates to client devices during the deployment process, rather than manually including updates in the Microsoft Deployment Toolkit console.

46̀

Benefits Flexibility to customize the deployment process.

UDI Designer Wizard


OverviewPurposeThe UDI designer wizard extends the existing features of UDI to provide users with an customized experience that meet unique business and technical requirements.

Development Components Custom wizard pages

Displayed in the UDI Wizard and collect information required to complete the deployment process.

Wizard pages created using C++ in Microsoft Visual Studio®. Custom wizard page editors.

Configure the behavior of your custom wizard page. Create wizard page editors using WPF version 4.0, Microsoft Prism

version 4.0 and Microsoft Unity Application Block (Unity) version 2.1

47̀

UDI Designer Wizard


Relationship between UDI Wizard Designer and UDI Wizard

48̀

Use MDT Database to store Deployment Configuration Reduces configuration errors during deployment. Bulk database update approach to be reviewed ahead of deployment.



Ensure availability of Deployment Share Understand organizational impact of deployment share unavailability. Consider Linked Deployment Share functionality to provide availability /

accessibility of deployment share to clients. Microsoft recommended System Center 2012 Configuration Manager for

organizations with more than 500 client devices.

Automate LTI wizard using Customsettings.ini configuration file Avoid scenarios where users select enterprise or business wide

configuration settings that can be automated.

Avoid modifying ‘core’ MDT scripts in deployment share Modification Increases risk of failure to MDT and Deployment Share during

MDT upgrade. Should customization be required, add these to a separate script folder in

repository.

49̀

DemoPlatform Delivery Service LTI Demo Guide

MDT 2013 is the recommend best practice for generating Reference Images, even reference images used within System Center 2012 Configuration Manager. Go to the Platform Delivery Service Demo Guide Lite-Touch Installation (LTI) and perform the lab demo for LTI with Image generation.

50̀

What’s New Deployment Types

Monitoring & ReportingMDT Integration Remote Control

Deployment Methods

ComplianceInternet Based Client Management


51̀

Importance System Center 2012 Configuration Manager with Microsoft

Deployment Toolkit 2013 are the recommended deployment tools for enterprise scale deployment and migration projects.

Overview

Purpose System Center 2012 Configuration Manager is used to deploy and

manage a wide range of operating systems, including client platforms, server platforms and mobile devices.

Typical Concerns Deployment concepts and operations are consistent across MDT

2013 and System Center 2012 Configuration Manager. Infrastructure requirements are typically less than those required

by earlier versions of System Center Configuration Manager.


52̀

Note - Additional deployment benefits can be provided by integrating MDT 2013 with System Center 2012 Configuration Manager.

What’s New?

The following features are improvements to the deployment component of System Center 2012 Configuration Manager: Deployment scalability – The functionality of the PXE Service

Point and its configuration is moved to the distribution point to increase scalability.

User Device Affinity (UDA) Support – You can associate a user with a client device where to take advantage of User Device Affinity. UDA provides the ability to deploy the most suitable application type (E.g. Virtual, MSI, Remote) to a user based on the client device used to access the application.

Enhanced media deployment functionality - Deploy client devices using media to anywhere in the System Center 2012 Configuration Manager hierarchy

Update reference images offline in administrative console - Apply Windows Updates to reference images using System Center 2012 Configuration Manager Software Library


53̀

Service Pack 1Overview

Description Service Pack 1 will be available in early 2013 and extends/adds to the

functionality of System Center 2012 Configuration Manager in the following areas:


Deployment Windows 8.1 and Windows Server 2012 operating system deployment

supported. Windows 8.1 native application deployment support. Software deployment for Windows RT, Windows Phone 8, iOS and Android with

Windows Intune and System Center 2012 Configuration Manager integration. Support for Windows to Go USB deployment. Management - the following devices can now be managed: Windows 8.1, Windows Server 2012, Windows 8.1 Phone, Windows RT Devices. Unix and Linux Servers – Hardware and software Inventory, software

distribution, software updates, secure communication and reporting functionality provided.

Mac OS X Desktop – Hardware and software inventory, network discovery, software distribution and software update functionality provided.

Windows Embedded Devices – support for thin clients, POS terminals, kiosks and digital signage.

54̀

Service Pack 1Overview


Windows Intune Interoperability – Manage Windows Intune devices through a single System Center 2012 Configuration Manager console.

Infrastructure – Support for a Windows Azure distribution point, to help reduce infrastructure costs.

User Experience – Software distribution can be prevented when client devices use 3G and 4G network connections, improving user experience and reducing cost.

Automation – Increased support for PowerShell.

Security – Real-time administrative actions for Endpoint Protection related tasks.

Package Conversion Manager – PCM v2.0 converts System Center Configuration Manager 2007 packages into System Center 2012 Configuration Manager SP1 applications.

55̀

Advantages Less up-front configuration time when compared with ZTI, UDI, Offline or

OEM deployments. Level of automation for the deployment can be selected.

Deployment MethodsLite Touch Installation

Description The Lite Touch deployment method is for medium sized organizations who

require high volume deployments. Lite Touch is beneficial for organizations that typically have fewer than 500

client devices. Lite Touch requires interaction by the user or deployment engineer to

complete the deployment process. The level of interaction with the deployment is dependent on the level of automation configured in the deployment task sequence.

Disadvantages User interaction required for all deployments. Increases the risk of configuration errors – users or deployment

technicians need to know some configuration settings prior to deployment.


56̀

Advantages Users can perform a deployment or migration away from the

office. Administrative control can be retained – deploy only to allowed

users and client devices.

Deployment MethodsOffline Installation

Description This method can provide an end to end deployment of a client

device without the need for connectivity to the corporate network.

Disadvantages User interaction required to complete the deployment or

migration. Troubleshooting and support challenges when problems occur. Increased challenge to maintain version control and location/cost

of deployment media.


57̀

Advantages Reduce network traffic by pre-loading the reference image before

deployment. Can speed up the deployment process.

Deployment MethodsOEM Installation

Description This deployment method pre-loads a reference image on the client

device in a staging environment prior to deploying the client device in a production environment. This is typically performed by a Original Equipment Manufacturer (OEM).

Disadvantages Additional up-front configuration needed when compared to other

deployment methods. If changes are required to the reference image, the pre-loading

process will need to repeated, or a traditional deployment will be required.


58̀

Contractors Using Shared PC’s.

My Data & Apps Follow Me.

Bring Your Own Device.

High volume deployment requires increased administrative effort.

Deployment MethodsDecision Matrix


Option Level of

automation can be selected.

Benefits

Lite Touch Install

Provides increased administrative control and user flexibility in deployment.

Zero Touch Install / User Driven Install(Recommended)

Offline Installation

Deploy client devices without network connectivity in a secure manner.

Increased risk of configuration errors.

Limitations

Additional up-front configuration required.

Additional infrastructure required.


User interaction required.

Reduce network bandwidth and speed up deployment.

OEM Installation


Provides users with greater mobility to work.

Can be booted on multiple computers

Windows to Go Installation(Recommended)

Applicable Scenarios

Efficient Mobile Workforce.

Windows 8.1 Applications in the Enterprise.

Better Together.

My Data & Apps Follow Me.

Windows 8.1 Applications in the Enterprise.

The Effective Developer / Administrator.

Better Together. Secure Workplace.

59̀

Task Sequence Pre-Staged Media – Creates a file to be pre-staged on a new hard drive that includes a reference image.

User Driven Installation Task Sequence – Creates a task sequence to provide users with an customized experience that meets unique business and technical requirements.

Deployment TypesOverview

Client Task Sequence - Creates a task sequence for deploying operating system images to client computers. This deployment type is the standard choice for Lite Touch Installation or Zero Touch Installation.

Task Sequence Stand Alone Media – Creates media used to deploy a reference image and associated configuration settings and applications without network access.


Task Sequence Bootable Media - Creates media used to deploy a reference image using System Center 2012 Configuration Manager infrastructure.

Windows to Go – The deployment of Windows to Go will be supported by System Center 2012 Configuration Manager Service Pack 1.

60̀

Benefits New deployment methods – Provide users with the option to

select regional settings, preferred languages and administrator defined applications to enable a customized migration to an approved client device that is suitable for deployment.

Store configuration information for deployment centrally – provide users with different requirements the same automated deployment experience.

Support for additional languages – enable more users to migrate without the need to duplicate administrative effort.

Improved diagnostics, monitoring, error reporting, and recovery – troubleshoot and identify deployment problems as they happen.

Microsoft Deployment Toolkit 2013 IntegrationOverview

Description Integration of MDT 2013 and System Center 2012 Configuration

Manager provides an easier path for users to migrate to a new Windows operating system.


61̀

Recommendations Integrate the latest release of the Microsoft Deployment Toolkit

with System Center Configuration Manager 2007 or System Center 2012 Configuration Manager when it becomes available.

MDT 2013 should be integrated with System Center 2012 Configuration Manager SP1 to provide support for the Windows ADK RTM deployment component, enabling deployment of Windows 8.1 and Windows Server 2012.

Microsoft Deployment Toolkit 2013 IntegrationSupported Configuration


MDT 2010 Update 1

MDT 2013 MDT 2013 Update

1

System Center Configuration Manager 2007


System Center 2012 Configuration Manager SP1 Beta

62̀

MDT Database vs. Collection Variables Collection Variables can define custom settings per device or user

collection in System Center 2012 Configuration Manager, useful when a group of similar users or devices require the same configuration.

The MDT Database extends the functionality of collection variables by centrally storing all deployment configuration settings, providing an easier method to update and keep track of settings without needing to manually update collections.

Microsoft Deployment Toolkit 2013 IntegrationMDT Database

Description The MDT database provides a separate database instance from

System Center 2012 Configuration Manager where deployment configuration information can be stored.


63̀

Users receive a limited deployment experience.

Microsoft Deployment Toolkit 2013 IntegrationDecision Matrix


Option

Users receive a feature rich and flexible deployment experience.

BenefitsIntegrate Microsoft Deployment Toolkit 2013 with System Center 2012 Configuration Manager(Recommended)Do not integrate Microsoft Deployment Toolkit 2013 with System Center 2012 Configuration Manager

Limitations

64̀

Use MDT Database to store Deployment Configuration information Integration with Microsoft Deployment Toolkit 2013 required.

Implement the full functionality offered by System Center 2012 Configuration Manager Use Reporting, Monitoring and Remote Control features to complement

platform delivery activities and improve the user experience with System Center 2012 Configuration Manager.


Use complementary technologies and tools to enhance the platform delivery solution provided by System Center 2012 Configuration Manager. Security and Compliance Manager and the System Center 2012

Configuration Manager Toolkit provide freely available benefits to secure the infrastructure.

Microsoft BitLocker Administration and Monitoring (MBAM) and the Diagnostic and Recovery Toolset (DaRT) are available with the Microsoft Desktop Optimization Pack


Protect client devices using System Center 2012 Configuration Manager security features Software Update, Anti-malware and Compliance features provide a

centralized and secure method to keep client devices protected and users free from security threats.

65̀

Q. Is Windows 8.1 supported by System Center 2012 Configuration Manager RTM? No. Support will be provided with System Center 2012 Configuration

Manager Service Pack 1. Microsoft Deployment Toolkit 2013 can be used to deploy Windows 8.1 ahead of the release of Service Pack 1.

Frequently Asked Questions

Q. What operating system support is withdrawn with the release of System Center 2012 Configuration Manager? Windows 2000 Server is no longer supported by System Center 2012

Configuration Manager

Q. Are there any additional licensing considerations to think about when reviewing the features of System Center 2012 Configuration Manager? Yes, the anti-malware (EndPoint Protection) feature has additional licensing

requirements. All other features are included in the existing license.


windows accelerate it pro bootcamp: platform delivery (module 2 of 8)

Technology

overview windows

pro windows

architecture of windows

touch windows

enterprise windows

version of windows

windows vista

windows technology