| Author |
 Topic  |
|
|
Pesos
Honorable But Hopeless Addict
USA
2684 Posts
Status: offline |
 Posted - 09/24/2009 : 6:19:46 PM
|
Hi guys,
I am in Bakersfield (woohoo!) and have to build up some older machines with win7... They don't boot USB, they don't have DVD drives, and the only bootable NIC I have is a 3com 3c905 that I carry around for RIS installs...
Well WDS doesn't work with 3c905s (BRILLIANT MICROSOFT!!!!) -- so I attempted to inject the driver using instructions I found googling - mounted the boot.wim on my WDS server, used peimg to inject the driver, then committed and unmounted. No errors... Yet I still get the network cannot initialize under WDS when trying to boot... I then exported and reimported the boot.wim into WDS... Still no dice...
Did I miss something? Do I need to inject the driver into a boot.wim that is not already in the WDS console? Any help would be appreciated thank you!!!
-Wes
|
-Wes |
|
|
MrEclipseguy
Honorable But Hopeless Addict
USA
1268 Posts
Status: offline |
Posted - 09/24/2009 : 7:35:34 PM
|
Are you getting to the point where you get the logon prompt? If so are you entering doamin\username and password?
Or are you not even getting to that point? |
Mike
Even though WDS is the spawn of Satan he ain't that Scary!! |
 |
