Microsoft has targetted the System Preparation Tool (sysprep.exe) specifically
for organizations that use disk cloning for mass deployments. Sysprep strips the
SID from the PC being imaged and installs a miniature version of Windows Setup.
You then use the imaging software of your choice to clone the “reference
machine”.
When you start a new PC using the new image, mini-setup runs allowing you to
specify network info, languages and locales, display settings, … The
mini-setup can be scripted by having an answer file, sysprep.inf, and thus the
imaging process can be totally hands free.
The target PCs must use the same HAL, NTOSKRNL.EXE, and boot device.
The sysprep support files must be in the C:\SYSPREP folder of the image. The
required sysprep files, sysprep.exe and setupcl.exe, can be copied from the
Deploy folder on the W2K installation CD. Of course to have a fully automated
installation, you need to create a customized sysprep.inf file. Run setupmgr.exe to select the options needed for your
deployment. The answer file must be named sysprep.inf and must exist in the
C:\SYSPREP folder in order to automate the mini-setup process on the clone. The
C:\SYSPREP folder will be removed as part of the installation process when the
image is generated.
sysprep has four primary parms:
- /quiet : forces mini-setup to run in silent mode
quiet means no user
interaction. used with an answer file
- /nosidgen : mini-setup runs, but SID is not changed
use /nosidgen if
your cloning product handles creating unique SIDs
- /noreboot : computer will not automatically reboot
not sure why you
would use this since the point is an automated installation
- /pnp : this forces Plug and Play device detection
not useful if hardware
is not compatible. Otherwise, it makes for smoother installation.
You run sysprep and then create the clone image. You
are now ready to mass deploy your workstations.
Related Tips:
- Automating Client Installation and Upgrade
- Q192855: System Preparation Tool Does Not Save Desktop Preferences
- Q214679: Sysprep Does Not Rename Accounts Containing the Computer
Name
- Q216680: How to Identify an Installation Created with the Sysprep
Tool
- Q216915: Using the System Preparation Tool on Dissimilar Computers
- Q216937: Windows 2000 System Preparation Tool and Answer File
Usage
- Q226315: Computer Account Organizational Unit May Be Specified
Using the Unattend.txt Utility
- Q238955: How to Use Cmdlines.txt File During Sysprep.exe Setup
Wizard
- Q240126: Best Practices for Using Sysprep with NTFS Volumes
- Q243072: SourcePath Value Set Back to the First CD-ROM Drive
Letter with Sysprep.exe
- Q244836: Sysprep Resets Custom Connectoid Names in My Network
Places
- Q248257: Program Installation Problems on Sysprep or Riprep
Installed Systems
- Q247952: The InstallDefaultComponents Key in the Networking
Section Always Defaults to Yes
- Q251042: Sysprep Does Not Change ACLs on Registry Keys
- Q251241: How to Use the System Preparation Tool to Prepare
Computers for Shipping
- Q250498: Setup Manager Incorrectly Writes the OEMPnpDriversPath
Line in the Sysprep.inf File
- Q253340: Non-Present SCSI Devices Appear in Device Manager When
You Are Using Sysprep Version 1.1
- Q254078: How to Add OEM Plug and Play Drivers to Windows
Installations
- Q256204: Unsigned Drivers Not Installed During Sysprep Mini-Wizard
Without “-pnp” Switch
- Q259144: Computer May Hang After Using Sysprep on ACPI-Enabled
Computer
- Q257813: Using Sysprep May Result in “Stop 0x7b (Inaccessible Boot
Device)” on Some Computers
- Q259303: FAT32 to NTFS File System Conversion Does Not Work When
Using Sysprep
- Q264942: Extended Keys on a USB Keyboard May Not Function
Correctly During Mini-Setup After Using Sysprep
- Q228908: Requirements for Imaging Clients with Riprep.exe