1. Enabling Diskless Windows Boot With iSCSI Suzanne Morgan Program Manager WDEG Storage Microsoft Corporation Steve Marfisi Manager Development emBoot Inc.

2. iSCSI Momentum And Market 40% of large U.S. enterprise respondents have already deployed or intend on to deploy iSCSI SANs by the end of 2006 – Lehman Brothers Sept. CIO Survey Vast Majority of iSCSI Initiator hosts run Windows Blade Server is the fastest growing server segment Migration from DAS to SAN benefits apply to boot volumes as well as Data volumes iSCSI Initiator Ports 0 200,000 400,000 600,000 800,000 1,000,000 1,200,000 1,400,000 200420052006200720082009 1-Gbps NIC, Driver Ports 1-Gbps Accelerated NIC Ports 1-Gbps HBA Ports 10-Gbps NIC, Driver Ports 10-Gbps Accelerated NIC Ports 10-Gbps HBA Ports

3. iSCSI Software Enabled SAN Boot Goals High Availability Multipath support for load balancing and failover Support for Microsoft Cluster Server Lower Deployment Cost Reduce costs of Deploying sets of identical Windows Systems Use standard imaging tools available today Reduce SAN boot cost to entry and connectivity cost Blade Server Cost Optimization Removing hard drive reduces cooling, power consumption Lower cost for blade vendors to manufacturer blades Disaster and Recovery Boot LUN can be replicated to remote sites Server can boot standby boot LUN in case of failure Deployed Servers can be re-purposed

4. Architecture And Solution Solution Enables boot from LUN located on iSCSI SAN Can be implemented in either NIC Option ROM, Server ROM or PXE No changes needed to NIC driver in Windows iSCSI Software Initiator UNDI Microsoft iSCSI Microsoft Windows Vendor Int13 NDIS iBF Table Boot Parameter Driver NIC TCPIP NIC NDIS Miniport PreBootWindows

5. Deployment Notes iSCSI Software Enabled SAN boot is designed to be deployed via existing image cloning tools on the market today Support for iSCSI boot RFC 4173 Including DHCP Option 17 and Option 12 Microsoft is investigating the support of single image boot functionality (multiple servers booting from a single image with individual identities) in a future Windows release

6. iSCSI Target Support For Boot Nothing unique needed on the iSCSI target side Supported with iSCSI targets Logo’d under the Designed for Windows Logo Program for hardware

7. Solution Framework Solution is enabled by Microsoft Participating NIC, server vendor or IHV implements required changes in their firmware/BIOS (Tested via WHQL) Solution/configuration prescribed/ delivered by OEM or solution provider Boot version Betas/RC can be downloaded from http://connect.microsoft.com/ Invitation Code: ms-8RR8-6K43 http://connect.microsoft.com/ iSCSI Boot Solutions can be submitted to www.microsoftstoragepartners.com www.microsoftstoragepartners.com

8. iSCSI Boot Component Logo Requirement Highlights Compliance with iSCSI RFC Including support for login redirection Compliance with existing DHCP/TCP industry specifications Implement iBFT (iSCSI Boot Firmware Table) per specification Compliance with existing industry BIOS specifications

9. Longhorn Server iSCSI Boot Futures Support of Windows/setup installation of Windows Server directly to iSCSI target LUN From Windows Installation CD or network share Supported with new imaging mechanisms included with Windows Longhorn Server

10. Steve Marfisi Manager Development emBoot Inc.

11. emBoot Architecture – iSCSI OptionROM iSCSI Software Initiator UNDI Microsoft iSCSI Microsoft Windows Vendor Int13 NDIS iBF Table Boot Parameter Driver NIC TCPIP iSCSI OptionROM can obtain iSCSI parameters via: DHCP root path options winBoot/i server Hot-key menu for R/W local parameters Vendor or emBoot supplied UNDI NIC NDIS Miniport PreBootWindows iSCSI Software Initiator TCP/IP NIC or BIOS Integration

