Windows Vista Deployment Tools Anders Bjrling Senior Consultant

Windows Vista Deployment Tools Anders Björling Senior Consultant Microsoft

Agenda Windows Imaging Format (WIM) files Windows Deployment Services (WDS) Windows Automating Installation KIT (WAIK) System Image Manager (SIM) Image. X Windows PE USMT 3. 0

Going Out on a WIM File-based Image Format Introduced with SMS 2003 OSD Feature Pack *Store Multiple Images within one actual file File based imaging Enables compression and single instancing (a technique which allows you to store two or more copies of a file for the space cost of one copy) Service an image offline Install a disk image on partitions of any size Provides API for WIM image for developers Non-destructive deployment

Why Do I Care? Vista ships on a WIM (Install. WIM) Windows PE ships on a WIM inside the WAIK (Winpe. wim)

What Else Has Changed? Going away: Unattend. txt, Sysprep. inf, Winbom. ini, Cmdlines. txt => unattend. xml WINNT. exe, WINNT 32. exe, and source-based installs => setup SYSOCMGR => OCSETUP (online) ocsetup. exe "DHCPServer" /quiet /norestart SYSOCMGR => PKGMGR (offline) pkgmgr /o: "C: wim_mount; C: wim_mountWindows" /n: "C: unattend. xml"

HAL independence One image can support all hardware No support for non-ACPI hardware BUT: One Hal for 32 bit arch and one Hal for 64 bit arch

Image-Based Setup (IBS) All Windows Vista release will ship as a Sysprep’d image (install. WIM) Setup applies (install. WIM) Images, using Unattend answer files (Unattend. XML) for custom installation Windows Vista Setup supports upgrading FAT/FAT 32 to NTFS, with the default format type NTFS Two ways to “Install” Windows Vista: Apply install. WIM and use Unattend. XML to customize setup. EXE Install Vista, configure, capture, and deploy using Vista Imaging tools (Image. X)

Tools of the Trade Digging into the tools

Introduction Design 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 / Co-existence path from RIS

Introduction Product Technology Roadmap Historically • 3 overlapping solutions • Dissimilar infrastructures • Gaps in functionality SMS 2003 10/03 Address critical shortterm SMS & ADS needs Unify infrastructure, consolidate to 2 clearly differentiated solutions • Address key SMS & ADS customers needs • Still have overlapping solutions and dissimilar infrastructures • WDS platform designed for IT Generalist / MORG, LORG & core OEM scenarios • SMS designed for MORG & LORG advanced scenarios • ADS scenarios largely incorporated into SMS 2003 OSD FP SMS v 4 Q 404 SMS v 4 OS Deployment builds on WDS VSMT ADS 1. 0 9/03 Q 404 ADS 1. 1 WDS RTW RIS in WS 2003 CY 2003 Transfer technology 2004 2005 Longhorn Client Timeframe WDS in LH Server Longhorn Server Timeframe & Beyond

Introduction Release Roadmap WDS Server WDS MGMT OOB Hotfix for Server 2003 SP 1 WDS Server WDS MGMT Server 2003 SP 2 WDS Client Windows Vista Longhorn Server WDS Client WDS Server WDS MGMT BETA Q 2 2006 RTM Q 3 2006 Q 4 2006 H 1 2007 H 2 2007

Scenarios New Machine Deployment End-to-end solution for clean installs Bare metal Machine re-provisioning Deployment of Windows Vista, Longhorn Server, Windows XP, Win 2 K 3, and Win 2 K 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

Scenarios PXE Boot of Windows PE Common Win. PE uses Custom deployment solution Recovery environment RAMDISK boot support for Win. PE 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

Scenarios Extensibility Points Scalable PXE server built on unified architecture Replaceable plug-ins augment core networking functionality Published APIs Able to run without Active Directory Win. PE PXE boot files for 3 rd party PXE Server use Client < - > Server communication protocol Develop custom deployment application SMS & BDD use extensibility points

Scenario Walkthrough End-to-End Deployment Installing the server Configuring the server Adding images Deploying a client Maintaining images Installation Configuration Image Add Deployment Maintenance

Scenario Walkthrough Installing the Server Methods of installation Server 2003 = install the hotfix / service pack Longhorn Server = install the server role Actions Copy server binaries Create services Installation Configuration Image Add Deployment Maintenance

Scenario Walkthrough Configuring 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 Installation Configuration Image Add Deployment Maintenance

Scenario Walkthrough Adding Images Boot Images Win. PE 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 Installation Configuration Image Add Deployment Maintenance

Scenario Walkthrough Image Deployment Choose a boot method for Win. PE PXE boot Other media – CD, DVD, hard drive, UFD, etc… Complete WDS Client installation screens Complete first boot actions (OOBE) Installation Configuration Image Add Deployment Maintenance

