Transcript Alexander Wechsler Enterprise Architect|CEO Microsoft Regional Director Germany|eMVP Wechsler Consulting GMBH & Co.

Alexander Wechsler
Enterprise Architect|CEO
Microsoft Regional Director Germany|eMVP
Wechsler Consulting GMBH & Co. KG
Session Code: EMB203
Solution Scenario
Tailspin 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
Deployment Options
POSReady Installation
USB
Install from USB drive
Install to USB drive
DVD
Manual install from DVD
Server
Remote install (RIS)
Full system image install
POSReady 2009 Feature Areas
Hardware Integration
● On-screen keyboard
● Boot from USB mass
storage device
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
Hardware
Integration
Flexibility
Security
Base
OS
Application
Compatibility
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
Deployment
Deployment
● Install from DVD/USB
to hard drive or USB
hard drive
● Deploy from
Windows Server
● Cloning from FBReseal
Localization
Localization
● Language Collection
Support for basic,
complex script, and
East Asian
● Multilingual User
Interface Pack
Deployment Considerations
Environment Pre-requisites
Customization Process
1
2
3
4
5
Receive
OEM
image
Customize
Clone
Capture
Deploy
Select Deployment Method (WDS / SCCM)
Customization Process Flow
Image Customization Process Flow
1
OEM delivers POSReady
2009 installed
2
Engineers
perform customization
of OEM build
5
Image deployed
to target POS
3
Changes are packaged to
a final images (FBReseal)
4
Image
captured & catalogued
for development
Customize Image
Customize / Reseal
Capture Image
Reference PC
WinPE \ ImageX
Windows Server
Getting to .WIM
Windows Automated Installation Kit Steps:
1. Create WinPE boot ISO
2. Add tools/drivers
3. Create bootable CD
4. Capture reference machine image to server
Waik
DVD
WinPE .ISO
WinPE
boot
Dev
Machine
ImageX
Drivers
Tools
Capture
Script
Image Sealing / Capture
Deploy Image
Target Systems
Window Server
POSReady WIRELESSREGISTER en-US
POSReady COUNTERREGISTER en-US
Windows 7 MGRSWORKSTATION en-US
x86
x86
x86
01/09/2009
01/09/2009
10/09/2008
WDS Deplyoment
Systems Management
Patch Management
Software Update Services
XP Pro equivalent
Device Management
System Statistics and Reporting
Pre-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
Loose integration
w/RIS
Built-in integration
w/WDS
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
Bare metal deployment w/PXE
Side-by-side
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
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
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
Targeting POS Devices
Deployment Scenarios (General)
•Fresh install of a new OS on client or server (New or repurposed hardware)
• Install new version of OS on existing client or server hardware-with
Applications
• Securely save/restore user state & settings (local or network)
• 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
• Install Windows 7/Server 2008 on existing client or server
• Migrate applications in-place
• CD set, DVD set, USB flash drive
• Low bandwidth connectivity - with applications
• No connectivity (No status reporting)
• WDS PXE integration
• Control deployment action with ConfigMgr
advertisements
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
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
OS Deployment Architecture
 Admin creates Task
 Admin creates OS
Sequence and advertises
to collection containing
client
image and boot image
and replicates to DP.
Site Server
 Client sends status as
Task Sequence executes
MP
DP
 Client retrieves
 Client retrieves
Task Sequence
from MP and
executes it
boot image and OS
image referenced
in Task sequence
Client
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
Start OS Deployment
Check deployment readiness
Configure RAID controller
Install SMS client
Format & partition hard drive
Install software
updates
Save user state & settings
Deploy OS image
Install applications
Save system settings
Reboot to WinPE
Steps in old OS
Add device drivers
Reboot to new OS
Steps in WinPE
Bare Metal starts here
Restore user state &
settings
Steps in new OS
27
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”
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
WDS & ConfigMgr Integration
 Admin advertises
ConfigMgr Site
Server
task sequence to
collection containing
new computer
 ConfigMgr provider in
WDS looks for computer
in ConfigMgr database
WDS
Server
Site
DB
 If computer is found,
ConfigMgr
MP
WDS proceeds. If not
found, WDS tries next
provider
 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
Image SCCM PXE
Distribution
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
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”)
Standalone media
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
POSReady Guidance
Deployment Planning Guide
Available now at
http://microsoft.download.com
Breakout Sessions
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“
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
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)
HOLs, Interactive, Sunday and Demo Sessions
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
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
Sunday and Demo Session
EMB101-SUN: Windows Embedded101
EMB01-Demo: Embedding Windows Seven into devices
Useful URLs
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
Blogs
http://blogs.msdn.com/obloch
http://blogs.msdn.com/mikehall
http://blogs.msdn.com/jcoyne
Other
http://www.wechsler-consulting.de
http://windowsfordevices
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.