MrEclipseguy

Did not try the Vista Wim. I just went back to the first wim you created, and tried that again. I'm concerned though becuse I feel that I took the same steps in creating my wim files that you took, so I'm not real sure where it all went wrong. In any case it is working. I suppose I'll try to re-create mine again and see if I can get them working as I have time. Thanks for your time and assistance in getting this working for me. Certainly appreciated. I'm sure I'll have more questions as I now move into the automation side of WDS and all that its capable of.

I went back and tried the first wim you created by importing it as you said. Then once it was imported I created a cpture boot image and then another boot image using the capture boot image I created second, and it worked... If your available and here in the US, I'd like to call and talk to you regarding this if possible, Let me know. And thanks for sticking with me on this... It is much appreciated.

What is the reasoning for using the Vista drivers over the XP-Win2K drivers? I'm not building/imaging a Vista box.

I replaced the first wim that you supplied with the second one. I just copied it to the folder where my wims reside. Should that have done the trick?

No luck. I did contact Dell again and we ran through several things including disabling the MebX (Intel Management Engine BIOS). We also looked at the system setup and turned off "Execute Disable" but we think that should not have had any reason to change or fix the issue, just a thought to try and change that. He suggested that I try and contact Microsoft, which I suppose is an option at this point. I have a few threads already out on the message boards at Microsoft, but no hits yet. I'm stumped.

Not yet. I will certainly make time tomorrow as I've finished up with the other stuff I've been working on. Been a long two days.

Hey there, Sorry I have not been able to get to this yet. I'll probably have some time tomorrow to try this one. Just wanted to let you know I had gotten it. Thanks.

Ok, I was able to see it during PXE. Still a no go with your build though. Sits there for a number of minutes beofre timing out with "The network location cannot be reached".

Copied the Wim up to the WDS server and PXE booted the machine I wish to image. Did not see the wim that you created. When looking at the path to where they reside I see a BCD file and log file that are assosiated with each of the other wims. I'm assuming this may be the case for why I cannot see it in PXE? On another note reading through your details on what you did to inject the drivers, I can say I had the same structure. Only difference is I had a boot index of 2 and not 1, and my total size after the injection is slightly smaller then yours 117,344 for mine 118,606 for yours.

Will give this a try and let you know. Thanks

http://en.wikipedia.org/wiki/Image:Intel_Core_2_Duo.png Nic is Intel 82566DM-2 Gigabit Network Connection Driver that is installed during the initial build is the E1e5132.inf which Dell lists as the R162323 package on its site. I'm convinced that I need another driver I just don't know which one at this point. Are you thinking the same?

Well I plugged in the Service tag and it brought me to the same link you had posted, which is where I downloaded the Intel drivers from. Even talked to a Dell tech and he also said I had the correct driver. that being the E1e5132.inf XP version which is also the driver listed within the device manager prior to prepping the built machine that was previously on the network and working fine. He also recommended updating the BIOS which I have done. Getting ready to try Dell tech support again to see if I can get any further with them, even though they say WDS imaging is not something they support, which I understand, but if their hardware/drivers are not compatible I think it's something they need to address.

I've been able to image and deploy, but only with the Optiplex 745. I've not been able to image or deploy for that matter since I can't even get a good image of the Optiplex 755's I think the issue lies with the 755's. Drivers, a setting, or something that will not allow it to talk on the network through PXE. I don't think it's an issue with getting the drivers injected, but maybe getting the RIGHT driver injected.

Mine fails to reach the server when I've PXE booted and selected to capture the image from a sysprepped machine. I am able to choose a volume to capture, I throw in the image name and description and at the next page choose a location to save the image locally, in my case C:\temp\Optiplex.wim, then I tick the box to put the image up to the WDS server and throw in the WDS server name and hit connect and it sits there for about 3 or 4 minutes then comes up with the error that it cannot make the connection to the WDS server. If I hit Shift F10 and do a ipconfig /all it returns no IP address. If I ping the WDS server it fails When I PXE boot it does show that it is assigning an IP address. I see the NIC is talking whether I'm plugged straight in or throgh a switch. I've walked through my entire setup and config of the WDS server. In the past I was able to get an Optiplex 745 imaged up and was able to make contact with the WDS server. I do have a 745 that I can test with to see if that even works still. I think what I'll do is see if I can image one up based on the config I currently have, and if I can do that then that will let me know that it is something to do with the 755's, most likely the NIC. Will let you know how it turns out. In the mean time if you have any suggestions let me know. ............................Fast Forward......................... I plugged in a 745 I had sitting around and sysprepped it then PXE booted and was able to make contact with the WDS server and am in the process of imaging it up to the server. So, that leads me to believe the issue lies with the 755 either driver or other issue. Has anyone else had any success with a Dell Optiplex 755 and WDS imaging?

