You need to patch your RIS server, and your RIS image. Take a look at MS article Q315074. You will either need to upgrade your server to SP3 or obtain the hotfix from MS to upgrade your BINL service. Also, the NTLDR in your \RIS\Setup\i386\templates directory must be replaced with the proper version listed in the MS Q article. After patching the image you will need to stop and restart the BINL service and everything should work. I did get a RIS server working, but the procedures MS has is very confusing. IT took a couple of trys to get everything right.

Droid

Thanks Droid, finally got it working.

Some further info that may be useful to others who read this, installing SP3 on the RIS server means you also need to install SP3 on the DC's if you are using the managed computer options. Also I found that SP3 caused all my previous RISetup images to stop functioning, new RISetup images work, even though all the file versions appear to be the same, how wierd is that? (I assume this isn't the case for everyone otherwise there would be an outcry!)

Thanks again,
Roger

Hi Wolfgang,

You need to make sure the inf files are in the directory you add to the OemPnPDriversPath. i.e. either

1) add \Drivers\video to the path and put the files directly in that directory, or
2) put files in \Drivers\video\Intel\845\etc and add the *full* path to OemPnPDriversPath

Hope this helps,

Roger

Whilst I'm here....my GX260 RIS woes are not over.

1) The graphics driver writes to the registry to add some (unwanted) menus to the 'right-click-desktop' menu, and seems to need administrator rights to do this. If users log in on a freshly ris'ed machine they get garbage on their menu.

2) The Pro1000 driver/NIC does not seem to activate in time for the computer account to connect to active directory which means group policies applied to computers don't work.

Solved 2) by disabling onboard 1000MT NIC and installing Pro100S NIC.
Solved 1) in the case of this particular machine by logging in as local administrator, but this would not be suitable for machines across our enterprise.

Unless I find solutions to both I'll have to ban Dell GX260's from our enterprise, at least until some solutions appear.

Hi,

I had the same problem with RIS-Installation. Solved the problem with SP3 on RIS-Server and DC. But i still have unsolved Problems :(
I dont get Audio and Video Drivers work with RIS-Installation. I put the Drivers in the $OEM$ - Tree ($OEM$-Directory is at the same level as the i386-Directory) and wrote the correct path in the answer file (OemPnPDriversPath= \Drivers\Video;\Drivers\Audio). At the end of the XP-Installation the drivers are not installed :(

Anyone knows a Solution?

tia

Wolfgang

Best solution: Disable the onboard LAN - install a less 'cutting edge' NIC

To all the expert out there,
Please help !!
I've encountered exactly the same problem as you guys and follow thru all steps carefully but still get the same error mesg.
I have my RIS server and DC setup onto the same machine,SP3 has been applied but still no hope,any ideas what could be the problems ?
I even setup an new Server with SP3 installed also does not help
Pls advise and help

Thanks,

Hi Droid,
Pls help and respond if you are in active.
Read your how-to-guide posted here,I did everything includes patching of RIS server except patching of the RIS image,pls enlighten me on how to patch the images ?
Thanks

Hi, as u can read i had the same problems a few lines later in this thread. I solved the Problem with using the newest drivers from Dell-Support-Homepage. The drivers which come with the Gx260-Computer did not work for me, they are not recognized from RIS-Server. I downloaded newer drivers for nic, chipset, vga and all devices are installed by the RIS-Server. Hope this helps!

Sorry for my poor english...;-)

greetings

wschmi

If you're still having problems with the

"The operating system image you selected does not contain the necessary drivers.."

bit, then Microsoft Q315074 and SP3 should solve it.

To patch the current RIS image follow the part in the Q article about extracting 24240_enu_i386_zip.exe, copying the Setupldr.exe to the templates folder (e.g.~\RemoteInstall\Setup\ language\images\ your image\i386\Templates) and rename it to NTLDR.

The files mentioned don't seem to be a part of SP3, but images created post-SP3 do seem to have a NTLDR file that works with the 1000MT. As I couldn't get the old images to work, (even on PC's that previously RIS'ed without a problem), if you're still having problems then I would strongly recommend creating new images once you have applied SP3 to the RIS server.

Also please note, even if you get this working, if you make any use of Active Directory group policies, and apply them to computers, the Intel Pro 1000 still causes problems, because the drivers don't seem to initialize in time, and computer based policies are not applied, which may not be initially obvious but can cause strange problems.

As I stated before, IMHO the best option currently is to disable the onboard 1000MT and use an older NIC.

HTH
Roger

Thanks Roger,
I still have some other questions that needs your advice.
The path specified in the .sif under unattended section normally $OEM$\$1\Driver\NIC\,can I put other oem vendors within its structure to read somthing like this : OEM$\$1\Driver\NIC\Intel
\3com
\xircom
\linksys
I've copied Intel1000 driver to \Intel folder and other folders remains keep their own drivers,will that causes problem ?

Yes you can add subfolders to the directory, but the inf file needs to be placed directly in the folder that's in the OEMPnpDriversPath, so if you want to put your inf files in drivers\nic\intel\pro1000Mt\etc then you must also add the full path to the OEMPnpDriversPath variable.

Generally the structure below the directory where the inf file resides must mirror what is expected by the inf file, so if the inf file expects file A to be in a folder called Bob, then file A should be in drivers\nic\Bob or drivers\nic\intel\pro1000Mt\etc\Bob.

For the 1000MT drivers as downloaded from the Dell website, it's not so complex, just stick all the files in the same directory and make sure this directory is what's in the OEMPnpDriversPath variable

HTH,
Roger

This is exactly what I did except the disable. Install a mainstream 3com Nic with the 2000 pnp drivers in your OEM folder structure for both the 10/100/1000 and the 3com. The RIS will run on the 3com and install the 2000 drivers for both Nic's. After the RIS pull the 3com and run as "normal" from the 10/100/1000. I can get 2000 to work with the onboard Nic, I just can't get it to RIS. Pain in the butt but it works. I had to do the same thing to get the RIS to work on a Compaq Deskpro model too.

Can somebody give me a link to the Hotfix for XP ( 24240_enu_i386_zip.exe ). it seems not to be widely available

I tried the first parts of the solution but i think, i'm running stuck on that hotfix.

Guys,

           Need your expertise ! !  I am using Imagecast IC3 for PC Deployment and was able to find out that my GX260 Intel Pro 1000 NIC is not supported.. Is there any other way I could have my GX260 NIC be supported aside from replacing it with another NIC..

 

Regarding Imagecast, it is possible to add network drivers to the Client Builder portion of the application.  I wasn't the one who did it here a year ago, but all you'd need to do is obtain the DOS/real-mode drivers, go into the Client Builder and when you get to the point where you select a network card click add and select the appropriate file.  That should take care of it for IC3.

I'm still stuck on the RIS/XP/Intel1000 issue.  I've read here that there's a patch, but it sounds like it applies to a Windows 2000 RIS server.  Has anyone gotten it to work with RIS on a Server 2003 system?  We can deploy Server 2003 to GX260s but not XP.  And yes, we've tried adding the drivers to the oem folder as described elsewhere.  It is as if 2003 RIS ignores those drivers and the Microsoft site has little information about RIS specific to 2003.

Thanks!

Chris