I've read several guides on using DFS-R with WDS and MDT to replicate REMINST and DeploymentShare, and I have a particularly strange problem.
On the receiving server, after configuring WDS and mounting the DeploymentShare into MDT's DeploymentWorkbench, I also performed the following:
1) in .\Control\Bootstrap.ini, changed DeployRoot to \%wdsserver%\DeploymentShare$
2) Changed the UNC path at the root of the MDT Deployment Share in the DeploymentWorkbench to match that of the current server.
3) In Unattend.xml files located: .\Control**, modified the following value to match the current server: <cpi:offlineImage catelog://HOST/
I am able to boot and grab the LiteTouch PE image off the local WDS TFTP server, but the WIM files, the scripts, everything else is being pulled off the WDS server at the remote site (the original WDS server that was the source of the files within the DFS-R replicated folder).
What do I do in order to solve this problem? I've grepped all the files below the DeploymentShare to look for instances of the hostname of the WDS server at the remote site (the source of the files), but I found none.
Here are the guides I referred to:
Best Answer
bootstrap.ini is the control file that's injected into the boot wim. It is what controls which share the WinPE stage connects to. Did you remember to regenerate the boot file after changing bootstrap.ini?
Sidenote: You could do this a bit smarter, by using subnet filtering to dynamically set the correct values. That way you wouldn't need to maintain separate boot images per location. (Never tested this in WinPE though, so not sure it works)