Creating, Validating, and Testing Boot Images

2014-11-18 19:28| 发布者: Test| 查看: 318| 评论: 0|来自: Microsoft

摘要: Applies To: Windows Server 2008 R2 Create a Windows PE image to use with ImageX for copying your image If you have the Windows Automated Installation Kit (WindowsAIK) installed, you can view the inst ...

Applies To: Windows Server 2008 R2

Create a Windows PE image to use with ImageX for copying your image

If you have the Windows Automated Installation Kit (Windows AIK) installed, you can view the instructions for creating a Windows PE image in “Step-by-Step: Basic Windows Deployment for IT Professionals,” located in the documentation directory of the Windows AIK installation.

Important
You must run a 64-bit version of Windows on the computer that is used to create the Windows PE image for the image to be deployable on a computer running Windows Server 2008 R2. Because Windows Server 2008 R2 is available only in 64-bit versions, this documentation discusses the creation and use of only 64-bit Windows PE versions.

Note
The Windows AIK is required for the following procedure. If you have installed the Windows AIK by using the default directory location, you can copy and paste the following commands into a command prompt.

To create bootable Windows PE media for use with ImageX

On your technician computer, run the copype.cmd script to create a local Windows PE build directory. For example, at a command prompt, type:

cd C:\Program Files\Windows AIK\Tools\PETools\copype.cmd

where can be x86, amd64, or ia64, and is the path to the local directory. For example:

copype.cmd amd64 C:\winpe_amd64
Copy winpe.wim to the appropriate folder, and then rename it to boot.wim. For example: copy C:\winpe_amd64 C:\winpe_amd64\ISO\sources\boot.wim and rename it to copy C:\winpe_amd64 C:\winpe_amd64\ISO\sources\boot.wim.
Optionally, create a configuration file called Wimscript.ini by using a text editor such as Notepad. The configuration file instructs the ImageX tool to exclude certain files during the capture operation. For example:

[ExclusionList]
- ntfs.log
- hiberfil.sys
- pagefile.sys
- "System Volume Information"
- RECYCLER
- Windows\CSC
[CompressionExclusionList]
- *.mp3
- *.zip
- *.cab
- \WINDOWS\inf\*.pnf

Save the configuration file to the same location as the ImageX tool as specified in the previous step. For example:

C:\winpe_amd64\ISO\

Important
The ImageX tool automatically detects Wimscript.ini only if the .ini file is saved to the same location as the ImageX tool. We also recommend that you include the bcdboot tool in the ISO layout, which will be needed when deploying images to make the image bootable after deployment.

Copy C:\Program Files\Windows AIK\Tools\AMD64\bcdboot.exe C:\winpe_amd64\ISO\.
Copy the following files to the C:\winpe_amd64\Boot directory:
- Copy C:\Program Files\Windows AIK\Tools\AMD64\oscdimg.exe C:\winpe_amd64\Boot
- Copy C:\Program Files\Windows AIK\Tools\PETools\amd64\boot\etfsboot.com C:\winpe_amd64\Boot
Create an image (.iso) file by using the oscdimg tool. For example, at a command prompt, type:

cd C:\winpe_amd64\Boot

oscdimg.exe -n -betfsboot.com C:\winpe_amd64\ISO C:\winpe_amd64\winpe_amd64.iso
Burn the image (winpe_x86.iso) to a CD-ROM disc. The Windows AIK does not include CD-ROM burning software. Use trusted third-party software to burn the image to a CD-ROM disc.

You now have a bootable Windows PE RAM CD containing the ImageX tool. For more information about Windows PE, see the Windows Preinstallation Environment (Windows PE) User’s Guide (Winpe.chm).

Capture the installation onto a network share

Capture an image of your source computer by using Windows PE and the ImageX tool. Then, store that image on a network share. Alternatively, you can save this image to another drive, such as a connected USB flash drive, or you can mount the iSCSI disk on another computer, and then capture the image for deployment.

To capture the installation onto a network share

On your source computer, insert your Windows PE media and restart the computer.

