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

2. Using Windows Deployment Services And Microsoft System Center To Deploy And Manage A Point-of-Service (POS) System Running POSReady Alexander Wechsler Enterprise Architect|CEO Microsoft Regional Director Germany|eMVP Wechsler Consulting GMBH & Co. KG Session Code: EMB203

3. Scenario Planning

4. 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

5. Deployment OptionsPOSReady Installation • Install from USB drive • Install to USB drive USB • Manual install from DVD DVD • Remote install (RIS) • Full system image install Server

6. POSReady 2009 Feature Areas Flexibility • Add/remove components • Customize installation Hardware Integration • On-screen keyboard • Boot from USB mass storage device HardwareIntegration Flexibility Security • New support for security updates including SP3 • Continued support for IE hardening, Windows Firewall, Group Policy, and File Based Write Filter Deployment • Install from DVD/USB to hard drive or USB hard drive • Deploy from Windows Server • Cloning from FBReseal Confidence Connectivity Base OS Security Deployment ApplicationCompatibility Localization • 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 Community

7. Deployment Considerations Environment Pre-requisites Customization Process 1 2 3 4 5 • Receive OEM image • Customize • Clone • Capture • Deploy Select Deployment Method (WDS / SCCM)

8. To answer your question, I think it will be easier for the audience to follow the flow this way since they can easily see the arrow down from step 3 to 4, instead of having an arrow across the screen to show movement from step3 to 4. Customization Process Flow Image Customization Process Flow 1 2 3 OEM delivers POSReady 2009 installed Engineers perform customization of OEM build Changes are packaged to a final images (FBReseal) 5 4 Image captured & catalogued for development Image deployed to target POS

9. Customize Image

10. demo Customize / Reseal

11. Capture Image Reference PC WinPE \ ImageX Windows Server

12. Getting to .WIM Windows Automated Installation Kit Steps: Create WinPE boot ISO Add tools/drivers Create bootable CD Capture reference machine image to server WinPEboot ImageX Drivers Tools Waik DVD WinPE .ISO Capture Script Dev Machine

13. demo Image Sealing / Capture

14. Deploy Image Target Systems Window Server POSReady WIRELESSREGISTER en-US x86 01/09/2009 POSReady COUNTERREGISTER en-US x86 01/09/2009 Windows 7 MGRSWORKSTATION en-US x86 10/09/2008

15. demo WDS Deplyoment

16. Systems Management Patch Management • Software Update Services • XP Pro equivalent Device Management • System Statistics and Reporting • Pre-built management packs

17. What’s New in ConfigMgr OSD?

18. New ConfigMgr Objects (1 of 2) • OS Image • ConfigMgr package containing a WIM file • But no programs – images are deployed via task sequences • WIM file may contain multiple images • May be manipulated and edited using standard WIM tools provided with Windows 7 • Binary Delta Replication supported • OS Install Package • ConfigMgr package containing Operating System installation source files (for setup.exe installs) • Replicated to Distribution Points

19. New ConfigMgr Objects (2 of 2) • Boot Image • Package containing the Windows PE image in a WIM file • Uses Windows PE 2.0 even when deploying an older OS • Replicated to Distribution Points & PXE servers • Task Sequence • Core OS deployment mechanism • Delivered to client via Management Point • Sequence of steps to execute

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

21. demo Targeting POS Devices

22. Deployment Scenarios (General)

23. Task Sequences Overview • Core mechanism for controlling all OS deployment operations • Sequence of steps to execute • Steps prior to deploying new OS • Steps to deploy new OS • Steps after the new OS is deployed • Completely hands-off for full automation of the process

24. Task Sequence Actions • Two kinds of actions • Fixed set of built-in actions that are implemented as part of ConfigMgr • Custom 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

25. OS Deployment Architecture  Admin creates Task Sequence and advertises to collection containing client  Admin creates OS image and boot image and replicates to DP. Site Server  Client sends status as Task Sequence executes MP DP  Client retrieves Task Sequence from MP and executes it  Client retrieves boot image and OS image referenced in Task sequence Client

26. Image Delivery Options • From 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. OS Deployment Architecture Steps in old OS Steps in WinPE Steps in new OS Bare Metal starts here

28. SCCM Image Capture • Reference machine is built with desired OS image and applications • Run “sysprep” to depersonalize the machine • Capture the image • Complete process can be automated using ConfigMgr • Base OS installation done via ConfigMgr as “unattended setup”

