Sysprep and cmdlines.txt

Hard to read the post try using the  tag around the sysprep unattended text. My first thoughts are that one of your setup.exes (driver setups) are rebooting. Also make sure that  a folder named $oem$ is in C:\sysprep\i386 and Cmdlines.txt file is in this folder.  Also does "c:\sysprep\sysprep.exe -clean -quiet" need to be in cmdlines.txt?

Hello,

try the following:

Inside the $OEM$ Folder create a $1 Folder underneath that a DRIVERFOLDER and copy all your drivers to this subfolder. Therefor you should extract the original Setup Files.

In your sysprep.inf within the unattend section after UnattendSwith=Yes add the following line: OemPnPDriversPath=DRIVERFOLDER\Name

This line assigns the minisetup to search for drives within these folders.

Also it is necessary that the DriverSigningPolicy= must be set to Ignore.

Greets

You didn't answer a very important question that zman asked:

"Also make sure that  a folder named $oem$ is in C:\sysprep\i386 and Cmdlines.txt file is in this folder. "

Make sure you check this.

When I look in the setupact.log I can see each setup.exe I am trying to run with an Exit code of 0 which I believe mean successful but the drivers don't get installed.

So according to this, the setup.exe's are running...which means everything is probably where it should be.  So the setup.exe files are not running.  Can you pass an additional switch other than /s, say a logging switch, so you can see what is going on?  Or try running them like this:

"cmd /c c:\drivers\Chipset\setup.exe -s"
"cmd /c c:\drivers\amtheci\setup.exe -s"
"cmd /c c:\drivers\amtsol\setup.exe -s"
"cmd /c c:\drivers\Video\setup.exe -s"
"cmd /c c:\drivers\Audio\setup.exe -s"
"cmd /c c:\sysprep\sysprep.exe -clean -quiet"

Agree with rhyous, remove the -s and see if they are actually running....

Also still not sure why

"c:\sysprep\sysprep.exe -clean -quiet" is in there....

If it is rebooting before the drivers are getting installed, then call the drivers from the Sysprep.inf file, add a GuiRunOnce section like this:

GuiRunOnce

"cmd /c
Olddog\w2k3SEr2\I386\cd2\CMPNENTS\R2\SETUP2.EXE /q /a"

I would use the OemPnpDriversPath section for the plug and play drivers and the GuiRunOnce section non plug and play.

OemPnpDriversPath=dell\Broadcom;dell\Intel;dell\MRAID;dell\PERC4IM;dell\PERC5;dell\SAS5

Hmmm, that is weird I thought GuiRunOnce only ran after the setup and when the user logs in???? Anywho, apparently there van be issues with GuiRunOnce:

• If an application requires a Windows Explorer shell to install, the GuiRunOnce section will not work because the shell is not loaded when the Run and RunOnce commands are carried out.

• Applications that use the same type of installation mechanism might not run properly if a /wait command is not used.  Exes that spawn other processes.

I would put all those apps you are running in a batch file and just run the batch file to see if that is the problem.

Start /wait <path>\<Setup> <command line parameters>

Start /wait <path>\<Setup> <command line parameters>

You could move the drivers to  guirunonce if they are not imperative to the system booting correctly or not needed until after the first login (synaptics pointer drivers).

I didn't see mention of this in the thread so I thought I would mention it.

When using the $OEM$ folder and it's subfolders to copy

files to the target PC, you have to include the OemPreinstall=Yes

line in the unattend.txt file under the section.

I think you should:

1) use programs like driverguide toolkit to extract drivers from setup.exe.

2) use ldprep to let minisetup know where drivers are stored.

HTH

Jary