WDS is a great time saver- but for some reason the documentation for it on the web sometimes lacks simple to follow guides- which means you waste time trying to help people do the simplest of things with it sometimes- hopefully the below will help you save some time! • Connect to your WDS server • Grab your drivers from the web and extract them to a folder (all too easy to leave them in a zip or executable!). Ensure they’re appropriate for the version of windows you are deploying (e.g. • Open up the WDS console. • Expand the servers area, then your server group and select drivers. Right click and chose Add Driver Package WDS Console – Add Driver • It’s often easiest to point it to the directory, rather than a specific INF in case the driver has multiple components, so select “Select all driver packages from a fodler and click browse to find the extraction path from the step above.

KB ID 0000314. Before Server 2008 R2 when we needed to inject drivers into our WDS images we had to do it like this. Now however the process is a lot more elegant! Simply import the drivers into WDS, then inject them into the boot images (Yes the boot images NOT the Windows Images you are deploying!). Windows Deployment Services is a server technology from Microsoft for network-based installation of Windows operating systems. It is the successor to Remote.

• Click next, and allow it to find the driver packages • Click next once you’ve got the packages you want and next to add them to the server: • It’ll start adding them in the WDS driver collection. • Once that’s done, you can add it to a group (which makes it easier to identify old drivers, etc) – if one doesn’t exist, you can create one to reflect the laptop details (like the one in the example below) • Click next and you’re done- you can untick the modify the filters for this group now and click finish to get straight into action. • Once added, you need to insert the driver into the boot image. Before that, though, you should back up the image- so expand Boot image then right click on the Windows Setup X86 and chose EXPORT IMAGE to save a copy of the image (date mark it for easy reference). • Then right click again on the image from before and chose add driver packages to image: • In order to find the driver packages you want, click on the Add button, and chose the attribute type and set it to driver group name and equal to.

Then, in the drop down box below, you can simply pick the driver group we created earlier and click add and ok. Then click on search for packages and it’ll pull back all the drivers you just added. • Simply click on next, then next again and it’ll mount and insert the driver image details. Once complete, you should be ready to go.

Imagex.exe /mountrw C: Temp PE boot. Go Sms Pro Free Download For Cherry Mobile Flare Price more. wim 1 C: Temp PE mount peimg.exe /inf=C: Temp PE VMWNIC vmxnet.inf C: Temp PE mount Windows peimg.exe /inf=C: Temp PE VMWNIC vmware-nic.inf C: Temp PE mount Windows imagex.exe /unmount C: Temp PE mount /commit But it isn't working. The drivers are added successfully, and I can PXE boot the updated boot image on the supported NICs, but when a machine with an unsupported NIC PXE boots with the updated image I still get 'there are no network adapters present' or something to that effect. Do I use Vista drivers for this or would Win 2003 or XP drivers suffice? I've tried both.

This is madness. We've had this problem on and off, mostly with older Dell machines, so we were forced to deploy a flat XP RIS image onto the machines, and let GPOs deploy the apps, and never really fixed the real issue. But I have to figure this out today!

I have seven Proliant DL360 G5s to deploy and I'm NOT setting them up manually one at a time! Win PE 2.0 ('boot.wim' off Vista's DVD) does not have the drivers for the HP NC373i NIC (rebadged Broadcom Nextreme II) so I can't PXE boot to capture or deploy the WDS image. I can, and have, gotten around the capture by capturing onto local storage, but I can't PXE boot and deploy the image without the NIC support. I've added the HP/Broadcom drivers to Win PE WIM by the book, but they don't work and I still have no NIC when I PXE boot. I got a little further. I got into the Win PE cmd (Shift F10) and ran ipconfig.

Got nothing, which makes sense. Then I issued wpeutil InitializeNetwork and got 'network initialized successfully', but nothing changed! I'm now reading about manually loading drivers into Win PE environment. I'll probably need to issue sc start xxx to get it to start after I load it. I can't believe this.

I don't think I'm doing anything wrong. And yet in over a year I've used WDS I have NEVER been able to successfully add additional NIC drivers to the boot images. Edit: edited a typo in a file name. Yes, that was it. I can PXE boot the Proliants!

I jumped over one hurdle and face planted into another. In the choice of images, I can see only our standard desktop image (Win XP 32bit).

The Win 2003 64bit image captured on this very same Proliant is not being offered for installation. It isn't a HAL mismatch so what the hell? Do I need to use 64bit Win PE to deploy 64bit images?

I need to read about that now. EDIT YES YES I DO NEED 64bit Win PE. And by definition a 64bit Broadcom driver. Why can't this just work?