2.3 Windows Deployment Services
WDS enables an end user without any technical expertise to
start a computer with no operating system and simply select a
Windows image to install from a menu. To achieve this, the computer
relies on a pre-startup execution environment (PXE) startup
process. PXE is a technology that uses Dynamic Host
Configuration Protocol (DHCP) to locate a specially configured
network server during a computer’s startup phase.
Note
PXE-BOOT COMPUTERS
For a WDS client computer to find a WDS server, the client
computer must have a PXE–startup compatible network card.
WDS is a far more scalable and manageable solution than is
simply storing WIM files on a network. However, WDS does have fairly
extensive infrastructure requirements:
-
AD DS A Windows Deployment
Services server must be either a member of an Active Directory
domain or a domain controller for an Active Directory domain.
The Active Directory domain and forest versions are irrelevant;
all domain and forest configurations support Windows Deployment
Services.
-
Dynamic Host Configuration
Protocol You must have a working DHCP server with an
active scope on the network because Windows Deployment Services
uses PXE, which in turn uses DHCP. The DHCP server does not have
to be on the Windows Deployment Services server, but it (or a
DHCP relay agent) does need to be on the same subnet as the
client.
-
Domain Name System A
working Domain Name System (DNS) server on the network is
required to run Windows Deployment Services. The DNS server does
not have to be running on the Windows Deployment Services
server.
-
NTFS volume The server
running Windows Deployment Services requires an NTFS file system
volume for the image store.
-
A high-speed, persistent connection
between the WDS servers and the target computers Such a
connection is necessary because of the size of the images being
distributed to the target computers. In addition, these servers
should be on subnets adjacent to the target computers to ensure
high-speed connectivity.
Aside from the extensive infrastructure requirements of WDS,
another limitation of this deployment solution is that it requires
end-user participation. The administrator cannot simply choose to
push an operating system to any computer in the organization.
As a result of these limitations, WDS does not scale well to
the largest corporate networks with multiple Active Directory
domains, IP subnets, or physical sites.
Note
WDS OUTSIDE OF ACTIVE
DIRECTORY
Windows Deployment Services is a server role that includes
the optional Transport Server role service. This role service
enables the transmission of any files or folders (such as
operating system images, data files, or an MP3 archive) without an
Active Directory infrastructure or DHCP. Using Transport Server to
deploy an operating system is far more complicated than using the
Deployment Server role service of WDS, which is the usual WDS role
service reserved for operating system deployment. Outside Active
Directory domains, you will most likely find deploying Windows 7
and Windows Server 2008 R2 to be easier by using network
shares.
2.4 System Center Configuration Manager 2007 R3
When used in conjunction with the other deployment methods,
System Center Configuration Manager 2007 R3 enables you to create a
fully managed deployment solution for large organizations. Unlike
other deployment options, System Center Configuration Manager 2007
R3 allows for a completely unattended operating system deployment to
remote computers.
System Center Configuration Manager 2007 R3 assists with the
many tasks involved when you apply automated procedures to multiple
servers and client computers, tasks such as:
-
Selecting computers that have the hardware necessary for a
given operating system and that you are ready to support.
-
Distributing the operating system source files to all
sites, including remote sites and sites without technical
support staff.
-
Monitoring the distribution to all sites.
-
Providing the appropriate user rights for the
upgrade.
-
Automatically initiating the installation of software
packages, with the possibility of having users control the
timing.
-
Resolving problems related to the distributions or
installations.
-
Reporting on the rate and success of deployment.
-
Verifying that all computers in your organization have
received the standardized operating system configuration.
Deploying Windows 7 or Windows Server 2008 R2 with System
Center Configuration Manager 2007 R3 requires a high-speed,
persistent connection between the servers and target computers used
in the deployment process. Such a connection is necessary because of
the large size of the images being distributed to the target
computers.
Among the disadvantages of System Center Configuration Manager 2007 R3 is, first,
that unlike the other deployment methods mentioned, it is a separate product requiring a
purchase beyond Windows Server 2008 or Windows Server 2008 R2. In addition, installing
and configuring a System Center Configuration Manager 2007 R3 infrastructure requires
significant technical expertise. A third disadvantage of System Center Configuration
Manager 2007 R3 is that, unlike WDS, you can’t use it to deploy an operating
system onto a bare-metal system without using bootable media. The target computer
requires the System Center Configuration Manager 2007 client software or is booted by
using other bootable media. (Because of this last limitation, in fact, System Center
Configuration Manager 2007 R3 is typically used in conjunction with WDS and not as a
replacement for it.)
