Sysprep & Vbscript problems

  • Thread starter Thread starter James
  • Start date Start date
J

James

The issue - I want to have my imaged systems to show the nic icon and
have it named. Sysprep's mini setup blows that info away.

I found a vbscript that will do this for me, and I want to run it as a
Sysprep 'additional command'. But I can't get it to work. The script
runs fine manually, or if I tell Setup Mgr to log on as Administrator
and then use the Run Once settings.

I do know that the program runs (by embedding it in a batch file and
using echo statements so that I can see the dos prompt before it goes
away), the code just doesn't work.

Commands I've tried in cmdlines.txt:

"prog.vbs"
"wscript.exe prog.vbs"
"cscript.exe prog.vbs"
"prog.bat" (call from batch file)

I realize that not all programs will work as an 'additional command'
but this is just simply reading and writing from the registry and all
values are in HKLM and aren't user specific.

I don't really want to have to do the Run Once solution as I'm not
sure how to automatically log off the Admin user afterwards.

Finally, I've seen many posts with Windows 2000 that say the $oem$
folder has to be next to the i386 folder and not a subfolder of it.
I've had it in both locations just to be safe, but does this 'bug'
still exist with Win XP?

Most frustrated.

J.
 
J.
You may need the explicit path, i.e.
"c:\windows\system32\cscript.exe c:\vblocation\prog.vbs""
-Stephan
 
Back
Top