|
|
Pesos
Honorable But Hopeless Addict
USA
2684 Posts
Status: offline |
Posted - 09/24/2009 : 7:40:28 PM
|
| No before that it stops telling me can't initialize network |
-Wes |
|
|
|
Robovitch
Welcome Newcomer
USA
23 Posts
Status: offline |
Posted - 09/24/2009 : 7:49:43 PM
|
Hi Wes,
after you injected the NIC drivers into the boot.wim did you rebuild the deploy in the Boot Images section of WDS? I have found that when I add a new NIC driver I have to recreate the Deployment image in the Boot Images folder on my WDS server.
Sorry if this is redundant info and best of luck to you!
Rob |
|
|
|
Pesos
Honorable But Hopeless Addict
USA
2684 Posts
Status: offline |
Posted - 09/24/2009 : 7:52:50 PM
|
| Hi rob, how do I do this? After I injected, I exported the boot.win in the wds console, then deleted it from the console, then reimported the exported wim... |
-Wes |
|
|
|
Robovitch
Welcome Newcomer
USA
23 Posts
Status: offline |
Posted - 09/24/2009 : 8:09:49 PM
|
Hi Wes,
1) Open up your WDS Console and drill down to "Boot Images"
2) right click on "boot Images" and select "Add Boot Image"
3) It will open up a Wizard which walks you through the process but it goes thusly:
First window is: Image File - Browse to your boot.wim that has the new NIC driver in it. Highlight the boot.wim and click "open". Then click "next".
In the "Image Metadata" window change the "image Name" to whatever you call your Deployment boot.wim. You can enter a description if needed. Hit "Next" and then "next" again. The Wizard will then add the image to you "Boot Images" section in WDS Console.
You may need to close and reopen the console to see the new deployment file that you created. Once this is done you should be able to PXE boot the target PC and find the new deployment with the new NIC driver. With a spot of luck you are good to go.
thanks for putting up with the novella.
Rob
|
|
|
|
Pesos
Honorable But Hopeless Addict
USA
2684 Posts
Status: offline |
Posted - 09/24/2009 : 8:14:00 PM
|
Hi Rob, no problem... I didn't explain very well.
I have a boot image already in WDS console... the path to this image is d:\remoteinstall\boot\x86\images\boot.wim
I then used imagex.exe to mount this exact file (the one that is already showing in the WDS console) to d:\temp
I then used peimg.exe to inject the 3com inf into d:\temp, and unmounted using /commit
It churned for a bit and said successful...
I then used the WDS console to export the boot image to the desktop, then deleted it from the console, then did Add Image (as you laid out above) and re-added it to the console...
no dice... |
-Wes |
|
|
|
Rhonda
Moderator
USA
470 Posts
Status: offline |
Posted - 09/27/2009 : 10:28:27 PM
|
| I would export the boot.wim first from WDS and then import the driver and add it back to WDS again. Have you looked to see if the driver is in the driver store of the WinPE? You can also look at the log files by pressing F8 to get a command prompt and going to C:\minint\smsosd\osdlogs. Which log files exist? Is there anything interesting in them? When at the command prompt do you have an ip address? Can you ping anything? |
Setup and Deployment MVP
Follow my Tweet at RhondaLayfield |
|
|
|
Pesos
Honorable But Hopeless Addict
USA
2684 Posts
Status: offline |
Posted - 09/27/2009 : 10:39:56 PM
|
| Thanks Rhonda, I will give that a try and report back... I ended up having to push my custom WIM from within the existing winxp installation (via USB 1.1 which took forever!) but am looking forward to getting this working for the future! |
-Wes |
|
|
|
Pesos
Honorable But Hopeless Addict
USA
2684 Posts
Status: offline |
Posted - 11/25/2009 : 5:29:52 PM
|
Since I am now at a new site with a number of 3com nic'd machines, I figured it was time to give this another go. This time I extracted the .inf and .sys files from a machine that had had its 3com driver updated by Microsoft Update, so that I knew it would be a "vista/win7" happy driver.
I also finally came across updated documentation that explained how to properly inject with the new waik using DISM (rather than imagex and peimg). Following these steps worked for me and I now have a 3com-friendly boot.wim!
http://technet.microsoft.com/en-us/library/dd744355%28WS.10%29.aspx |
-Wes |
|
|
|
Rhonda
Moderator
USA
470 Posts
Status: offline |
Posted - 11/26/2009 : 10:34:01 AM
|
| Deployment Image Servicing and Management (DISM) is the utility that replaced imagex (for mounting and un-mounting wims) and peimg (for adding drivers) and International Configuration (for adding language packs)in the latest WAIK 2.0 (also called Windows Automated Installation Kit for Windows 7). Mark did a few articles on this (DISM) for Windows ITPro magazine. |
Setup and Deployment MVP
Follow my Tweet at RhondaLayfield |
|
|
|
Pesos
Honorable But Hopeless Addict
USA
2684 Posts
Status: offline |
Posted - 11/26/2009 : 11:46:21 AM
|
| Good to know I'll check them out! When I made the original post I was stuck in Bakersfield on a 768kb DSL line with a deadline - the 1.7 GB WAIK d/l was not an option!!! I still think it's kind of silly that basic driver injection is not a part of the core WDS server package... |
-Wes |
|
|
|
superhl
Welcome Newcomer
20 Posts
Status: offline |
Posted - 01/28/2010 : 11:13:02 AM
|
| I am having similar problems I Imagex and added a NETRTLE.INF driver to boot wim. I can pxe with no problem but when I arrive at boot screen I select "Deployment boot" select enter and erros out stating "WDSClient: An error occured while obtaining and IP address fromthe dhcp address ....... I can inject the driver dvrload.exe from usb and Initialize and will get IP address. Using Imagex I injected the driver both for index 1 and one index 2 and still not boot. thanks for any help!1 |
|
|
|
superhl
Welcome Newcomer
20 Posts
Status: offline |
Posted - 01/28/2010 : 11:14:36 AM
|
| I forgot to state that I am running windows 2003 deployment and trying to image a windows xp tablet with a realtek driver. thanks |
|
|
|
Rastor728
Old Timer
USA
357 Posts
Status: offline |
Posted - 01/28/2010 : 1:10:56 PM
|
I had this problem as well, and created the old fashioned boot floppy from the WDS Server and used that to boot the workstation to PXE prompt to start the deployment process.
Of course you have to have a floppy drive on the server and workstation for it to work.....I was lucky.
I made sure the 3Com drivers were imported to WDS drivers so after the deployment, of course the NIC's still worked without any issue. |
"a fanatic is one who cannot change his mind and will not change the subject." --Sir Winston Churchill |
|
|
|
superhl
Welcome Newcomer
20 Posts
Status: offline |
Posted - 01/28/2010 : 5:01:22 PM
|
| PXE is not the problem. I can pix to the boot process but when I select "Capture XP". I am not getting an ip. I can insert usb with the driver and at the c:\drvload.exe .... and the server will ask me to login. thanks |
|
|
|
superhl
Welcome Newcomer
20 Posts
Status: offline |
Posted - 01/29/2010 : 08:19:35 AM
|
| Will a windows 2008 server boot.wim work with a windwos 2003 server? thanks |
|
|
|
Pesos
Honorable But Hopeless Addict
USA
2684 Posts
Status: offline |
Posted - 01/29/2010 : 10:48:41 AM
|
| Yes WDS on win2003 can serve newer wims, 2008/vista/win7/2008r2 etc |
-Wes |
|
|
|
superhl
Welcome Newcomer
20 Posts
Status: offline |
Posted - 01/30/2010 : 8:44:04 PM
|
could this be the problem? Notice the erros.copied from setupapi.log
[DIF_SELECTBESTCOMPATDRV - PCI\VEN_10EC&DEV_8136&SUBSYS_0778152D&REV_02\4&62FFB1C&0&00E0]
>>> Section start 2010/01/29 14:40:57.645
cmd: winpeshl.exe
dvi: Using exported function 'NetClassInstaller' in module 'X:\WINDOWS\system32\NetCfgx.dll'.
dvi: Class installer == NetCfgx.dll,NetClassInstaller
dvi: Using exported function 'NciDeviceInstall' in module 'X:\WINDOWS\system32\nci.dll'.
dvi: CoInstaller 1 == nci.dll,NciDeviceInstall
!!! 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: CoInstaller 1: Enter 14:40:57.692
dvi: CoInstaller 1: Exit
dvi: Class installer: Enter 14:40:57.692
dvi: Class installer: Exit
dvi: Default installer: Enter 14:40:57.707
dvi: {Select Best Driver}
dvi: Selected driver installs from section [RTL8136.ndi] in 'x:\windows\system32\driverstore\filerepository\netrtx32.inf_f093b1d0\netrtx32.inf'.
dvi: Class GUID of device changed to: {4d36e972-e325-11ce-bfc1-08002be10318}.
dvi: {DIF_DESTROYPRIVATEDATA} 14:40:57.707
dvi: CoInstaller 1: Enter 14:40:57.707
dvi: CoInstaller 1: Exit
dvi: Class installer: Enter 14:40:57.707
dvi: Class installer: Exit
dvi: {DIF_DESTROYPRIVATEDATA - exit(0x00000000)} 14:40:57.707
dvi: Set selected driver complete.
dvi: Selected:
dvi: Description - [Realtek RTL8101 Family PCI-E Fast Ethernet NIC (NDIS 6.0)]
dvi: InfFile - [x:\windows\system32\driverstore\filerepository\netrtx32.inf_f093b1d0\netrtx32.inf]
dvi: Section - [RTL8136.ndi]
dvi: Signer - [Microsoft Windows]
dvi: Rank - [0x0dff2001]
dvi: {Select Best Driver - exit(0x00000000)}
dvi: Default installer: Exit
<<< Section end 2010/01/29 14:40:57.707
<<< [Exit status: SUCCESS]
|
|
|
|
superhl
Welcome Newcomer
20 Posts
Status: offline |
Posted - 02/04/2010 : 1:47:46 PM
|
| Does anyone no of other steps I can try to troubleshoot. thanks |
|
|
|
Pesos
Honorable But Hopeless Addict
USA
2684 Posts
Status: offline |
Posted - 02/04/2010 : 1:50:14 PM
|
| Sorry, I haven't worked with XP/2003 capture/deployment on WDS... We always use WDS legacy (RIS) for that... |
-Wes |
|
|
| |
Topic |
|
can't get WDS working with 3com 3c905 urgent!