Note
To boot from the CD/DVD-ROM drive, you may have to override the boot order. During initial boot, select the appropriate function key to override the boot order.

Windows PE starts and then launches a command prompt window. You may wish to run diskpart and use “List vol” to list all the available volumes to ensure that you are using the correct drive letters for your image. The letters in use will likely be different from the ones that were in use when you last restarted the computer.

Capture an image of the reference installation by using the ImageX tool located on your Windows PE media. For example, at the command prompt, type:

e:\imagex.exe /capture d: d:\myimage.wim "my Win7 Install" /compress fast /verify
Copy the image to a network location. You can do this because Windows PE provides network support. For example, at the command prompt, type:

net use y: \\network_share\images copy d:\myimage.wim y:
If necessary, provide network credentials for appropriate network access.

Integrate iSCSI Software Initiator support into a Windows PE image

Important
This section is intended for installation purposes only, and does not include support for MPIO with iSCSI connections.

Note
This procedure is only required if you want to access the iSCSI Initiator graphical user interface (GUI) from Windows PE to access an iSCSI target device that is not the boot device, such as an additional iSCSI disk to copy a deployment image to or from. The command line version of iSCSI (msiscsicli.exe) is accessible from Windows PE.

The following are prerequisites for doing this installation:

A computer that is running Windows Server 2008 R2 and using the Windows AIK
A DVD burner and software

To integrate iSCSI Software Initiator support into a Windows PE image

After installing the Windows AIK, open the deployment command prompt (Administrator: Windows PE Tools Command Prompt), and then do the following:
1. Run copype.cmd . For example, copype.cmd AMD64 C:\bin. When complete, the command prompt changes to C:\bin.
2. Mount the boot.wim by using the following: imagex /mountrw C:\bin\ISO\sources\boot.wim 1 C:\bin\mount
Add drivers as appropriate by using the Dism command with the /Add-Driver option. For example:

Dism /image:C:\winpe_x86\mount /Add-Driver /driver:C:\test\drivers\mydriver.inf

Copy the following files from a computer that is running Windows Server 2008 R2 to the corresponding folder of the mounted Windows Imaging Format (WIM):

Note
Some of the files may already be in the Windows PE image.

        
    

                
            
\windows\System32
iscsicli.exe
iscsicpl.dll
iscsicpl.exe
iscsidsc.dll
iscsied.dll
iscsiexe.dll
iscsium.dll
iscsiwmi.dll
8 File(s)        918,120 bytes

\windows\System32\Drivers
msiscsi.sys
1 File(s)        168,552 bytes

\windows\System32\en-US
iscsicpl.dll.mui
iscsicpl.exe.mui
iscsidsc.dll.mui
iscsiexe.dll.mui
4 File(s)         84,992 bytes

Mount the registry hives for editing by doing the following:

Click Start, click Run, type regedit.exe, and then press ENTER.
On the User Account Control page, click Continue.
Click HKEY_LOCAL_MACHINE, and on the File menu, click Load Hive.
Change the directory to C:\bin\mount\windows\system32\config.
Click Software, and then click OK.
When you are prompted for a name, type PE_Soft.

Repeat the preceding steps to mount the System hive. When you are prompted for a name, type PE_Sys.

Note
The naming convention is important to ensure that you do not have to rename the corresponding portions of the registry files. The names must match or the relevant sections will not be added.

Merge PE_Soft.reg and PE_Sys.Reg into the registry hives that were loaded in the previous steps. See the sections that follow this procedure to copy the contents that are required for these two files.

Unload the hives by doing the following:
1. In regedit, click PE_Soft, and on the File menu, click Unload Hive.
2. Click PE_Sys, and on the File menu, click Unload Hive.
Unmount and commit the changes to the WIM. For example:

imagex /commit /unmount C:\bin\mount

Software registry hive (PE_Soft)

This section includes the contents that you must add to a text file named PE_Soft.reg to merge the registry hive.

        
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\PE_Soft\Microsoft\Windows NT\CurrentVersion\Svchost]

