Using Windows Deployment Services And Microsoft System Center To Deploy And Manage A Point-of-Service (POS) System Running POSReady

Alexander WechslerEnterprise Architect|CEOMicrosoft Regional Director Germany|eMVPWechsler Consulting GMBH & Co. KGSession Code: EMB203

Scenario Planning

Solution ScenarioTailspin Toys

Retailer with 2000 lanes and 400 stores

Multiple hardware types

Lab environment available

Sever based environment in stores

PCs managed centrally with SCCM/WSUS

Remote install (RIS)Full system image install

Manual install from DVD

Install from USB drive Install to USB drive

Deployment OptionsPOSReady Installation

USB

DVD

Server

Application Compatibility● Support for .NET Framework

3.5, IE7, WMP11, SQL Express, Office Viewers

● Support included for SCCM/SCOM, Powershell, Forefront, Steady State, Defender, and Malicious Software Removal Tool

Localization● Language Collection

Support for basic, complex script, and East Asian

● Multilingual User Interface Pack

POSReady 2009 Feature AreasHardware Integration● On-screen keyboard ● Boot from USB mass

storage device

Deployment● Install from DVD/USB

to hard drive or USB hard drive

● Deploy from Windows Server

● Cloning from FBReseal

Flexibility● Add/remove components● Customize installation

Security● New support for

security updates including SP3

● Continued support for IE hardening, Windows Firewall, Group Policy, and File Based Write Filter

Base OS

Flexibility HardwareIntegration

Security Deployment

ApplicationCompatibility Localization

Deployment Considerations

Environment Pre-requisites

Customization Process

Receive OEM image

Customize Clone Capture Deploy

Select Deployment Method (WDS / SCCM)

1 2 3 4 5

5

Image captured & catalogued for development

4

Customization Process FlowImage Customization Process Flow

Changes are packaged to a final images (FBReseal)

3

Image deployed to target POS

Engineers perform customization of OEM build

2

OEM delivers POSReady 2009 installed

1

Customize Image

Customize / Resealdemo

Capture Image

Reference PC WinPE \ ImageX Windows Server

Getting to .WIM

WinPEboot

ImageX Drivers Tools

Capture Script

WinPE .ISO

Dev Machine

Windows Automated Installation Kit Steps:1. Create WinPE boot ISO2. Add tools/drivers3. Create bootable CD4. Capture reference machine image to server

WaikDVD

Image Sealing / Capturedemo

Window Server

Deploy ImageTarget Systems

POSReady WIRELESSREGISTER en-US x86 01/09/2009POSReady COUNTERREGISTER en-US x86 01/09/2009Windows 7 MGRSWORKSTATION en-US x86 10/09/2008

WDS Deplyomentdemo

Systems Management

Patch Management

Software Update ServicesXP Pro equivalent

Device Management

System Statistics and ReportingPre-built management packs

What’s New in ConfigMgr OSD?Scenario

SMS 2003 OSD FP ConfigMgr OSD

Integrated in core product No Yes

End-to-end deployment Yes Yes

Fully automated Yes Yes

Wipe-and-load upgrade Yes Yes

Bare metal deployment w/PXE Loose integration w/RIS

Built-in integration w/WDS

Side-by-side BDD scripts Yes, w/built-in SMP

Fully offline deployment No Yes

Integrated Windows 7 upgrade planning

No Yes

Full server deployment No Yes

Security Good Much stronger

Flexibility/customizability Good Excellent

Windows 7/LH compatibility Good Excellent

Device driver management No Yes

New ConfigMgr Objects (1 of 2)

OS ImageConfigMgr package containing a WIM file

But no programs – images are deployed via task sequencesWIM file may contain multiple imagesMay be manipulated and edited using standard WIM tools provided with Windows 7Binary Delta Replication supported

OS Install PackageConfigMgr package containing Operating System installation source files (for setup.exe installs)Replicated to Distribution Points

New ConfigMgr Objects (2 of 2)

