$oem$\$$\Setup\Scripts\setupcomplete.cmd
#1
Posted 28 December 2006 - 02:58 PM
Distribution\Operating Systems\Windows Vista\sources\$oem$\$$\Setup\Scripts
This allows me to run a cleanup.cmd that cleans things up in my vista unattend installs. You could use this for other things as well like installing applications or running .net applications. I found this spot to work better than in the unattend.xml run synchronous under specialize microsoft-windows-deployment.
The setupcomplete.cmd runs later in the unattend process.
Matt
#2
Posted 30 December 2006 - 02:49 PM
#4
Posted 02 January 2007 - 08:45 AM
I am trying to use it to install apps, but it runs the first 3 lines of the cmd and then nothing else. I don't see any errors in setupact.log, but it only runs the first 3 lines of the Setupcomplete.cmd.
#5
Posted 02 January 2007 - 09:10 AM
Here is what I did to get both to launch
test.bat & test.cmd
instead of
test.bat
test.cmd
The & ran both files.
#6
Posted 02 January 2007 - 11:59 AM
The log c:\Windows\panther\unattedGC\Setupact.log shows Setupcomplete.cmd was found and run, but no other info.
#7
Posted 03 January 2007 - 09:51 AM
I did put a exit command at the bottom of my setupcomplete.cmd
Maybe try putting all your commands (but the net use keep those in setupcomplete.cmd) in a seperate bat or cmd file and have setupcomplete.cmd call that file and see if that works.
Matt
------------------------------------------------------------------------------------------------------------------------------------------------------
Run a Custom Script after Windows Setup CompletesYou can make further customizations after Windows Setup completes by adding commands to the %WINDIR%\Setup\Scripts\SetupComplete.cmd file. This file enables you to install additional applications, run custom Windows scripts (cscript/wscript), or make other modifications to the system before a user logs on.
Note:
Commands in the Setupcomplete.cmd file are executed with local system privilege.
After Windows is installed, but before the logon screen appears, Windows Setup searches for the SetupComplete.cmd file in the %WINDIR%\Setup\Scripts\ directory.
If a SetupComplete.cmd file is found, the file is executed. Otherwise, installation continues normally. Windows Setup logs the action in the Setupact.log file.
Note:
You cannot reboot the system and resume running SetupComplete.cmd.
Setup does not verify any exit codes or error levels in the script after executing SetupComplete.cmd.
The functionality of Setupcomplete.cmd differs from the RunSynchronous and RunAsynchronous commands in that Setupcomplete.cmd runs after Windows Setup completes while the RunSynchronous and RunAsynchronous commands run during Windows Setup.
#8
Posted 03 January 2007 - 10:12 AM
fail totally to see why you'd even use this, run your app's, run cleanup.cmd, and anything else never touching this iffy junk MS threw in
done said it several times in these posts Firstlogon.cmd, as an Admin with all right's and at the end run cleanup.cmd
#9
Posted 03 January 2007 - 10:16 AM
#10
Posted 17 January 2007 - 05:32 AM
maxXPsoft, on Jan 3 2007, 10:12 AM, said:
Yes, you've said it a lot but how about explaining it?
Are you refering to an arbitary cmd file that is executed by the runonce key or something else?
#11
Posted 17 January 2007 - 08:54 AM
http://www.msfn.org/...showtopic=90863
I'll separate to leave this
This post has been edited by maxXPsoft: 17 January 2007 - 09:20 AM



Help
Back to top