"Godzilla"=hex(7):4d,00,53,00,69,00,53,00,43,00,53,00,49,00,00,00,00,00

[HKEY_LOCAL_MACHINE\PE_Soft\Microsoft\Windows NT\CurrentVersion\iSCSI]

[HKEY_LOCAL_MACHINE\PE_Soft\Microsoft\Windows NT\CurrentVersion\iSCSI\Discovery]
"AllowiSNSFirewallException"=dword:00000001

[HKEY_LOCAL_MACHINE\PE_Soft\Microsoft\Windows NT\CurrentVersion\iSCSI\Discovery\Authentication Cache]

[HKEY_LOCAL_MACHINE\PE_Soft\Microsoft\Windows NT\CurrentVersion\iSCSI\Discovery\Send Targets]

[HKEY_LOCAL_MACHINE\PE_Soft\Microsoft\Windows NT\CurrentVersion\iSCSI\Discovery\Static Targets]

[HKEY_LOCAL_MACHINE\PE_Soft\Microsoft\Windows NT\CurrentVersion\iSCSI\Discovery\Tunnel Address]

System registry hive (PE_Sys)

This section includes the contents that you must add to a text file named PE_Sys.reg to merge the registry hive.

        
    

                
            
Windows Registry Editor Version 5.00
 [HKEY_LOCAL_MACHINE\PE_Sys\ControlSet001\Enum\Root\LEGACY_MSISCSI]
"NextInstance"=dword:00000001

[HKEY_LOCAL_MACHINE\PE_Sys\ControlSet001\Enum\Root\LEGACY_MSISCSI\0000]
"Service"="MSiSCSI"
"Legacy"=dword:00000001
"ConfigFlags"=dword:00000000
"Class"="LegacyDriver"
"ClassGUID"="{8ECC055D-047F-11D1-A537-0000F8753ED1}"
"DeviceDesc"="@%SystemRoot%\\system32\\iscsidsc.dll,-5000"

[HKEY_LOCAL_MACHINE\PE_Sys\ControlSet001\Enum\Root\ISCSIPRT]

[HKEY_LOCAL_MACHINE\PE_Sys\ControlSet001\Enum\Root\ISCSIPRT\0000]
"ClassGUID"="{4d36e97b-e325-11ce-bfc1-08002be10318}"
"Class"="SCSIAdapter"
"HardwareID"=hex(7):52,00,4f,00,4f,00,54,00,5c,00,69,00,53,00,43,00,53,00,49,\
  00,50,00,72,00,74,00,00,00,00,00
"ConfigFlags"=dword:00000000
"Driver"="{4d36e97b-e325-11ce-bfc1-08002be10318}\\0000"
"Mfg"="@iscsi.inf,%msft%;Microsoft"
"Service"="iScsiPrt"
"DeviceDesc"="@iscsi.inf,%iscsiprt%;Microsoft iSCSI Initiator"
"Capabilities"=dword:00000000

[HKEY_LOCAL_MACHINE\PE_Sys\ControlSet001\Enum\Root\ISCSIPRT\0000\Device Parameters]

[HKEY_LOCAL_MACHINE\PE_Sys\ControlSet001\Enum\Root\ISCSIPRT\0000\Device Parameters\StorPort]

[HKEY_LOCAL_MACHINE\PE_Sys\ControlSet001\Enum\Root\ISCSIPRT\0000\LogConf]

[HKEY_LOCAL_MACHINE\PE_Sys\ControlSet001\Enum\Root\ISCSIPRT\0000\Control]
"ActiveService"="iScsiPrt"

[HKEY_LOCAL_MACHINE\PE_Sys\ControlSet001\Services\iScsiPrt]
"DisplayName"="iScsiPort Driver"
"ImagePath"=hex(2):73,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,44,00,\
  52,00,49,00,56,00,45,00,52,00,53,00,5c,00,6d,00,73,00,69,00,73,00,63,00,73,\
  00,69,00,2e,00,73,00,79,00,73,00,00,00
