+ Post New Thread
Page 1 of 2 12 LastLast
Results 1 to 15 of 22
O/S Deployment Thread, Clients can't connect to MDT Deployment Share in Technical; Morning guys, I seem to have a major issue with our deployment server. Last Friday I imported new drivers to ...
  1. #1
    Harry_Greatorex's Avatar
    Join Date
    Jul 2013
    Location
    Burgess Hill
    Posts
    61
    Thank Post
    5
    Thanked 1 Time in 1 Post
    Rep Power
    0

    Angry Clients can't connect to MDT Deployment Share

    Morning guys,

    I seem to have a major issue with our deployment server. Last Friday I imported new drivers to the driver pool for some new PC's we bought. Since then, ANY PC which we deploy to, won't find the LAN driver, we have to manually add it off USB for it to continue the deployment. This happens for old computers which we haven't touched the drivers for. The new computers don't get the LAN drivers either. So today I updated the boot images, and now when I boot into MDT and type in the deployment share UNC path, and my domain credentials, it comes up with a message saying "Invalid Credentials: Network location cannot be reached". I have tried my own personal credentials, which have domain admin rights, and the actual domain administrator account, same error every time. Anybody got any ideas? At the moment, we can't image any of our new PC's, or even any of our old ones. I have even set up a new deployment share and tried connecting to that, with the same results.

    Regards
    Harry

  2. #2

    Join Date
    Jun 2012
    Location
    UK
    Posts
    34
    Thank Post
    0
    Thanked 6 Times in 5 Posts
    Rep Power
    6
    Sounds like your lan driver isn't in your boot image, at the mdt login box press shift+f10 (i think) this will open a command prompted, run ipconfig /all to see if you have a network connection/ip

  3. #3
    Harry_Greatorex's Avatar
    Join Date
    Jul 2013
    Location
    Burgess Hill
    Posts
    61
    Thank Post
    5
    Thanked 1 Time in 1 Post
    Rep Power
    0
    Interesting. As i mentioned, none of our drivers, new or old have been removed, only added. Ive put our driver discs in and tried reimporting, but no drivers get imported as they already exist. I tried what you suggested and it doesn't give me an IP address, im guessing that means it has no drivers? Even though the drivers are on the server boot images regenerated?

  4. #4
    themightymrp's Avatar
    Join Date
    Dec 2009
    Location
    Leeds, West Yorkshire
    Posts
    1,259
    Thank Post
    218
    Thanked 232 Times in 200 Posts
    Rep Power
    74
    Do you separate your drivers out into sub-folders in MDT based upon machine model? If so you could delete the new ones from the database and regenerate the images? Or failing that, sort by date added and delete them.

  5. #5
    Harry_Greatorex's Avatar
    Join Date
    Jul 2013
    Location
    Burgess Hill
    Posts
    61
    Thank Post
    5
    Thanked 1 Time in 1 Post
    Rep Power
    0
    No i don't have them sorted by model. I started the job after MDT was installed and configured and everything was just dumped in the root. I have just re-added all the drivers off the discs and i still have the same issue.

  6. #6
    themightymrp's Avatar
    Join Date
    Dec 2009
    Location
    Leeds, West Yorkshire
    Posts
    1,259
    Thank Post
    218
    Thanked 232 Times in 200 Posts
    Rep Power
    74
    Have you tried the option to completely re-generate the boot image instead of doing the optimized version? I've had issues before where completely regenerating them (which can take a while) fixes various issues. Are you also replacing the boot images in WDS to take advantage of your newly integrated drivers?

  7. #7
    Harry_Greatorex's Avatar
    Join Date
    Jul 2013
    Location
    Burgess Hill
    Posts
    61
    Thank Post
    5
    Thanked 1 Time in 1 Post
    Rep Power
    0
    Yes to both. It still seems to be a driver issue, i just don't see how. Nothing else on the server or network in general has changed. Very frustrating as we have new computers people are waiting for that we can't build!

  8. #8
    themightymrp's Avatar
    Join Date
    Dec 2009
    Location
    Leeds, West Yorkshire
    Posts
    1,259
    Thank Post
    218
    Thanked 232 Times in 200 Posts
    Rep Power
    74
    Just as a check, right click on the MDT deployment share (from within the deployment toolkit) and go to properties. Under the Windows PE x86/x64 components tabs, has it got the tick box to enable all network drivers to be included in the selection profile? Because if that is unticked you will be making a boot image without drivers!!

    deploy components.jpg
    Last edited by themightymrp; 16th June 2014 at 12:47 PM.

  9. #9
    Harry_Greatorex's Avatar
    Join Date
    Jul 2013
    Location
    Burgess Hill
    Posts
    61
    Thank Post
    5
    Thanked 1 Time in 1 Post
    Rep Power
    0
    This is what i have...looks ok to me!

    wds.PNG

  10. #10
    themightymrp's Avatar
    Join Date
    Dec 2009
    Location
    Leeds, West Yorkshire
    Posts
    1,259
    Thank Post
    218
    Thanked 232 Times in 200 Posts
    Rep Power
    74
    Yep that looks good. It looks like you are running a newer version of MDT than me (still on 2010). Is there a way to sort the driver database by date added? And then delete the ones you imported on Friday?

  11. #11
    Harry_Greatorex's Avatar
    Join Date
    Jul 2013
    Location
    Burgess Hill
    Posts
    61
    Thank Post
    5
    Thanked 1 Time in 1 Post
    Rep Power
    0
    We are on MDT 2012 here. There is, but also drivers that i have re-added since then as well.

  12. #12

    Join Date
    Jun 2006
    Posts
    5
    Thank Post
    0
    Thanked 0 Times in 0 Posts
    Rep Power
    0
    We have seen this where there is a conflict between drivers. Try making a selection profile that only uses one set of network drivers to try to pinpoint the erroneous driver.

  13. #13
    Harry_Greatorex's Avatar
    Join Date
    Jul 2013
    Location
    Burgess Hill
    Posts
    61
    Thank Post
    5
    Thanked 1 Time in 1 Post
    Rep Power
    0
    How would i go about doing that? Sorry i'm very new to WDS/MDT.

  14. #14
    Harry_Greatorex's Avatar
    Join Date
    Jul 2013
    Location
    Burgess Hill
    Posts
    61
    Thank Post
    5
    Thanked 1 Time in 1 Post
    Rep Power
    0
    Right i have removed all the new drivers i added the other week, so im left with what we had before, i have regenerated boot images and re-added them into WDS, but the problem still persists.

  15. #15
    themightymrp's Avatar
    Join Date
    Dec 2009
    Location
    Leeds, West Yorkshire
    Posts
    1,259
    Thank Post
    218
    Thanked 232 Times in 200 Posts
    Rep Power
    74
    So it lets you boot into WinPE but then doesn't have network connection? Correct?



SHARE:
+ Post New Thread
Page 1 of 2 12 LastLast

Similar Threads

  1. Replies: 2
    Last Post: 26th March 2014, 12:27 PM
  2. Can't Connect to the domain
    By spider6986 in forum Windows
    Replies: 6
    Last Post: 19th October 2009, 04:10 PM
  3. [MS Office - 2003] Outlook - User can not connect to exchange server
    By Tony_Mc in forum Office Software
    Replies: 2
    Last Post: 26th January 2009, 03:38 PM
  4. Replies: 1
    Last Post: 23rd January 2008, 10:47 AM
  5. Replies: 3
    Last Post: 30th April 2007, 11:32 PM

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •