• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2671
  • Last Modified:

i cant install NIC driver to image for WDS. need help

i want to deploy windows 2008 image to the clients over the ethernet, but i cant get the NIC driver to work at windows PE.

i use WDS on windows 2008 server, i did everything to install the .INF file manually at the command prompt in boot up and also downloaded the WAIK and tried the imagex command to mount and added the driver file and unmounted but i still get an error regarding "Cant obtain an IP from dhcp" and when i do ipconfig, no driver exist.

what should i do????

i tried to install the .INF file manually at boot up, it does install but after i reboot to the server the driver doesnt stay there.

what should i do????
0
johnsar
Asked:
johnsar
  • 22
  • 18
1 Solution
 
merowingerCommented:
You have to add a Network Driver which supports the OS which you Windows PE has. What's your PE Version?!
0
 
johnsarAuthor Commented:
2.1
0
 
johnsarAuthor Commented:
u mean the driver should be for Windows PE or the Windows 2008 ????
0
Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

 
johnsarAuthor Commented:
WDS server installed on win 2008 32bit.

u mean the driver should be for Win 2008 32bit?????
0
 
merowingerCommented:
No, PE is normally based on XP, VISTA, or Windows 7
The following command should list the pe version:
imagex /info yourpe.wim

Here's the list on which OS PE is based:
PE 1.0 - Windows XP
PE 1.1 - Windows XP and SP1
PE 1.2 - Windows XP and SP1 and Windows Server 2003
PE 1.5 - Windows XP SP2
PE 1.6 - Windows XP SP2 and Windows Server 2003
PE 2.0 - Windows Vista
PE 2.1 - Windows Vista SP1 and Windows Server 2008
PE 3.0 - Windows 7
PE 3.1 - Windows 7 SP1

As PE comes with WAIK it depends normally on which WIAK Version you've installed
0
 
johnsarAuthor Commented:
i just installed WIndows 2008 r2 because i can easily add the drivers on WDS interface.

i downloaded the drivers and added that way, but still i get  "Cant obtain IP from DHCP".

while im there, i did shift + f10 and did ipconfig and nothing showed them.

so it means the drivers didnt install?

but i added them on WDS interface.

my NIC card is Realtek RTL8168D/8111D Family PCI-E Gigabit Ethernet NIC (NDIS 6.20).

please can you help me with this?

anything wrong?
0
 
johnsarAuthor Commented:
0
 
merowingerCommented:
if ipconfig does not deliver any result. then the nic driver is normally missing or does not match. You really have to make sure that the nic driver matches to your pe version.
No i think you link isn't correct. Try this one:
http://www.realtek.com.tw/downloads/downloadsView.aspx?Langid=1&PNid=13&PFid=5&Level=5&Conn=4&DownTypeID=3&GetDown=false
0
 
johnsarAuthor Commented:
i try again and let u know
0
 
johnsarAuthor Commented:
still not working.

i pressed shift + F10 and to manually install the driver, i was in x:\sources. i did x: and i tried to go to my Administrator account but my Admin account wasnt there, there was only Public folder.

Where should i put the .inf files to install?

they should be on the server where WDS is or it can be on USB or the computer in which i am booting to the WDS server???
0
 
merowingerCommented:
try to inject them in windows pe before booting from it.
0
 
johnsarAuthor Commented:
how can i inject them in windows pe??

it doesnt give me the chance to inject them, the error message comes very fast and then i have to reboot again.

it automatically takes me to the win pe where it gives me an error about not having dhcp, and thats where i can press shift plus f10 but its too late. because by that time i already get that error and i have to restart again.

0
 
johnsarAuthor Commented:
it looks complicated.

dont u have any other easier solution??
0
 
johnsarAuthor Commented:
ok. i will try that.

but i manually added the driver in pe by doing drvload netrtx32.inf and then did wpeutil initializenetwork

and i could ipconfig /release and /renew and got an ip from dhcp in win pe.

but the problem is that its not permenanet. the driver doesnt stay in pe permanently that way.

right???

it should stay or shouldnt??
0
 
merowingerCommented:
it should yes
0
 
johnsarAuthor Commented:
what does it mean if it shouldnt stay there after i even reboot the computer and connect to the server at boot up???
0
 
johnsarAuthor Commented:
wtf, i used dism to inject a driver but i get an error

it says "DISM does not support servicing a Windows Vista RTM or earlier operating system".

what does it mean?
0
 
johnsarAuthor Commented:
i did this to inject the driver, can u please check if its right?