"ErrorControl"=dword:00000001
"Start"=dword:00000000
"Type"=dword:00000001

[HKEY_LOCAL_MACHINE\PE_Sys\ControlSet001\Services\iScsiPrt\Parameters]
"BusType"=dword:00000009

[HKEY_LOCAL_MACHINE\PE_Sys\ControlSet001\Services\iScsiPrt\Enum]
"0"="Root\\ISCSIPRT\\0000"
"Count"=dword:00000001
"NextInstance"=dword:00000001

[HKEY_LOCAL_MACHINE\PE_Sys\ControlSet001\Services\MSiSCSI]
"DisplayName"="@%SystemRoot%\\system32\\iscsidsc.dll,-5000"
"Group"="iSCSI"
"ImagePath"=hex(2):25,00,73,00,79,00,73,00,74,00,65,00,6d,00,72,00,6f,00,6f,00,\
  74,00,25,00,5c,00,73,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,73,\
  00,76,00,63,00,68,00,6f,00,73,00,74,00,2e,00,65,00,78,00,65,00,20,00,2d,00,\
  6b,00,20,00,6e,00,65,00,74,00,73,00,76,00,63,00,73,00,00,00
"Description"="@%SystemRoot%\\system32\\iscsidsc.dll,-5001"
"ObjectName"="LocalSystem"
"ErrorControl"=dword:00000001
"Start"=dword:00000002
"Type"=dword:00000020
"ServiceSidType"=dword:00000001
"RequiredPrivileges"=hex(7):53,00,65,00,41,00,75,00,64,00,69,00,74,00,50,00,72,\
  00,69,00,76,00,69,00,6c,00,65,00,67,00,65,00,00,00,53,00,65,00,43,00,68,00,\
  61,00,6e,00,67,00,65,00,4e,00,6f,00,74,00,69,00,66,00,79,00,50,00,72,00,69,\
  00,76,00,69,00,6c,00,65,00,67,00,65,00,00,00,53,00,65,00,43,00,72,00,65,00,\
  61,00,74,00,65,00,47,00,6c,00,6f,00,62,00,61,00,6c,00,50,00,72,00,69,00,76,\
  00,69,00,6c,00,65,00,67,00,65,00,00,00,53,00,65,00,43,00,72,00,65,00,61,00,\
  74,00,65,00,50,00,65,00,72,00,6d,00,61,00,6e,00,65,00,6e,00,74,00,50,00,72,\
  00,69,00,76,00,69,00,6c,00,65,00,67,00,65,00,00,00,53,00,65,00,49,00,6d,00,\
  70,00,65,00,72,00,73,00,6f,00,6e,00,61,00,74,00,65,00,50,00,72,00,69,00,76,\
  00,69,00,6c,00,65,00,67,00,65,00,00,00,53,00,65,00,54,00,63,00,62,00,50,00,\
  72,00,69,00,76,00,69,00,6c,00,65,00,67,00,65,00,00,00,00,00
"FailureActionsOnNonCrashFailures"=dword:00000001
"FailureActions"=hex:50,46,00,00,01,00,00,00,01,00,00,00,03,00,00,00,14,00,00,\
  00,01,00,00,00,c0,d4,01,00,01,00,00,00,e0,93,04,00,00,00,00,00,00,00,00,00
"RebootMessage"="See Note 3 below"
"FailureCommand"="customScript.cmd"

[HKEY_LOCAL_MACHINE\PE_Sys\ControlSet001\Services\MSiSCSI\Parameters]
"ServiceDll"=hex(2):25,00,73,00,79,00,73,00,74,00,65,00,6d,00,72,00,6f,00,6f,\
  00,74,00,25,00,5c,00,73,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,\
  69,00,73,00,63,00,73,00,69,00,65,00,78,00,65,00,2e,00,64,00,6c,00,6c,00,00,\
  00
"ServiceDllUnloadOnStop"=dword:00000001

[HKEY_LOCAL_MACHINE\PE_Sys\ControlSet001\Services\MSiSCSI\Enum]
"0"="Root\\LEGACY_MSISCSI\\0000"
"Count"=dword:00000001
"NextInstance"=dword:00000001

