Windows 7 / Getting Started

DHCP Requirements

Windows Deployment Services will configure accessible DHCP servers during installation, adding required scope options to the DHCP scopes. It may be necessary under some circumstances to modify DHCP servers manually to support advanced Windows Deployment Services scenarios. The following list describes how to manage DHCP scope modifications:

  • Microsoft DHCP and Windows Deployment Services on the same server When Windows Deployment Services is installed on the same physical server as the DHCP service, the Windows Deployment Services PXE server and the DHCP server will both attempt to listen on port 67 for DHCP requests. To prevent this, the Windows Deployment Services PXE server must be configured not to listen on this port. This allows booting PXE clients to learn about the presence of the Windows Deployment Services PXE server from the DHCP response generated by the DHCP server.
  • Microsoft DHCP and Windows Deployment Services on separate servers with the clients on the same subnet as the Windows Deployment Services server When Windows Deployment Services and Microsoft DHCP exist on different servers, no additional settings are required. Both servers respond to DHCP requests. The DHCP server responds with an IP address offer; the Windows Deployment Services PXE server responds with the PXE boot information.
  • Microsoft DHCP and Windows Deployment Services on separate servers with the clients on a different subnet from the Windows Deployment Services server The recommended approach in this scenario is to use IP Helper tables on the router or switch to forward PXE requests to the Windows Deployment Services server (as well as the DHCP server). An alternative approach is to configure DHCP options 66 and 67 on all scopes to specify the Windows Deployment Services server and the path to the boot program.
  • Third-party DHCP and Windows Deployment Services on separate servers No additional action should be required for Windows Deployment Services to coexist with third-party DHCP servers. The Windows Deployment Services PXE server will respond with boot file location information only, allowing DHCP to service the IP address request.

Note RIS requires the RIS server to be authorized as a DHCP server in AD DS. This is not required to operate Windows Deployment Services.

[Previous] [Contents] [Next]

In this tutorial:

  1. Configuring Windows Deployment Services
  2. Introducing Windows Deployment Services
  3. Service Architecture
  4. PXE Services
  5. Operating Modes
  6. Legacy Mode
  7. Mixed Mode
  8. Native Mode
  9. Planning for Windows Deployment Services
  10. Choosing a Version of Windows Deployment Services
  11. New Features of Windows Deployment Services in Windows Server 2008 R2
  12. Server Requirements
  13. Client Computer Requirements
  14. DHCP Requirements
  15. Routing Requirements
  16. Capacity Requirements
  17. Installing Windows Deployment Services
  18. Windows Server 2003
  19. Windows Server 2008 R2
  20. Windows 7 Configuring Deployment Services
  21. Preparing Discover Images
  22. Windows Importing Images
  23. Importing Boot Images
  24. Importing Install Images
  25. Managing and Deploying Driver Packages
  26. Deploying Driver Packages to Clients Using Method 1
  27. Deploying Driver Packages to Clients Using Method 2
  28. Deploying Driver Packages to Clients Using Method 3
  29. Managing Driver Groups and Driver Packages
  30. Adding Driver Packages to Boot Images
  31. Managing Image Security
  32. Pre-staging Client Computers
  33. Configuring Administrator Approval
  34. Windows 7 Installing
  35. Capturing Custom Images
  36. Creating Multicast Transmissions
  37. Performing Multicast Deployment
  38. Using Windows Deployment Services with Microsoft Deployment Toolkit