Tuesday, January 18, 2011

Windows PE autorun scripts

I've set up a Windows Preinstallation Environment on a USB Thumb Drive (version from the latest iteration of the Windows Automated Install Kit/WAIK), and I'm working on getting a deployment environment set up.

However, we'd like to make it so our Level 1 technicians can use the deployment system, and because of this, I've written several batch files to minimize the amount of command line work the technicians have to do.

Is there a way I can get these scripts to autorun after the PE environment has finished initializing?

  • Use the Windows Automated Installation Kit to create a custom WinPE image with a Winpeshl.ini answer file (see http://technet.microsoft.com/en-us/library/cc766156(WS.10).aspx)

    From newmanth
  • Generally I don't do autorun scripts for fear that someone would accidentally wipe their machine. The solution I found worked well was to provide a single batch file with a simple name, and tell them to type that at the command-prompt and press return. If you have multiple images for different makes/models you could call it a name based on the made model, e.g. type "dellgx280" to re-image a Dell GX280.

    You can however modify the startnet.cmd file (WinPE's equivalent of autoexec.bat) to do it if you really want. That just a case of mounting the PE image r/w, locating the file (at %systemroot%\system32), editing it, then commiting and unmounting.

    tearman : This doesn't mess with the disks, it just sets up the network configuration and launches the installer. Preferably the partitioning will be taken care of manually for both the reason you describe and differentiating systems.
    From mh
  • I am having a terrible time finding the startnet.cmd file in %systemroot%\system32. I have searched it and looks like it doesn't exist. Does anybody have any suggestions? ~ALM

  • You can find the start net.cmd file within the boot.wim file. You will need to mount the image using the command imageX /mountrw c:\boot.wim 1 c:\winmount

    From Damion

0 comments:

Post a Comment