This blog explains how to install and troubleshoot a new Configuration Manager PXE service point. And how to make all needed packages available for the task sequence on the new distributing point.
In short this is what I do. (I already have a server configured with ConfigMgr and a ConfigMgr distribution point at the new site)
- Install the Windows Deployment Service role on the Server.
- Setup a ConfigMgr PXE service point on the Server.
- Deploy both (x86/x64) boot images to the new PXE service point
- Deploy all referenced packages in a task sequence to the distribution point.
There is a lot of good blog post on this already.
J.C. Hornbeck has a blog post on How To Properly Install And Set Up A New Instance Of WDS And A PXE Service Point in his blog post Troubleshooting the PXE Service Point and WDS in Configuration Manager 2007
You can then use the PowerShell script from Michael Niehaus to add distribution point to all referenced packages in a task sequence. I personally use the updated script from jscheffelmaer that can be downloaded from his blog post Checking Task Sequence Package References for a DP.
Place SCCM.psm1 in the module folder
on the computer you are running the CheckTSPrompt1.3.ps1 script from. You would need to start the powershell with elevated rights to alter the execution policy to allow running of unsigned script.
copy .SCCM.psm1 $pshome\Modules\SCCM\SCCM.psm1
Se screenshots of the powershell script at jscheffelmaer blog post.
EDIT: 2012-03-20: If there already is a distribution point with all the needed packages, you could with an easy wizard copy all packages distributed to that distribution point to another. Follow the instruction on TechNet for the use of the Configuration Manager Console built-in Copy Package Wizard on How to Copy Multiple Packages to One Distribution Point