I've had slow OSD deployments since I've used SCCM and have kind of dealt with them as just one of those things.  Now we're really ramping up the deployments and need to track this issue down.

What concerns me is that the clients are getting the WIM file from the correct DP.  I have a DP on the Site server but also have one on a local machine were we do all of our OSDs.  What is the best way make sure the clients get the WIM from the local DP?

Hi,

Make sure the clients are within the correct boundary groups and the correct site system is assigned to it. That is how it determines which DP it should use.

Regards,
Jrgen

Which wim? The WinPE one or the OS.wim (e.g. Win 8.1). The first one is controlled by the PXE-enabled DP being used (using IPhelpers or DHCP options), the second one by using boundary/groups.

Hi,

I just assumed it was the Windows OS .wim file... if PXE boot is slow and it is using the correct DP you can try modifying the TFTP Block Size.

http://windowsitpro.com/configuration-manager/speed-sccm-tftp-performance-pxe-clients

Note that I have hade issues with some models with that setting like the HP Probook 4500, it doesn't work with a high number in the TFTP block size value.

Regards,
Jrgen

All,

I am looking at the boundaries and boundary groups now.  I believe that is my issue.  I will report back shortly.

All,

I believe this is the issue however I'm still seeing the install.wim being downloaded from the Site Server not the local DP.  I have a boundary that includes the subnet of the local DP.  I've created a new Boundary Group that only includes this boundary and have associated only the local DP to that boundary group.

I'm sure I'm still missing something so any further help is appreciated.

It turns out I have a permissions issue on the DP that is local.  I'm working on that now.  Thank you Jrgen I'm sure your are correct that the boundaries was also another issue.