Transcript Installing Windows Deployment Service

Installing Windows Deployment
Service
Option 1: Install both Deployment Server and
Transport Server role service (which is the
default)
Option2: Install only the Transport Server role
service
Installing Windows Deployment
Service
Option 2 is for advanced scenarios, such as
environment w/o AD DS, DNS, DHCP.
Option 2 enable you to boot from the network
using PXE, Pre-Boot Execution Environment, and
TFTP, Trivial File Transfer Protocol, a multicast
server, or both. (PXE, TFTP, FTP)
Option 2 does not contain or support WDS image
store.
What is PXE?
The Preboot eXecution Environment (PXE, also
known as Pre-Execution Environment;
sometimes pronounced "pixie") is an
environment to boot computers using a
network interface independently of data
storage devices (like hard disks) or installed
operating systems.
What is PXE?
It makes use of several network protocols like
Internet Protocol (IP), User Datagram Protocol
(UDP), Dynamic Host Configuration Protocol
(DHCP) and Trivial File Transfer Protocol (TFTP)
and of concepts like Globally Unique Identifier
(GUID), Universally Unique Identifier (UUID) and
Universal Network Device Interface and extends
the firmware of the PXE client (the computer to
be bootstrapped via PXE) with a set of
predefined Application Programming Interfaces
(APIs).
Transport Server
• Must be a member of Local Administrators
group on the server to install the roll service.
Deployment Server
AD DS.
A WDS server must be either a member of an AD
DS domain or a domain controller for an AD DS
domain.
(The AD DS domain and forest versions are
irrelevant; all domain and forest configurations
support WDS.)
Deployment Server
DHCP
Needs a working DHCP server with active scope
on the network because WDS uses PXE, which
relies on DHCP for IP addressing.
DNS
Needs a working DNS server on the network
before you can run WDS.
Deployment Server
NTFS
The server running WDS requires an NTFS file
system volume for the image store.
To install the role, you must be a member of the
Local Administrators group on the server. To
initialize the server, you must be a member of
the Domain User group.
DHCP Option 60
• If you install WDS on a server that’s already
running DHCP, during the configuration of
WDS the DHCP Option 60 page will appear.
• If you install DHCP on a machine that already
has WDS installed, you must manually enable
Option 60 in DHCP.
DHCP Option 60
• WDS and DHCP are installed on the same server:
• You must tell WDS not to listen on port UDP 67,
leaving it available for DHCP traffic only.
• You set Option 60 in DHCP for the client to find the
WDS server.
• During a WDS client’s boot process, the normal DHCP
traffic occurs. The client broadcasts for an IP address
to port 67.
• Traditionally, only DHCP listens on port UDP 67, but
WDS also listens on port UDP 67.
DHCP Option 60
• Needed only if:
• You have a PXE Service that binds on UDP 4011 and
that runs on the same host that also runs a dhcp
service (bound on UDP 67)
• You need this PXE Service to provide the "network
boot program" details to your PXE clients.
These details are actually: TFTP server IP address
(DHCP option 66) and network boot program file
name (DHCP option 67)
DHCP Option 60
• do not set this dhcp option 60 if you have a PXE
Service running on an host that does not run any
dhcp or bootp service.
DHCP Option 60
• If your TFTP server runs on the host with IP address
192.168.1.10, and if your network boot program file
name is pxelinux.0, just configure your dhcp server
so that its option 66 is "192.168.1.10" and option 67
is "pxelinux.0".
• No dhcp option 60, no "PXEClient".
• Note that your DHCP server can also run on the same
host (192.168.1.10 in this example)