[HKEY_LOCAL_MACHINE\PE_Sys\ControlSet001\Services\netbt]
"Start"=dword:00000000

[HKEY_LOCAL_MACHINE\PE_Sys\ControlSet001\Services\AFD]
"Start"=dword:00000000

[HKEY_LOCAL_MACHINE\PE_Sys\ControlSet001\Services\Tcpip]
"Start"=dword:00000001

[HKEY_LOCAL_MACHINE\PE_Sys\ControlSet001\Services\MSiSCSI]
"ImagePath"=hex(2):25,00,73,00,79,00,73,00,74,00,65,00,6d,00,72,00,6f,00,6f,00,\
  74,00,25,00,5c,00,73,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,73,\
  00,76,00,63,00,68,00,6f,00,73,00,74,00,2e,00,65,00,78,00,65,00,20,00,2d,00,\
  6b,00,20,00,47,00,6f,00,64,00,7a,00,69,00,6c,00,6c,00,61,00,00,00

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\PE_Sys\ControlSet001\Control\Class\{4D36E97B-E325-11CE-BFC1-08002BE10318}]
"LegacyAdapterDetection"=dword:00000000
"Class"="SCSIAdapter"
"ClassDesc"="@%SystemRoot%\\System32\\SysClass.Dll,-3005"
@="@%SystemRoot%\\System32\\SysClass.Dll,-3005"
"IconPath"=hex(7):25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,\
  74,00,25,00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,73,\
  00,65,00,74,00,75,00,70,00,61,00,70,00,69,00,2e,00,64,00,6c,00,6c,00,2c,00,\
  2d,00,31,00,30,00,00,00,00,00
"Installer32"="SysClass.Dll,ScsiClassInstaller"

[HKEY_LOCAL_MACHINE\PE_Sys\ControlSet001\Control\Class\{4D36E97B-E325-11CE-BFC1-08002BE10318}\0000]
"InfPath"="iscsi.inf"
"InfSection"="iScsiPort_Install_Control"
"ProviderName"="Microsoft"
"DriverDateData"=hex:00,80,8c,a3,c5,94,c6,01
"DriverDate"="6-21-2006"
"DriverVersion"="6.0.6000.16386"
"MatchingDeviceId"="root\\iscsiprt"
"DriverDesc"="Microsoft iSCSI Initiator"
"EnumPropPages32"="iscsipp.dll,iSCSIPropPageProvider"

[HKEY_LOCAL_MACHINE\PE_Sys\ControlSet001\Control\Class\{4D36E97B-E325-11CE-BFC1-08002BE10318}\0000\Parameters]
"TCPConnectTime"=dword:0000000f
"TCPDisconnectTime"=dword:0000000f
"WMIRequestTimeout"=dword:0000001e
"DelayBetweenReconnect"=dword:00000005
"MaxPendingRequests"=dword:000000ff
"EnableNOPOut"=dword:00000000
"MaxTransferLength"=dword:00040000
"MaxBurstLength"=dword:00040000
"FirstBurstLength"=dword:00010000
"MaxRecvDataSegmentLength"=dword:00010000
"MaxConnectionRetries"=dword:ffffffff
"MaxRequestHoldTime"=dword:0000003c
"LinkDownTime"=dword:0000000f
"IPSecConfigTimeout"=dword:0000003c
"InitialR2T"=dword:00000000
"ImmediateData"=dword:00000001
"ErrorRecoveryLevel"=dword:00000002
"PortalRetryCount"=dword:00000005
"NetworkReadyRetryCount"=dword:0000000a
"SrbTimeoutDelta"=dword:0000000f

[HKEY_LOCAL_MACHINE\PE_Sys\ControlSet001\Control\Class\{4D36E97B-E325-11CE-BFC1-08002BE10318}\0000\PersistentTargets]
@=""

