cmdlines.txt in a sysprep image

[thammerling]

Hi everyone, i'm having a dickens of a time getting cmdlines.txt to work.

Let me start by saying that I am working on a master image for the school district I work for. We run novell servers, so we use zenimg to create and push down images. I made a nice clean image, and sysprep -resealed it. I then used zenimg to push the image up to our storage server. I then realized that I would want to use cmdlines.txt to do some stuff. I used the zenworks image explorer to add the cmdlines.txt file and to update the sysprep.inf with the appropriate InstallFilesPath. Everything looks ok to me, but it isn't working at all (it doesnt even appear to be touching the cmdlines.txt!)

Please see the attached pic for a rundown of the file structure... Notice the two $oem$ folders. I had read conflicting reports of where your $oem$ folder should be, so i made two of them, both containing the same files.

My cmdlines.txt is as follows

[COMMANDS]

"DriverInstall.bat"

DriverInstall.bat is located at the root of both $oem$ folders and contains the following

echo "omg! we are in cmdlines.txt - The one located at *the path it's at*!!!"

c:\windows\system32\cscript.exe c:\sysprep\DriverInstalls.vbs

pause

and then the DriverInstalls.vbs is just a vbs file to do some junk, not really important since I never even hit my cmdlines.txt.

oh, and my sysprep.inf is as follows

;SetupMgrTag

[unattended]

OemSkipEula=Yes

InstallFilesPath=C:\sysprep\i386

UpdateInstalledDrivers=1

DriverSigningPolicy=Ignore

TargetPath=\WINDOWS

OemPnpDriversPath=drivers\audio;drivers\chipse;drivers\modem;drivers\nic;drivers\other;drivers\video;drivers\wlan

OemPreinstall=Yes

[GuiUnattended]

AdminPassword=myencryptedadminpassword

EncryptedAdminPassword=Yes

OEMSkipRegional=1

TimeZone=20

OemSkipWelcome=1

[userData]

ProductKey=myproductkey

FullName="admin"

OrgName="MASD"

ComputerName=*

[setupMgr]

DistFolder=C:\sysprep\i386

DistShare=windist

[Display]

BitsPerPel=32

Xresolution=1024

YResolution=768

[identification]

JoinWorkgroup=MASD

[Networking]

InstallDefaultComponents=Yes

[sysprepMassStorage]

*a whole TON of storage devices, which i have removed to make the post more readable*

So my question is, do i need to start from scratch and put in all this stuff and THEN reseal the box? (i know that some values are read from sysprep.inf and written into the registry when a machine is resealed... any help would be greatly appreciated!

Taylor

[thammerling]

a quick update, while I am waiting to hear back from the ppl of this forum, i'm starting from scratch so that i have my cmdlines.txt in place when i reseal the box...

T

[thammerling]

Starting from scratch and making sure the cmdlines.txt was in there didn't help a scootch

Still hoping someone can save me

T

[bj-kaiser]

you didnt say, where you put your cmdlines.txt. Maybe in a wrong path?

[thammerling]

I put my cmdlines.txt and my DriverInstall.bat in BOTH of the $oem$ folders.

[bj-kaiser]

the documentation I just read says for sysprep it has to be in the sysprep folder.

[thammerling]

can you please post a link to that documentation? I have always read it has to be in the $oem$ folder

[thammerling]

http://support.microsoft.com/kb/238955

that is one of the pieces of documentation I have read.

[bj-kaiser]

http://support.microsoft.com/kb/238955

that is one of the pieces of documentation I have read.

*d'oh*

didn't ask what version of Windows you are using. I supposed latest stable version, so I looked in the Windows Deployment Tools Reference for XP SP2.

So you are using Windows 2000 I suppose, after looking at the products that article applies to.

[thammerling]

bugger, my bad, i'm a tad slow. I am in fact using xp Sp2. BJ, can you link to the documentation for xp sp2 commandlines.txt? (seeing as how i'm a spaz and read the documentation for 2k)

T

[bj-kaiser]

http://www.microsoft.com/downloads/details...9b-beda3080e0f6

[thammerling]

hrm... I have that deploy cab, and when i look in ref.chm I find this

To run Cmdlines.txt during Mini-Setup

In the distribution folder, create:

%SYSTEMDRIVE%\Sysprep\i386\$OEM$

Copy Cmdlines.txt to the %SYSTEMDRIVE%\Sysprep\i386\$OEM$ folder.

In Sysprep.inf, add:

[unattended]

InstallFilesPath = C:\Sysprep\i386

Run Sysprep.

Either way, I have tried it with the cmdlines.txt in both $oem$'s and at the root of the sysprep folder, and none have worked.

I'm stumped!

I found this how-to, and it seems like i'm doing everything right... i'm boggled!

http://www.geocities.com/kilian0072002/sysprep/sysprep.html