In my setup, we have a Primary Site and we have about 250 DP's out in the field at our off-site locations.  We do system imaging at these locations, however I appear to be running into a problem.  To abbreviate, I'll use PSS1 as our Primary Site Server and DP1 as an example DP.  The IP of PSS1 is 10.100.10.1 and the IP of DP1 is 10.14.72.100.

I have what appears to be the proper boundaries in place for the IP range of the location where DP1 is and it is assigned in boundary groups to have the Site System Server for that group point to DP1. 

However, whenever they do an F12 to PXE boot, it's showing it downloading from PSS1 with the IP of 10.100.10.1 instead of 10.14.72.100

I'm new to the management of our SCCM infrastructure, but for the life of me, I cannot figure out why this is happening.  I checked the SMSPXE log on DP1 and it shows the mac address of the system being imaged and that it found the optional advertisement.

Any help would greatly be appreciated!  Thanks in advance!

Either one of two things are happening (OK both could be true):

Your boundary groups are, in fact, wrong.  In this case, double check the IP address your client is getting and make sure it is only a member of the intended boundary group.  A boundary can be a member of more than one group, and the client will treat all such DPs in all groups as equal.

Your packages don't exist at the DP and fallback is causing it to use the Primary site instead.  make sure you have all packages associated with your TS (including boot images) copied to the desired DP.  If the data is missing at the "local" DP (configured via boundary groups) then it will check for any DPs that have Fallback enabled.... and it's a pretty common practice for that to be the DP at your primary data-center.

I'm almost 100% it's going to be one of those two things from how you'r describing it.

If your boundaries are set right then make sure that your distrbution points are also set for enable PXE support for clients.

John Killgore

The boundary appears to be proper, no other overlapping IP ranges.  Under the Site Systems tab, it shows DP1.corp.domain.com  (using fake names here).  The boundary groups tab has 2 items in there, one being Site Assignment and one with the site name and then Content Location.  Site name being the physical name we call this location, we'll call it Warehouse 1.

If I go to the Boundary Groups link it shows all of our Warehouse location IP ranges and under the References tab, it shows "Use this boundary group for site assignment" and it shows our main Site Name "ABC - Primary Site", and Site System Servers is blank below.

When I open the Warehouse 1 - Content Location group, I see the IP range below that I specified for this warehouse and under references, the Site Assignment is unchecked, and below where it says Site System Servers, it says DP1.corp.domain.com        Site:  ABC    Connection:  Fast.

If I review the SMSPXE logs on DP1 and PSS1, I can see the mac address of the system trying to boot and it says Found Optional Advertisement, but PSS1 actually shows the Client IP address the system got, which is within the boundary I set up, along with found optional advertisement, followed by Looking for Bootimage ABC000FE, and it kicks off without a hitch.

I verified that the boot images and all content is listed and present on DP1.

Is there an alternate log file I should be checking?  I just don't get why its showing the system in DP1 and PSS1's logs together.

Also, PXE support is enabled for DP1...if I disable it, it still boots to PSS1 and once I enable it, it still boots to PSS1, but shows entries under DP1 and PSS1 log files.

Are the boot images distributed to "DP1"?

Also, are you saying that clients in Warehouse1 are actually using your primary site server PXE point to boot? Check to make sure IP helpers are correct and point to DP1 at the Warehouse1 site.

Jeff

• Marked as answer by TJWatGE 13 hours 8 minutes ago

The boot image and all content is on DP1 as well, for some reason it's looking back at PSS1 for all of the content and booting. 

Our network team responded a few hours ago, I just haven't had time to jump back on here.  They mentioned that the helper address on the BVI interface at the warehouse was pointing back to the PSS, so once they corrected it to point to DP1 at that site, all is good now.

Thank you for the suggestion as it was the right one!