Boot ImagePackage containing the Windows PE image in a WIM fileUses Windows PE 2.0 even when deploying an older OSReplicated to Distribution Points & PXE servers

Task SequenceCore OS deployment mechanismDelivered to client via Management PointSequence of steps to execute

Targeting POSReady devices

POSREady Devices are Windows Embedded Standard Devices from an SCCM perspectiveEnable the collection of the OSProductSuite resource property of the image [SMS_def.mof]Create a collection for these devicesAdd additional criteria to distinguish POSReady devices from WES systems

Targeting POS Devicesdemo

Deployment Scenarios (General)

•Fresh install of a new OS on client or server (New or repurposed hardware)

New machine

•Install new version of OS on existing client or server hardware-with Applications

•Securely save/restore user state & settings (local or network)

Wipe-and-load

•Install new OS on new client hardware for an existing user

•Reinstall applications on new computer over new OS

•Move user state from old computer to new computer via network file share

Side-by-side

•Install Windows 7/Server 2008 on existing client or server

•Migrate applications in-place

In-place migration

•CD set, DVD set, USB flash drive

•Low bandwidth connectivity - with applications

•No connectivity (No status reporting)

Offline with removable media

•WDS PXE integration

•Control deployment action with ConfigMgr advertisements

PXE boot

Task Sequences Overview

Core mechanism for controlling all OS deployment operationsSequence of steps to execute

Steps prior to deploying new OSSteps to deploy new OSSteps after the new OS is deployed

Completely hands-off for full automation of the process

Task Sequence ActionsTwo kinds of actions

Fixed set of built-in actions that are implemented as part of ConfigMgrCustom actions that can be any command line executable, including running VBscript

No requirement that OS deployment operations be included

Hence task sequences provide a more general purpose sequencing mechanism in ConfigMgr

OS Deployment Architecture

DPMP

Site Server

Client

Admin creates OS image and boot image and replicates to DP.

Admin creates Task Sequence and advertises to collection containing client

Client retrieves Task Sequence from MP and executes it

Client retrieves boot image and OS image referenced in Task sequence

Client sends status as Task Sequence executes

Image Delivery OptionsFrom DP via HTTP at time of deployment

“download-on-demand”This option is unique to task sequences

From DP via SMB at time of deployment “run-from-net”Same as for Software Distribution

Pre-staged from DP into ConfigMgr client cache using BITS“download-and-execute”Same as for Software Distribution

From removable media (CD, DVD, USB Flash drive) for offline or low-bandwidth scenarios

27

Start OS Deployment

Check deployment readiness

Save user state & settings

Save system settings

Reboot to WinPE

Configure RAID controller

Format & partition hard drive

Deploy OS image

Add device drivers

Reboot to new OS

Install SMS client

Install software updates

Install applications

Restore user state & settings

Steps in old OS Steps in WinPE Steps in new OS

Bare Metal starts here

OS Deployment Architecture

SCCM Image CaptureReference machine is built with desired OS image and applicationsRun “sysprep” to depersonalize the machineCapture the imageComplete process can be automated using ConfigMgr

Base OS installation done via ConfigMgr as “unattended setup”

PXEIntegrate with Server 2008 WDS PXE server

Managed as an ConfigMgr site roleUse “Import Computer Information” wizard to create computer records (DDRs) in ConfigMgr databaseAdvertise task sequence to imported computersPXE boot target computer

PXE server respondsChecks ConfigMgr databaseDownloads Windows PE

WDS & ConfigMgr Integration

New Computer

ConfigMgr SiteServer

ConfigMgr provider in WDS looks for computer in ConfigMgr database

If computer is found, WDS proceeds. If not found, WDS tries next provider

WDS Server downloads WinPE to new computer

ConfigMgrMP

SiteDB

WDS PXE Server hosts multiple providers. ConfigMgr puts its provider first in the list.

WDSServer

ConfigMgr code in WinPE contacts MP to get task sequencethat was advertised

New computer PXE boots