[HKEY_LOCAL_MACHINE\PE_Sys\ControlSet001\Control\Class\{4D36E97B-E325-11CE-BFC1-08002BE10318}\Properties]
"DeviceType"=dword:00000004
"DeviceCharacteristics"=dword:00000100
"Security"=hex:01,00,04,90,00,00,00,00,00,00,00,00,00,00,00,00,14,00,00,00,02,\
  00,34,00,02,00,00,00,00,00,14,00,ff,01,1f,10,01,01,00,00,00,00,00,05,12,00,\
  00,00,00,00,18,00,ff,01,1f,10,01,02,00,00,00,00,00,05,20,00,00,00,20,02,00,\
  00

Create an ISO image to burn to a CD or DVD

For additional details, see “Walkthrough: Create a Custom Windows PE Image” in the WinPE.CHM file, included with the Windows AIK.

To create a bootable CD-ROM

On your technician computer, at a command prompt, create an .iso file by using oscdimg. For example,

oscdimg -n –b C:\winpe_AMD64\etfsboot.com C:\winpe_ AMD64\ISO c:\winpe_ AMD64\winpe_ AMD64.iso
Burn the image (winpe_ AMD64.iso) to a DVD-ROM by using a utility capable of burning an .iso image to DVD.

Test and validate the completed Windows PE image

After you have copied the customized Windows PE bits to your choice of media (DVD/CD/USB flash drive) and booted to Windows PE, complete the following procedure.

To test and validate the Windows PE image if you have integrated support for the iSCSI GUI

At a command prompt, type Net start MSiSCSI, and then press ENTER.
Change directories to x:\windows\system32, type iscsicpl.exe, and then press ENTER. This launches the graphical user interface (GUI) for the Microsoft iSCSI Initiator.
On the iSCSI device, provision the storage and set up the device to authenticate with PE iSCSI qualified name (IQN).
On the computer that is running Windows PE, do the following:
1. On the iSCSI GUI, click the Target tab, and then, in the Quick Connect field, type the portal (IP address for the target computer).
2. Log on to the computer.
3. Open a command prompt, type diskpart, and then press ENTER.
4. Type list disk, and then press ENTER.
5. Select the new disk by typing Select Disk where X is the disk number of the disk that is connected, and then press ENTER.
6. Create the partition, format it, and then assign a drive letter to it. For example, to create a partition, format it as NTFS, and assign the next available drive letter, you would use the following commands:
  
  Create Partition Primary
  
  Format FS=NTFS quick
  
  Assign
  
  :
7. Test the target.

--------------------------------------------------------------------

Typo in step 2 of To create bootable Windows PE Media for use with ImageX

The article says:

Copy winpe.wim to the appropriate folder, and then rename it to boot.wim. For example: copy C:\winpe_amd64 C:\winpe_amd64\ISO\sources\boot.wim and rename it to copy C:\winpe_amd64 C:\winpe_amd64\ISO\sources\boot.wim.

I think it should say:

Copy winpe.wim to the appropriate folder, and then rename it to boot.wim. For example: copy

Copy C:\winpe_amd64\winpe.win C:\winpe_amd64\ISO\sources\boot.wim.

Typo in step 3 of To create bootable Windows PE Media for use with ImageX

The contents of the Wimscript.ini file should be in code example style similar to the listing of files to copy in step 3 of "To integrate the iSCSI Software Initiator..."

Typo in step 4 of To create bootable Windows PE Media for use with ImageX

First paragraph refers to the location of the ImageX tool "as specified in the previous step". The previous step covers creating Wimscript.ini.

There is a missing step before step 3 covering copying the ImageX tool to the WinPE target folder. EG

copy "c:\program files\Windows AIK\Tools\amd64\imagex.exe" c:\winpe_amd64\iso\

Typo in step 6 of To create bootable Windows PE Media for use with ImageX

The folder c:\winpe_amd64\boot is not created in the previous steps. The copy commands as listed will create a file called boot.

The etfsboot.com file is already in the c:\winpe_amd64 folder. The oscdimg.exe file should probably be placed there too and step 7 modified to run from that folder.