PENDING PXE Client Downloading from Wrong Distribution Point

[jasonmoran]

Hello

I am struggling with a problem where I just cannot find a solution to. I have built a SCCM Distribution Server with the intention of imaging Workstations at a Remote Site and distributed our existing Task Sequences and associated applications as well to the new SCCM Distribution Server. I have also created Boundaries and Boundary Groups and ensured the new Boundaries and Boundary Groups were assigned to the new Distribution Point server and only the new one. I also reviewed the Boundaries to find any overlap and was not able to. Upon PXE Booting, the Clients are Downloading the Boot Image from the new Distribution Point server but then start downloading the content identified in the Task Sequence from the original Distribution Point server/s. The Task Sequence is distributed across all of the Distribution Point servers and I have verified that the content was distributed successfully. The PXE Clients successfully image from my SCCM environment but refuse to pull from the desired DP. I have reviewed the SMSTS.LOG file but as the workstation successfully images, it is hard to find the culprit. My SCCM is at 1902 5.00.8790.1000

Thank you all in advance.

 

[Garth]

What type of Boundaries are you using? IP Ranges (the best), AD sites (OK), IP subnets (Run for the hills).

 

[jasonmoran]

Hello Garth ... Thank you for your response. I'd like to say the environment I have inherited is only using one of them but it is using all three. Having said that the Boundary Group that the new DP is using was using IP Range and IP Subnet. I have removed IP Subnet, from the Boundary Group and removed the IP Subnet from the list of Boundaries as well. I will kick off another image in hopes this helps.

 

[jasonmoran]

Ok ... removing the IP Subnet from the Boundary Group and the list for Boundaries hasn't changed anything. My test client is still pulling from the wrong DP

 

[jasonmoran]

I have discovered my issue, I had a overlapping Boundy, due to a AD Site Boundary. Thanks Garth for the clue. I don't think I will forget to stick to just one type of boundary.