Don't have a link, but these are the steps I've taken to inject a driver. Add additional network card drivers to boot.wim 3. Update the WDS boot image to include the new third-party network driver. To do this, follow these steps. Note The following procedure assumes that the Windows Automated Installation Kit (AIK) is installed on the WDS server. If the Windows AIK is not installed on the WDS server, you can perform the same procedure on another computer that does have the Windows AIK installed. Then, map a network drive to the WDS server. a. On the WDS server, click Start, click Run, type wdsmgmt.msc, and then press OK. b. Under your WDS server, double-click Boot images. c. Right-click the boot image that you want, and then click Disable. d. Right-click the same boot image, click Properties, and then click General. e. Note the name and location of the boot image that is displayed in the File name box. f. At a command prompt, type the following: C:\program files\windows aik\tools\petools\copype.cmd x86 c:\windowspe-x86 Note Keep this command prompt window open for the next step. Imagex /info Drive:\remoteinstall\boot\x86\images\boot.wim Notes • Drive:\remoteinstall represents the path at which the Remoteinstall folder is installed. • Boot.wim is the name of the boot image. g. Note the boot index number of the bootable image that is displayed. To identify the boot index number, locate the line that contains "boot index: X." Note X is the boot index number. The number indicates that image number X is marked as bootable and that the image is to be updated. The second image is the default image that you would typically modify. However, always verify which image is marked as bootable. h. At a command prompt, type the following: Imagex /mountrw Drive:\remoteinstall\boot\x86\images\boot.wim 2 mount peimg /inf=path to inf file\driver.inf mount\Windows imagex /unmount /commit mount Notes • Drive:\remoteinstall represents the path at which the Remoteinstall folder is installed. • Driver.inf is the name of the third-party driver. Path to inf file is the location of the inf file • The Imagex /mountrw command mounts the specified image, with read/write permissions, to the specified directory. 4. Enable the boot image on the WDS server. To do this, follow these steps: a. On the WDS server, click Start, click Run, type wdsmgmt.msc, and then click OK. b. Under WDS server, double-click Boot images. c. Right-click the boot image that you want, and then click Enable. If the above method produces errors follow this method instead. Create a new folder at the root of the C: drive. Call it WinPE :\>MD C:\WinPE Disable the Boot.wim from the WDS server console Using Copype.cmd form the WAIK, extract the WinPE tools to a folder on C: :\>”C:\Program Files\Windows AIK\Tools\PETools\copype.cmd x86” C:\Windowspe-x86 This command extracts the WinPE tools to a folder on the C: drive and updates the PATH variable to include the necessary tools. Leave this CMD windows open for use during the process Using imagex.exe mount the boot.wim file from the WDS server to the C:\WinPE folder :\>imagex /mountrw drive:\remoteinstall\boot\x86\images\boot.wim 2 C:\WinPE (My Example: imagex /mountrw J:\remoteinstall\boot\x86\images\boot-(2).wim 1 c:\winpe\mount) This command will mount the boot.wim file to the C:\WinPE folder in Read/Write [rw] mode for editing. Be sure to disable the boot.wim file from the WDS console before running this command. The 2 represents the second pass of the boot process. This is where driver files are injected. Using peimg.exe inject the .inf driver files into the mounted boot.wim image file :\>peimg /inf=”Path to inf files\driver.inf” /image=C:\WinPE (My example: peimg /inf=c:\dell\drivers\r162313\win2k_xp\b57win32.inf c:\winpe\mount) This command will inject the driver files into the boot.wim image. Substitute Path to inf files for your path and driver.inf for the actual name of the driver file. Include the “” only if your path contains spaces. Example: :\>peimg /inf=C:\Driver Files\e1000325.inf” /C:\WinPE Finally, unmount and save your boot.wim file using this command :\>imagex /unmount /commit c:\WinPE\mount Create a new Capture.wim file based on the updated boot.wim following the same directions detailed above. This will ensure that the drivers are available in both Capture and Boot images I've gotten drivers injected succesfully, or so I think. At least it completes successfully, and unmounts as if it was done right. I need to try a few more drivers, but in talking to Dell the E1e5132.inf file from the R162323 driver file on their site is the correct one. I have the entire guide I've used if you want me to email that to you.