1.07k likes | 3.5k Views
Windows Deployment Services. Riedwaan Bassadien Solutions Specialist Management Solutions Microsoft. Agenda. Introduction to Microsoft Windows Deployment Services (WDS) Usage Scenarios Walkthrough of WDS Server Setup and Client Deployment Technology Overview
E N D
Windows DeploymentServices Riedwaan Bassadien Solutions Specialist Management Solutions Microsoft
Agenda • Introduction to Microsoft Windows Deployment Services (WDS) • Usage Scenarios • Walkthrough of WDS Server Setup and Client Deployment • Technology Overview • Integration with Microsoft Windows Vista / Windows Server “Longhorn” Setup and Deployment Technologies • Demo • Transition from Remote Installation Services
IntroductionHistory of RIS and OS deployment • RIS = original in-box solution for OS Deployment • Problems and limitations • No support for Microsoft Windows Vista deployments • Existing management tools leave much to be desired • Minimal localization and accessibility story • Fragmentation of Microsoft PXE boot strategy
IntroductionDesign goals • Deliver great ‘in-box’ OS provisioning solution • Deliver platform components to enable custom solutions • Remote boot capability • Plug-in model for PXE Server extensibility • Client-server communication protocol • Unify on single image format - WIM • Improve management experience • MMC (UI) and command-line tools • Migration / coexistence path from RIS
IntroductionProduct technology roadmap Unify infrastructure, consolidate to 2 clearly differentiated solutions Address critical short-term SMS and ADS needs Historically • 3 overlapping solutions • Dissimilar infrastructures • Gaps in functionality • Address key SMS and ADS customers needs • Still have overlapping solutions and dissimilar infrastructures • WDS platform designed for IT Generalist and core OEM scenarios • SMS designed for MORG and LORG advanced scenarios • ADS scenarios largely incorporated into SMS SMS 2003 OSD FP SMS 2003 10/03 SMS v4 Q404 SMS v4 OS Deployment builds on WDS VSMT ADS 1.0 9/03 ADS 1.1 Transfer technology Q404 WDS in LH Server WDS RTW RIS inWS 2003 2007 CY 2003 2004 2005 2006
IntroductionRelease roadmap WDS Server WDS MGMT OOB Hotfix for Server 2003 SP1 WDS Server WDS MGMT Server 2003 SP2 WDS Client Windows Vista Windows Server “Longhorn” WDS Client WDS Server WDS MGMT BETA RTM H2 2007 H1 2007 Q2 2006 Q3 2006 Q4 2006
ScenariosNew machine deployment • End-to-end solution for clean installs • Bare metal • Machine re-provisioning • Deployment of Windows Vista, Windows Server “Longhorn”, Windows XP, Win2K3, and Win2K • Full sysprep image support (in WIM format) • New client application replaces OSChooser • PXE boot and non-PXE boot options • Fully automated installs from the moment of power on • Integration with Active Directory
ScenariosPXE boot of Windows PE • Common WinPE uses • Custom deployment solution • Recovery environment • RAMDISK boot support for WinPE 2.0 • Improved download speeds • Adjustable TFTP block size • WIM format provides compression and single instancing • Simplified MGMT tasks for adding / removing images • May be achieved without Active Directory
ScenariosExtensibility points • Scalable PXE server built on unified architecture • Replaceable plug-ins augment core networking functionality • Published APIs • Able to run without Active Directory • WinPE PXE boot files for third-party PXE Server use • Client < - > Server communication protocol • Develop custom deployment application • SMS and BDD use extensibility points
Scenario WalkthroughEnd-to-end deployment • Installing the server • Configuring the server • Adding images • Deploying a client • Maintaining images Maintenance Configuration Image Add Deployment Installation
Scenario WalkthroughInstalling the server • Methods of installation • Server 2003 = install the hotfix / service pack • Windows Server “Longhorn” = install the server role • Actions • Copy server binaries • Create services Maintenance Configuration Image Add Deployment Installation
Scenario WalkthroughConfiguring the Server • Initialize the server • ‘REMINST’ share and folder structure created • TFTP root established • Services started • Authorizing the server in DHCP no longer a requirement Maintenance Configuration Image Add Deployment Installation
Scenario WalkthroughAdding images • Boot Images • WinPE 2.0 in WIM format • Image usually contains • WDS Client (setup binaries) • PXE boot binaries • Install Images • Sysprepped OS image in WIM format • Basic option – Pull images from DVD • Custom option –Admin-specified WIM files Maintenance Configuration Image Add Deployment Installation
Scenario WalkthroughImage deployment • Choose a boot method for WinPE • PXE boot • Other media – CD, DVD, hard drive, UFD, etc… • Complete WDS Client installation screens • Complete first boot actions (OOBE) Maintenance Configuration Image Add Deployment Installation
Scenario WalkthroughImage maintenance • Creation of custom sysprepped images using the WDS image capture utility • Updates include drivers, language packs, and hotfixes / QFEs • Offline servicing = updating an image prior to installation onto new hardware • Bring image offline and service on WDS Server • Online servicing = updating the image post installation to new hardware • Use Windows SIM to create unattend files and apply packages during deployment Maintenance Configuration Image Add Deployment Installation
Technology OverviewWDS Server • WDS Server service • Core PXE Server • Image Store + Communication Protocol • TFTPD • Transport protocol used during PXE boot and WinPE download • File share that contains • Windows PE boot images • Windows installation images • Windows Imaging (WIM) format provides single instancing and compression • Related management files • Windows Server “Longhorn” RMT integration
Windows PE PXE boot Scenario: network boot into Windows PE and run custom installation Technical DrilldownNetwork boot support • Scalable PXE server built on unified architecture • Replaceable plug-ins • Published APIs • Does not require Active Directory • Scenario: write plug-in that talks to SQL database WDS Service • Server supports one or more plug-ins • Plug-ins can use any data store Plug-in PXE Server Plug-in Plug-in
Image Groups Units of single instancing and security File resources live in RES.RWM Metadata only WIMs Filtering vs. Security Images referenced by name and image group Technical DrilldownImage Store Images ImageGroup1 Resource only WIM RES.RWM Install.WIM Metadata only WIM Install $OEM$ LangPacks Unattend Install2.WIM Install2 ImageGroup2
Technology OverviewWDS management • Single set of management tools for common server tasks • UI tool = MMC console application (common tasks) • Command-line tool = scriptable (all tasks) • Both tools use MGMT API layer • Remote administration • Other WDS MGMT utilities • WDS Capture utility – GUI utility to capture images into WIM format • “Light” version of ‘IMAGEX /capture’ functionality + UI • Active Directory Users and Computers extension • Updated version of RISETUP (Server 2003 Only)
Technical DrilldownWDS Image Capture walkthrough Create WDS Capture image from existing WinPE boot image using MGMT tools Image Capture Process 1 2 Install OS on reference machine WIM Customize OS, install apps and drivers, etc. 3 Run Sysprep WDS Capture 4 Boot into WDS Capture image 5 Volume Run WDS Capture utility to create image (optionally upload to WDS server) 6
Technology OverviewWDS Client • Client setup application that runs within WinPE • Special mode of Windows Vista’s Image Based Setup (IBS) • Allows deployment of Windows Vista / Windows Server “Longhorn” and down-level images • Logic to communicate with WDS server • Drives the client setup experience • UI flow unique to WDS installations • Language selection / regional options allow for • Changing keyboard layout and input device • WDS Client UI language • Installing language packs (Windows Vista / Windows Server “Longhorn” only) • Automation using unattend.xml settings
Technical DrilldownPXE boot of WIM image • Boot option supported for WinPE 2.0 images only • Enabled through file system mini-filter (wimfsf.sys) and OS loader functionality • EFI machines = pxeboot.com functionality included in bootmgfw.efi RAM on Client Machine Boot.SDI Boot.WIM Volume (NTFS) SDI Header Bootmgr.exe PXEBoot.com System32 BCD Winload.exe RAMDISK
WDS Server Client Unattend Image Unattend Get WDS settings based on Machine $OEM$ (downlevel) Get WDS settings based on User Options limited based on image selected WDS Client (WinPE phase) Reboot OS First Boot Cred Image Sel. Disk Config WDS Module WDS Module Apply Image OS Config/Settings driven by unattend (.txt or .xml) No persistence of setup options / settings through reboot. Begin processing image unattend. Blackboard Technical DrilldownUnattended installations • Unattended installation options include • PXE Boot – pressing F12 not required • WDS Client • OOBE / first boot • Domain Join (uses unattend mechanism)
demo Windows Deployment Services
Technology OverviewIntegration with New Deployment Technologies • Image Based Setup (IBS) • WDS Client runs as a special mode of Setup.exe • WDS Client shares UI with IBS • Full localization and accessibility functionality • Support for various input device types and keyboard layouts • WinPE • Native boot OS • Platform used to run the WDS Client • Windows Imaging (WIM) • WinPE boots from a compressed WIM file • WDS image store • Image capture utility used to create and deploy custom WIM images • Unattend • WDS Client integration with unattend.xml format • Windows System Image Manager (Windows SIM) • Used to author unattended setup files for use in WDS
WDS binaries but RIS functionality OSChooser RISETUP and RIPREP MGMT through RIS utilities Transition from RISUpgrade from and coexistence with RIS Modes of WDS Operation Legacy Mixed Native • “Best of both worlds” • WinPE and OSChooser • RISETUP, RIPREP and WIM • MGMT of new: WDS MMC / CLI • MGMT of legacy: RIS utils • No RIS functionality • WinPE only • WIM only • MGMT through WDS MMC / CLI Only mode available on LH Server Transition
Thank you to our Partners for their support of TechDays 2007
Tech Days 2007 – Evaluation Form Guidelines Tech Days will be using scanned evaluation forms. We need you to please include your delegate ID number which you received at registration onto the form. If your Delegate ID number is 1234, then please colour in the number 1 on line 1, the number 2 on line 2, the number 3 on line 3 and the number 4 on line 4 so that there is 1 digit on each line to make up the completed 4 digit code. Please fill in your First Name, Surname and Company name in the spaces provided as a back up.
© 2006 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista 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.