Longhorn OS DeploymentLonghorn OS Deployment& Manufacturing Features& Manufacturing Features
Mark MyersSenior Program ManagerIndustry Engagement & Engineering
AgendaAgenda
BackgroundGoals - Next version of Windows codenamed “Longhorn” Manufacturing Tools Overview – The FutureOPK compared to (WAIK) Windows Automation Installation KitLonghorn OEM Pre-install Tool Kit (OPK) Tools Overview
Setup Manager and Unattend supportImage Based Setup (IBS)Windows Imaging (Ximage)Multi Lingual User Interface (MUI)Windows PE Windows Deployment Services (WDS)File ServicesSummary – How it all WorksRecovery Environment
Available Resources
BackgroundBackground
Today’s OS installation routine is designed for the retail end user scenario
OS is designed with too many dependencies and lacks flexibility with image creation, updates, and deployment
Hardware dependencies and language localization requires creation and maintenance of too many OS Images
OS installs are time consuming and inefficient (Text mode, GUI Mode, etc.)
Pre-installation tool kit lacks support for full end to end preinstall scenario’s
Access to Windows PE environment now available to ISV, IHV, ODM, OEM’s and Corporate Account (SA)
Goals of Longhorn Manufacturing FeaturesGoals of Longhorn Manufacturing Features
Provide an end-to-end solution for easy image creation, modification and deployment out of the box
Reduce the total number of OS images required by OEMs and System builders
Consolidate existing tools to gain efficiencies on factory floor and with image creation
Increase factory velocity by providing tool enhancements around scripting, server storage and deployment automation tools
Provide enhanced documentation throughout the OS beta cycle through post RTM of the Longhorn OS
Create a new servicing infrastructure to allow for both online and offline servicing of the OS components and or images
Overview – The FutureOverview – The Future
Longhorn OS is built from the ground up from a list of components
A component is a unit of distribution, with servicing and binding characteristics
Has resources(files, registry, etc.)
Contain dependencies on other components
Exposes configurable properties
OS Components
FileSystem
Net-working
MediaPlayer
Audio
Shell
Manufacturing Features ReviewManufacturing Features Review
Automation
Utilities
Installing LH
Recovery Env.
ADS
File Services
SetupIBS Imaging
Unattend
WDS
Automation ToolsSetup Manager
OPK WAIK
Retail OEMs Corps
WinPE
MUI
Backup/Restore
Difference Between OPK and WAIKDifference Between OPK and WAIK
Used by OEMs for bare metal pre-installation
Focus is on BTO, BTP scenarios
Contains Windows PE as part of OPK license
OEM Specific Licensing and Documentation contained
OPK WAIK
Meant for corporations, IHV, ISV, and System Integrators
Focus is on IT Pro network or local OS based installations
Contains all tools and documentation except Windows PE and OEM licensing information
OEM Pre-Installation Kit Windows Automated Installation Kit
Manufacturing Features ReviewManufacturing Features Review
Automation
Utilities
Installing LH
Recovery Env.
ADS
File Services
SetupIBS Imaging
Unattend
WDS
Automation ToolsSetup Manager
OPK WAIK
Retail OEMs Corps
WinPE
MUI
Backup/Restore
Setup ManagerSetup Manager
Tasks:Automate the OS Installation process
Ability to add drivers, applications, QFE’s and Service Packs during the OS installation phase
Update OS based components and feature settings
Application:Create an Unattend.xml file for both install and
image update
Ability to modify an OS image offline, that is not booted
Setup Manager – Creating the Setup Manager – Creating the Unattend.xmlUnattend.xml
Unattend.xml File InformationUnattend.xml File Information
Becomes the new universal setup answer file for the Longhorn OS (Components, Servicing, and Applications installs)
Created using the new SetupMgr application or Notepad
Fully scriptable file based on XML standardUse a variety of script engine types to perform modifications (VBS, Java, Perl, etc)
All Unattend.txt settings will be either migrated over or evolved into new settings within the new Unattend.xml file
Can be used by partners to add required sections/settings for Factory install processing
Ability to fully automate orders within the factory, building and deploying an OS image on the fly based on customer orders
Setup Manager Setup Manager OS and Application Management Options
Setup Manager and OfflineSetup Manager and OfflineImage ModificationImage Modification
Ability to add, remove and modify components, drivers (in-box and 3rd party), languages, and SP/QFE’s
Support for modifying an image offline as an image on the server
Support for modifying an image offline locally on the client machine
offline image editing on the Server using Setup Manager UI and scripting support
Offline image editing on the Client using Setup servicing tool built for use within in Windows PE
Manufacturing Features ReviewManufacturing Features Review
Automation
Utilities
Installing LH
Recovery Env.
ADS
File Services
SetupIBS Imaging
Unattend
WDS
Automation ToolsSetup Manager
OPK WAIK
Retail OEMs Corps
WinPE
MUI
Backup/Restore
Image-Based Setup (IBS)Image-Based Setup (IBS)
Every OS build, including the final release of Longhorn will ship as a Sysprep’d OS image which has been “Installed”
Combination of all scripting files (OEMinfo, OOBEini, WinBom, etc) into a single scriptable Unattend file
Moving from Winntxx to Setup.exe installation program
Windows “Longhorn” Setup supports upgrading FAT/FAT32 to NTFS, with the default format type NTFS
Two ways to “Install” Longhorn:Using the RTM CD to install using Unattend.xml script via local media or via the network
Install, configure, capture, and deploy using an image (MS or 3rd party)
IBS + Unattend used to modify (add, remove, and configure) components in an offline way
Image-Based Setup PhasesImage-Based Setup Phases
DownlevelUpgrade
WinPEOn Line
ConfigurationFirst Boot OOBE
Basic Setup GUI:Basic Setup GUI:
Data Entry Data Entry
Setup SelectionsSetup Selections
Apply ImageApply Image
Prepare boot dataPrepare boot data
Offline configOffline config
Machine OOBE Machine OOBE options and options and settings:settings:
• EULA acceptEULA accept
• RegistrationRegistration
• Machine nameMachine name
• Users Users
• ConnectivityConnectivity
• Regional SettingsRegional Settings
Component Component Configuration:Configuration:
• Boot to “basic” Boot to “basic” OSOS
• Apply license filesApply license files
• ConfiguratioConfigurationn
““Unattend.xml”Unattend.xml”
• Common Common componentscomponents
• SKU Specific SKU Specific componentscomponents
• Optional Optional ComponentsComponents
Make device Make device “unique”“unique”::
• Sysprep Sysprep specialization specialization “Uniqueness” “Uniqueness” performedperformed
UpgradeBare Metal
Install
Manufacturing Features ReviewManufacturing Features Review
Automation
Utilities
Installing LH
Recovery Env.
ADS
File Services
SetupIBS Imaging
Unattend
WDS
Automation ToolsSetup Manager
OPK WAIK
Retail OEMs Corps
WinPE
MUI
Backup/Restore
Goals For Windows ImagingGoals For Windows Imaging
Provide vendors and partners with a complete end to end solution ranging from CD distribution to ADS network provisioning
Create and promote a shared imaging format across Microsoft for OS images complete with Applications
Platform architecture neutral, works across hardware platforms supported by Windows
Increase the velocity of OS installation and deployment while reducing the size of Windows while in transit
Solution for consistent, reliable installation, upgrades, andrecovery of Windows
Reduce engineering costsInitial development of image by saving time with image creation
Initial deployment of image by saving space and net bandwidth
Servicing of image by supporting OS servicing mechanism
Windows Imaging (WIM)Windows Imaging (WIM)
WIM is a file-based imaging format that exposes functionality via a command line interface tool called Ximage.exe
Compressed file streams for smaller more manageable imagesSingle instancing of files across Sku’s contained within images
FlexibleManage images without extraction and or bootingBoot images from within the WIM for faster executionMetadata is XML and is extensible
WIMGAPIFull API set. Only way to customize image metadataDocumented within the OPK and WAIK
WIM File System Filter Allows images to be mounted as folders and read or modified without extraction/recapture steps
WIM Boot FilterBoot an image within a WIM. Only one image within a WIM file may be marked as bootable from that WIM
Windows Imaging Details (con’t)Windows Imaging Details (con’t)
CD/DVD Spanning Split WIM files into multiple WIM parts (.swm files) of a specified size – targeted for spanning images over multiple pieces of media
Support for applying images from multiple WIM parts
Full edit support of images – FS driver used to mount and edit images
Mount images as read-only or read-write
Commit or discard changes to the WIM image
Export images from one WIM to another or to a new WIM
Delete images from within a WIM
NTFS and FAT interoperabilitySupports all NTFS features (object IDs, hard links, EFS, etc.)
Windows Imaging Details (con’t)Windows Imaging Details (con’t)
Supports variable sized target drivesPlatform Architecture IndependentSingle instance of duplicate files
File size and SHA-1 hash compareOptional byte-by-byte compare
Ability to combine multiple images into single image file (WIM)Multiple compression options
Based on existing MS compression technologies LZX or LZNT1 Compression algorithms usedBetter compression results than sector-based imaging
Command line tool that will support full scripting options for capture, mounting, editing and deploying
Manufacturing Features ReviewManufacturing Features Review
Automation
Utilities
Installing LH
Recovery Env.
ADS
File Services
SetupIBS Imaging
Unattend
WDS
Automation ToolsSetup Manager
OPK WAIK
Retail OEMs Corps
WinPE
MUI
Backup/Restore
Multi-Lingual User Interface (MUI)Multi-Lingual User Interface (MUI)
Multi-Lingual User Interface (MUI) is the future localization model for the Longhorn OS
System code/data are language neutral with English as just another UI language
Localized OS products are created by adding the MUI language component to the language neutral base
UI language change is just a user setting or a script setting for OEM, System Builders, and Corporations
Multiple UI languages can be installed and used on a single OS SKU based on licensing policies with OOBE providing user with Language selection option
In unattend.xml, you specify which language UI to install to new or existing OS images
Support for Offline add of MUI language to existing images
Multi-Lingual User Interface (MUI) (con’t)Multi-Lingual User Interface (MUI) (con’t)
MUI Languages will be RTM’d based on completion (Prioritization list coming)
MUI components may be as small as 40 MB with the largest being approx 150 MB
Globalization information planned to be published within the new WDK starting with Beta 1 for driver and application support
Support for adding, switching between languages support with OS present/online
Componentization for Globalization & Componentization for Globalization & Localization:Localization:
Notepad GermanNotepad English
Notepad.Resources.
ManifestResourcesCulture: de
Notepad.Resources.
ManifestResourcesCulture: en
Language Dependent
CompNotepad.
ResourcesCulture: de
Language Dependent
Comp:Notepad.
ResourcesCulture: en
Notepad
Language Neutral Comp
Culture: *
Notepad.ManifestResourcesCulture: en
Notepad.ManifestResourcesCulture: de
US Dev MUI Factoring ProcessUS Dev MUI Factoring Process
Localization Process
Manufacturing Features ReviewManufacturing Features Review
Automation
Utilities
Installing LH
Recovery Env.
ADS
File Services
SetupIBS Imaging
Unattend
WDS
Automation ToolsSetup Manager
OPK WAIK
WinPE
MUI
Backup/Restore
Retail OEMs Corps
What Is Windows PE?What Is Windows PE?
Windows PE is a reduced version of Microsoft’s Windows XP and Windows Server 2003 products
Can be created from either a x86-based 32-bit operating system SKU or an Itanium OS SKU today
Future Windows PE provides full networking, driver injection, WMI support, Ramdisk, and access to thousands of supported APIs
Windows PE is used to build, test, and deploy OS images
Windows PE is a base platform for a variety of third party support related solutions
Hardware and software test and diagnostic tools
OS and utilities-based deployment
Virus scanning and recovery-based products
Replacement to MS-DOS and 16-bit dependencies
Windows Preinstallation EnvironmentWindows Preinstallation Environment
Kerberos
Distributed File Service STS
.NET Framework
MSMQ Transaction Service
ASP.NET
Smart Card
Windows Media Services
IIS
Active DirectoryPKIVPN RAS
WMIDirectory/Security Services
Network Access Services
File/Print Services
Web Services
Media Services
Application Services
Programming Frameworks
Integrated Development
16/32-bit program support
Mass storage device support
Full networking
NTFS
Full APIs
Full Drivers
32/64-bit program support
Mass storage device support
Hardware (x64, x86 ,IA64)
API subset
NTFS
TCPIP
Limited Drivers
Complete OS SolutionCustomizable Boot
Environment
Windows PE is a scaled down copy of Windows XP or
Server 2003 It replaces
MS-DOS in deployment anddiagnostic scenarios.
Forced rebootEvery 24 hours of uptime.
Windows PEWindows XP Pro/2003
Longhorn Version of Windows PELonghorn Version of Windows PE
Feature parity with Server 2003 Service Pack 1 Windows PE feature sets:
WMI support for access to multiple hardware based providers and classesWindows based driver injection and PnP boot supportRAMDISK boot support for Hard Drive (HD), Compact Disc (CD), DVD, USB Flash Drive (UFD), and Pre-Boot eXecution Environment (PXE)
Min 256 MB required on boot machineRead only Ramdisk todaySub 30 second boot times possible using either network or USB Flash Drive (UFD)
Internet Connection Firewall supportEnsures Windows PE safe from viruses, worms, etc
WinPE Boot support on USB Flash Devices Currently an OEM only feature in XP/Server 2003
Formal documentation; Application debug and Win32/64 bit APIs NOT supported
Longhorn Version of Windows PE (con’t)Longhorn Version of Windows PE (con’t)
Additional features currently being finalized:Support for Hot Plug PnP within Windows PE with faster driver PnP due to new inf. parsing design
Ramdisk boot support with up to 32 Meg of Read/Write scratch space
File Based Write Filter (FBWF) support for allowing writes even when booted on read only media such as CD or DVD
Implementing a boot manager on EFI just like x86 32 and x64 based systems (ex. boot.ini)
Smaller default size (under 100MB) with faster boot times based on WIM boot support. Compressed Windows PE at around 60MB
New servicing infrastructure on par with Windows Longhorn solution (CBS/CSI)
Additional planned F6 media support (CD/DVD, UFD, and network shares)
Manufacturing Features ReviewManufacturing Features Review
Automation
Utilities
Installing LH
Recovery Env.
ADS
File Services
SetupIBS Imaging
Unattend
WDS
Automation ToolsSetup Manager
OPK WAIK
WinPE
MUI
Backup/Restore
Retail OEMs Corps
Windows Deployment ServicesWindows Deployment ServicesReplaces Remote Installation Services from Windows 2000Will ship an update for WS2K3 with Longhorn Client in 06’Provides the ability to install Longhorn, XP, WS2K3, and W2K imagesUtilizes WinPE as the new Client Installation Wizard (CIW) as the boot environmentKey scenarios:
Bootable componentized WinPE deployment via WDS Server:Compressed WIM image with RAMDISK boot supportSupport for customized versions of WinPE Boot support for x86 32 and 64 bit as well for IA64
Solution for selection and deployment of OS images from WDS server:WinPE based WDS Client – UI consistent with Longhorn Setup WDS Client can run in fully unattended fashionIntegration with Active Directory also supported
Scalable PXE Server built on new unified Microsoft PXE Server architecture
Uses “Provider” logic: plug-ins to augment core networking functionalityTo-be published APIsWDS BINL service can now handle more than 1600 requests per second
Improved command line and console manageabilityNative support for WIM images
Manufacturing Features ReviewManufacturing Features Review
Automation
Utilities
Installing LH
Recovery Env.
ADS
File Services
SetupIBS Imaging
Unattend
WDS
Automation ToolsSetup Manager
OPK WAIK
WinPE
MUI
Backup/Restore
Retail OEMs Corps
Longhorn File ServicesLonghorn File Services
Diskpart: Combining features and utilities into a single tool to allow the following functions to be fully scripted:
Active (since Windows XP)
Inactive (Windows Server 2003)
Format – NTFS both 3.1 and 4.0 along with Fat and Fat32
Create partition primary <MBR>
Readonly
Hidden partitions (0x12, 0x27)
Shrinking volumes
Extend of the OS partition
Self-healing NTFS for fix and repair of file system without UI and lengthy end user wizards
Virtual Disk Services “VDS”: Designed to expose NTFS and File Services APIs at the programming level
Manufacturing Features - How it All WorksManufacturing Features - How it All Works
CD InstallCD Install
1
Unattended Unattended InstallInstall
2
Distribution ShareUnattend Configuration
Offline Image EditOffline Image Edit
3
WDSWDS4
WinPE
WIM
WDSIBS
SetupMgr
XImage
WinPE BootCopy WIM
Manufacturing Features ReviewManufacturing Features Review
Automation
Utilities
Installing LH
Recovery Env.
ADS
File Services
SetupIBS Imaging
Unattend
WDS
Automation ToolsSetup Manager
OPK WAIK
WinPE
MUI
Backup/Restore
Retail OEMs Corps
Longhorn Recovery EnvironmentLonghorn Recovery Environment
Startup Repair:Default startup recovery tool in Longhorn running in the recovery environment
Diagnostic based auto-recovery from unbootable states
Minimal level of user input required
Manual diagnostic and repair tools available to advanced users
Recovery Environment:WinPE platform extendable by OEMs with custom recovery tools
Available on a hidden recovery partition or on CD/DVD
Recovery environment can be launched from the installation media
CD/DVD with Recovery and Startup Repair can be created by the user
Partition installed by default via Longhorn setup
Longhorn Recovery EnvironmentLonghorn Recovery Environment
Goals:
Provide automatic diagnosis and recovery for unbootable systems
Empower end users with the ability to automatically recover from ≥ 80% of known causes for unbootable systems
Minimize end-user impact (data loss, downtime) when fixing unbootable systems
Reduce PSS calls for unbootable systems by >50% from XP
Provide support orgs with diagnostics to reduce call times
Provide a centralized and secure platform for manual system recovery
Integrate UX of various system recovery tools
Allow for combination of Microsoft and OEM’s to use this environment for support
Drive down OEM costs
Recovery Environment ComponentsRecovery Environment Components
Two scenarios: automatic and manual recovery
Longhorn Recovery Feature DetailsLonghorn Recovery Feature Details
Automatic failover to on-disk Windows PE-basedrecovery environment
Every Longhorn box has 2 partitions by defaultAlso support CD and remote installation based recovery
Automatic failure diagnosisBased on enhanced instrumentation
Guided recovery experienceWizard for non-technical usersRecovery console like environment for experts
Built-in undo of most recovery actionsError reporting on repair success and failureIntegration with automated support request tools
All diagnoses and recovery actions logged
Use existing capabilities for diagnosis and recoverySystem RestoreOEM base OS image
How To Deploy the Recovery EnvironmentHow To Deploy the Recovery Environment
Attended SetupLimited scenarios only (e.g. disk is unpartitioned)
Unattended.xmlDisk partitioning for recovery environment
Specifying tool paths and support information
DiskpartIf deploying through WIM images, disk partitioning must be done using diskpart
Specifications/requirements of the recovery partition will be provided
OPKLink recovery partition to main OS
Update recovery tool path
Update support tool/information
Startup Repair GoalsStartup Repair Goals
Goals:Reduce support costs by giving users the ability to automatically recover their systems from unbootable states without calling support
Provide a centralized location for diagnostic/repair information and tools if a user does call support
Allows for seamless access in case of system failure or problems
Problems and Repair ActionsProblems and Repair ActionsProblem Repair Action
Registry Corruption System Restore XCopy from backup registry
Missing or Damaged System and Driver Files
System Restore XCopy from file cache
Bad Disk Metadata BCDMD MBR fix-up Partition table fix-up Boot sector fix-up
Bad File System Metadata ChkDsk
Buggy or Incompatible Driver System Restore Driver disabling
Incompatible Hotfix/SP Installation System Restore
Bad Hard Drive *Disk Failure Diagnostics
Missing or Damaged Boot Configuration Data
Rebuild boot configuration data
These problems were identified as the leading causes for boot failures based on PSS statistics* Detection only
SecuritySecurity
When launching the recovery environment from hard disk, a user must supply a username/password pair
User must have admin privileges
Everything in WinPE runs as SYSTEM
Needed to mitigate elevation of privilege attacks
Recovery environment on CD/DVD will not require this username/password check
Recovery Environment OEM Extensibility Recovery Environment OEM Extensibility OptionsOptions
Choice of using Microsoft Recovery Environment or notThrough OPK options within Unattend.xml or via OEM pre-install process
Branding and Support information captured through Windows Longhorn Setup Manager
Specify 3rd Party Backup Tool
Support contact information to be displayed to user
Specify Support Incident Tool/InformationSeparate EXE able to run in Windows PE environment
Not Extensible/ModifiableDiagnostics
Recovery Logic
UI flow
UI Look and Feel
Call To ActionCall To Action
Hire and train internal staff on Win32/64 bit development. Porting your current test, diagnostic and deployment tools to Windows PE
End of MS-DOS availability is 12/31/05
Request to 3rd party IHVs to provide native Windows PE based test and diagnostic tools for their hardware partners and customers
Complete factory or internal process improvements nowMove hard disk duplicators to network-based deployments.
Enable web based “build to order” solutions for customers
Enable USB 2.0 boot in your core BIOSs for USB Flash Drive based boots
Move your pre-installation process to an image based process to ensure fast and efficient OS image deployments
Community ResourcesCommunity Resources
Windows Hardware & Driver Central (WHDC)www.microsoft.com/whdc/default.mspx
Technical Communitieswww.microsoft.com/communities/products/default.mspx
Non-Microsoft Community Siteswww.microsoft.com/communities/related/default.mspx
Microsoft Public Newsgroupswww.microsoft.com/communities/newsgroups
Technical Chats and Webcastswww.microsoft.com/communities/chats/default.mspx
www.microsoft.com/webcasts
Microsoft Blogswww.microsoft.com/communities/blogs
Additional ResourcesAdditional Resources
Community Siteshttp://www.microsoft.com/communities/default.mspx
List of Newsgroupshttp://communities2.microsoft.com/communities/newsgroups/en-us/default.aspx
Attend a free chat or webcasthttp://www.microsoft.com/communities/chats/default.mspx
http://www.microsoft.com/seminar/events/webcasts/default.mspx
Locate a local user group(s)http://www.microsoft.com/communities/usergroups/default.mspx
Non-Microsoft Community Siteshttp://www.microsoft.com/communities/related/default.mspx
© 2005 Microsoft Corporation. All rights reserved.This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.
