Export (0) Print
Expand All
0 out of 2 rated this helpful - Rate this topic

Using Custom Setup Scripts

Using Custom Setup Scripts

You can add custom scripts to run before or after Setup runs.

To run a script before Setup, add a PreSetup.cmd file to the same folder as SetupLauncher.exe.

To run a post-Setup script, add a PostSetup.cmd file to the same folder as Setuplauncher.exe.

The following commands are supported for pre- and post-Setup scripts:

  • Regedit.exe

Note:   /e command line switch is not supported for

  • Reg.exe
  • Factory.exe (-winpe option only)
  • Diskpart.exe
  • Notepad.exe
  • Xcopy.exe
  • Replace.exe
  • Ping.exe
  • Tracert.exe
  • IPConfig.exe

SetupLauncher.exe launches Setup with the following steps:

  1. Looks for Presetup.cmd and runs if it exists in the same folder as setuplauncher.exe.
  2. Looks for Unattended.xml (first using the command line switch, or if the switch is absent, then looks in the same folder as setuplauncher.exe) and uses it if found.
  3. Looks for DriverInstall.xml (first using the command line switch, or if the switch is absent, then looks in the same folder as setuplauncher.exe) and uses it if found.
  4. Launches Setup.exe.
  5. Once Setup.exe has terminated, looks for PostSetup.cmd in the same folder as setuplauncher.exe.
© 2006 Microsoft Corporation. All rights reserved.



Did you find this helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft. All rights reserved.