Using Sysprep for Servers to Maximize Consistency

Another method of creating images for the deployment of Windows Server 2003 involves using the System Preparation tool or Sysprep. Sysprep is very similar to RIPrep in that it is an image preparation tool. Unlike RIPrep, though, Sysprep does not take advantage of RIS server management or deployment. Sysprep is used for standalone image preparation. After a Sysprep image is created from a template system, one of several third-party applications can be used to capture the image to a file for redeployment to other systems.

Sysprep was introduced with Windows 2000 with a purely command line interface intended for desktop image creation. Many updates were made to Sysprep when Windows XP was introduced, including a wizard-based setup manager, but it was still primarily a tool designed for preparing images for desktops. With Windows Server 2003, Microsoft has made Sysprep a supportable method for preparing server-based disk images.

How Sysprep Works

As mentioned earlier, Sysprep is very similar to RIPrep. For example, both image types can include applications that might have already been installed on the image system, and the images can be customized before and after deployment of the image. Also, both image types require the same HAL for target systems. It follows from these similarities that the steps necessary to prepare a Sysprep server image are similar to creating a RIPrep server image. The following steps outline the process:

1. A template system is prepared by installing the operating system, installing applications, and customizing settings according to company specifications.

2. Sysprep is run on the computer, which then powers off.

3. Using a third-party tool, an image of the Sysprepped system is copied to a file server.

4. A new system is booted using a third-party tool, and the image is installed.

5. The new system is started and a mini-setup runs. The mini-setup is a pared down version of the full Windows setup.

6. The new system reboots and is ready to go.

HAL

HAL must be the same on the source and target systems for Sysprep to function. This is especially true when it comes to ACPI and non-ACPI computers. ACPI images cannot be deployed on non-ACPI systems, and non-ACPI images cannot be installed on ACPI systems.

There are some key differences between this process and the RIPrep process of which deployment administrators should be aware:

• Sysprep images cannot be deployed or managed with a RIS server. There are several third-party tools that can be used to capture the image. Xcopy can even be used to copy the system to a network share.

• Because RIS is not involved, Active Directory is not required. Sysprep can be used to create Windows Server 2003 images in an environment that does not have AD.

• A mini-setup is run when the newly imaged system is powered on. The mini-setup only prompts for information necessary to make the installation unique again, such as computer name , network configuration, or domain membership. The mini-setup can be completely automated by creating an .inf answer file. With RIPrep, there is a longer setup process for RIS imaged systems.

Taking Advantage of New Sysprep Features

In addition to enabling Sysprep to support server images, Microsoft has further enhanced the tool for Windows Server 2003.

The new Sysprep can image a fully configured server with Internet Information Server (IIS) installed. For companies that support several Web servers, this would be a key deployment option.

Sysprep has a new mode of operation called Factory. By running Sysprep with a -factory switch, updated or out-of-the box drivers will be picked up by the image before the system is fully set up.

In conjunction with the Factory mode of operation, Sysprep can include an answer file, winbom.ini, that goes beyond driver installation and can actually gather and install applications from a network share at install time. This feature enables you to use a smaller image for deployment, with applications installing automatically from the network.

Finally, the -PnP switch commonly used with Windows 2000 systems is no longer necessary. Because the Plug and Play functionality in Windows XP and Windows Server 2003 is dramatically improved, getting an image to work on systems with different hardware components is a lot easier.

winbom.ini, Not sysprep.inf

The answer file for running Sysprep in factory mode is winbom.ini, not sysprep.inf. Setup Manager can be used to create either of these files.