local-lad-steve Posted March 22, 2010 Posted March 22, 2010 Hello, i am having much trouble with WDS. having had problems with the boot images (capture image and deploy image) and injecting the network drivers i successfully captured an XP image for a Dell Optiplex 380. However, after trying to deploy the image to another 380 machine, WDS gets as far as "copying windows files", "expanding windows files" and before it begins to "install features" it reboots the PC and obviously has no OS installed. i took a copy of the log file "setupapi.app.log" off the PC and all successes apart from the below. this looks to be trying to search for a wireless .dll file, however, i am confused by this as i am using a Dell Optiplex 380. am i missing something? >>> [DIF_SELECTBESTCOMPATDRV - PCI\VEN_14E4&DEV_1692&SUBSYS_04001028&REV_01\4&2696CBC&0&00E0] >>> Section start 2010/03/19 16:35:22.820 cmd: X:\Sources\setup.exe !!! dvi: Loading module 'X:\WINDOWS\system32\wlaninst.dll' failed. !!! dvi: Error 126: The specified module could not be found. !!! dvi: Error 126 loading CoInstaller(wlaninst.dll,WlanDeviceClassCoInstaller) !!! dvi: Error 126: The specified module could not be found. !!! dvi: Loading module 'X:\WINDOWS\system32\wwaninst.dll' failed. !!! dvi: Error 126: The specified module could not be found. !!! dvi: Error 126 loading CoInstaller(wwaninst.dll,WwanDeviceClassCoInstaller) !!! dvi: Error 126: The specified module could not be found. <<< Section end 2010/03/19 16:35:22.852 <<< [Exit status: SUCCESS] >>> [setupInstallServicesFromInfSectionEx - MS_NETBT_SMB.PrimaryInstall.Services] >>> Section start 2010/03/19 16:35:34.583 cmd: X:\Sources\setup.exe <<< Section end 2010/03/19 16:35:34.583 <<< [Exit status: FAILURE(0xe0000101)] any ideas as to why this deployment might be failing? thanks
dirtydog Posted March 22, 2010 Posted March 22, 2010 strange, I too had to inject drivers for our new 380's into WDS but im deploying Win7 and seems ok on a test image Ive done so far.
local-lad-steve Posted March 22, 2010 Author Posted March 22, 2010 yes it's odd!! cant find any reference to the same problem although the above error does pop up here and there on forums. any ideas would be greatly appreciated!! need to get this sorted over next few days. thanks.
local-lad-steve Posted March 22, 2010 Author Posted March 22, 2010 Resolved it today. went back to the beginning and started as fresh. cleared the server of WDS and any subsequent files/folders, created a new image and injected the NIC driver into a fresh boot.wim. full unattended XP deployment all working fine!!
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