Admin advertises task sequence to collection containing new computer

Image SCCM PXE Distribution

demo

Stand-alone Media (1 of 2)

For scenarios with low or no network connectivity, designed to run fully offlineOne task sequence and all referenced packages are put on the media with the task sequence runtime engineWorks for CDs, DVDs, USB Flash Drives

OS image (only) can span multiple CDsNo mixing of media types

Media is created locally on Admin UI computerPackage content comes from DPs

Stand-alone Media (2 of 2)

Can be started from bare metal, or a running OS with or without the ConfigMgr client No status messages are sent, so no reporting until computer is deployed and ConfigMgr client checks inCannot use task sequence actions “Install Software Updates” or “Auto-Apply Drivers” (use “Apply Driver Package”)

Standalone mediademo

The forgotten scenario – Dual Boot

Dual/Multiple boot of OS versionsSilent download in background e.g. as a software packageSwitch task deployed as SW update changes boot.ini to use the new image

Benefits• Large deployments are easier to handle (switch thousands of

clients immediately)• Higher robustness (fallback to old image still possible)Drawbacks• Requires higher disk footprint (up to three times image size!)• Require some custom development depending on system needs

POSReady GuidanceDeployment Planning GuideAvailable now at http://microsoft.download.com

White paper

question & answer

Breakout Sessions

Windows Embedded Standard and POSReadyEMB303: Windows Embedded Standard 2011: How to Embed Windows 7 into DevicesEMB309: Create a Multitouch and Gesture Aware Device Using Windows Embedded Standard 2011EMB308: Componentization Architecture in Windows Embedded Standard 2011EMB306: Using Windows PowerShell on Windows Embedded StandardEMB302: Deploying Windows Embedded with StyleEMB203: Using Windows Deployment Services And Microsoft System Center To Deploy And Manage A Point-of-Service (POS)

Windows Embedded CEEMB301: Technical introduction to the new Windows Embedded CE 6.0 R3EMB307: Windows Embedded CE6.0: Tools and Techniques to Face the Embedded Development ChallengesEMB201: Windows Embedded CE and ConnectivityEMB305: From Expression Blend to Windows Embedded CE: build the UI of next generation devices

GeneralEMB202: What a desktop developer needs to know to develop for Windows EmbeddedEMB304: Windows Embedded: from sensors to serversEMB310: Windows Embedded: "Demos only“

HOLs, Interactive, Sunday and Demo Sessions

Sunday and Demo SessionEMB101-SUN: Windows Embedded101EMB01-Demo: Embedding Windows Seven into devices

Hands On LabHigher Fidelity internet experience with Internet Explorer EmbeddedIntroduction to Connection ManagerCreating a custom Windows Embedded Standard 2011 operating system image for an applicationNew Servicing and Deployment Scenarios in Windows Embedded Standard 2011 Embedded Enabling Features in Windows Embedded Standard 2011 Configuring and Using PowerShell to Manage Windows Embedded Standard 2011 Devices

Interactive sessionsEMB01-IS: Delivering Applications as AppliancesEMB02-IS: Windows for Devices: Learn about the Future of Windows EmbeddedEMB03-IS: The Schtick: Solving Real-Time Challenges, connectivity and GUI with Windows Embedded CEEMB04-IS: Deploying and maintaining Windows Embedded Standard with different

Useful URLs

Otherhttp://www.wechsler-consulting.dehttp://windowsfordevices

Blogshttp://blogs.msdn.com/oblochhttp://blogs.msdn.com/mikehallhttp://blogs.msdn.com/jcoyne

Microsoft Web siteshttp://windowsembedded.comhttp://msdn.microsoft.com/en-us/windowsembedded/ce/default.aspxhttp://msdn.microsoft.com/en-us/windowsembedded/standard/default.aspxhttp://technet.microsoft.com/en-us/windowsembedded/posready/default.aspx

Complete an evaluation on CommNet and enter to win an Xbox 360 Elite!

© 2009 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Windows 7 and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS,

IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.