Dism /image:C:\Users\vahid01\Desktop\mount /Add-Driver /Driver:C:\Users\vahid01\Desktop\driver\netrtx32.INF

is it correct?

\mount is the dir where dism mounted the image and \driver is the dir where the driver file is.

thanks.
0
 
merowingerCommented:
i think the error means that your winpe image cannot be changed with the new tool dism.exe. This was released with WinPE 3.0 and your using 2.1.
Please try this command:
http://technet.microsoft.com/en-us/library/cc749350(WS.10).aspx
0
 
bgoeringCommented:
Make sure you are updating both the boot and the install images on your WDS with the drivers.
0
 
merowingerCommented:
got it work with the correct driver?
0
 
johnsarAuthor Commented:
yeah. the drivers were correct.

i was just making a mistake of adding the driver file to the wrong boot.wim image.

i had to add the driver to the boot.wim image which was located in c:\Remoteinstall dir, not anywhere else.

the one which is in c:\remoteinstall\boot\x86\image\boot.wim  .

did u know that??
0
 
johnsarAuthor Commented:
merowinger: what is your opinion about making my WDS server available over the internet so that remote users use it over the internet??

how is it possible?
0
 
merowingerCommented:
yes id did know that :)
Internet...WDS?!? What your triying to do? OS Installation over the Internet?
0
 
johnsarAuthor Commented:
yeah. over WAN.

can it be done???

like if my brother living somewhere else and want to install an OS, he can connect to my server and do the installation over the internet.

how would you do that??
0
 
merowingerCommented:
No that isn't possible. Maybe you could handle it a little bit with SCCM but not with native WDS
0
 
johnsarAuthor Commented:
so such configuration is possible with SCCM?

but it would be a good technique ey?
0
 
merowingerCommented:
No it's even hard with SCCM as a Network Boot isn't possible.
So the only possibilty i see is to use SCCM Standalone Medias (USB, DVD) which contains Windows PE and the Win7 WIM Image. After the Image was applied, the SCCM Client is installed and the Network is connected to the Internet it could contact a SCCM Server which is in Native Mode and its Component Servers are published to the internet. Or the Client connects to the Company LAN via DirectAccess or VPN.
BUT: For all of those approaches there's needed a lot of doing
0
 
merowingerCommented:
AddOn: On the abobe Scenatio the whole OS Deployment process comes from a Standalone Media, only some futher settings or applications are then installed via the Internet
0
 
johnsarAuthor Commented:
so you mean its hard to do such thing???

but there are guides on the internet for that?
0
 
merowingerCommented:
Yes it's hard and as i already said, it's not really OS Deployment over the Internet
0
 
johnsarAuthor Commented:
do companies do that? is it common?

should i learn about it as a skill if i want to work in a company as a  network engineer or admin???
0
 
merowingerCommented:
No it's no common.
To manage Clients over the Internet via SCCM Native Mode, Direct Access or VPN Access is common, but not to install OS over it.
You should know about the methods how Clients can access the Internet and which restrictions exists.
Searching a new job? :)
0
 
johnsarAuthor Commented:
yeah.

well, a client can access the internet via direct connection,  proxy, VPN, ........

you mean that?
0
 
merowingerCommented:
i don't know your tasks at you new job.
It makes no sense if you learn SCCM when your new company uses another product.
So as a network engineer / admin you should be familiar with the basic networking features like dns/dhcp/wins/active directory/routing/subnetting, and also the possibilities how client get access to the company lan (e.g. vpn, direct access)
0
 
johnsarAuthor Commented:
yeah, i am looking for a junior position.

also it is possible to use VNC or RDP over the internet to connect to servers/clients as a method other than using vpn or DA. right???
0
 
merowingerCommented:
VNC and TeamViewer should work over the internet without the client connected to company lan. I don't know if RDP also supports this.
0
 
merowingerCommented:
just start answering quiestions here to improve your skills ;)
0
 
johnsarAuthor Commented:
looks like Direct Access can be complex to set up. as it requires ipv6 which i dont know a thing about. lol.

but can you please tell me how its possible to use vpn to get connected to a companies lan to use their resources as if u are locally there?

what would be the minimal vpn configuration to reach this goal?

is it the same way that u can setup ur vpn server on like windows 7 or vista or its different method????

i mean can i do that with my win 2008 server without any special hardware like router and as such???
0

Featured Post

Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

  • 22
  • 18
Tackle projects and never again get stuck behind a technical roadblock.
Join Now