12. emBoot Architecture – PXE OptionROM PXE OptionROM obtains iSCSI parameters via winBoot/i server Vendor or emBoot supplied UNDI iSCSI Software Initiator UNDI Int13 NDIS iBF Table Boot Parameter Driver NIC TCPIP NIC NDIS Miniport PreBootWindows iSCSI Preboot Initiator TCP/IP PXE Integration PXE / TFTP Server Downloaded iSCSI Bootstrap winBoot/i Server Microsoft iSCSI Microsoft Windows Vendor

13. winBoot/i Implementation Lessons Learned Disk Imaging – need to consider Availability of existing imaging tools Ability to handle open files or local disk offline Key things to consider as implementing Platform's PXE firmware and Windows NIC driver should be revved to latest versions

14. winBoot/i Implementation OEM integration for NIC or BIOS/System vendors available optionROM payload requirements (uncompressed) in BIOS are approx. 82-88 KB depending on the UNDI layer optionROM re-uses UNDI layer, no need to develop new transport Some OEM customization may be needed to get/set/configure boot parameters End user software product Shipping in Q2, 2006

15. Blade chassis with 3 blades, each with power- chewing, potential-for- failure hard disks. iSCSI storage installed on network. Boot volumes carved out of iSCSI storage and assigned client (initiator) names, matching corresponding blades’ iSCSI initiator name. Microsoft iSCSI-boot- capable initiator + winBoot/i client tools installed on blades. winBoot/i server software installed. Blades’ network adapters are assigned to iSCSI boot volumes. Hard disks’ boot volumes copied to iSCSI storage. winBoot/i clients are now ready for iSCSI boot, using one of: emBoot PXE bootstrap emBoot OptionROM on NIC emBoot OptionROM embedded in BIOS Local disks can now be removed, or kept for paging or other swapping tasks. Blades are started, and receive boot instructions from winBoot/i management. iSCSI storage delivers OS+applications+data to winBoot/i clients (blades)

16. iSCSI Boot Demo

17. Call To Action Implement Windows supported architecture for iSCSI boot Review iSCSI Boot Component Logo requirements prior to implementation Included in latest Logo doc version Test iSCSI boot pre-boot init & target interoperability iSCSI boot pre-boot init & UNDI interoperability NDIS miniport in iSCSI boot configurations E-mail: for access to spec for early implementation Boot @ microsoft.com

18. iSCSI Boot Implementers

19. iSCSI Boot Solution Providers

20. Additional Supporting iSCSI Vendors http://www.microsoft.com/windowsserversystem/storage/technologies/iscsi/default.mspx

21. Related WinHEC Sessions STO116: Windows SAN: Resolving Technical Barriers to Adoption and Deployment STO123: Windows Storage Directions: Windows Vista and Beyond STO133: Windows Vista Storage Support and Logo Requirements SER112: Windows Enterprise Storage Directions SER119: Windows Server High Availability with Windows Server Longhorn Failover Clustering

22. iSCSI Resources Microsoft iSCSI website http://www.microsoft.com/windowsserversystem/storage/iscsi.mspx Download Latest Microsoft iSCSI Initiator http://www.microsoft.com/downloads/details.aspx?FamilyID =12cb3c1a-15d6-4585-b385-befd1319f825&DisplayLang=en http://www.microsoft.com/downloads/details.aspx?FamilyID =12cb3c1a-15d6-4585-b385-befd1319f825&DisplayLang=en Microsoft support for iSCSI Clusters FAQ http://www.microsoft.com/windowsserversystem/ storage/technologies/iscsi/iscsicluster.mspx http://www.microsoft.com/windowsserversystem/ storage/technologies/iscsi/iscsicluster.mspx iSCSI deployment guide white paper http://www.microsoft.com/windowsserversystem/ storage/technologies/iscsi/deployiscsi.mspx http://www.microsoft.com/windowsserversystem/ storage/technologies/iscsi/deployiscsi.mspx For information about iSCSI support http://support.microsoft.com/default.aspx To get a list of vendors with iSCSI Software enabled SAN boot solutions More information on XIMAGE and Vista/Longhorn Server Deployment http://www.microsoft.com/technet/windowsvista/expert/ximage.mspx Boot @ microsoft.com

23. © 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.