close

Вход

Забыли?

вход по аккаунту

?

WDS - Microsoft

код для вставкиСкачать
Longhorn OS Deployment
& Manufacturing Features
Mark Myers
Senior Program Manager
Industry Engagement & Engineering
Agenda
Background
Goals - Next version of Windows codenamed “Longhorn”
Manufacturing Tools
Overview – The Future
OPK compared to (WAIK) Windows Automation
Installation Kit
Longhorn OEM Pre-install Tool Kit (OPK) Tools Overview
Setup Manager and Unattend support
Image Based Setup (IBS)
Windows Imaging (Ximage)
Multi Lingual User Interface (MUI)
Windows PE
Windows Deployment Services (WDS)
File Services
Summary – How it all Works
Recovery Environment
Available Resources
Background
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 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 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
Shell
File
System
Networking
Media
Player
Audio
Manufacturing Features Review
Retail
OEMs
Corps
OPK
WAIK
Setup Manager
Automation Tools
Automation
Unattend
IBS
Imaging
MUI
File Services
Recovery Env.
Backup/Restore
WDS
ADS
WinPE
Setup
Utilities
Installing LH
Difference Between OPK and WAIK
OPK
OEM Pre-Installation Kit
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
WAIK
Windows Automated Installation Kit
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
Manufacturing Features Review
OEMs
Retail
Corps
WAIK
OPK
Setup Manager
Automation Tools
Automation
Unattend
IBS
Imaging
MUI
File Services
Recovery Env.
Backup/Restore
WDS
ADS
WinPE
Setup
Utilities
Installing LH
Setup 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 Unattend.xml
Unattend.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 standard
Use 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
OS and Application Management Options
Setup Manager and Offline
Image 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 Review
Retail
OEMs
Corps
OPK
WAIK
Setup Manager
Automation Tools
Automation
Unattend
IBS
Imaging
MUI
File Services
Recovery Env.
Backup/Restore
WDS
ADS
WinPE
Setup
Utilities
Installing LH
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 Phases
Downlevel
Upgrade
WinPE
Upgrade
Bare Metal
Install
Basic Setup GUI:
Data Entry
On Line
Configuration
First Boot
Component
Configuration:
Make device
“unique”:
• Boot to “basic”
OS
• Sysprep
specialization
“Uniqueness”
performed
• Apply license files
• Configuration
OOBE
Machine OOBE
options and
settings:
• EULA accept
• Registration
• Machine name
Setup Selections
“Unattend.xml”
• Users
Apply Image
• Common
components
• Connectivity
Prepare boot data
Offline config
• SKU Specific
components
• Optional
Components
• Regional Settings
Manufacturing Features Review
OEMs
Retail
Corps
WAIK
OPK
Setup Manager
Automation Tools
Automation
Unattend
IBS
Imaging
MUI
File Services
Recovery Env.
Backup/Restore
WDS
ADS
WinPE
Setup
Utilities
Installing LH
Goals 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, and
recovery of Windows
Reduce engineering costs
Initial 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)
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 images
Single instancing of files across Sku’s contained within images
Flexible
Manage images without extraction and or booting
Boot images from within the WIM for faster execution
Metadata is XML and is extensible
WIMGAPI
Full API set.
Only way to customize image metadata
Documented 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 Filter
Boot 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)
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 interoperability
Supports all NTFS features (object IDs, hard links, EFS, etc.)
Windows Imaging Details (con’t)
Supports variable sized target drives
Platform Architecture Independent
Single instance of duplicate files
File size and SHA-1 hash compare
Optional 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 used
Better compression results than sector-based imaging
Command line tool that will support full scripting
options for capture, mounting, editing and
deploying
Manufacturing Features Review
Retail
OEMs
Corps
OPK
WAIK
Setup Manager
Automation Tools
Automation
Unattend
IBS
Imaging
MUI
File Services
Recovery Env.
Backup/Restore
WDS
ADS
WinPE
Setup
Utilities
Installing LH
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)
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 &
Localization:
Notepad.ManifestResources
Culture: en
Language Neutral Comp
Localization Process
Culture: *
Language
Dependent
Comp:
Notepad.
Resources
Culture: en
Notepad.
Resources.
ManifestResources
Culture: en
Notepad.ManifestResources
Culture: de
Language
Dependent
Comp
Notepad.
Resources
Culture: de
Notepad
Notepad.
Resources.
ManifestResources
Culture: de
Notepad English Notepad German
US Dev MUI Factoring Process
Manufacturing Features Review
Retail
OEMs
Corps
OPK
WAIK
Setup Manager
Automation Tools
Automation
Unattend
IBS
Imaging
MUI
File Services
Recovery Env.
Backup/Restore
WDS
ADS
WinPE
Setup
Utilities
Installing LH
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 Environment
Windows XP Pro/2003
Windows PE
Complete OS Solution
Customizable Boot
Environment
Full Drivers
Full APIs
NTFS
Full networking
Mass storage device support
16/32-bit program support
Integrated Development
Programming Frameworks
Windows PE is a scaled down
copy of Windows XP or
Server 2003
It replaces
MS-DOS in deployment and
diagnostic scenarios.
Forced reboot
Every 24 hours of uptime.
.NET Framework IIS ASP.NET
Application Services
Limited
Drivers
NTFS
MSMQ
Transaction
Service
Media Services
Windows
TCPIP
API
subset Media Services
Web Services
File/Print Services
Network Access Services
Directory/Security Services
Hardware (x64, x86 ,IA64)
Distributed File Service
Mass storage device support
STS
VPN RAS PKI Smart Card
32/64-bit program support
Active Directory WMI Kerberos
Longhorn 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
classes
Windows based driver injection and PnP boot support
RAMDISK 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 machine
Read only Ramdisk today
Sub 30 second boot times possible using either network or USB Flash
Drive (UFD)
Internet Connection Firewall support
Ensures 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)
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 Review
Retail
OEMs
Corps
OPK
WAIK
Setup Manager
Automation Tools
Automation
Unattend
IBS
Imaging
MUI
File Services
Recovery Env.
Backup/Restore
WDS
ADS
WinPE
Setup
Utilities
Installing LH
Windows Deployment Services
Replaces Remote Installation Services from Windows 2000
Will ship an update for WS2K3 with Longhorn Client in 06’
Provides the ability to install Longhorn, XP, WS2K3, and W2K images
Utilizes WinPE as the new Client Installation Wizard (CIW) as the
boot environment
Key scenarios:
Bootable componentized WinPE deployment via WDS Server:
Compressed WIM image with RAMDISK boot support
Support 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 fashion
Integration 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 functionality
To-be published APIs
WDS BINL service can now handle more than 1600 requests per second
Improved command line and console manageability
Native support for WIM images
Manufacturing Features Review
Retail
OEMs
Corps
OPK
WAIK
Setup Manager
Automation Tools
Automation
Unattend
IBS
Imaging
MUI
File Services
Recovery Env.
Backup/Restore
WDS
ADS
WinPE
Setup
Utilities
Installing LH
Longhorn 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 Works
IBS
WDS
4
1
WDS
CD Install
WIM
Setup
Mgr
3
2
Offline Image Edit
Unattended
Install
WinPE Boot
Copy WIM
Distribution Share
Unattend Configuration
XImage
WinPE
Manufacturing Features Review
Retail
OEMs
Corps
OPK
WAIK
Setup Manager
Automation Tools
Automation
Unattend
IBS
Imaging
MUI
File Services
Recovery Env.
Backup/Restore
WDS
ADS
WinPE
Setup
Utilities
Installing LH
Longhorn Recovery Environment
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
Startup Repair:
Default startup recovery tool in
Longhorn running in the
recovery environment
Diagnostic based autorecovery from unbootable
states
Minimal level of user input
required
Manual diagnostic and repair
tools available to advanced
users
Longhorn 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 Components
Two scenarios: automatic and manual recovery
Longhorn Recovery Feature Details
Automatic failover to on-disk Windows PE-based
recovery environment
Every Longhorn box has 2 partitions by default
Also support CD and remote installation based recovery
Automatic failure diagnosis
Based on enhanced instrumentation
Guided recovery experience
Wizard for non-technical users
Recovery console like environment for experts
Built-in undo of most recovery actions
Error reporting on repair success and failure
Integration with automated support request tools
All diagnoses and recovery actions logged
Use existing capabilities for diagnosis and recovery
System Restore
OEM base OS image
How To Deploy the Recovery Environment
Attended Setup
Limited scenarios only (e.g. disk is unpartitioned)
Unattended.xml
Disk partitioning for recovery environment
Specifying tool paths and support information
Diskpart
If deploying through WIM images, disk partitioning must be done
using diskpart
Specifications/requirements of the recovery partition will be
provided
OPK
Link recovery partition to main OS
Update recovery tool path
Update support tool/information
Startup 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 Actions
Problem
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
Security
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
Options
Choice of using Microsoft Recovery Environment or not
Through 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/Information
Separate EXE able to run in Windows PE environment
Not Extensible/Modifiable
Diagnostics
Recovery Logic
UI flow
UI Look and Feel
Call 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 now
Move 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 Resources
Windows Hardware & Driver Central (WHDC)
www.microsoft.com/whdc/default.mspx
Technical Communities
www.microsoft.com/communities/products/default.mspx
Non-Microsoft Community Sites
www.microsoft.com/communities/related/default.mspx
Microsoft Public Newsgroups
www.microsoft.com/communities/newsgroups
Technical Chats and Webcasts
www.microsoft.com/communities/chats/default.mspx
www.microsoft.com/webcasts
Microsoft Blogs
www.microsoft.com/communities/blogs
Additional Resources
Community Sites
http://www.microsoft.com/communities/default.mspx
List of Newsgroups
http://communities2.microsoft.com/communities/newsgroups/
en-us/default.aspx
Attend a free chat or webcast
http://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 Sites
http://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.
Документ
Категория
Презентации
Просмотров
30
Размер файла
1 082 Кб
Теги
1/--страниц
Пожаловаться на содержимое документа