Intel® Server Utilities Deployment Procedure for Windows* Preinstallation Environment White Paper December 2009 Revision 5.
INFORMATION IN THIS DOCUMENT IS PROVIDED IN CONNECTION WITH INTEL® PRODUCTS. NO LICENSE, EXPRESS OR IMPLIED, BY ESTOPPEL OR OTHERWISE, TO ANY INTELLECTUAL PROPERTY RIGHTS IS GRANTED BY THIS DOCUMENT.
Contents 1 Introduction .....................................................................................................5 1.1 1.2 1.3 1.4 1.5 2 Purpose of This Document .......................................................................5 Intended Audience .................................................................................5 Prerequisites .........................................................................................5 Terminology ............................................
Revision History Revision Number Description Revision Date 1.0 Initial release April 2007 2.0 Added information on WinPE* 1.5, 2.0 ,and 2.1 May 2008 3.0 Updated WinPE* 2.0/2.1 with detailed steps to add Intel Utilities and Drivers. January 2009 4.0 Updated Section 2.2, Building WinPE* 2.x Customized Image March 2009 5.0 Added Section 2.3, Building WinPE* 3.
1 Introduction 1.1 Purpose of This Document The purpose of this white paper is to provide basic guidance to prepare a customized Windows* Preinstallation Environment (Windows* PE) image, wherein customization refers to the inclusion of the Intel configuration and deployment Utilities and its drivers to the Windows* PE OS.
The following CDs are required for building WinPE* image Table 1: Prerequisites WinPE* Version 1.4 Build tools Windows* OS WinPE* 1.5 Windows* PE version 2004 CD containing build tools Windows* XP with Service Pack 2 (SP2) CD WinPE* 1.6 Windows* PE version 2005 CD containing build tools Windows* Server 2003 with Service Pack 1 (SP1) CD WinPE* 2.0 Windows Automated Installation Kit*(AIK) v1.0.0.0 Windows* Vista DVD WinPE* 2.1 Windows Automated Installation Kit* (AIK) v1.0.0.
1.5 IMB Driver The Intelligent Management Bus (IMB) driver is the reference implementation of an IPMI specification for the Windows NT operating system. It is a driver that supports IPMB messaging to server management firmware on IPMI conformant servers. IBSMUtil Driver IBSMUtil Driver is used to access SMBIOS data. Flash Update Driver Flash Update Device Driver is used to update the BIOS (Basic Input/Output System) of a server.
2 Steps for Customized Windows*PE CD Preparation 2.1 For WinPE* 1.5 and 1.6 The Microsoft Windows* PE 1.5/1.6 image is modified to install Intel drivers for the execution of Intel utilities.
3. Copy the text in Appendix A and paste above the “network configuration entries” section. Note: Please be careful to do the “Soft return” and “Hard return” when you copy and paste from PDF format Appendix to your c:\build_x86\WINPESYS.INF (Soft return – Press the Enter key; Hard return – Press the keys Shift+Enter) 2.1.3 Step 3: Creating Customized Windows* PE The ‘mkimg.
Windows PE* image files are copied. For example: c:\build_x86\drvinst.exe /inf:c:\Utility_Drivers c:\winpe where ‘c:\Utility Drivers’ contain all of the files for the Intel Server Configuration Utilities including: -IMB driver: imbdrv.inf, imbdrv.sys -IBSMUtil driver: ibsmutil.inf, ibsmutil.sys -Flash Update driver: flashud.inf, FLASHUD.sys This adds Intel driver files (IMB, IBSMUtil and Flash update) to the Windows PE image.
2.1.6 Step 6: Enabling Multi Processor Support This section enables the Multi Processor support for Windows* PE OS. 2.1.7 1. Delete the Uni processor kernel exe (‘ntoskrnl.exe’) in the \i386\system32 folder. For example: del c:\winpe\I386\SYSTEM32\ntoskrnl.exe 2. Rename the Multi processor kernel ‘ntkrnlmp.exe’ to ‘ntoskrnl.exe’. For example: ren c:\winpe\I386\SYSTEM32\ntkrnlmp.exe ntoskrnl.exe 3. Open the ‘txtsetup.sif’ file that is present in \i386\ folder.
2.2 For WinPE* 2.0 and 2.1 This section helps create a customized WinPE 2.x image from Windows* AIK image as detailed in the following sections: Prerequisites Building customized WinPE* 2.x Image. Creating a Bootable WinPE* 2.x CD-ROM, USB flash drive (UFD) and HDD. 2.2.
Note: All the examples continued are for creating x86 based WinPE 2.x image. You can change x86 to amd64 for building an Intel64 WinPE 2.x image. The script creates the following directory structure and copies all the necessary files for that architecture. For Example, \winpe2\x86 \winpe2\x86\ISO \winpe2\x86\mount Your current working directory will now be “c:\winpe2\x86” Step 2: Create a custom WinPE 2.x Image. Mount the base Windows PE* image (Winpe.wim) to the \mount directory by using ImageX.
Repeat the same steps for all the packages mentioned in following table: Table 3: List of Packages to be installed with WinPE* 2.
2.2.3 • Commit changes to the image and unmount Format: IMAGEX /UNMOUNT [/COMMIT] [image_path] imagex /unmount c:\winpe2\x86\mount /commit where, ‘c:\winpe2\x86\mount’ is the path to be unmounted /commit is the flag tp save changes to the mounted WIM file. • Replace the default WinPE2.1 image copy c:\winpe2\x86\winpe.wim c:\winpe2\x86\ISO\sources\boot.wim /Y Creating a Bootable WinPE* 2.x CD, UFD and HDD Step 1: Creating a Bootable WinPE* 2.
Step 3: Create a bootable HDD device. • On the deployment sever, insert your Windows PE media and restart the computer. You can use the step1 (Creating a useable WinPE* 2.1 CR ROM) to create a WinPE* media. • Type “diskpart” from a windows 2008 or Windows PE image. Follow the below sequence of commands, assumption the user understands which is the correct partition assigned to the hard disk based on size of device. In this example it is Disk 0.
2.3 For WinPE* 3.0 This section helps create a customized WinPE 3.0 image from Windows* AIK image as detailed in the following sections: Prerequisites Building WinPE* 3.0 Customized Image Creating a Bootable WinPE* 2.x CD, UFD and HDD Capturing the Installation onto a Network Share Deploying from a Network Share 2.3.1 Prerequisites Following is the prerequisites for building a Windows PE* build image: • Install the Microsoft Windows* Automated Installation Toolkit (AIK) • Install .Net framework 2.
2.3.2 Building WinPE* 3.0 Customized Image This section provides a step-to-step guide to build a WinPE* 3.0 image. The first step in creating a customized Windows® PE 3.0 image is to modify the base Windows PE image (winpe.wim) by using the Deployment Image Servicing and Management (DISM) tool. DISM extracts the files to a local directory and enables you to add and remove packages (optional components and language packs). In addition, you can add out-of-box drivers.
Format: Dism /Mount-wim /WimFile: /index: /MountDir: For example: Dism /Mount-Wim /WimFile:c:\winpe_x86\winpe.
Step 5: • You must use the DISM tool to install the appropriate packages. The packages are located in the directory \Windows AIK\Tools\PETools\ • The winpe-xml package is now included in the base boot.wim. • Since the base image has MSIPMI driver installed by default, insert the “winpe-wmi.
2.3.3 Creating a Bootable WinPE 3.0 CD, UFD and HDD Creating a bootable CD Burn the image (Winpe_x86.iso) to a CD-ROM disc. Windows AIK does not include CDROM burning software. Use trusted third-party software to burn the image to a CDROM disc. Creating a bootable UFD • Connect the UFD to a machine running Windows* 2008 or Windows PE* image • Type “diskpart” from command prompt.
diskpart>list disk diskpart>select disk 0 diskpart>clean diskpart>create partition primary size=350 diskpart>select partition 1 diskpart>active diskpart>format diskpart>exit Caution:- selecting a wrong disk can wipe out entire data. 2.3.4 2.3.5 • Once you have a formatted, active partition, you can copy the Windows PE source files from your bootable media to the hard disk. A Windows PE RAM disk requires the following directory structure.
2. Format the hard drive to reflect the disk configuration requirements by using the DiskPart tool from the Windows PE Command Prompt window.
3 Booting From Customized CD Insert the above-created CD into the computer on which you want to run Windows PE and start the computer. The computer will start Windows PE OS from the CD, which is a read only media. Once the OS is up, the user can navigate to the Intel’s system configuration utilities repository and run the utilities. Note: For WinPE 1.x, plug and play hardware detection occurs only while the Factory.exe Windows PE command runs.
Appendix A - Adding Intel Drivers in winpesys.inf ; ;Intel drivers ; HKLM,"SYSTEM\ControlSet001\Control\Class\{4D36E97D-E325-11CE-BFC108002BE10318}\0001","InfPath",REG_SZ,"oem3.inf" HKLM,"SYSTEM\ControlSet001\Control\Class\{4D36E97D-E325-11CE-BFC108002BE10318}\0001","InfSection",REG_SZ,"IMBDrvInstallSection" HKLM,"SYSTEM\ControlSet001\Control\Class\{4D36E97D-E325-11CE-BFC108002BE10318}\0001","ProviderName",REG_SZ,"Intel, Inc.
HKLM,"SYSTEM\ControlSet001\Control\Class\{4D36E97D-E325-11CE-BFC108002BE10318}\0002","InfSection",REG_SZ,"Flashud_Inst" HKLM,"SYSTEM\ControlSet001\Control\Class\{4D36E97D-E325-11CE-BFC108002BE10318}\0002","InfSectionExt",REG_SZ,".NT" HKLM,"SYSTEM\ControlSet001\Control\Class\{4D36E97D-E325-11CE-BFC108002BE10318}\0002","ProviderName",REG_SZ,"Intel, Inc.
HKLM,"SYSTEM\ControlSet001\Control\Class\{4D36E97D-E325-11CE-BFC108002BE10318}\0003","DriverDate",REG_SZ,"6-5-2006" HKLM,"SYSTEM\ControlSet001\Control\Class\{4D36E97D-E325-11CE-BFC108002BE10318}\0003","DriverVersion",REG_SZ,"1.0.0.0" HKLM,"SYSTEM\ControlSet001\Control\Class\{4D36E97D-E325-11CE-BFC108002BE10318}\0003","MatchingDeviceId",REG_SZ,"*intelutildev" HKLM,"SYSTEM\ControlSet001\Control\Class\{4D36E97D-E325-11CE-BFC108002BE10318}\0003","DriverDesc",REG_SZ,"Intel Server Management Utility Device v1.
HKLM,"SYSTEM\ControlSet001\Enum\Root\SYSTEM\0002","ClassGUID",REG_SZ,"{4D 36E97D-E325-11CE-BFC1-08002BE10318}" HKLM,"SYSTEM\ControlSet001\Enum\Root\SYSTEM\0002","Class",REG_SZ,"System" HKLM,"SYSTEM\ControlSet001\Enum\Root\SYSTEM\0002","HardwareID",REG_MULTI_ SZ,"2a,00,49,00,4e,00,54,00,30,00,38,00,30,00,30,00,00,00,00,00" HKLM,"SYSTEM\ControlSet001\Enum\Root\SYSTEM\0002","Driver",REG_SZ,"{4D36E9 7D-E325-11CE-BFC1-08002BE10318}\\0002" HKLM,"SYSTEM\ControlSet001\Enum\Root\SYSTEM\0002","Mfg",REG_SZ,"Intel, Inc
HKLM,"SYSTEM\ControlSet001\Enum\Root\SYSTEM\0003","Driver",REG_SZ,"{4D36E9 7D-E325-11CE-BFC1-08002BE10318}\\0003" HKLM,"SYSTEM\ControlSet001\Enum\Root\SYSTEM\0003","Mfg",REG_SZ,"Intel Corporation" HKLM,"SYSTEM\ControlSet001\Enum\Root\SYSTEM\0003","Service",REG_SZ,"IBSMUT IL" HKLM,"SYSTEM\ControlSet001\Enum\Root\SYSTEM\0003","DeviceDesc",REG_SZ,"Inte l Server Management Utility Device v1.
HKLM,"SYSTEM\ControlSet001\Services\imbdrv","InstallRefCount",REG_DWORD,0000 0001 HKLM,"SYSTEM\ControlSet001\Services\imbdrv\Security","Security",REG_BINARY,01, 00,14,80,b8,00,00,00,c4,00,00,00,14,00,00,00,30,00,00,00,02,00,1c,00,01,00,00,00 ,02,80,14,00,ff,01,0f,00,01,01,00,00,00,00,00,01,00,00,00,00,02,00,88,00,06,00,00, 00,00,00,14,00,fd,01,02,00,01,01,00,00,00,00,00,05,12,00,00,00,00,00,18,00,ff,01, 0f,00,01,02,00,00,00,00,00,05,20,00,00,00,20,02,00,00,00,00,14,00,8d,01,02,00,01, 01,00,00,00,00,00,05,04
HKLM,"SYSTEM\ControlSet001\Services\int0800\Security","Security",REG_BINARY,01, 00,14,80,b8,00,00,00,c4,00,00,00,14,00,00,00,30,00,00,00,02,00,1c,00,01,00,00,00 ,02,80,14,00,ff,01,0f,00,01,01,00,00,00,00,00,01,00,00,00,00,02,00,88,00,06,00,00, 00,00,00,14,00,fd,01,02,00,01,01,00,00,00,00,00,05,12,00,00,00,00,00,18,00,ff,01, 0f,00,01,02,00,00,00,00,00,05,20,00,00,00,20,02,00,00,00,00,14,00,8d,01,02,00,01, 01,00,00,00,00,00,05,04,00,00,00,00,00,14,00,8d,01,02,00,01,01,00,00,00,00,00,05 ,06,00,00,00,00,00,14,0
0,18,00,fd,01,02,00,01,02,00,00,00,00,00,05,20,00,00,00,23,02,00,00,01,01,00,00,0 0,00,00,05,12,00,00,00,01,01,00,00,00,00,00,05,12,00,00,00 HKLM,"SYSTEM\ControlSet001\Services\IBSMUTIL\Enum","0",REG_SZ,"ROOT\\SYSTE M\\0003" HKLM,"SYSTEM\ControlSet001\Services\IBSMUTIL\Enum","Count",REG_DWORD,0000 0001 HKLM,"SYSTEM\ControlSet001\Services\IBSMUTIL\Enum","NextInstance",REG_DWOR D,00000001 ; ; ; 32 Intel® Server Utilities Deployment Procedure for Windows* Preinstallation Environment – White Paper
