Dell External OEMR 2850, User Manual

Page: 29 / 176

Choosing a Microsoft Windows PE-Based Deployment Method
29
Bootable Windows PE CD With Networking Enabled
This process includes:
• Creating a bootable Windows PE CD with the appropriate network
drivers. This step enables networking services to start, get an IP address,
and bring the target system into a functioning network.
NOTE:
See "Running Deployment Scripts Using DTK and Microsoft Windows
PE" for details on how to create a customized version of a single Windows PE
bootable CD that works across all Dell supported systems and provides an
underlying networking stack.
• Creating scripts to automatically map to a predefined network share.
• Accessing scripts, configuration files, and operating system installation
files from the network.
Preparing and Populating the Network Share
This process includes:
• Creating a network share on a system that is always available over the
network for the target systems to be deployed
• Ensuring that a large amount of space is available for storing operating
system installation files
• Ensuring that proper permissions are assigned to this share so that the
target systems can read files from and write files to the share
This deployment method is also easy to assemble. In addition, it provides
greater flexibility in terms of making changes to the scripts and configuration
files. Any change to the system configuration, for example, will not require
re-creation of the bootable CD. This method also provides access to the
remote share as writable media. Hence, the configuration files captured
during the deployment automation process can be saved to this remote share.
Using a Third-Party Deployment Solution Framework
You can use the DTK with any existing third-party deployment solution
framework that provides a
Automated Deployment Services (ADS) booting
infrastructure for Windows PE 1.0 or Windows Deployment Services (WDS)
booting infrastructure for Windows PE 2.0 that can be used as the transport
mechanism for the DTK utilities. Because each third-party deployment
framework is unique, however, these solutions fall outside the scope of this