RIS - $OEM$

[dtorres]

I am a little unclear in reguards to the setup of the $OEM$ folder in a RIS deployment. I have it working to the point where the drivers get copied to the machine, but since I am using one image for 3 differnt platforms I need a way to specify multiple video/audio/nic drivers. I have created the following file structure at the same level as the i386 dir.
i386
$OEM$\$1\Drivers Nic
audio
video

How can I specify mutiple nic's, video and audio drivers. The drivers that are in the NIC folder do not install during the PnP phase of the windows install on one machine but on another they do, I am having a similar issues with the video and audio drivers.

Thank You

 

[qtin]

Since you know about $OEM$ I assume you know about this article:

http://support.microsoft.com/default.aspx?scid=kb;en-us;254078

The RIS Installations part only works w/ the flat file. If you have an image that you added software to and riprepped it you need to do the sysprep.inf stuff under "Riprep Images". MS doesn't recommend it, but you can change the registry of the machine you imaged while it is on the server - very handy when you mistype something in sysprep.ini.

 

[dtorres]

Well I have created a flat image which I added the PnP drviers for the differnt machines this flat imaging is going to get installed on. The issue I am running into is that only some of the PnP drivers are getting installed.

If three of the latop modems have different video cards, how do I seperate those drivers in the following folders:

i386
$OEM$\$1\Drivers\
video

I can't just dump all the drivers for each of the video cards into the one folder because files will get over written if they have a similar name. Once the image has been deployed to the machine all the drivers in the Drivers folder exist on the local machine. This is perfect, but I want the device drivers to ne installed during the PnP portion of the setup. Some of the devices do and some of them don't.

Am I able to break down the device folder even further for example:

i386
$OEM$\$1\Drivers\
video machine_type_1
machine_type_3
machine_type_3

I am not concerned about customizing the image because all applications will be installed via active directory using MSI packages that have been created. So I basically need to have this flat image work on all machine types. it works on one perfectly but the other two are not picking up the correct video and network drivers. I need to find a way to structure the folders so I can organize the drivers in a better fashion when PnP begins to do its thing and search the directory for the drivers needed.

 

[qtin]

I acutally have never messed around w/ the flat file setup since we like to modify a couple of things (no ICW / No Tips at startup... etc)

From what I have learned messing w/ riprep (Sorry if you realize this already) - The OEM/PnP setup looks for the .inf file for the device. This is not always in the same place as the setup.exe that you downloaded from hp.com. A good example is the audio drivers - yeah, setup.exe is in the root of the directory you just extracted but the inf for 2k/xp is .\SMAXWDM\W2K_XP. You need to point to that last little bit or it will never work. To make life easy you also need to keep the same directory structure of the extracted files.

Also, a quick way to find exactly where the .inf you need is to install the drivers on a base machine using device manager. That is the only way you are going to find the correct path to the .inf

Yes, you can break stuff down to each type of machine. I actually did mine in reverse and have:
Machine1 \audio
\video
Machine2 \audio
\video

A snip from my sysprep.ini (D510 \ VL420 are models we use):
[Unattended]
OemPnpDriversPath="Drivers\D510\Audio\SMAXWDM\W2K_XP;Drivers\D510\Video;Drivers\D510\Chipset\inf;Drivers\D510\DVI;Drivers\D510\USB2;Drivers\VL420\Chipset\Win2000;Drivers\VL420\Video\Atidrive

About the only thing you can do is keep reimaging a couple of machines and making small changes as you go. One place to check to see if your OemPnpDriversPath you changed in the .sif is working is the following registry key:
HKLM\Software\Microsoft\Windows\CurrentVersion\DevicePath. This is where all that crap gets appended to so Windows knows where to look for the .inf files. If something doesn't install during the OEM/Pnp setup isntall it again from device manager using the default settings and see what file it is looking for. You can grab a path out of that and recreate it in your driver directory structure.

 

[osceolakid]

We made a universal RIS image and if the drivers are unique we combine them in one folder. If not create two folders say like:

$OEM$\$1\Drivers\Video\Video1

Of course need to totally enumerate out in sif:

[Unattended]
OemPreinstall = yes
OemPnpDriversPath =\Drivers\NICs;\Drivers\NICs\Nic450;\Drivers\videos;\drivers\video1;

osceolakid