Windows.system tool .sysprep.exe

This document describes how to use the system preparation tool (sysprep.exe) to perform disk replication. You can create an image for the Windows 2000 installation and installed programs and data through the cloning process, and deploy a large number of identical installations throughout the organization.There is a problem with the installation of copying Windows 2000, that is, each clone computer has the same security identifier (SID) and computer name. This may prevent the clone computer from running properly in the working group or domain (that is, the same host name or IP address may appear in the same LAN ).To solve this problem, the administrator can use the system preparation tool (sysprep.exe) to delete computer-specific configuration settings, such as the computer name and Sid. Then, the images can be securely reused and installed on other computers.

To install a Windows 2000 System for cloning, perform the following steps:

1.	Install Windows 2000 on the instance computer. You can install windows in interactive mode, or use the response file to make the process automatically.
2.	Restart the computer and log on as an administrator.
3.	Install and customize all programs to be deployed with Windows 2000.
4.	Add a local user account, add a domain, or perform these two operations.
5.	Check the configuration to verify that the computer contains all required components, settings, and data.
6.	Click Start, click Run, Type CMD in the open box, and press Enter.
7.	At the command prompt, type CD/, press enter, type MD sysprep, and then press enter again.
8.	Insert the Windows 2000 Professional CD-ROM into a CD or DVD drive and type expandCD drive letter:/System/tools/deploy. Cab-F: * C:/sysprep, and press Enter. Note that this command assumes that you created the sysprep folder on drive C in step 1. If you place the folder on another drive, change the command.
9.	At the command prompt, type CD/sysprep and press Enter.
10.	To run sysprep.exe, type sysprep/ParametersAnd press Enter. For more information, see the parameter sysprep.exe in this document.
11.	Shut down the computer, remove the hard disk from the computer, and then clone it using a third-party disk image. Note that-RebootWhen sysprep.exe is enabled, the computer is automatically disabled.

When you start Windows 2000 from a cloned disk or the original disk, the following events occur:

1.	Setupcl.exe starts and generates a new Sid.
2.	The minimal installer Wizard starts to customize a new computer. If you do not provide the sysprep. inf response file, the wizard runs interactively.

Back to Top

To create a sysprep. inf response file, type setupmgr.exe at the command prompt and press Enter. Follow the instructions on the screen to complete the wizard operation. You can also use a text editor to create a response file or modify an existing response file.

For more information, view the unattend.doc file in the deploy. cab file in the support/tools folder on the Windows 2000 CD-ROM, or visit the following Microsoft Web site:

Http://www.microsoft.com/windows2000/techinfo/reskit/en-us/deploy/dggb_aut_cwrh.asp (http://www.microsoft.com/windows2000/techinfo/reskit/en-us/deploy/dggb_aut_cwrh.asp)

Back to Top

You must meet the following conditions to run sysprep.exe and use the sysprep. inf response file:

•	The sysprep.exeappssetupcl.exe and sysprep. INF files must be in the sysprep folder. The sysprep. inf file can be on a floppy disk, but the file name must still be sysprep. INF. When the minimum installer is started, it checks whether the sysprep. inf file exists in the floppy drive. If the sysprep. inf file exists, it copies the file as $ winnt $. inf to the % WINDIR %/system32 folder. Any existing file with this name will be overwritten.
•	The sysprep folder must be located in the root folder of the volume where the WINNT folder is located.
•	The file name must be sysprep. INF. If the file name is not sysprep. inf or is located elsewhere, the minimal installer ignores it and runs in interactive mode. Note that if the required response file is missing, the minimum installer returns to the interactive mode to collect the missing information.

Back to Top

Sysprep.exe switches sysprep.exe to the following switch:

•	/Quiet-Cancels the confirmation dialog box message that is usually displayed on the screen.
•	/Nosidgen-Notify setupcl.exe not to generate a new Sid when restarting, and then run the minimal installer wizard.
•	/Reboot-Automatically restart the computer.
•	/PNP-Force the minimum installer to re-run the complete PNP device enumeration next time the computer is started. In this mode, the minimum installation time is increased and can be used in the sysprep. inf file.Oempnpdriverspath.

