Right, but if the child site doesn't have the PXE role it won't won't have SMSPXEIMAGES$. Thanks for the links, but I already have PXE and OSD working at the parent site.

So do you know what's the purpose of SMSPXEIMAGES$, why have both, why doesn't it just use the standard DP for everything?

The SMSPXEIMAGES$ share is located in the file structure for WDS, under the folder Remoteinstall. They are placed there so that the WDS can use the file during PXE boot. /Jörgen-- visit my System center blog at http://ccmexec.com --

Hi, The boot images used during the actuall PXE boot itself is downloaded from the parent site if you don't have a PSP on the child site. After WinPE is loaded it will use the closest DP to pull all the packages. The boot images would have to be on alla DP's depending on the scenario used to deploy the clients. Reards, Jörgen-- visit my System center blog at http://ccmexec.com --

I'm confused about how I should setup OSD for a parent and child primary. If the parent site has the PXE role/WDS/ip-helper addresses working, then the child site doesn't need those roles also, it can just store images and driver packages, is that right? If so, only the Distribution Points in the parent site need the boot images? In other words, when the PXE process starts from the parent, are the boot images always used from the parent site DPs, or will a PXE client in the child site boundaries need to find the boot image in the child site DPs SMSPXEIMAGES$? (which won't exist if it doesn't have WDS/PXE role) Thanks!

OK, that make sense I guess, since WDS needs a static path to the WIMs and the standard shares may change (SMSPKGD$, SMSPKGE$). I went with the plan I mentioned above, so far it's working but I'm still testing: Boot images: - Need to be in \\PARENT\SMSPXEIMAGES$, but not on the child (if the child does not have PXE role) - Also need to be in \\PARENT and \\CHILD (standard DPs) Operating System Images: - Only need to be in \\PARENT and \\CHILD (standard DPs) Operating System Install Packages: - Only need to be in \\PARENT and \\CHILD (standard DPs) Driver Packages: - Only need to be in \\PARENT and \\CHILD (standard DPs)

Thanks for the reply. So does this look correct: Boot images: - Need to be in \\PARENT\SMSPXEIMAGES$, but not on the child (if the child does not have PXE role) - Also need to be in \\PARENT and \\CHILD (standard DPs) Operating System Images: - Only need to be in \\PARENT and \\CHILD (standard DPs) Operating System Install Packages: - Only need to be in \\PARENT and \\CHILD (standard DPs) Driver Packages: - Only need to be in \\PARENT and \\CHILD (standard DPs) I'm curious why the boot images need to be in the standard and PXE DPs?

Hi, If you for instance reinstall a client from within windows not using PXE the boot image will be downloaded from the local DP to the client. Regards, Jörgen-- visit my System center blog at http://ccmexec.com --

Hello - When PXE point is enabled then the folder is created called SMSPXEIMAGES$, and boot image is stored in that folder. MOre details, see http://technet.microsoft.com/en-us/library/bb932177.aspx For more details refer http://www.windows-noob.com/forums/index.php?/topic/569-how-can-i-deploy-windows-xp-sp3-using-sccm-2007-sp1-part-1/Anoop C Nair