use the FQDN not the NetBIOS name of the share On Fri, May 2, 2014 at 1:01 PM, Patrick Jamieson <[email protected]> wrote: > Hi All, > > > > I’m having issues qualifying two new machines in our environment. I’m > trying to build Windows 7 on the Lenovo x240 and t440. After the first > reboot, both machines will log in to the local admin account, but both > return the following error (also attached): > > > > “A connection to the deployment share (…) could not be made. Can not reach > DeployRoot. Possible cause: Network routing error or Network Configuration > error.” > > > > From there, the dialog box gives me the option to retry or cancel, but > retrying doesn’t help. Checking the logs, the only relevant error info I > can find simply says that the network path was not found, and it retries a > few seconds later. This error shows up in both bdd.log and litetouch.log. > I can usually get the build to progress if I restart the machine without > actually canceling the error. It doesn’t appear to be a driver issue, since > the driver is installed and I can browse the web without a problem. > > > > From researching, it sounds like the most likely cause is that the machines > log in too quickly and the network cards are not yet active. This makes > sense to me, since these are the first machines we’re trying to build with > SSD’s as the primary drive. Every suggestion I tried though leads to no > results. Things I’ve already tried: > > > > 1.) Editing ZTIUtility.vbs to wait a few seconds before testing for > network activity. This seems to be the most popular suggestion online, but > doesn’t give me any results. I’ve tried having it wait for 5 seconds and 2 > minutes, neither helps. > > http://social.technet.microsoft.com/Forums/en-US/9c8c8f48-7e4f-4981-9890-86a37c0bf3a2/unable-to-connect-to-deployment-share-after-restart-mdt2012?forum=mdt > > > > 2.) Changing local group policy after the OS is laid down to wait for > network connectivity before logging in. The setting itself I changed was > ‘Computer Configuration > Administrative Templates > System > Logon > Always > wait for the network at computer startup and logon’. This actually makes > rebooting the machine after I see the error much more reliable, but the > dialog box still pops up after the first login. I changed this by having > MDT run a script that overwrites the contents of > C:\Windows\System32\GroupPolicy. It works (I can see that the setting goes > from “Not Configured” to “Enabled”) but it doesn’t actually solve the > problem. > > http://social.technet.microsoft.com/Forums/en-US/cf35f66a-998f-4dbb-bb26-f7479de0505b/message-containing-password-has-been-suppressed?forum=mdt > > > > If anyone has any suggestions it would be very much appreciated. > > > > Thanks for your help, > > > > Patrick
