Windows Server Guides

Note Pxe Client

The term PXE client refers to the role that a computer takes in the PXE boot process. A PXE

client can be a server, desktop, laptop, or any other computer equipped with a PXE boot

code.

The firmware on a PXE client tries to locate a PXE redirection service on the network through the PXE redirection service (Proxy DHCP) to receive information about available PXE boot servers . The firmware then asks the boot server for the file path of a network bootstrap program (NBP), downloads it into the computer's random access memory (RAM) using TFTP, optionally verifies it, and then executes it .

The PXE protocol can be viewed as a combination of DHCP and TFTP DHCP locates the appropriate boot server or servers; TFTP downloads the initial bootstrap program and additional files

When a PXE boot is initiated, the PXE read-only memory (ROM) requests an IP address from a DHCP server. As part of this process, the client computer identifies itself as being PXE-enabled. When the client obtains a valid IP address from a DHCP server, it attempts to locate and establish a connection with the PXE server to download NBP.

If you use Windows Deployment Services, the PXE server does not need to be authorized. Authorization checks occur only if you choose to enable authorization checking and the PXE server is configured to listen on port 67. In this case, authorization checks take place only in scenarios in which Windows Deployment Services is running on a computer that does not have the DHCP server role installed. If Windows Deployment Services and DHCP are running on the same physical computer, the DHCP server is listening on port 67 and is responsible for ensuring authorization

Windows Deployment Services

You will typically use Windows Deployment Services (WDS) if you deploy new computers in a medium or large organization. WDS enables you to manage images and unattended installation scripts and provides attended and unattended installation options. It facilitates the partitioning and formatting of physical media, the installation of the client operating system, and post-configuration tasks. WDS simplifies installation and provides consistency across your network environment.

WDS provides server components, client components, and management components. Server components include a PXE server, a TFTP server, and a shared folder and image repository that contain boot images, install images, and files needed for the network boot. They also provide a networking layer, a multicast component, and a diagnostics component.

Client components include a GUI. When a user selects an operating system image, the client components communicate with the server components to install the image. Management components consist of a set of tools to manage the server, operating system images, and client computer accounts.

WDS reduces the complexity of deployments and the cost associated with inefficient manual installation processes; facilitates network-based installation of Windows operating systems, including Windows Vista and Windows Server 2008; and deploys Windows images to computers without operating systems. It supports mixed environments that include Windows Vista, Windows Server 2008, Windows XP, and Windows Server 2003 and provides an end-to-end solution for the deployment of Windows operating systems to client computers and servers.

You can configure WDS by using the WDS MMC snap-in or by using the wdsutil command. If you choose to use the wdsutil command, you must run the command prompt as an administrator.

+1 0

Average user rating: 5 stars out of 1 votes