29. PXE • Integrate with Server 2008 WDS PXE server • Managed as an ConfigMgr site role • Use “Import Computer Information” wizard to create computer records (DDRs) in ConfigMgr database • Advertise task sequence to imported computers • PXE boot target computer • PXE server responds • Checks ConfigMgr database • Downloads Windows PE

30. WDS & ConfigMgr Integration ConfigMgr Site Server Admin advertises task sequence to collection containing new computer Site DB ConfigMgr provider in WDS looks for computer in ConfigMgr database If computer is found, WDS proceeds. If not found, WDS tries next provider ConfigMgr MP WDS Server  WDS Server downloads WinPE to new computer WDS PXE Server hosts multiple providers. ConfigMgr puts its provider first in the list. ConfigMgr code in WinPE contacts MP to get task sequence that was advertised  New computer PXE boots New Computer

31. demo Image SCCM PXE Distribution

32. Stand-alone Media (1 of 2) • For scenarios with low or no network connectivity, designed to run fully offline • One task sequence and all referenced packages are put on the media with the task sequence runtime engine • Works for CDs, DVDs, USB Flash Drives • OS image (only) can span multiple CDs • No mixing of media types • Media is created locally on Admin UI computer • Package content comes from DPs

33. 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 in • Cannot use task sequence actions “Install Software Updates” or “Auto-Apply Drivers” (use “Apply Driver Package”)

34. demo Standalone media

35. The forgotten scenario – Dual Boot • Dual/Multiple boot of OS versions • Silent download in background e.g. as a software package • Switch 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

36. POSReady Guidance Deployment Planning Guide Available now at http://microsoft.download.com White paper

37. question & answer

38. Required Slide Track PMs will supply the content for this slide, which will be inserted during the final scrub. Breakout Sessions Windows Embedded Standard and POSReady • EMB303: Windows Embedded Standard 2011: How to Embed Windows 7 into Devices • EMB309: Create a Multitouch and Gesture Aware Device Using Windows Embedded Standard 2011 • EMB308: Componentization Architecture in Windows Embedded Standard 2011 • EMB306: Using Windows PowerShell on Windows Embedded Standard • EMB302: Deploying Windows Embedded with Style • EMB203: Using Windows Deployment Services And Microsoft System Center To Deploy And Manage A Point-of-Service (POS) Windows Embedded CE • EMB301: Technical introduction to the new Windows Embedded CE 6.0 R3 • EMB307: Windows Embedded CE6.0: Tools and Techniques to Face the Embedded Development Challenges • EMB201: Windows Embedded CE and Connectivity • EMB305: From Expression Blend to Windows Embedded CE: build the UI of next generation devices General • EMB202: What a desktop developer needs to know to develop for Windows Embedded • EMB304: Windows Embedded: from sensors to servers • EMB310: Windows Embedded: "Demos only“

39. Required Slide Track PMs will supply the content for this slide, which will be inserted during the final scrub. HOLs, Interactive, Sunday and Demo Sessions Sunday and Demo Session • EMB101-SUN: Windows Embedded101 • EMB01-Demo: Embedding Windows Seven into devices Hands On Lab • Higher Fidelity internet experience with Internet Explorer Embedded • Introduction to Connection Manager • Creating a custom Windows Embedded Standard 2011 operating system image for an application • New 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 sessions • EMB01-IS: Delivering Applications as Appliances • EMB02-IS: Windows for Devices: Learn about the Future of Windows Embedded • EMB03-IS: The Schtick: Solving Real-Time Challenges, connectivity and GUI with Windows Embedded CE • EMB04-IS: Deploying and maintaining Windows Embedded Standard with different

40. Required Slide Track PMs will supply the content for this slide, which will be inserted during the final scrub. Useful URLs Other • http://www.wechsler-consulting.de • http://windowsfordevices Blogs • http://blogs.msdn.com/obloch • http://blogs.msdn.com/mikehall • http://blogs.msdn.com/jcoyne Microsoft Web sites • http://windowsembedded.com • http://msdn.microsoft.com/en-us/windowsembedded/ce/default.aspx • http://msdn.microsoft.com/en-us/windowsembedded/standard/default.aspx • http://technet.microsoft.com/en-us/windowsembedded/posready/default.aspx

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

42. Required Slide © 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.