In my organization, we manage two separate domains (Domain A and Domain B). We were previously using Windows Deployment Services (WDS) with custom boot images, but we faced issues where the images would only load up to 10% before becoming unreadable on the client side. Has anyone experienced this problem? We're currently in the process of rebuilding our WDS server, but I want to determine if that's the right course of action since PXE booting is quite convenient for our helpdesk staff when they need to image machines. For now, we've reverted to using a SCCM Distribution Point from Domain A, which is working fine, but we're trying to set up a Task Sequence that stages our boot image from Domain B and reboots into that. Unfortunately, our attempts haven't been successful. I'd like to return to our WDS solution as it allowed us to choose which SCCM domain to boot into. What's the best approach here?
3 Answers
Are you using the SCCM PXE boot option instead of WDS? I find that without WDS, we face fewer issues during the booting process. Just keep in mind that since Microsoft is phasing out WDS, you should consider long-term solutions for your deployment needs.
If you're running multiple domains, there's really no need for duplicate infrastructure. SCCM can handle management across different domains and forests without the hassle of rebuilding WDS. You should explore utilizing SCCM's capabilities better instead of maintaining WDS, which is becoming obsolete.
You could definitely create a Task Sequence in the SCCM of Domain A that lets your staff decide which domain to join while imaging. There are better ways to manage this without setting up another SCCM in Domain B. I even consulted an AI about this, and it suggested a few methods that could streamline your process!
We've just rebuilt our WDS server and it's working again, but with Microsoft dropping support for WDS, I’m worried how long it will last.