jtcheah

Johan Arwidmark affirms my approach to configuring WDS from within Server Manager as opposed to leaving it unconfigured as so many would advocate; more specifically designating where to install the remoteinstall folder and whether accept known and unknown computers. I had issues with SCCM 2012 OSD/WDS/PXE as described above as I was a little trigger happy instead of troubleshooting Boot Image distribution. What I ended up doing to get it to work was: Ensuring the SCCM Admin account I'm logging in with has domain admin rights (This is important for WDS reinstall) Backup or rename folder x:\remoteinstall or whichever drive it is located. Uninstall WDS service Remove Distribution Point role from the respective PXE server Reboot Reinstall WDS Configure WDS in Server Manager (include destination of remoteinstall folder, accept PXE requests from known and/or unknown computers, and uncheck add image) Add Distribution Role back to the site server and configure for PXE Redistribute all required software back to this DP. Make sure you WinPE boot disks (both x86, and x64 configured for PXE within their properties tab under sources) Distribute both Boot disk to the distribution/pxe point. Make sure the remoteinstall folder has smsboot (option 67 of DHCP will point to smsboot\x86\wdsnbp.com so make sure that file is there) and other sms related folders that are automatically re-created If you do receive abortpxe.com after it's another series of troubleshooting steps but not as severe as this one. Jeff