PXE boot not working
Hi, Have you configured WDS not to respond to "UseDHCPPorts = 0" from technet: You must have a functioning DHCP server with an active scope. WDS will utilize PXE which requires a DHCP server. Whether you plan to co-host WDS and DHCP on the same server or use two different servers you must configure WDS to listen on a specific port. DHCP and WDS both require port number 67. If you have co-hosted WDS and DHCP you can move DHCP or the PXE site role to a separate server or use the procedure below to configure the WDS server to listen on a different port. Modify the following registry key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WDSServer\Providers\WDSPXE Set the registry value to: UseDHCPPorts = 0 For the new configuration to take effect run the following command on the co-located DHCP and WDS server: WDSUTIL /Set-Server /UseDHCPPorts:No /DHCPOption60:Yes More information: http://technet.microsoft.com/en-us/library/bb680753.aspx Regards, jrgen-- My System Center blog ccmexec.com -- Twitter @ccmexec
September 25th, 2012 5:50am

Hi, I have a Windows Server 2008(VM) running with Domain Controller, DNS, DHCP, WDS. I want another VM (in the same physical machine) to boot over network (PXE/Network boot). I have made the following configurations, Created a Legacy Network adapter and mapped it to the new VMConfigured DHCP with following scope options, 003, 006, 015, 060, 066Made the VM to boot from Legacy Network adapterReserved an IP for VM with its MAC address in DHCP But still the VM is not getting an IP address from the server. What other configurations to be made? Thanks, Ashok Prabhu. J
Free Windows Admin Tool Kit Click here and download it now
October 1st, 2012 5:32am

Hi, Have you configured WDS not to respond to "UseDHCPPorts = 0" from technet: You must have a functioning DHCP server with an active scope. WDS will utilize PXE which requires a DHCP server. Whether you plan to co-host WDS and DHCP on the same server or use two different servers you must configure WDS to listen on a specific port. DHCP and WDS both require port number 67. If you have co-hosted WDS and DHCP you can move DHCP or the PXE site role to a separate server or use the procedure below to configure the WDS server to listen on a different port. Modify the following registry key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WDSServer\Providers\WDSPXE Set the registry value to: UseDHCPPorts = 0 For the new configuration to take effect run the following command on the co-located DHCP and WDS server: WDSUTIL /Set-Server /UseDHCPPorts:No /DHCPOption60:Yes More information: http://technet.microsoft.com/en-us/library/bb680753.aspx Regards, jrgen-- My System Center blog ccmexec.com -- Twitter @ccmexec
October 1st, 2012 5:42am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics