User's Manual

Choosing a Microsoft
®
Windows
®
PE-Based Deployment Method 21
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 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 document. If you plan to utilize a third-party deployment
solution framework, keep in mind that the DTK is a Windows PE-based set of tools and scripts, so the
deployment solution framework must also support embedded Windows PE as a pre-operating
system environment.
Deployment Matrix (Windows PE)
Depending on the scope, current business needs, network setup, and process, you might select any of the
suggested methods of deployment. Table 2-1 outlines three typical methods of deployment and the
environment most suitable for each.
Table 2-1. Deployment Method Matrix
Deployment Methods Complexity Advantages Disadvantages
Local deployment
(bootable CD)
Relatively simple
• Necessary if a network connection
is not available or is too slow.
• Can install supported Windows
operating systems.
• Any change requires the
creation of a new
bootable CD.
• Limited space on CD for
some operating system
installation files.
• Deployment tasks must
be performed at the
individual target system.
• CDs are read-only media
and require the creation
of a RAMDISK for
temporary data storage.
• Installation time is high.