Справочник Пользователя для HP (Hewlett-Packard) HP SmartStart Scripting Toolkit Win32 Edition Best Practices
Configuring HP ProLiant systems with Windows PE 17
PXE-based Windows PE deployment
This section describes how to use a PXE server to boot Windows® PE through a network. Review the
server specification to determine whether PXE is supported on the target server. Currently, the Microsoft®
RIS server is the only PXE server officially supported by Microsoft® with Windows® PE. Third-party PXE
servers have not been validated with Windows® PE. Refer to RIS documentation for information about
setting up and using RIS.
server specification to determine whether PXE is supported on the target server. Currently, the Microsoft®
RIS server is the only PXE server officially supported by Microsoft® with Windows® PE. Third-party PXE
servers have not been validated with Windows® PE. Refer to RIS documentation for information about
setting up and using RIS.
NOTE: Using a PXE server to boot Windows® PE through a network is only supported when used in
conjunction with RIS.
Using PXE to boot Windows® PE eliminates the need to create a physical Windows® PE CD. Because the
Windows® PE image files reside in the RIS server, files can easily be modified if needed. With network
access, scripts, utilities, and data files can be stored on the RIS server or on other file servers on the
network. For detailed information about using RIS with Windows® PE, refer to the Windows® PE tools
documentation.
Windows® PE image files reside in the RIS server, files can easily be modified if needed. With network
access, scripts, utilities, and data files can be stored on the RIS server or on other file servers on the
network. For detailed information about using RIS with Windows® PE, refer to the Windows® PE tools
documentation.
To build a Windows® PE image for use with a PXE server to automatically configure an HP ProLiant
system:
system:
1.
Build the Windows® PE folder structure as described in "Microsoft Windows Preinstallation
Environment (on page
Environment (on page
2.
Store the command batch file on RIS or on other servers on network. In the following example, the
customized command batch file is located on \\fileserver\share.
customized command batch file is located on \\fileserver\share.
factory -winpe
net use f: \\fileserver\share
f:\startdeploy.cmd
net use f: \\fileserver\share
f:\startdeploy.cmd
For more information about using a batch file, refer to "Unattended configuration using startnet.cmd
(on page
(on page
3.
Use the edited STARTDEPLOY.CMD file to begin the deployment process. Be sure that the
STARTDEPLOY.CMD script is located in the directory that will be used to create the Windows® PE
ISO image. If STARTDEPLOY.CMD is used to create a connection to a network resource, the file must
exist on the CD.
STARTDEPLOY.CMD script is located in the directory that will be used to create the Windows® PE
ISO image. If STARTDEPLOY.CMD is used to create a connection to a network resource, the file must
exist on the CD.
To use the Windows® PE image with RIS, refer to the Windows® PE tools documentation.
Network-based Windows PE deployment
This section assumes that the scripts, data files, and utilities are stored on a file server. Windows® PE runs
startnet.cmd at the end of the boot process and launches the customized command batch file
automatically.
startnet.cmd at the end of the boot process and launches the customized command batch file
automatically.
To build a Windows® PE image to automatically configure an HP ProLiant system through a network:
1.
Build the Windows® PE folder structure as described in "Microsoft Windows Preinstallation
Environment (on page
Environment (on page
2.
Modify WinPE_Directory\Platform\system32\startnet.cmd to include the following:
factory -winpe
net use f: \\fileserver\share
f:\startdeploy.cmd
net use f: \\fileserver\share
f:\startdeploy.cmd
For more information about using a batch file, refer to "Unattended configuration using startnet.cmd
(on page
(on page
3.
Use the edited STARTDEPLOY.CMD file to begin the deployment process. Be sure that the
STARTDEPLOY.CMD script is located in the directory that will be used to create the Windows® PE
STARTDEPLOY.CMD script is located in the directory that will be used to create the Windows® PE