Joanne Posted June 14, 2016 Posted June 14, 2016 So I'm imaging my laptops 1 at a time because only 1 of my USB-LAN adaptors works with my MDT bootable USB stick. When I use the one that doesn't work it just says cannot connect to deployment share. I've put the drivers in the Out-Of-Box drivers in the Deployment Workbench, but I guess it needs the drivers on the stick, because that's all it is using at the time. Where do I put them? When I plug the stick into my machine I have : boot en-us fonts resources sources bootmgr (file) I've tried copying the driver files into the resources folder, but this didn't work. Thanks in advance. PS/ I'm an MDT n00b - so you need to explain things slowly!!
sted Posted June 14, 2016 Posted June 14, 2016 it should just be a case of update your deployment share and replace the boot.wim on the pen drive 1
Joanne Posted June 14, 2016 Author Posted June 14, 2016 OK - where do I get the new boot.wim from? The LiteTouchPE.wim file in the deployment share is the same size as the boot.wim on the pen drive and it hasn't been modified...
sted Posted June 14, 2016 Posted June 14, 2016 OK - where do I get the new boot.wim from? The LiteTouchPE.wim file in the deployment share is the same size as the boot.wim on the pen drive and it hasn't been modified... i think litetouchpe.wim=boot.wim if not set it to generate an iso and pinch it from that as to unmodified pass everytime you run the update deployment share option from mdt it should (if there is anything to update) it should alter the litetouchpe.wim file to reflect changes
Joanne Posted June 14, 2016 Author Posted June 14, 2016 I've clicked on 'update deployment share' and it's updating those wim files now.
Joanne Posted June 14, 2016 Author Posted June 14, 2016 So I clicked Update Deployment Share - Then chose to completely regenerate boot images - This updated the LiteTouchPE.wim files. I deleted the boot.wim on the USB drive then copied the LiteTouchPE.wim and renamed to boot.wim. It's not worked! Could it be that the drivers aren't right or something? I downloaded from the manufacturererer website!
sted Posted June 14, 2016 Posted June 14, 2016 So I clicked Update Deployment Share - [ATTACH=CONFIG]37304[/ATTACH] Then chose to completely regenerate boot images - [ATTACH=CONFIG]37305[/ATTACH] This updated the LiteTouchPE.wim files. I deleted the boot.wim on the USB drive then copied the LiteTouchPE.wim and renamed to boot.wim. It's not worked! Could it be that the drivers aren't right or something? I downloaded from the manufacturererer website! it wouldnt be the first time try plugging it into a non networked pc and seeing if those drivers install in windows (that way it dosent magically get them from windows update) it could also be they are unsigned drivers which i dont think by default can be added to mdt
Joanne Posted June 14, 2016 Author Posted June 14, 2016 WAIT!! I've swapped USB ports around and the adaptor is lighting up now!
sted Posted June 14, 2016 Posted June 14, 2016 WAIT!! I've swapped USB ports around and the adaptor is lighting up now! at a guess you were using a usb3 port and the drivers for that werent in the boot.wim (one reason i use windows 10 as a boot os)
Joanne Posted June 14, 2016 Author Posted June 14, 2016 I've tried importing the drivers that my machine said it was using when I plugged it in. Updated deployment share.... still doesn't find it. Such a shame. It would make the job twice as fast if I could get it working. I'm importing the drivers into the out of box drivers bit. That right? - - - Updated - - - at a guess you were using a usb3 port and the drivers for that werent in the boot.wim (one reason i use windows 10 as a boot os) The USB port that the LAN adaptor is in is USB 2 and the USB pen is in USB3.... ONE MORE TIMEZ!!
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now