I am having issues getting clients to PXE boot on my Secondary Site to do bare metal OS installs. I have a primary site and a secondary site setup in a lab. The sites are separate AD sites (and subnets) separated via a RRAS server and are working fine from a communication standpoint in SCCM. Primary site works fine doing PXE boot bare metal installs to Hyper-V guests. Secondary Site is also configured with Hyper-V with the intent to test the same installation scenario. Secondary Site is configured with PXE service point and WDS are installed as well as there being a DC running DHCP and DNS. The task sequence to deploy the OS is advertised to a collection containing the Secondary Site client (which was imported into the SCCM DB and is using a legacy NIC) however when the client boots into PXE it never receives an IP address. The smspxe.log is below and indicates the requests are being ignored. Any suggestions on other logs to look at to help troubleshoot this? MAC=00:1D:D8:B7:1C:01 SMBIOS GUID=27BBB8C0-87B7-45A0-A404-FC38FDC2AD44 > Device found in the database. MacCount=1 GuidCount=0 smspxe 10/28/2010 3:08:15 PM 5280 (0x14A0) [192.168.040.025:67] Recv From:[000.000.000.000:68] Len:548 134f730 smspxe 10/28/2010 3:08:19 PM 6048 (0x17A0) Ignoring req from [000.000.000.000:68] Dest Server:[192.168.040.002] smspxe 10/28/2010 3:08:19 PM 6048 (0x17A0) [192.168.040.025:4011] Recv From:[192.168.040.025:68] Len:548 15a9db0 smspxe 10/28/2010 3:08:19 PM 6048 (0x17A0) [192.168.040.025:67] Recv From:[000.000.000.000:68] Len:548 e1dbb0 smspxe 10/28/2010 3:08:27 PM 5888 (0x1700) [192.168.040.025:67] Recv From:[000.000.000.000:68] Len:548 121edb0 smspxe 10/28/2010 3:08:35 PM 5888 (0x1700) Ignoring req from [000.000.000.000:68] Dest Server:[192.168.040.002] smspxe 10/28/2010 3:08:35 PM 5888 (0x1700) [192.168.040.025:4011] Recv From:[192.168.040.025:68] Len:548 1356d70 smspxe 10/28/2010 3:08:35 PM 5888 (0x1700) [192.168.040.025:67] Recv From:[000.000.000.000:68] Len:548 100e630 smspxe 10/28/2010 3:08:51 PM 6048 (0x17A0) [192.168.040.025:67] Recv From:[000.000.000.000:68] Len:548 f4c930 smspxe 10/28/2010 3:09:07 PM 6048 (0x17A0) Ignoring req from [000.000.000.000:68] Dest Server:[192.168.040.002] smspxe 10/28/2010 3:09:07 PM 6048 (0x17A0) [192.168.040.025:4011] Recv From:[192.168.040.025:68] Len:548 1118bb0 smspxe 10/28/2010 3:09:07 PM 6048 (0x17A0) [192.168.040.025:4011] Recv From:[192.168.040.025:9000] Len:274 121fc70 smspxe 10/28/2010 3:09:08 PM 5888 (0x1700) [192.168.040.025:67] Recv From:[000.000.000.000:68] Len:548 15a98f0 smspxe 10/28/2010 3:09:38 PM 5888 (0x1700) [192.168.040.025:67] Recv From:[000.000.000.000:68] Len:548 ec7db0 smspxe 10/28/2010 3:10:09 PM 5888 (0x1700) Ignoring req from [000.000.000.000:68] Dest Server:[192.168.040.002] smspxe 10/28/2010 3:10:09 PM 5888 (0x1700) [192.168.040.025:4011] Recv From:[192.168.040.025:68] Len:548 ebd3b0 smspxe 10/28/2010 3:10:09 PM 5888 (0x1700) [192.168.040.025:67] Recv From:[000.000.000.000:68] Len:548 1118230 smspxe 10/28/2010 3:11:11 PM 5888 (0x1700) [192.168.040.025:67] Recv From:[000.000.000.000:68] Len:548 f4d7f0 smspxe 10/28/2010 3:12:14 PM 5888 (0x1700) Ignoring req from [000.000.000.000:68] Dest Server:[192.168.040.002] smspxe 10/28/2010 3:12:14 PM 5888 (0x1700) [192.168.040.025:4011] Recv From:[192.168.040.025:68] Len:548 159f3b0 smspxe 10/28/2010 3:12:14 PM 5888 (0x1700) [192.168.040.025:4011] Recv From:[192.168.040.025:9000] Len:274 e1e9b0 smspxe 10/28/2010 3:14:08 PM 5888 (0x1700) [192.168.040.025:4011] Recv From:[192.168.040.025:9000] Len:274 f4f8b0 smspxe 10/28/2010 3:19:09 PM 5888 (0x1700) [192.168.040.025:4011] Recv From:[192.168.040.025:9000] Len:274 e201b0 smspxe 10/28/2010 3:24:09 PM 5888 (0x1700)

Have you checked for duplicate/obsolete records for this computer account in the ConfigMgr database? Does the MAC address that smspxe.log reports match the MAC address of the ConfigMgr computer account you created? It would be worth using the SQL profiler to watch ConfigMgr's activity during the PXE boot sequence and use the NBS_GetPXEAction data to verify that the resource ID it reports matches the resource ID of the computer account in ConfigMgr Good luck!

Well I setup a physical machine and the OSD ran fine via PXE on the secondary site. Deleted the record out of SCCM and dropped the Hyper-V NIC and added it anew with a different MAC address. Think I used SCVMM to assign the MAC the first go round and may have uninstalled that and reinstalled it in the past so it might have started handing out duplicate MACs with my testing. Hyper-V machine OSD via PXE working like a charm as well.