Scenario Walkthrough Image 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 Installation Configuration Image Add Deployment Maintenance

Windows Deployment Services

Transition from RIS Upgrade from and Co-existence with RIS Modes of WDS Operation Legacy Mixed Native WDS binaries but RIS functionality OSChooser RISETUP and RIPREP MGMT through RIS utilities “Best of both worlds” Win. PE and OSChooser RISETUP, RIPREP and WIM MGMT of new: WDS MMC / CLI MGMT of legacy: RIS utils No RIS functionality Win. PE only WIM only MGMT through WDS MMC / CLI Transition Only mode available on LH Server

End-To-End Walkthrough Option 60 Client DHCP PXE ROM 2. Boot Image Selection 3. Image Selection and Apply Port 67 Option 60 PXE Request MMC CLI Management Interface (API) Service WDS Server DHCP Discover 1. PXE Phase WDS Server (PXE) BINL … Port 4011 Unattend RPC Network Layer WDS Image Store Files Reg Credentials Image Metadata REMINST TFTP of PXE boot files and Win. PE SMB download of install image Boot Images Active Directory

Windows Automated Installation Kit (WAIK) Imaging Setup Windows System Image Manager XImage Installs on Windows Longhorn, Windows Vista, Windows XP SP 2 (. NET Framework 2. 0 required) A suite of tools designed to help OEMs and large enterprises deploy Windows Vista.

Automated Installation Kit

System Image Manager (SIM) Replacement for Setup Manager Interacts live with a “catalog” of an installation Generates unattend. XML Built in validation of unattend. xml Can be confusing at first

Unattend. XML <unattend xmlns="urn: schemas-microsoft-com: asm. v 3"> <settings> <component name="setup"> <User. Data> <Accept. Eula>yes</Accept. Eula> <Full. Name>Windows User</Full. Name> <Computer. Name>winvista-beta 1</Computer. Name> <Product. Key>ABCDE-FGHIJ-KLMNO-PQRST-UVWXY</Product. Key> </User. Data> <Auto. Logon> <Logon User. Name="username" Password="password" Count="3" /> </Auto. Logon> <Image. Install> <Image> <Install. To Disk. ID="0" Partition. ID="1" /> </Image. Install> </component> </settings> </unattend>

System Image Manager

Tools of the Trade: Image. X Command line tool for WIM management Learn to use this Mount Windows PE to a directory to modify Mount a Windows Vista WIM to insert an unattend file Mount a Windows Vista WIM to insert a script, file or hotfix Split a WIM into distribution chunks (CD size) Capture/Apply a disk Contains an API

Image Editing Enabled with file system mini-filter (wimfltr. sys) Mount an image to a specified folder Images must be mounted to an existing file system Allows for read/write access to an image Changes are queued and can be committed or discarded with an unmount operation Mounted Image 2 Mount Windows Program Files Temp Users tmp files 3 1 4 Mount(RW) Images Commit vista. wim

Image. X

MUI Support Multi-language support (MUI) Windows Vista is language-neutral at its core No localized versions Multiple language packs available for Enterprise Languages can be added and removed

Pkgmgr additional language

Windows PE Bootable, special purpose Windows environment Not DOS Use for these Windows Vista tasks Installation Troubleshooting Recovery

Windows PE 2. 0 Now available to everyone for deploying Windows Vista! Key part of the Windows Vista deployment and recovery process “Hot” (online) Plug n Play support Can be serviced offline just like Windows Vista Inject drivers, add or remove optional components offline (PEIMG) Inject drivers online (Drvload) Boot from RAM with compressed WIM image Creates a writeable 32 MB ramdisk

Windows PE 2. 0 Things you can do Can format partitions with NTFS Network access using Windows Vista drivers Can use VBScript for complex tasks Extensible with XML Unattend. xml on Win. PE

Tools for Working With Windows PE tools Disk. Part Drvload (Online) Oscdimg PEImg (Offline) BCDEdits the Boot Configuration Data (BCD) Use to add Windows PE to the boot menu

Windows PE

User State Migration Tool 3. 0 Support for Windows Vista and Office 2007 Integrates with Configuration Manifest Infrastructure (CMI) for migrating OS settings to Windows Vista New XML-based configuration files Encryption capability Minor command line changes One part of a larger migration engine Is the workflow, not the logic

USMT 3. 0 Requirements Sufficient disk space for saved state data Source computer Windows 2000 Professional Windows XP Home, Windows XP Professional x 64 Windows Vista, Windows Vista Itanium, Windows Vista x 64 Destination computer Windows XP versions Windows Vista versions Microsoft Internet Explorer 5 or later

Scan. State and Load. State Scan. State Collects files and settings from source computer Controlled by XML files Creates USMT 3. MIG file Load. State Controlled by XML files Reads USMT 3. MIG file Restores saved state onto destination computer