We have three sites:
Primary Site: 600+
RemoteSite1: 150
RemoteSite2: 150

As of right now our primary site updates and distributes packages and applications to all three sites.
We only do OSD's in our Primary Site but want to get all sites to do the OSD's.

I am wanting to setup a Distribution Point in the remote sites.
Enable PXE, and assign those DP's to there respective Boundary Groups (built by sites in AD).

My questions I guess are these:
Does this sound like best practices?
Should I have PXE and WDS in all sites?
Is Pull-DP's better to have?

There's no such thing as best practice. There's doing want needs to be done per your requirements and limitations according to the supported capabilities of the product.

What is prompting you to do this?

Architecturally it is fine, but if you have the bandwidth to support what you have, there's no specific reason you need to do this. PXE over the WAN is generally not recommended though as it can take a long time. Thus if your driving factor here is PXE availability at the remote locations, then yes, this is a perfectly acceptable course of action.

No, you shouldn't use a PullDP unless you have a specific reason to do so like the number of DPs in your environment would exceed the supported maximum or you don't have a pure hub and spoke network topology.

I like what Jason said, "There's doing want needs to be done per your requirements and limitations according to the supported capabilities of the product."  For the scenario, you describe, I would have a PXE-enabled distribution point at each remote site.

Jeff

Thank you for the replies.

What is prompting us to do this finally is that we have been pushing application and programs to the other sites for a few years now (with some lag) but the techs at those sites have been creating their own OSD's with MDT or just building from scratch.  We want to get up and running with just using ConfigMgr for it all as well as take the lag out of the updates and application pushes.

Thank you again for the replies.