<div>
Hi admitech,<br />
<br />
&nbsp;Apart from DHCP option 66, did you also set 67?<br />
&nbsp;Option 66 is only the server, 67 is the bootimage to use. Normally something like:<br />
&nbsp;boot\x86\pxeboot.com or boot\x64\pxeboot.com<br />
<br />
&nbsp;Regards,<br />
<br />
&nbsp;Luc
</div>


<div>
Luc:<br />
<br />
Thanks I did not. I was not sure what to put for my environment. Is this just generic and based upon x64/32/ia64, etc? Do I need option 60? If so how do I create it?<br />
<br />
Thanks so much!
</div>


<div>
<div class="content wysiwyg-content">
<b>Server</b>: 2012 R2<br />
<b>Mode</b>: Native<br />
<b>PXE</b>: Response set to respond to all then require approval for unknown...<br />
<b>Computer account location</b>: specified to same domain as WDS<br />
<b>Boot</b>: Set to Require the user to press F12 to continue the PXE boot<br />
<b>DHCP</b>: Do not listen on DHCP ports (tried all option for both check boxes)<br />
<b>Multicast:</b> Set to obtain IP address from DHCP<br />
<b><b>DHCP Authorization:</b> This is where it fails! Try to hit the box for &quot;Authorize this Windows Deployment Services server in DHCP. Tried dynamically and explicitly specifying the DC and GC. I get an error (see attached here)</b><br />
<b>Network: </b>Tried dynamic ports from Winsock and the default UDP ports.<br />
<br />
I tried setting up the DHCP scope options for the hostname of WDS. #60 is custom, how do I set this up or maybe I don't need it? The DHCP server and WDS and the client all can communicate but DHCP (clustered) and WDS are on different 2012 R2 servers.<br />
<a href="https://filedb.experts-exchange.com/incoming/2016/09_w40/1119655/WDSfail.PNG" target="_blank" class="file-inline" title="WDSfail.PNG (51 KB)"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 512 512"><path d="M67.508 468.467c-58.005-58.013-58.016-151.92 0-209.943l225.011-225.04c44.643-44.645 117.279-44.645 161.92 0 44.743 44.749 44.753 117.186 0 161.944l-189.465 189.49c-31.41 31.413-82.518 31.412-113.926.001-31.479-31.482-31.49-82.453 0-113.944L311.51 110.491c4.687-4.687 12.286-4.687 16.972 0l16.967 16.971c4.685 4.686 4.685 12.283 0 16.969L184.983 304.917c-12.724 12.724-12.73 33.328 0 46.058 12.696 12.697 33.356 12.699 46.054-.001l189.465-189.489c25.987-25.989 25.994-68.06.001-94.056-25.931-25.934-68.119-25.932-94.049 0l-225.01 225.039c-39.249 39.252-39.258 102.795-.001 142.057 39.285 39.29 102.885 39.287 142.162-.028A739446.174 739446.174 0 0 1 439.497 238.49c4.686-4.687 12.282-4.684 16.969.004l16.967 16.971c4.685 4.686 4.689 12.279.004 16.965a755654.128 755654.128 0 0 0-195.881 195.996c-58.034 58.092-152.004 58.093-210.048.041z"/></svg>WDSfail.PNG</a>
</div>
</div>


WDSfail.PNG

Server: 2012 R2
Mode: Native
PXE: Response set to respond to all then require approval for unknown...
Computer account location: specified to same domain as WDS
Boot: Set to Require the user to press F12 to continue the PXE boot
DHCP: Do not listen on DHCP ports (tried all option for both check boxes)
Multicast: Set to obtain IP address from DHCP
DHCP Authorization: This is where it fails! Try to hit the box for "Authorize this Windows Deployment Services server in DHCP. Tried dynamically and explicitly specifying the DC and GC. I get an error (see attached here)
Network: Tried dynamic ports from Winsock and the default UDP ports.

I tried setting up the DHCP scope options for the hostname of WDS. #60 is custom, how do I set this up or maybe I don't need it? The DHCP server and WDS and the client all can communicate but DHCP (clustered) and WDS are on different 2012 R2 servers.

Windows Deployment Services not communicating to clients. DHCP server and WDS are on separate servers

The Dynamic Host Configuration Protocol (DHCP) is an auto configuration protocol used on IP networks and an extension of the Bootstrap Protocol. DHCP allows for computers to be configured automatically to communicate with each other over an IP network without the need for manual setup by a network administrator. The implementation of DHCP relies on a DHCP server to hand out network configuration information to DHCP-capable clients that request an IP address (and other information required or useful in communicating with other devices on an IP network). In addition to an IP address, common configuration information served over DHCP includes a default gateway, subnet mask and DNS sever(s).

DHCP

Windows Server 2012 is the server version of Windows 8 and the successor to Windows Server 2008 R2. Windows Server 2012 is the first version of Windows Server to have no support for Itanium-based computers since Windows NT 4.0. Windows Server 2012, now in its second release (Windows Server 2012 Release 2) includes Foundation, Essentials, Standard and Datacenter, and does not support IA-32 or IA-64 processors.

Windows Server 2012

The Windows operating systems have distinct methodologies for designing and implementing networks, and have specific systems to accomplish various networking processes, such as Exchange for email, Sharepoint for shared files and programs, and IIS for delivery of web pages. Microsoft also produces server technologies for networked database use, security and virtualization.

Windows Networking

A desktop computer is a personal computer designed for use at a single location due to its size and power requirements, usually by one person. The most common configuration has a case that houses the power supply, motherboard, disk storage (usually one or more hard disk drives and optical disc drives); a keyboard and mouse for input; and computer monitor and printer for output. The case may be oriented horizontally and placed atop a desk or vertically and placed underneath or beside a desk.