cmdlines.txt for different machines?

[rsa]

Machine is a Dell Optiplex

I want to run some device-driver installations on unattended setup.

These come as "Setup.exe"s for Networking, Graphics, Sound etc...

So I want to include a cmdlines.txt that itself calls a batchfile to add the GUIRunOnce-Keys for the Setup.exes

Like:

REG ADD %KEY%\005 /VE /D "Intel Chipset Software Installation Utility" /f

REG ADD %KEY%\005 /V 1 /D "%systemdrive%\dell\drivers\R162291\Setup.exe -s" /f

This seems to work.

My problem:

I have a lot of other machines on my network, that may require re-installation.

So I have different .SIFs on my RIS-Server.

But to my knowledge, I can only have one cmdlines.txt -

So what would be the best way to specify batchfiles for installation of different hardware requirements?

Many Thanks,

Reinhard

[Tripredacus]

You'll have to do some research first, but there is a way I can think of off the top of my head. Think of this workflow:

call a program that launches devcon to search for a unique hardware id (DEV_NUMBER) for a device that should return a different hardware id for each build. Store that returned variable. Use a logic statement such as:

IF $var = "1234" then set $txt = "path\cmdlines.txt"

IF $var = "5678" then set $txt = "path2\cmdlines.txt"

Then your next section would be how you call your .txt file, but it would be '\\server\ & $txt'

I don't know how you would go about getting the .SIF to do this, but it is just my idea in a general sense.

[rsa]

Is there no way to determine which *.SIF has called cmdlines.txt ?

You'll have to do some research first, but there is a way I can think of off the top of my head. Think of this workflow:

call a program that launches devcon to search for a unique hardware id (DEV_NUMBER) for a device that should return a different hardware id for each build. Store that returned variable. Use a logic statement such as:

IF $var = "1234" then set $txt = "path\cmdlines.txt"

IF $var = "5678" then set $txt = "path2\cmdlines.txt"

Then your next section would be how you call your .txt file, but it would be '\\server\ & $txt'

I don't know how you would go about getting the .SIF to do this, but it is just my idea in a general sense.