Hey Johan, thanks for the reply. I checked the BDD.log to get the value that I mentioned in the post. Per the log: Property DEPLOYROOT is now = E:\Deploy. It does not say the server name :/ This is a Lite Touch deployment using the DPs within MDT(Shown Below)...
On Mon, Jun 17, 2013 at 10:06 AM, Johan Arwidmark < [email protected]> wrote: > Well, for a normal Lite Touch deployments (not ConfigMgr), you will see > in the BDD.LOG which server the client connects to (check the deployroot > value). And MDT Lite Touch does not use DPs, it’s called Deployment Shares. > **** > > ** ** > > For ConfigMgr OSD you can see in the smsts.log which DP packages are > requested from. You can also add a pause to the task sequence and enumerate > the current settings, which also tells you what DP’s that is being used.** > ** > > ** ** > > Is this a MDT Lite Touch deployment you are troubleshooting, or a > ConfigMgr OSD you are troubleshooting?**** > > ** ** > > / Johan**** > > ** ** > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Chris Howie > *Sent:* den 17 juni 2013 16:25 > *To:* [email protected] > *Subject:* Re: [MDT-OSD] MDT OSD DP Content Issue**** > > ** ** > > Hey Johan, I have tried doing that for all of the DPs in MDT. However, I > literally cannot tell where the computer is requesting content from during > OSD. All of the DPs that are in the deployment workbench have the correct > content. :/**** > > -Chris**** > > ** ** > > On Mon, Jun 17, 2013 at 9:15 AM, Johan Arwidmark < > [email protected]> wrote:**** > > Just compare the files in the non-working deployment share, with a working > deployment share.**** > > **** > > / Johan**** > > **** > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Chris Howie > *Sent:* den 17 juni 2013 16:04 > *To:* [email protected] > *Subject:* [MDT-OSD] MDT OSD DP Content Issue**** > > **** > > The Environment: > > Hello everyone, I have been beating my head on my desk over this issue the > past couple of days. I am running a MDT 2008 environment with 8 DPs > side-by-side a ConfigMgr 2007 environment running approximately 60 DPs. MDT > is being used for XP deployments and ConfigMgr is being used for Windows 7. > **** > > The Issue: **** > > I recently added some new drivers for a particular model to the out-of-box > driver repository in MDT. I updated all of the files on all of the MDT > distribution points and everything works great for all locations except > one. Essentially, the logs tell me that there are no drivers present for > that model because it skips all of the drivers. I cannot find in any of the > logs where this machine is pulling its content from so that I can manually > go update that location. All it says is E:\Deploy is where the content is > coming from, but that is it. None of the DPs defined in MDT have this > folder except for one and the content is up to date. > > The Question: > > Does anyone have an idea on how I can figure out where the content is > coming from so that I can update it?**** > > Thanks for the ideas!!!**** > > ** ** >
