4
How do you deploy your servers today? How long does the process take, start to finish? Do you have consistent, repeatable, documented processes? Is you process flexible enough to handle technology changes such as those introduced by Windows Server code name “Longhorn”?

5
But it’s just like desktop deployment, right? Well, it’s not quite that simple…

7
Servers have some unique challenges: OS configuration is more involved Role installation and configuration, server product installation, etc. Settings could greatly affect stability, functioning of the server Security is crucial Migration processes are different Upgrades are more common (in some scenarios) Side-by-side migrations are common Refresh is rare

10
Windows Server “Longhorn” changes the landscape New capabilities are available Customers and partners will need to do some reengineering New products to consider…

11
Windows Deployment Services New features in Windows Server “Longhorn”: Multicast with an improved algorithm Join multicast sessions at any time Flow control and congestion control to improve reliability Improved TFTP performance TFTP windowing Configurable block size x64 Extensible Firmware Interface (EFI) support Replacement for the venerable BIOS The near future

12
DEMO

13
System Center Configuration Manager (SCCM) 2007 To be released in H2 CY07 Service Pack 1 will be required for full Windows Server “Longhorn” support Significant investments in OS deployment capabilities, task sequencing, integration with WDS Improves on the SMS 2003 OS Deployment Feature Pack Picks up much of the functionality from ADS The near future

14
DEMO

15
Windows Server Deployment Solution Accelerator Tying it all together Based on BDD 2007 (which will continue supporting Windows Vista and Windows XP deployments, as well as SMS 2003 OSD), to provide consistent tools for client and server Leverage the latest tools and technologies To be released shortly after Windows Server “Longhorn” The near future

23
Servicing and componentization The OS is made up of components Each component exposes its configuration Patches, service packs, and languages are components too and can be applied offline! Drivers can be injected just like components Roles leverage components Setup Exclusively image-based, no more text-mode 32- or 64-bit executable Image on the DVD is SYSPREP’d No more BOOT.INI, uses BCD instead

24
XML files Unattend.txt is now Unattend.xml Sysprep.inf is now Unattend.xml WINBOM.INI is now Unattend.xml CMDLINES.TXT is now Unattend.xml (kind of) Notepad is no longer the preferred editing tool USMT now uses XML instead of INF files HAL independence One image can support all hardware No support for non-ACPI hardware

25
Microsoft Windows Preinstallation Environment (Windows PE) Core part of the deployment process Available to everyone! DOS is dead Imaging File-based Windows Imaging Format (WIM) images are key Tools are available to create, modify, mount, deploy, service, etc. There is no such thing as “i386 source”

28
Windows Server Deployment Solution Accelerator can help Shows you how to use the new deployment tools together as part of an end-to-end deployment process Provides tools and scripts to increase automation and lower costs Leverages and enhances other Microsoft tools and products Simplifies the overall experience Even the tools require guidance Things to watch out for, decisions that need to be made, possible alternatives