SOLVED When PXE booting to install OSD, SCCM trying to get content from the wrong DP

[George]

One of our offices is having issues when trying to build new PC's.

This particular location has 2 DP's both on different VLAN's.

DP 1 is the PXE server and it hosts the Content and Boot images.
DP 2 has all the content and is mainly used by the corporate environment for software update deployments, software catalogue (Self serve, etc).

The issue I have is when we F12 Pxe boot it works just fine. Once we select the task sequence it can't find the relevant content.

After further investigation I can see that DP1 can pxe boot but for some reason it is trying to get the content from DP2.

From what I can see the boundary groups are also correct but SCCM has chosen to grab content from DP2 even though it is PXE booting from DP1.

Any help would be appreciated.

I am going insane trying to resolve this.

 

[Prajwal Desai]

"DP1 can pxe boot but for some reason it is trying to get the content from DP2" - Does the Task sequence contains references to the content which is stored on DP2 ?.

 

[George]

"DP1 can pxe boot but for some reason it is trying to get the content from DP2" - Does the Task sequence contains references to the content which is stored on DP2 ?.

I don't believe so but I will double check. Our other DP's around the country do not have the issue and they all use the same Task Sequence for OSD. Only one of our offices has this problem and it was only recently provisioned with a VLAN for PXE / OSD deployment.

Is there any other areas I should check Prajwal?

 

[Prajwal Desai]

Check the smsts.log file to see what packages is it pulling from the other DP. Unless the TS has references to packages that are on DP2, the TS should pull the content from DP1 only.

 

[George]

there was nothing obvious in any of the logs.

However after adding a boundary with an IP range the issue was resolved.

What I can't understand is why SCCM wasn't respecting the IP subnet boundary. We had to add a specific ip range.

We don't have this issue at any other site.

All of sites have a subnet boundary and they work fine. This one we effectively had to double up.

It's fixed.... I just wish i understood why. I don't like things being fixed and not knowing why

 

[Prajwal Desai]

Cool.. Marking this thread as Solved.