WDS allows you to capture the following kinds of images using the Windows Image
(.wim) format:
■ Boot Image Windows PE 2.0 is the new boot image format and it presents
you with a boot menu that contains a list of images that users can
install. The standard boot images included with Vista and Server 2008 are
located on the installation media at \Sources\boot.wim.
■ Capture Image This launches the WDS capture utility instead of Set-up.
The reference computer previously prepared with Sysprep boots into a
capture image and becomes the host from which an image is created, and
then saves the image as a .wim file.
■ Discover Image This forces the client computer to start in WDS mode
to discover the WDS server. This is meant for computers that are not
PXE-enabled.
■ Install Image The standard install image included with Vista and
Windows Server 2008 is located on the installation media at \Sources\
install.wim.
The following prerequisites are required for creating images:
■ Sufficient disk space is needed when creating new images; also, images
must be kept on an NTFS volume.
■ A writable CD or DVD drive with writable media is required for creating
bootable media.
■ Local Administrator membership is required.
■ The version of sysprep.exe that is running to prepare a client computer
to be captured must match the version of sysprep.exe located on that
operating system.
■ Windows IAK is needed to create bootable .ISO images.
You can also associate an unattend file with an image. This means you will be
able to deploy images with WDS to client computers and have the unattend.xml
file answer all the questions needed by user input (such as entering credentials,
choosing an install image, and configuring the disk), making the operating system
rollout completely automatic. The unattend file is stored on the WDS server in the
\WDSClientUnattend folder. This is called the WDS client unattend file.
A second unattend file is called the Image unattend file. It is used to automate
the remaining phases of setup (e.g., offline servicing, Sysprep specialize, and
Mini-Setup).
In addition to installing the Deployment Server you also have the choice of
installing the Transport Server. The Transport Server will be used to enable multicast
downloads of data. This is a subset of the functionality of WDS. The Transport
Server can be a stand-alone server and does not need the AD DS, DHCP, or DNS
server roles to function.
Creating multicast transmissions of images allows you to deploy a large number
of client computers without putting a burden on the network. By default, this feature
is disabled. The following two options are available for the multicast type:
■ Auto-Cast As two clients request the same image at different timed intervals
they are both joined to the same transmission.
■ Scheduled-Cast Based on a schedule specified by date and or start time,
the transmission will begin for a number of clients requesting images.
(.wim) format:
■ Boot Image Windows PE 2.0 is the new boot image format and it presents
you with a boot menu that contains a list of images that users can
install. The standard boot images included with Vista and Server 2008 are
located on the installation media at \Sources\boot.wim.
■ Capture Image This launches the WDS capture utility instead of Set-up.
The reference computer previously prepared with Sysprep boots into a
capture image and becomes the host from which an image is created, and
then saves the image as a .wim file.
■ Discover Image This forces the client computer to start in WDS mode
to discover the WDS server. This is meant for computers that are not
PXE-enabled.
■ Install Image The standard install image included with Vista and
Windows Server 2008 is located on the installation media at \Sources\
install.wim.
The following prerequisites are required for creating images:
■ Sufficient disk space is needed when creating new images; also, images
must be kept on an NTFS volume.
■ A writable CD or DVD drive with writable media is required for creating
bootable media.
■ Local Administrator membership is required.
■ The version of sysprep.exe that is running to prepare a client computer
to be captured must match the version of sysprep.exe located on that
operating system.
■ Windows IAK is needed to create bootable .ISO images.
You can also associate an unattend file with an image. This means you will be
able to deploy images with WDS to client computers and have the unattend.xml
file answer all the questions needed by user input (such as entering credentials,
choosing an install image, and configuring the disk), making the operating system
rollout completely automatic. The unattend file is stored on the WDS server in the
\WDSClientUnattend folder. This is called the WDS client unattend file.
A second unattend file is called the Image unattend file. It is used to automate
the remaining phases of setup (e.g., offline servicing, Sysprep specialize, and
Mini-Setup).
In addition to installing the Deployment Server you also have the choice of
installing the Transport Server. The Transport Server will be used to enable multicast
downloads of data. This is a subset of the functionality of WDS. The Transport
Server can be a stand-alone server and does not need the AD DS, DHCP, or DNS
server roles to function.
Creating multicast transmissions of images allows you to deploy a large number
of client computers without putting a burden on the network. By default, this feature
is disabled. The following two options are available for the multicast type:
■ Auto-Cast As two clients request the same image at different timed intervals
they are both joined to the same transmission.
■ Scheduled-Cast Based on a schedule specified by date and or start time,
the transmission will begin for a number of clients requesting images.
No comments:
Post a Comment