Reply to thread

Message: [QUOTE="Susan Miller, post: 14006288"] I realize it's kind of tacky to respond to my own message, found more about sysprep: [URL]http://techgurulive.com/2008/09/25/how-to-install-configure-and-applying-sysprep-to-clone-a-hard-drive-windows/[/URL] It's a little old but the switches probably still work. noreboot would keep my system from rebooting before I could clone it! Sysprep.exe has command line switches you can use: /quiet Prevents confirmation dialog boxes from being displayed to the user while Sysprep runs on the master computer. This is useful for the administrator who wants to automate Sysprep by adding it to the GuiRunOnce key of the Unattend.txt file. /nosidgen Notifies Sysprep not to generate new SIDs on the reboot (note that the disk cannot be duplicated if this switch is used). This is useful for the administrator who doesn’t intend to clone the computer on which Sysprep is running or who wishes to preinstall domain controllers. /reboot Forces Sysprep to reboot the computer at completion instead of shutting down, and then start Mini-Setup. This is useful for auditing the system and verifying that Mini-Setup is operating correctly. /noreboot Prevents sysprep from shutting down after running. /pnp Forces a complete re-enumeration of all devices in the system. This will add about 5 to 10 minutes to the duration of the Mini-Setup Wizard. For Plug and Play devices, this switch is not required; it is only useful when ISA or other non-Plug and Play devices that cannot be dynamically detected exist on the target systems. /forceshutdown Forces the system to shutdown in the case where the system will not do so normally after running Sysprep.exe (with or without using the /reboot switch). This option is available only in Sysprep 1.1. [/QUOTE]

Verification