RIS Driver Issues

[freaky_seb]

Hey folks.

 

So I've got a Windows 2003 server setup to do remote XP installations via RIS.

 

I'm running into some trouble trying to add network drivers to the XP image so that the installer can use the network adapter on one of our new machines (it's an Asus 10" EEE with an Atheros Network Adapter.)

 

I grabbed the drivers from the CD for the ethernet adapter. The .sif file already exists as one of the old IT technicians set RIS up. I added the path for the driver into the ristndrd.sif file (located in \templates) I've done everything I can think of to get this to work, but when I try to remote boot the machine, I still get the message that

 

"the operating system image you selected does not contain the necessary drivers for your network adapter."

 

I'm not sure why; the driver is most definitely there, and I don't know of anything else that's required for RIS to see the driver other than the things I specified above that I did (I followed directions as per the MS website How to add a third-party OEM network adapter to a RIS installation.

 

I've of course restarted the WDS service/server itself multiple times.

 

I really don't understand why this isn't working, as I have followed all instructions found on the net, has anyone got any ideas?

[mac_shinobi]

Hey folks.

 

So I've got a Windows 2003 server setup to do remote XP installations via RIS.

 

I'm running into some trouble trying to add network drivers to the XP image so that the installer can use the network adapter on one of our new machines (it's an Asus 10" EEE with an Atheros Network Adapter.)

 

I grabbed the drivers from the CD for the ethernet adapter. The .sif file already exists as one of the old IT technicians set RIS up. I added the path for the driver into the ristndrd.sif file (located in \templates) I've done everything I can think of to get this to work, but when I try to remote boot the machine, I still get the message that

 

"the operating system image you selected does not contain the necessary drivers for your network adapter."

 

I'm not sure why; the driver is most definitely there, and I don't know of anything else that's required for RIS to see the driver other than the things I specified above that I did (I followed directions as per the MS website How to add a third-party OEM network adapter to a RIS installation.

 

I've of course restarted the WDS service/server itself multiple times.

 

I really don't understand why this isn't working, as I have followed all instructions found on the net, has anyone got any ideas?

 

Get the latest NIC driver for that laptop / EE pc and ensure its NDIS2 one and try that ?

[ChrisH]

 

I really don't understand why this isn't working, as I have followed all instructions found on the net, has anyone got any ideas?

 

Try FOG, you know it makes sense

[freaky_seb]

Get the latest NIC driver for that laptop / EE pc and ensure its NDIS2 one and try that ?

 

Did that mate, same message. So I guess the drivers are ok

 

Try FOG, you know it makes sense

 

Now having a look into FOG, it looks very good, may give it a go!

 

I've been having trouble adding any driver to our master RIS install since we ran SP3 on Win2003 so patch the conficker virus. It changed the RIS service to the WDS service, I'm wondering if thats the problem.

[mac_shinobi]

It changed the RIS service to the WDS service, I'm wondering if thats the problem.

 

Most likely because WDS and RIS work differently ( at least as far as configuration of it ) - WDS has an xml file that you have to configure amongst other things.

 

FOG should get you up and running

[freaky_seb]

Most likely because WDS and RIS work differently ( at least as far as configuration of it ) - WDS has an xml file that you have to configure amongst other things.

 

FOG should get you up and running

 

Yeah, I figured as much, the image is working fine for the older machines which already have the drivers integrated. But I can't add any more drivers.

 

The only problem we will have with FOG is that we will have to run it on a VM, we have no more servers :'(