ellie666 Posted November 27, 2015 Posted November 27, 2015 hi I've just set up WDS on my SBS 2011 std and am trying to capture the images of some new bespoke pc's I've build, all using Gigabyte MOBO's. However when ever I try to capture the image I get a message about no matching network card drivers installed. I can't put the drivers directly into WDS as they're not signed apparently and when I try and install them using DISM it seems to make no difference. Does anyone have any suggestions please. thanks Elliott
Oaktech Posted November 27, 2015 Posted November 27, 2015 what drivers are you looking for? They do indeed have to be signed. Unless they are a really scabby net card signed drivers should be available.
ellie666 Posted November 27, 2015 Author Posted November 27, 2015 standard gigabyte network card drivers - for windows 7 x64 - I had downloaded the ini's but wds didn't seem to like them and suggested they were unsigned
ellie666 Posted November 27, 2015 Author Posted November 27, 2015 unless they were the wrong ones , but they were direct of gigabyte support site
Oaktech Posted November 27, 2015 Posted November 27, 2015 Can you give me the hardware ID from device manager and I'll see if my Google Fu is stronger than yours!
mowgli82 Posted November 27, 2015 Posted November 27, 2015 Hi, you can add unsigned drivers, its just a bit of a pain to do. Injecting x64 unsigned drivers to boot.wim Download correct driver PXE boot > Wait for Error about Network Driver > Shift F10 >mount drive with driver on (Diskpark) and Exit Check you have the correct driver - boot the PC and wait for error > Shift F10 >drvload "\enter path to driver"\nameofdriver.inf > initializeNetwork >IPConfig /all - check for IP On the server – take a copy of your boot.wim # Mount the boot.wim image. dism /Mount-wim /WimFile:\boot.wim /index:2 /MountDir: # Add a single driver Dism /Image: /Add-Driver /Driver:c:\drivers\mydriver.INF # Or recursive if you have a directory full of drivers Dism /Image: < pathtomountedwimfile> /Add-Driver /Driver:c:\drivers /Recurse # For unsigned drivers Dism /Image: < pathtomountedwimfile > /Add-Driver /Driver:c:\drivers\mydriver.INF /ForceUnsigned # Save the changes to boot.wim. Dism /Unmount-Wim /MountDir: /Commit 1
Joanne Posted November 27, 2015 Posted November 27, 2015 I've started using the Windows 10 boot.wim because it has more drivers in it automatically. That sorted my WDS woes!
mowgli82 Posted November 27, 2015 Posted November 27, 2015 I've started using the Windows 10 boot.wim because it has more drivers in it automatically. That sorted my WDS woes! or this
ellie666 Posted November 27, 2015 Author Posted November 27, 2015 that sorted it I was missing the line with "forceunsigned" - now I just need to work out how to capture the image as it's only giving me the option to deploy?!!!!!!!
mowgli82 Posted November 27, 2015 Posted November 27, 2015 in the WDS console right click your boot image with the correct driver and click create capture image......if when you have done this the capture images fails to allow the machine to boot. mount the image using dism, don't make any changes then unmount and commit, re-import the image and you should be good to go. oh an you will will need to sysprep the pc otherwise the drive won't show up in the capture menu. 1
ellie666 Posted November 27, 2015 Author Posted November 27, 2015 thanks I'm all sorted now, although I now have 2 capture images and 1 boot !!
ellie666 Posted December 1, 2015 Author Posted December 1, 2015 so my capture worked fine (I believe) but now I'm getting WDSClient: an error occurred while obtaining an IP address from the DHCP server --- I have tried injecting loads of different drivers from the original gigabyte mobo cd but it has made no difference HELP thx Elliott
ellie666 Posted December 1, 2015 Author Posted December 1, 2015 btw if I shift f10 I can ping my servers and have an ip address
Joanne Posted December 1, 2015 Posted December 1, 2015 Is this in the PXE boot bit? Are the clients running a UEFI BIOS?
Joanne Posted December 1, 2015 Posted December 1, 2015 THERE'S YOUR PROBLEM!! Change it to legacy BIOS. Usually in the advanced bit, make sure PXE is enabled in legacy mode.
sted Posted December 1, 2015 Posted December 1, 2015 THERE'S YOUR PROBLEM!! Change it to legacy BIOS. Usually in the advanced bit, make sure PXE is enabled in legacy mode. if you have a 2012r2 server and a windows 8.1/10 boot image you don't need to do that and are better off not as the cps boot faster I find in uefi mode
ellie666 Posted December 1, 2015 Author Posted December 1, 2015 but my images are build already in uefi mode
Joanne Posted December 1, 2015 Posted December 1, 2015 if you have a 2012r2 server and a windows 8.1/10 boot image you don't need to do that and are better off not as the cps boot faster I find in uefi mode OP said they were using SBS 2011...? I've found UEFI never works for me. I'm using 2008 R2. I deploy Windows 7 images and with new laptops I have to revert to legacy BIOS to reimage the machine, then you can put the bios back to UEFI for Windows 8.1 / 10 builds. I believe UEFI won't work with Windows 7 though (not in the several schools I've set up WDS in anyways!).
sted Posted December 1, 2015 Posted December 1, 2015 OP said they were using SBS 2011...? I've found UEFI never works for me. I'm using 2008 R2. I deploy Windows 7 images and with new laptops I have to revert to legacy BIOS to reimage the machine, then you can put the bios back to UEFI for Windows 8.1 / 10 builds. I believe UEFI won't work with Windows 7 though (not in the several schools I've set up WDS in anyways!). no im not 100% sure win7 supports uefi at least out of the box
ellie666 Posted December 1, 2015 Author Posted December 1, 2015 uefi windows 7 works absolutlely fine and I've captured images with it, BUT I can't rollout those images using wds apparently - so do I have to convert the windows 7 installation to bios (if even possible) or start again from scratch with a bios image
Joanne Posted December 1, 2015 Posted December 1, 2015 OK does your image machine not boot with legacy BIOS enabled then? Have you tried putting a machine into legacy BIOS to put the image on it, then changing the BIOS back to UEFI when it's imaged? 1
ellie666 Posted December 1, 2015 Author Posted December 1, 2015 that seems to have done it - I tried that just before I read your post
Joanne Posted December 2, 2015 Posted December 2, 2015 Excellent! Good to hear. I've had nightmares with UEFI BIOSes, imaging and acer machines in the past. This was all in a reception classroom. It was a living nightmare! Hah!
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