Automatically deploy Windows 2000 using Sysprep
Operating system white paper
Summary
This document discusses how to use your simple utility sysprep on your hard disk to copy and customize systems to quickly deploy Microsoft® Windows® 2000 operating systems on multiple computers with compatible configuration. This white paper takes into account the changes in this utility version 1.1, which is an update to the operating system CD version 1.0.
introduction
The Microsoft® Windows® 2000 System Preparation (Sysprep) Utility is located under the /Support/Tools/Deploy.cab folder of the Windows 2000 operating system CD. This document discusses how to prepare and use Sysprep when deploying a Windows 2000 operating system on multiple computers with compatible configuration. (The next discussion takes into account the changes in this utility version 1.1, which is updated 1.0 version 1.0 on the operating system CD.
Note that the recommended version of Sysprep and the current version (released in April 2000) can be found in the Microsoft TechNet. Click here to access the Access Sysprep version 1.1.
Sysprep for Windows 2000 is a simple utility that is used to prepare (or clone) and custom systems on your hard disk. It self-itself does not perform a true main image replication on the target computer (implementing this dedicated third-party utility), but it ensures uniqueness of the security identifier (SID) on each target computer. Sysprep Calls the Mini-Setup Wizard that customizes the copy image via computer specific information (such as user name, computer name, time zone, and domain member).
Once the workstation or server disk is ready, the administrator can easily deploy by copying the disk on each computer in the unit, reducing deployment cost, thereby reducing overall cost cost (TCO). Combine Sysprep with Microsoft management technologies such as Systems Management Server or IntelliMirrorTM, companies benefit from many aspects: stronger disaster recovery capabilities, easier operating systems and application management, and improved hardware and software inventory life cycle.
This document assumes that you are familiar with the installation of Windows 2000 Professional and Windows 2000 Server. If you plan to use the Sysprep to automatically deploy the server, it is recommended to first learn how to make a Windows 2000 Server server a domain controller (implemented by calling the Active DirectoryTM Installation Wizard), as well as knowledge about Windows 2000 SID.
Disk replication
Enterprise customers deployed for Windows-based thousands of computers with similar hardware configurations in the same type of computing environment hopes to customize a computer, and then copy their hard drives (or "Image") to other computers of the company. Similarly, network administrators want to quickly replace the computer in a time-critical environment when necessary.
System administrators in units typically pre-install customer computers, or physically access each client to install the operating system, and sysprep is designed to reduce the cost of such tasks. It enables administrators (or third-party integrators) to copy a single workstation to multiple clients, which greatly saves management time and resources. Administrators only need to make a set of assumptions about computer settings, thereby reducing the overhead of standard Windows installation.
Demand and prerequisites
demand
To use sysprep as part of the disk replication process, you must meet the following needs:
The host computer and target computer must have a compatible hardware abstraction layer (HAL), that is, HAL supported on each computer must belong to the same general series. For example, advanced configuration and power interface (ACPI) multiprocessor HAL is not compatible with non-ACPI multiprocessor HAL. (To determine the type of HAL in the computer running Windows 2000, open the device manager, then expand your computer object.) If you use Sysprep 1.0, the mass storage controller on the host computer must be the same as the controller on the target computer. The tool's version 1.1 addresses this demand problem: Before creating a master image, the administrator must first identify different massive storage controllers installed on each target computer in the sysprep.inf file (see below). This allows SysPrep to pre-demonstrate the necessary driver information so that Windows 2000 can load the correct driver when booting on a computer with a predefined mass storage controller. This method is suitable for the following scenarios: IDE to IDE. Creating a main image is different from the IDE controller used by the target computer. For example, the host computer uses the PCI IDE controller, and the target computer uses the Intel IDE controller. IDE to SCSI. Creating a main image using the IDE controller, the target computer uses the SCSI controller. For example, the host computer uses the PCI IDE controller, and some target computers are started from the SCSI controller (such as Adaptec 7800). SCSI to SCSI. Creating a home image is different from the SCSI controller used by the target computer. For example, the host computer uses the Adaptec 7800 controller, and some target computers use QLogic controllers. SCSI to IDE. Creating a main image using the SCSI controller, the target computer uses the IDE controller. For example, the host computer uses the Adaptec 7800 controller, and some target computers are started from the IDE controller. Plug and play devices, such as modems, sound cards, network cards, graphics, etc., do not have to be exactly identical, but they should be registered in the computer and they should be available. (To learn more, see the "Pre-installed Plug and Play Device" section below.) Required third-party software or disk replication hardware device. These products create a binary image of a computer hard disk, which copies the image to another hard drive, or stores the image into a file of a separate disk. (To learn which companies provide Windows 2000 deployment tools, especially disk image software, please visit http://www.microsoft.com/windows2000/guide/server/partners/deploymentisvs.asp.) Target computer hard drive must be The main computer hard drive is the same. If the target computer's hard drive is large, the partition size on the target hard disk must be the same as the host computer. However, you can use the extendoemPartition item in the Sysprep.inf file (see below) to extend the main partition that is formatted by the Windows NT® File System (NTFS). You must have a license to be copied to the operating system and application copy of the computer on multiple computers. Using sysprep does not grant any permissions, copy the software without the installed software vendor license.
Note If the deployment environment does not meet these needs (for example, HAL is not compatible), you can still benefit from the automatic deployment method for Windows 2000, see http://www.microsoft.com/windows2000/library/Resources/reskit/ Windows 2000 Deployment Planning Guide (Windows 2000 Deployment Planning Guide) in DPG. prerequisites
Before starting the disk replication process, you should prepare a primary computer, install and configure the software to deploy on the target computer in the same way. You should also have a good understanding of the computing environment and its impact on hardware and software. E.g:
Identify the application that the configuration file is not recognized. The application identified by the configuration file creates the required application settings in public positions to enable all login users to access them. The profile does not identify applications that need to be installed under a single user profile. Determine the installation method that is best suited for your environment: New installation (or "clean installation"), pre-installed or upgrade. New installation is usually "refresh" existing computer, install a new operating system on a clean hard drive. The operating system is installed in the pre-installation refers to the computer. The main choice for existing computers is to perform an upgrade, existing operating system (such as Windows 95 or Windows NT Workstation) Upgrade under SITU without having to reformat the hard drive. Understand the use of software in different locations, such as branches and around the world. Understand how the portboard uses how to affect the software location and installation.
Moreover, you should learn about basic deployment issues and policies such as hardware compatibility and basic input / output system (BIOS) updates, we don't detail this information here.
Note For more information on hardware and software compatibility issues, please visit http://www.microsoft.com/windows2000/upgrade/default.asp.
Finally, as mentioned earlier, ensuring that all softwares including the operating system, follow the license agreements signed with the software manufacturer. The strategies described in this document do not grant you any rights, and copy any software without the provisions of the Software Protocol.
Computer replication process overview
Five basic steps in disk replication processes:
Install Windows 2000. Install Windows 2000 Professional or Server on a computer that is similar to the target computer hardware. For more information on hardware requirements, see the "Demand and Prerequisites" section above. When establishing a computer, don't join the domain, and keep the local Administrator password is empty (if the password does not leave, you cannot change the password when you specify the Administrator password when the password is left. At the same time, you should also ensure that the main image is created on a private computer, not on a production computer. Configure a computer. Create a local user account with Administrator privileges and log in as a user to install and customize applications, such as Office 2000, business-specific applications, and other public applications or settings from all workstations created from the image. For the server, you may want to install Internet Information Services (IIS) or other standard Windows 2000 services (however, do not run the Active Directory Installation Wizard to make your computer a domain controller). After customizing the system, log out of the user and log in with the Administrator identity. The user profile is then copied under the Default Users folder. Verify the image. Run your computer audit according to your conditions to verify that the image configuration is correct. After the review is complete, delete resident information, such as all mapping drives, continuous connection, event logs, and history, then copy the main workstation. Prepare a computer for copying. It is sure that the computer is in the desired state and configuration, that is, the computer is ready to copy. Run the sysprep utility (optional to run sysprep.inf) to prepare your computer to copy. After Sysprep is complete, the computer will automatically shut down or indicate "Now safely shutdown". For more information on sysprep.inf, see the Sysprep Components section below. copy. At this point, the hard disk of the host computer has been triggered to run a plug-and-play device detection, create a new SID, and run the Minimum Install Wizard when the system is started next time. The system is now ready to copy or images. When any copying hard drive created from the hard disk or the image is started, the replication process will be completed. Refer to Appendix A: Disk replication process diagram.
Sysprep components
Windows 2000 Sysprep Utility consists of three files:
Sysprep.exe, command line tool, prepare hard drives on the host computer for copying. Setupcl.exe, regenerates a new SID tool for your computer. (This tool cannot be called directly, and must reside under the same folder as sysprep.exe.) Sysprep.inf, optionally answering files, used to automatically run the "minimum installation" process of the image computer.
Sysprep.exe and setupcl.exe are required files that are independent of each other. You can find these two files in the deploy.cab file on the Windows 2000 CD, and their latest version can download http://www.microsoft.com/windows2000/downloads/deployment/system from the Microsoft website. (The following "Example 1: Establish a Standard Department Workstation" and "Example 2: Deploy Remote Office Server" section provides examples of sysprep.inf response files.) Sysprep and setupcl
Once the application and settings are configured for the primary computer, you can run sysprep after you can use it, you can run sysprep, and sysprep is a simple program that performs the following tasks:
Configuration The Mount Starts the Minimum Install Wizard when the next restart is restarted, which includes re-enumerating all plug-and-play devices. Copy setupcl.exe to% systemroot% / system32 and schedule SETUPCL to run next time. Pretreatment of each part of Sysprep.inf before the computer is turned off. (For example, if you use sysprep 1.1 and you have specified different massive storage controllers in the SyspRepMassStorage section of your reply file, the part is processed at this time.) Putting a shutdown command to Windows.
Sysprep is complete and computer shutdown, that is, the hard disk is ready to copy. You can copy the disk with image hardware or software.
Note To find out which third-party vendors provide Windows 2000 deployment tools (including disk image software), visit http://www.microsoft.com/windows2000/guide/server/partners/dePloymentISVS.ASP.
When the primary computer starts or from any drive replicated from the host computer, the setupcl runs will be run, starting to detect the plug and playing device, and launch the Minimum Installation Wizard. "Minimum Install Wizard" looks for the sysprep.inf file to provide the information necessary to provide. If you find sysprep.inf on the% window / sysprep or master disk, the Minimum Install Wizard will grant the information contained in the syntax and determine if additional information is required to collect additional information from the computer. The computer then restarts, at which time the computer is ready, you can use it. The settings on the target computer will be based on the replicated image, and all changes made during the minimum installation process are applied.
Note If the host computer is connected to the domain, the computer will be deleted from the domain when running sysprep.exe, and no prompt does not appear. When you perform the Minimum Install Wizard, you can connect your computer (reconnect) to the field using sysprep.inf.
Sysprep syntax
This is the syntax of sysprep:
Sysprep [/ nosidgen | / quiet | / reboot | / pnp | / forceshutdown]
This tool is ready to copy the computer and then close the computer. You can use the following command line option to start Sysprep:
/ Quiet When Sysprep is running on the host computer, avoid displaying a confirmation dialog to the user. Some administrators add sysprep to the GUIRUNCE item for the UNATtend.txt file, I hope that Sysprep is automatically running, which is useful to them. / NOSIDGEN Notification Sysprep Do not regenerate new SID when restarting (note, you cannot copy the disk when you do not use this switch). Some administrators do not intend to clone the computer running sysprep, or want to preload domain controllers, which is useful to them. / Reboot Force Sysprep restarts the computer (not shutdown) while complete, then start "minimum installation". This is useful when reviewing the system and verifying that "minimum installation" is running correctly. / PNP enforces all devices in the system. This will extend the runtime of the Minimum Install Wizard to be 5 to 10 minutes. For plug and playing devices, the switch is not required; when there is an ISA or other non-plug-of-play device that cannot be dynamically detected on the target system, the switch is useful. / forceshutdown does not work properly when the system is running sysprep.exe (using or without / reboot switch). This option is only available in Sysprep 1.1. The Sysprep and SetupCL files can be located on the floppy disk, or under the% systemDrive% / sysprep folder on the hard disk, the folder and its content are automatically deleted after completing SYSPREP.
Sysprep.inf
As part of the establishment and deployment of standard images, you may need to customize a small amount of settings and parameters for a single target computer. For example, each Windows 2000-based computer requires a unique computer name. "Minimum Installation Wizard" usually prompts users to retain information. However, in many cases, if you know the necessary information and do not want to prompt users to enter this information, you can use an optional answer file sysprep.inf to implement automatic input. Using the sysprep.inf file, you can let the Minimal Installation Wizard prompt some information or create a fully automated installation.
To use sysprep.inf, there are two basic conditions:
It must be on the% systemDrive% / sysprep folder of the local hard drive with Sysprep and SetupCl, or on the main floppy disk. Do not use file names other than sysprep.inf.
Note You can use the tool "Install Manager" on the Windows 2000 CD to help create the sysprep.inf file. For more information on "Installation Manager", see the related content of Chapter 13 and Chapter 25 in Deployment Planning Guide.
The INF syntax used by the sysprep.inf file is the same as the SETUP Answer Unattend.txt, and most of the value used by Unattend.txt. In particular, sysprep.inf consists of a subset of the "Windows 2000 Unattended Installation Mode" parameter. To see all parameter lists, see Windows 2000 Guide to Unattended Setup in the deploy.cab file on the DEPLOY.CAB file on Windows 2000 CD. Note that only two parameters for sysprep.inf are: KeEppageFile and InstallFileSPath.
Sysprep.inf Answer file example includes the following parameters:
[GuiUnattended] TimeZone = 20OemSkipWelcome = 1 [UserData] FullName = "
Minimum installation wizard
The "Minimum Installation Wizard" started when the computer started from the replication disk. It collects all information required for newly replicated target computers. If you do not use sysprep.inf, "Minimum Install Wizard" displays the following screen:
Welcome to the Microsoft License Agreement Product ID Region Set User Name and Corporate Computer Name and Administrator Password TAPI Settings (when there is a modem when adapted to have modem) Network configuration Add to Working Group or Domain (Suitable for Workstation) Server License (Suitable for Server) /Restart
To bypass these pages, let Sysprep fully install it, at least specify the following: in sysprep.inf:
Minimal installation dialog box prompts bypass the keys and values required dialog welcome [GuiUnattended] OEMSkipWelcome = 1 Microsoft License Agreement [Unattended] OemSkipEula = Yes locale [GuiUnattended] OemSkipRegional = Yes user name and company [UserData] FullName =
The Minimum Installation Wizard is a very powerful and flexible tool for customizing the Sysprep installation. By specifying options in sysprep.inf, you can further configure and customize the sysprep image. For example, you can run the command when the user logs in after the "Minimal Installation Wizard" is logged in.
Note To view all Options list, see Windows 2000 Guide to Unattended Setup on the deploy.cab file on the Windows 2000 CD.
Pre-installed plug-and-play device
By default, the hardware driver is located in the Drivers.cab file of the Windows 2000 CD. When the Windows 2000-based computer is started, it automatically detects the plug-and-play device and exports any new hardware drivers that detected from the file. Add a new driver to the Sysprep installation
When you create a deployment image, if you do not include a plug-and-play device on the Windows 2000 CD, you need to specify the standby path in the OEMPNPDRIVERSPATH item of the Sysprep.inf Answer Unattended section. The folder named in this path should not only contain drivers, but also include directory and INF files. If the computer that the computer detected during the startup process is not in the default drivers.cab file, it will check the location specified in the OEMPNPDRIVERSPATH item.
The process of installing the driver to the Sysprep includes three basic steps:
Create a file structure that accommodates a new drive under the volume of the% WINDIR% folder. Copy the new drive into the corresponding subfolder. Add an OEMPNPDRIVERSPATH =
If after the "Minimum Install Wizard" is complete, you do not want the new driver to continue to remain on the volume, you can place the folder structure created in the front step in the sysprep folder. You need to adjust the OEMPNPDRIVERSPATH item accordingly. Sysprep folders (and all the subfolders) will automatically remove after the installation is complete.
Save the sysprep.inf file under the sysprep folder and run sysprep.exe. Any plug-and-play device (including using an OEM driver .INF file) is automatically installed on the Target computer during the Minimum Installation process. Note that you don't have to specify the / PNP command line switch unless there is an old (ISA) device on the target computer. If you use the / PNP command line switch, you will completely perform the plug and play re-enumeration of all devices, which will extend the SYSPREP minimum installation wizard for 5-10 minutes. In addition, when using the Sysprep version 1.1 Specify an additional massive storage controller, the / PNP command line switch can cause some additional hard disk controllers to appear in the Device Manager (this is only the negative impact of the display, no Impact system).
If the new driver does not have a digital signature, the Minimum Install Wizard will post the installation of the device until the administrator logs in to the computer. This is called the client and the server-side installation, which occurs during the "minimum installation".
Note To add a third-party mass storage driver to the Sysprep image used to start your computer, you need the sysprep version 1.1.
Extended Sysprep
The initial purpose created by Sysprep is designed to speed up the copy speed of the workstation, and it has other uses in Windows 2000, as described below.
Call the minimum installation wizard as a configuration tool
The Minimum Installation Wizard is responsible for collecting configuration information of the workstation and performs the necessary customization at the end of the installation process. However, it can also be called by sysprep, which is used as a separate tool when the computer has been almost fully established.
To avoid users who have to complete the entire installation process for custom computers, run sysprep to re-enable the Minimum Installation Wizard. Users can configure the computer to meet the needs of the computer simply answers. For example, if the user needs to join the domain, simply provide computer name or telephone information. In addition, if you need to reconfigure your computer, you can avoid reconstruction by running the Minimum Installation Wizard again. / NOSIDGEN Switch Avoid related steps in sysprep Creating a new computer SID. Copy server and creating domain controller
An important feature of Windows 2000 Sysprep is to copy the member server. The server's replication process is the same as the workstation replication process. Install the operating system, configure and install all applications or services, and then run Sysprep on the host computer.
The member server can be replicated because of the configuration information as a domain controller, or the installed service relies on configuration information in Active Directory, and then runs DCPROMO on the target computer to completely automatically deploy new domain controllers. (DCPROMO calls the Active Directory Installation Wizard, which is used to create domain controllers on a computer running Windows 2000 Server, Advanced Server, or DataCenter Server, or downgrade it.)
To automatically install the domain controller after completing the initial installation of Windows 2000, specify a value in the DCINSTALL section of the reply file. You can create a response file that contains only the DCINSTALL section. If you do not specify an option value, use the default value. Command Behavior DCPROMO / Answer:
Note To view the full content of the DCInstall section, see Windows 2000 Guide to Unattended Setup in the deploy.cab file on the DEPLOY.CAB file.
Recommended practice
This section discusses planning and development deployment, as well as some public strategies that integrate Sysprep and deployment.
Build a distribution folder for the establishment of the workstation (Distribution) folder
When you create a primary workstation, you may use sysprep to create several version of the workstation image. In addition, you may create images for several computers that require different types of hardware drivers (not included in Windows 2000 CD). Therefore, two benefits can be provided for the workstation to create a distribution folder:
Simplify tests because all related files can be found and accessed from the central location. The central location applied to the system's files and drivers ensures that the required files can be copied between multiple workstations to establish and consistency.
Note that if you need to add a driver to the workstation, you need a central establishment location. At the same time, when the main workstation is started, the installation of the distribution folder should be started, which will make the future update image generation and management more easily.
Note You can use the Installation Manager tool on your Windows 2000 CD to help create a distribution folder. For more information on "Installation Manager" and distribution folders, see the relevant parts of Chapter 13 and Chapter 25 in Deployment Planning Guide.
Automatic establishment of a reply file
As mentioned earlier, sysprep.inf is a response file for automatically implementing the final setting of the image computer. You can automatically create a system with a response file before running Sysprep. When Windows 2000 is installed from CD, users usually need to pass a series of screens to manually enter basic system settings information. UNATtend.txt Answer files can be automatically completed, eliminating the input operation of the user during the installation process. Answer files will also tell Setup how to interact with distribution folder (if you use this folder). Using Unattend.txt to achieve automatic deployment can bring several important advantages. The response file makes the test more easily because the configuration has been compiled into a script, which can reduce the chance of human error. In addition, the response file also allows you to maintain the source code easier, and rebuild the system from the header when needed.
Note For more information on UNATtend.txt Answer file, see "Unattend.doc" (UNATtend.doc file) on the Windows 2000 CD (Unattend.doc file) Part of the relevant part of Chapter 13, Chapter 25, and Appendix C in Deployment Planning Guide.
Configuring the default user profile
When configuring a workstation and install an application, create a local user account with administrator permissions. Installing an application as an administrator group member, you can customize the environment that end users will use and avoid the setting of the application that does not recognize the configuration file. Once the application is installed, you can enable the configuration file to the default user profile on the workstation. To do this, please follow these steps:
Click the system on the Control Panel. Click the User Profile tab. Select the created user profile from the configuration file stored on this unit. Click Copy to. Click Browse. Expand the folder list to display:% SystemDrive% / Documents and Setttings / Default User. (% SystemDrive% Location typically refers to the C: / drive, or installs the Windows 2000 drive.) Select to highlight the Default User folder, and then click OK. Click Change under Allow Using. Click Everyone in the Select User or Group dialog.
Focus on the foundation
If you are determined to create multiple images, you should attempt to limit their content to a common application in the core tool and environment. Multiple images will bring multiple tests and maintenance, which will greatly increase TCO. Try to make the basic workstation size as small as possible, then use sysprep.inf from defining installation.
You can also use the "Changes and Configuration Management" features of Windows 2000 (such as "Group Policy" and IntelliMirror management technology), managing the distribution of applications after an image-based operating system deployment. Please compare the benefits of using strategies and deploy applications as part of the image to the workstation, which will help you. The general usage criterion of each method is listed below:
Use policies and IntelliMirror publishing tools and applications used only by a particular user group. Deploying a single computer using common or widely used disk-based applications. Use disk-based applications deployment to workstation to eliminate dependence on network resources.
Note For more information on Group Policy and IntelliMirror, see the Introducture to Windows 2000 Group Policy and Chapter 23 in the Deployment Planning Guide. Determine core image components
You should determine which components in the system establishment in the planning phase belong to the basic image, which components should be set in the actual deployment phase.
Usually, if the software component is needed and planned, it is an image. Such examples include:
Viral scanning software core production software desktop, suitable for dialing the same company remote access number or using the Point-to-Point Tunnel Protocol (PPTP) "to access the same verification server portable
On the other hand, if a certain change depends on the type of workstation, you add such custom settings to the Sysprep.inf response file. Such examples include:
When installing an operating system on a user computer, the RunOcE item for pre-installed a specific application is used. A printer defined at the build level or working group level. Static Transmission Control Protocol / Internet Protocol (TCP / IP) address.
Typically, if you want to use a software or setting throughout the unit, it should be included in the image. However, if you want to customize it at a region or department level, it should have a default value in the image, which can be changed using Sysprep.inf and "Minimum Install Wizard".
Add multilingual support
Windows 2000 has very good multi-language support, which also applies to images of multiple languages that contain multiple languages. A single image that supports multiple languages is now maintained.
You can use the Sysprep installation to add multilingual support (if needed):
Use the Installation Manager to create a sysprep folder and copy the required language files into the folder. "Installer" defaults to copy the language file to the sysprep folder so that these files will be deleted after Sysprep. Copy the / i386 directory (including the lang subdirectory) to the Sysprep folder and set the InstallFileSPath item to point to% systemDrive% / sysprep / i386. These files will be deleted after Sysprep.
Minimize image sizes
You can use several strategies to reduce the size of the sysprep image, saving the required deployment time:
Run the Disk Cleanup Tool (Cleanmgr.exe). This will delete all Windows 2000 temporary files, recycle bin files, temporary Internet files, ActiveX® controls, and more. If you plan to use the Hibernate power management option, you should start this option before running Sysprep, or delete the sleep file when you create an image. Because the size of the sleep file is related to the system memory, it may take up most of the images. This file is called Hiberfil.sys (hidden system file), which is located at% systemDrive%. You can minimize image disk partitions using the ExtendoemPartition item. ExtendoemPartition extends the system partition to the setting size, or quickly fill the entire disk. (Note that this option is only valid for the NTFS partition.) If you want to reduce the sysprep image size by deleting the PageFile, you need:
Make sure the drive file system is FAT or FAT32. Run Sysprep.exe and turn off the system. Start with Windows 95, Windows 98 or MS-DOS boot disk (if FAT32, you must use a Windows 98 boot disk). Delete the volume C: / lower PageFile.sys. Sysprep will automatically generate PageFile when starting at the Minimum Installation. Note If the partitioned file system is NTFS, the above method is not supported. The unique way to delete PageFile.sys on NTFS partition is to temporarily install the driver to another system, and then use this second system to perform deletion (this method can also be used for FAT or FAT32 partitions). Running the disk defragmentation tools included in CHKDSK and Windows 2000, or similar third-party tools supported by Windows 2000. This will ensure that the system disk does not have any problems before replication. Consider using the installation center
Some companies have established a computer to outsource the task to the integration center, which is pre-installed by these centers. You can deploy a large number of computers in a short time by providing CD or web-based installations and writing correct sysprep.inf. You only need to use the Minimum Installation Wizard to complete the final information collection, and most of the workstations create tasks to external packages to the integration center, which has higher reliability than manual installation.
Distribution technology
After creating a Windows 2000-based image, you can use multiple ways to distribute: Use unattended response files via the network, physically install new image hard drives on the target computer, or use the bootable CD.
Note Before you start deployment, it is recommended that you first evaluate the BIOS on all target computers. To learn more about the BIOS recommended by the computer vendor for Windows 2000, please visit their corresponding website. At the same time, it should also be considered whether any hard drive on the workstation needs to be restrict.
Download from network
Windows NT 4.0 allows system administrators to deploy operating systems over the network using unattended response files. This feature is also available in Windows 2000, which can also distribute the copy image. If you want to distribute the copy image through the network, you first need:
Create a distribution point on the server that contains the image library. Create a network boot floppy disk containing an operating system with network capabilities, which is used to start the target computer.
Once logged in to the network via the boot disk, the target computer is connected to the network share, and starts the image restore by the drive image scheme. From the entire process starting from the login, it can be performed completely, or another method, that is, prior to starting the image restore, prompting the user from the available image list on the server, calling the BIOS Flash utility, and then creates or managing partitions.
Usually, network installation is the slowest deployment method, of course, the most dependent network. If you consider using this deployment method, and you have Windows 2000-based servers, you may want to use the Remote Installation Services (RIS) "for network installation (see" Sysprep and Remote Installation Services "section below).
Install new hard drive
Many large companies use the integration center to deploy new workstations. In essence, the hard disk of the main computer is removed and copied from another computer to disk, then mounted these disks onto the target computer.
This protocol involves the unpacking problem of the workstation, which is usually longer than the deployment time based on CD or network.
Use the bootable CD
Using the bootable CD can provide a complete Windows 2000 deployment (including applications) in a few minutes. The most convenient way to create a bootable CD is to use the CD creation tool that allows the floppy disk emulation. In short, you need to provide a boot floppy disk capable of reading CDs and Windows 2000 images. The boot floppy must be loaded into the corresponding CD driver and has an appropriate syntax to initiate an image recovery created by the drive image software. The BIOS on the target computer should enable the CD driver to start the device. After the establishment process is completed, the user can insert the CD into the computer, start from the CD, and then restore the partition. The restore process itself is based on the tool script provided by the image software.
Note that the target computer must have an el Torito No Emulation support that can start CD.
One benefit based on CD deployment is that it has a restricted network when it does not rely on (slow download speed). Its significant disadvantage is that the space limit on the CD is available for approximately 640 megabytes (MB). However, the current software allows the image to be placed on multiple CDs.
Comparison of sysprep and ris and unattended installation
Sysprep and remote installation services
In Windows 2000, there are many ways to deploy basic operating systems, applications, and specific settings on workstations. Remote Installation Services (RIS) is similar to sysprep, which can be used to install administrators configured on the workstation. Differently, it uses many of the functions of network hardware on the target computer, such as starting the workstation from the network adapter. Therefore, it is very dependent on the network infrastructure (including the Active Directory service).
Note For more information on remote installation services, see Step-by-Step Guide to Remote OS Installation
I remember the Sysprep-based deployment method we discussed earlier, such as using the bootable CD, which is not dependent on the network. Such methods are more suitable for deploying clients that are not connected to the network, or clients with slow access to the central server. In addition, Sysprep can be deployed in an environment where Active Directory is not implemented. Finally, Sysprep is more suitable for large deployment scenarios. In these scenarios, hundreds of computers are deployed in analog debugging areas, while do not connect their keyboard, mouse devices, and displays throughout the computer deployment.
Sysprep and unattended installation
Sysprep is very similar to those who participate in unattended, which are automated deployment methods designed to reduce end-user input requirements during installation. Moreover, the sysprep.inf response file after the customer installation image is automatically completed, and the syntax based on the syntax of the response files commonly used in the unattended installation is the same. (However, sysprep only supports a subset of parameters used in the unattend.txt file).
The difference between the two methods is more informationivity. With sysprep, you can build images that contain operating systems, basic settings, and core applications. This image can then be used as a master image, copy it to multiple computers with compatible hardware configurations during the new installation process. With no participation, you can only install the operating system one by one on the target computer. This means that you must install all applications separately afterwards. The advantage of this method is that it is not subject to the constraint of the hardware requirements of the SYSPREP method, and can be used in a variety of hardware configurations. Its main disadvantages are longer, especially when deployed by network, and involving many other steps, so it is not suitable for large deployment of large deployments.
Example 1: Establishing a standard department workstation
Program
Suppose a company has a 500 represented customer service department. All workstations are configured to run commercial applications recorded by retrieval customers, and there are also other office applications. Over time, the department has also become growing, so although each computer type is the same, its peripheral (network adapter, memory) and operating system version and application are different. The department has agreed to update the workstation with Windows 2000 Professional to reduce TCO to maintain multiple different operating systems and applications. All documents are stored on a file server and all workstations share a Microsoft Exchange server. This means that there will be no problems when deleting hard drive data, because any information is not stored on each user's computer.
The workstation name corresponds to the physical location of the representative, which is a combination of floor number and office room number and username.
In the process of re-deploy, companies IT staff can only access a job for a short period of time because the department takes 24 hours to answer the customer phone. Team members decide to use disk replication to deploy new standard images because all software configurations should be the same. In addition, they think that the upgrade existing configuration may increase risk and deployment time without bringing any additional benefits. Two deployment methods will be used: CD-based deployment can maintain low network traffic, and network-based methods can be applied to computers without CD-ROM drives.
process
IT administrators install Windows 2000 Professional, Office 2000, and Customer Service Applications on a computer that is very similar to the computer representatives of customers, starting to create a standard image. In addition, the hardware drivers on some computers are not in the Windows 2000 CD, which are also copied to the computer. Install the central shared printer while adding the company IntraN's preferences in Internet Explorer.
After the computer configuration is finished, the administrator has prepared the host computer, and can be copied by the customer service department. Administrators use the Installation Manager to create a sysprep.inf response file, which will automatically complete the installation process except for the computer name. The administrator creates a sysprep folder on the hard drive C: / and copies sysprep.inf, sysprep.exe, and setupcl.exe to that directory. The sysprep.inf file has the following parameters:
[Unattended] OemSkipEula = Yes [GuiUnattended] AdminPassword = * TimeZone = 20OemSkipWelcome = 1 [UserData] FullName = "Customer Service Department" OrgName = "MyCompany, Inc." [Identification] JoinDomain = CORPDOMDomainAdmin = CORPDOM / AcctAddIDDomainAdminPassword = CORPDOM / good! Pass3 [networking] installdefaultcomponents = yes
Because the UserData section does not include the ComputerName parameter, the Minimum Install Wizard will prompt you to enter your computer name.
The administrator runs sysprep from the C: / sysprep directory. When the computer is turned off, it indicates that it is ready to start copying. The administrator then runs the software-based disk image utility to create an image file. To speed up the network installation, the administrator can place the image on several web servers and then create a network boot disk to connect the computer to the web server and start installing. In addition, administrators use the CD Creative Utility from the master image to create the CD image and send it to the tool for copy. In step-by-step mode, the administrators group began to deploy workstations. The hardware in the computer is automatically detected when the installation department-specific image. When the customer service represents the first time the computer starts a computer, the Minimum Installation Wizard will prompt them to provide the computer name. At this time, the deployment process has been completed. Because the staff of the department is high, the administrator does not have to be redeployed, just run the Sysprep call "Minimum Installation Wizard" to change the computer name for the new user.
Example 2: Deploying a remote office server
Program
The large business IT department will deploy Windows 2000-based servers within the next few months. There are no IT administrators in the regional offices where many of the servers are located.
According to the company's needs and Windows 2000-based server infrastructure design, the components of the area server configuration are: Running files and printers shared Windows 2000-based servers with COM web services, web-based orders processing applications. The configuration of each region server will be exactly the same.
The IT department decided to use sysprep to copy these area servers. They plan to create a sysprep image and bootable CD, and then send it to the regional office while coming with a brief description of the end user. All servers in the company have a fixed Internet protocol (IP) address, so when setting these servers in the regional office, the unique address should be configured for each server.
Another point in this scenario is that some servers need to run Active Directory and serve as domain controllers. As mentioned earlier, the domain controller cannot be copied, but the server can be copied. Therefore, when the newly configured server is first started, the DCPROMO (it calls the Active Directory Installation Wizard) converts the server into a domain controller.
process
When you create a master image, the administrator first establishes Windows 2000-based servers on the hardware of similar regional office servers. Administrators install and configure Internet Information Services (IIS), web applications, and terminal services in Remote Management mode, so that the central IT group can easily manage remote servers.
After establishing and configuring the server, the administrator runs sysprep and then runs the disk replication software. Administrators use CD to create software to create a bootable CD. In order to avoid any local configuration issues, reduce people caused by manual input information as wrong risk, the IT group determines that the unique sysprep.inf file is distributed through the floppy disk without relying on the Minimum Installation Wizard prompting the regional user to enter IP address information.
Regional Office Staff is ready to establish a Windows 2000-based server, the user can start from the CD to restore the image. After the Restore image, when Windows 2000 is ready to load data from the hard disk, insert the floppy disk, prompt the Minimum Install Wizard to capture the information of the Sysprep.inf response file.
The following sysprep.inf response file is used for the server's fully automatic installation and provides IP addresses and computer names:
[Unattended] UnattendMode = FullUnattendedOemSkipEula = YesOemPreInstall = NoTargetPath = / WINNT [GuiUnattended] AdminPassword = * AutoLogon = YesOEMSkipRegional = 1TimeZone = 20OemSkipWelcome = 1 [UserData] FullName = "Corporate Server Name" OrgName = "Company Name, Inc." ComputerName = 005 -REGSRV-1 [LicenseFilePrintData] AutoMode = PerSeat [GuiRunOnce] Command0 = "dcpromo /answer:ansfile.txt"[Identification]JoinDomain = REGDOMCreateComputerAccountInDomain = YesDomainAdmin = CORPDOM / IDAcctDomainAdminPassword = password [Networking] [NetAdapters] Adapter1 = params.Adapter1 [ params.Adapter1] INFID = * [NetClients] MS_MSClient = params.MS_MSClient [params.MS_MSClient] RPCSupportForBanyan = No [NetServices] after MS_SERVER = params.MS_SERVER designated to be a server for a domain controller, the "minimum installation wizard" is completed, the computer The instructions of the GuirunOnce section in the answering file will be restarted and executed, and this article refers to the execution script and installs the server to run the domain controller of Active Directory.
The following scripts enhance the server to domain controllers:
[Guirunonce] command0 = "dcpromo /answer:ansfile.txt"
Among them, ANSFILE.TXT contains the following parameters:
[DCInstall] UserName = CorpAdminUserPassword = SomeGoodPa $$ wordUserDomain = corpmasterReplicaOrNewDomain = DomainTreeOrChild = ChildParentDomainDNSName = northamerica.myco.comChildName = region1.northamerica.myco.comDomainNetbiosName = REGION1AutoConfigDNS = No
Note To view the full parameter list, see Windows 2000 Guide to Unattended Setup in the deploy.cab file on the Windows 2000 CD.
to sum up
"System Preparation (Sysprep) is a tool preparing a primary computer for copying or cloning. Sysprep creates a unique SID for each clone client, so that the process is very secure. Sysprep Detect plug-and-play device and adjust the system with different devices. Sysprep Run "Minimum Install Wizard" to request user specific information, such as user name or time zone selection. Administrators can choose to use the answer file sysprep.inf to provide these answered and implement a completely automatic installation. Sysprep is responsible for preparing the system image, the image replication phase requires a third party's cloning utility, such as Symantec's Norton Ghost or PowerQuest DriveImage. Sysprep is especially useful for large unit deployment tasks, and hundreds of computers in these units require the same application and desktop configuration. Use Sysprep if there are multiple computers to perform new installations (for example, when deploying new computers). If multiple computers in the unit have only some standard hardware configurations, rather than many custom configurations, please use Sysprep, the latter is more suitable for unattended installation.
Sysprep greatly reduces deployment time because almost every component, including operating system, application, and desktop settings, can be configured without user intervention. The master image can be copied to the hard disk or CD-ROM, and then physically distribute to the client, saving time and network capacity of loading files over the network. Use Sysprep to deploy Windows 2000 to large desktops in large units, so that you can implement "Best Management Practices", such as standard desktops, management strategies, and restrictions. Finally, Sysprep is very helpful in reducing operating system TCO due to saving Windows 2000 deployment time and resources.
Other Information
For the latest information about Windows 2000, visit Microsoft TechNet and Windows 2000 website http://www.microsoft.com/windows2000, and Windows 2000 / Windows NT Forum http://computingcentral.msn.com/topics/windowsNT.
Frequently Asked Questions
Q: If I have multiple plug-and-play devices, do you have to create a separate distribution folder or image for them?
A: No. You can place all drivers of plug and playing device in the same operating system to the same location. For more information, see the "Pre-Installed Plug and Play Device" section in this article.
Q: I tried to use the sysprep.inf answer file on the floppy disk. Why can't the "minimum installation" can't find this file?
A: For Intel-based computers, if the floppy is booted earlier than the hard disk boot, you must insert the floppy disk before starting the "Minimum Install Wizard".
Q: When is the / NOSIDGEN switch?
A: I hope that the "Minimal Installation Wizard" is running, but it is possible to use / Nosidgen when you do not want to regenerate SID. For example, if the SETUP and response files are used to install Windows 2000 on your computer, you want to run the Minimum Install Wizard to add a workstation to the domain, you can use this switch.
Q: The image I created contains the application, but the user does not see these applications after logging in.
A: When establishing a host computer and install an application, you should verify that the user-specific data has been written to the default user registry. A convenient way of verification is to browse the Documents and Settings directories under Default User. It is also possible to verify that the installed application is available for all users, and can be used by using the application identified by configuration file, or installing to the user identifier and then allowing the configuration file to all users. See the "Recommended Practice" section of this article for more information. Q: When the Minimum Install Wizard prompts the user to enter the computer name, I don't want the user to change the password. what do I do?
A: Specify the administrator password in sysprep.inf. Thus, when prompted that the user enters the computer name, the administrator password will automatically appear in the correct box and cannot be changed.
Q: After running Sysprep on your computer, there do not appear on the taskbar on the taskbar on the taskbar display icon on the taskbar) option, but this option is selected in the host computer connection properties. Why don't you work?
A: Network settings need to be reset on the target computer, so this option is reset to the default value. This is a known limit for sysprep in LAN connection. It does not affect remote access.
Q: Do you still keep disk quotas after running sysprep?
A: Disk quota will retain "domain users". The disk quota is not reserved for the local user account.
Q: I want to run the command at the end of the Minimum Installation. what do I do?
A: Use the following steps to specify the cmdlines.txt file at the end of the "minimum installation":
Create the sysprep.inf file that will be used by sysprep. Note that this step is a necessary steps and must not be bypassed. In addition, the file name of the sysprep.inf file must be sysprep.inf and must be located under the sysprep off folder of the volume root directory containing the% SystemRoot% folder. The following entries are placed on the UNATtended section of the sysprep.inf file: installfilespath = drive: / path, where path is the folder to use. It is best to let DRIVE as a volume containing the% SystemRoot% folder. Create a Drive: / Path folder. You can use any of the desired folder names, but it must match the location specified in the sysprep.inf file. Create a folder named $ OEM $ under the Drive: / Path folder. Place the cmdlines.txt file under this folder.
Q: Can I use sysprep.exe to convert a file system to NTFS?
A: No. You need to convert the file system using the Convert.exe tools provided on the Windows 2000 CD before running Sysprep.
Appendix A: Disk replication process diagram
If your browser does not support the inline box, click here to view it in a separate page.
Appendix B: Sysprep.inf supports UNATtend.txt parameters
The response file used with the System Preparation tool is called Sysprep.inf. It uses the syntax and item names used to use the Windows 2000 PROFESSIONAL SETUP Answer Unattend.txt. Unattend.doc in Windows 2000 Resource Kit provides additional information about using the answer file. The supported parts and items in the answer file are listed below:
[Unattended] ExtendoemPartition is only valid on the Windows NT File System (NTFS) partition. Used to extend the partition where Windows 2000 is installed, so that SETUP extends the target partition to any unparalleled space available in physical adjacent. InstallFileSPath is only for sysprep.inf. Specifies the location of the file (such as language file) during the Minimum Installation process, so that the installation will not be interrupted to prompt the user input. Keeppagefile is only valid for sysprep.inf. When you run Sysprep, the Minimum Install Wizard automatically regenerates the system's PageFile to accommodate the difference between the primary computer and the target computer RAM. OEMPNPDRIVERSPATH Specifies the folder path of the Plug and Play Device (PNP) driver on the Windows 2000 CD. These folders must contain all files required to install specific devices - Catalog files, INF files, and drivers. OEMSKIPEULA determines whether users should prompt users to accept the Microsoft License Agreement in Windows 2000 (previously called "End User License Agreement" or EULA). Write this item and set it to YES, which is shown that the execution of the installer has read and agreed to the "license agreement" included in the product. It simulates that the end user represented by Windows 2000 has agreed to the "license agreement". Updatehal is only valid for sysprep.inf. If the administrator uses a compatible hardware abstraction layer (HAL), the HAL is based on an asynchronous processor interrupt controller (APIC) single processor (UP) host computer image on a compatible multiprocessor (MP) target computer. This item is required. Updateuphal is only valid for sysprep.inf. If the administrator uses a compatible HAL, the HAL is based on an APIC MP host computer image on a compatible APIC UP or MP target computer. [OEM_ADS] supports all items. [Guiunattended] Admin Conuse Word Settings Administrator (Administrator) account password. It is only valid only if the administrator password on the host computer is empty. Autologon If set to YES, set the computer to automatically log in again with the computer administrator account. This item is invalid when upgrading. AutologonAccountCreation Specifies whether a computer account is automatically created if the username specified for FullName. AutologonAccountCreation also allows the generated user account to automatically log in to your computer. AutologonCount Specifies the number of times the computer uses the administrator account and specifies the password. This value is decremented with each login, and the function is disabled after trying to specify the number of logins. OEMDuplicatorstring is only valid for sysprep.inf. This string contains any instructions for the replication utility used, as well as any other information that OEM or administrator wishes to store in the registry. This value is stored in the HKLM / System / Setup / OemduplicatorString registry key. OemskipRegional allows unattended "Regional Options" pages that skips the GUI mode installation and minimum installation. Oemskipwelcome allows unattended "Welcome" pages that skip the GUI mode installation and minimum installation. Timezone specifies the time zone where the computer is located. If there is no item, the user selects the time zone. [UserData] supports all items. [LicenseFilePrintData] supports all items. [Guirunonce] supports all items. [Display] Supports all items. [RegionalSettings] If the file is on the hard disk, you support all items. [TAPILOCATION] Supports all items.
This value is only valid when there is a modem installed on your computer. [Networking] No need to do anything. [Identification] supports all items. [NetClients] supports all items. The information contained in this document represents the current view of the issued problem in the date of publication, Microsoft Corporation to the discussion. Because Microsoft must comply with the changing market conditions, this document should not be understood as the commitment of the Microsoft party, and Microsoft does not guarantee the accuracy after the information given in the date of publication.
This white paper is for reference only. Microsoft does not make any promises or defaults for information on this document.
Compliance with all applicable copyright law is the user's responsibility. Without restricting the rights required by the copyright law, it is not possible to copy any form or means (electronic, mechanical, photocopying, recording, etc.), and disseminate this article in any form or means (electronic, mechanical, photocopy, recording, etc.). Any part of it is not allowed to store or introduce it into the retrieval system.
This document may involve Microsoft's patents, patent applications, trademarks, copyrights and other intellectual property rights. Unless explicitly expressed in any written license agreement in Microsoft, it does not mean that this document does not mean that you will receive these patents, trademarks, copyrights, or other intellectual property rights.
© 2000 Microsoft Corporation. all rights reserved.
Microsoft, Active Directory, ActiveX, Intellimirror, Windows, Windows Logo, and Windows NT are registered trademarks or trademarks of Microsoft Corporation in the United States and / or other countries (regions).
The actual companies and product names mentioned here may be a trademark of its respective owners.
Microsoft Corporation • One Microsoft Way • Redmond, Wa 98052-6399 • USA
05/00
1 Note that the value must be set according to the license protocol of the deployed operating system.