Before the calculation machine is closed, sysprep.exe executes the following tasks:

•	SetClonetagValue to indicate the run date and time of sysprep.exeHKEY_LOCAL_MACHINE/system/setup.
•	SetCmdlineAdd valueHKEY_LOCAL_MACHINE/system/setup. This "setup-newsetup-mini" value will start the minimum installer when the computer restarts, and thenSystemsetupinprogressThe value is changed0x1.
•	Make sure that the setupcl.exe file is in the % SystemRoot %/system32 folder. If the file does not exist, search for the file in the local folder and copy it to the % SystemRoot %/system32 folder. If the file cannot be found, sysprep.exe displays an error message and exits.
•	InHKEY_LOCAL_MACHINE/system/CurrentControlSet/control/Session Manager-Setupexecute: reg_mulit_sz: setupcl.exePlace a command in
•	The [sysprepmassstorage] section of the sysprep. inf file is processed to determine which drivers must be enabled in the system registry.
•	Sysprep. inf is copied to the WINNT/system32/$ winnt $. inf file. This file can be found when other components need any information in the sysprep. inf file. For example, if you want to promote your computer to a domain controller, You can include the [dcinstall] section.

For additional information about upgrading and downgrading Windows 2000 Domain controller without human involvement, click the following article number to view the article in the Microsoft Knowledge Base: 223757 (http://support.microsoft.com/kb/223757/EN-US) unattended promotion and demotion of Windows 2000 Domain Controllers sysprep folders are deleted when the minimum installer ends. Before the calculation machine is closed, sysprep.exe can execute other tasks. To enable sysprep to use installed components, the minioc. inf file is placed in the % WINDIR %/INF folder. This file will reference the dynamic link library (DLL) of a specific component, which can execute necessary tasks to prepare components for replication. When sysprep.exe is running, it opens the % WINDIR %/INF/miniproc. inf file and processes the [sysprepbeforeexecute] section. When the clone computer starts, the minimal installer opens the minioc. inf file and processes the [sysprepinitexecute] section.

The sysprep folder may also contain the provider. inf file. Third-party component providers use this file to ensure that sysprep.exe can be used to clone their components.

Back to Top

Format of the sysprep. inf file. The format of the sysprep. inf file is the same as that of the unattend.txt file used to automate Windows 2000 installation. However, this file only supports the following sections and parameters:

[Unattended]

•	Oemskipeula
•	Oempnpdriverspath
•	Installfilespath-This is a pointer that points to the installation source of the additional driver not provided by the Windows 2000 CD-ROM. This pointer is useful if the "region Settings" parameter is specified.
•	Extendoempartition
•	Keeppagefile-Indicates that sysprep.exe retains the current paging file or regenerate a new paging file.

[Oem_ads]• All items (logo and background)

[Guiunattended]

•	Adminpassword
•	Autologon
•	Timezone
•	Oemduplicatorstring-This is a response file parameter. Its value is a string that contains the description of the replication tool used and any other information that the OEM or administrator wants to store in the registry. The value can contain a maximum of 255 characters and is stored inHKEY_LOCAL_MACHINE/system/Setup/oemduplicatorstringMedium
•	Autologonaccountcreation
•	Autologoncount
•	Oemskipregional
•	Oemskipwelcome

[Userdata]All items supported

[Licensefileprintdata]• All items supported

[Guirunonce]

[Display]• All items supported

[Regionalsettings]• All items are supported if files are provided on the computer's hard disk. If region settings are specified, you can useInstallfilespathPoint to the location of the file.

[Networking]• Only installation of default components is supported. This section only exists in the sysprep. inf file. Please note that,InstalldefacomponcomponentsThe value does not work. It is always assumed to be "yes ".

[Identification]• All items supported

[Netclients]• Supports all items of the Microsoft network client service and the Netware Client Service.

[Tapilocation]• All items are supported. These values are valid only when the computer has a modem. For other references, see Microsoft Windows 2000 OEM preinstallation kit opk users guide (Microsoft Windows 2000 OEM preinstallation kit opk User Guide).