通过

Windows Server 2008 SP2 Deployment Guide

  • 项目

Applies To: Windows Server 2008

About this guide

This guide is for IT administrators who are deploying Windows Server® 2008 Service Pack 2 (SP2). This document includes technical information, procedures, and recommendations for installing SP2 in a business or corporate environment. Although this guide includes some basic operating system information, we assume that you already have a working knowledge of Windows Server 2008 and update installations.

For more information about deployment, see the following Microsoft resources:

Note

To provide feedback about this guide, e-mail ws08spfb@microsoft.com.

Terminology used in this guide

The terms defined in the following table are used throughout this document.

Term Definition

Integrated installation

This is also known as "slipstream installation." In this installation method, the service pack is integrated into the operating system. As a result, the operating system and service pack are installed simultaneously. You use the integrated installation to upgrade computers and to perform new installations on computers that do not have an operating system.

Offline

In the context of updating images, the term "offline" refers to updating or applying changes to an operating system image that is not currently running. For example, you might update a Windows® Image (.wim) file by using ImageX in the Windows Automated Installation Kit (AIK).

Online

In the context of updating images, the term "online" refers to updating or applying changes to an operating system that the computer is booted into. For example, installing an update by using Windows Update is an online operation.

Package

A collection of files representing an update that fixes a problem or introduces new functionality. Packages include the component files as well as the necessary metadata to manage the packages. Many packages are distributed as .msu files, each of which contains a compressed cabinet (.cab) file).

Service pack

The means by which product updates are consolidated and distributed. Service packs are software packages that may contain updates for system reliability, program compatibility, security, and so on. These updates are bundled together for easier downloading and installation. A service pack includes all fixes released to date, as well as additional improvements to existing components.

Stand-alone package

A version of the SP2 package that contains all of the files necessary to install the package on any computer (even without an Internet connection). In contrast, when you install the SP2 package from Windows Update, only the files needed for that specific computer are downloaded and installed. There is usually a considerable size difference between a package that is downloaded using Windows Update and the corresponding stand-alone package.

Update
  • Noun: Any update, update rollup, service pack, feature pack, critical update, security update, or hotfix that improves or fixes a software product released by Microsoft. For definitions of all of these types of updates, see article 824684 in the Microsoft Knowledge Base (https://go.microsoft.com/fwlink/?LinkID=43258).

  • Verb: To make a computer or file more current.

Upgrade
  • Noun: A software package that replaces a particular version of a product with a newer version of the same product.

  • Verb: To update existing program files, folders, and registry entries to a more recent version by using Setup.exe from the installation media. Upgrading leaves existing files and settings intact, in contrast to when you perform a new installation in which all files are deleted and then reinstalled.

In this guide

This guide covers the following:

  • Overview of SP2

  • Before you deploy SP2

    • Obtain the installation files

    • Perform pre-deployment tasks

  • Planning to Deploy SP2

    • Application compatibility

    • Installation options

  • Deploying SP2

    • Small-scale scenarios

    • Large-scale scenarios

  • Uninstalling Windows Server 2008 SP2

  • Troubleshooting

Overview of SP2

Windows Server 2008 SP2 is a set of updates and fixes for Windows Server 2008 that addresses feedback from our customers (in addition to the improvements that are delivered to users through Windows Update). In addition to including previously released updates, SP2 focuses on specific reliability and performance issues, support for new types of hardware, and support for a few emerging technology standards. Note that although SP2 is not intended to be a vehicle for releasing new features, some existing components do gain enhanced functionality through SP2. For more information about SP2, see the following Microsoft TechNet articles:

Before you deploy SP2

Complete the following steps before you deploy SP2:

  • Obtain the installation files.

  • Perform pre-deployment tasks.

Obtain the installation files

Obtain the SP2 files by using one of the following methods:

  • Windows Update. Windows Update contains SP2, so SP2 will be installed automatically on computers that are set to receive automatic updates. However, before SP2 is installed, the user must accept the Microsoft Software License Terms.

  • Stand-alone package. You can download SP2 from the Microsoft Download Center at https://go.microsoft.com/fwlink/?LinkId=145430.

  • Integrated installation. SP2 is integrated into the Windows Server 2008 SP2 installation DVD, and it is also available as part of the media kit for Volume License customers as well as TechNet and MSDN subscribers.

Perform pre-deployment tasks

Perform the following tasks before you install SP2. If you are installing SP2 by using Windows Update, be sure to perform these tasks before you accept the Microsoft Software License Terms.

  1. Check disk space requirements. The following table lists the approximate disk space requirements for the system partition, which includes the English (EN) language pack by default. Note that these requirements will increase if other language packs are installed on your computer. For more information about each installation method, see Installation options.

    Installation method Approximate disk space requirements

    Stand-alone installation
    • x86-based: 1.8 GB to 2.9 GB

    • x64-based: 3.2 GB to 4.9 GB

    • ia64-based: 2.9 GB to 3.2 GB

    Windows Update
    • x86-based: 350 MB

    • x64-based: 600 MB

    • ia64-based: 2.25 GB

    Integrated installation
    • x86-based: 9 GB

    • x64-based: 12 GB

    • ia64-based: 13 GB

Note

SP2 is supported for x86-, x64-, and ia64-based computers.
For more information about system requirements for Windows Server 2008, see https://go.microsoft.com/fwlink/?LinkId=108506.

  1. Back up important data. For Windows Update and stand-alone installations, Setup automatically takes a system restore point before the installation of SP2 begins, which backs up system files. However, you may want to back up any user data before you begin installing SP2.

  2. Read the release notes (https://go.microsoft.com/fwlink/?LinkId=129466).

  3. Install Hyper-V RTM. If you have enabled the Hyper-V role on Windows Server 2008 RTM, but have not upgraded from a pre-RTM version of Hyper-V to Hyper-V RTM by applying KB950050, then you need to perform one of the following actions:

    • Upgrade to Hyper-V RTM before installing Windows Server 2008 SP2.

    • Disable the Hyper-V role.

Note

Disabling the Hyper-V role does not guarantee that virtual machines that were saved while running a pre-RTM version of Hyper-V will run correctly on Hyper-V RTM. 

  - Verify that the management operating system and virtual machines are running the same version of the integration services. For more information, see [Version Compatibility for Integration Services](ee207413\(v=ws.10\).md)  
      
      
      

For more information on Hyper-V, see the [Hyper-V Planning and Deployment Guide](https://technet.microsoft.com/en-us/library/Cc794762)

  1. Ensure that drivers are up to date. Check Windows Update and the hardware vendor for updated drivers. Windows Update and the SP2 standalone installer include new functionality that will block SP2 installation if a problematic driver is installed or it will provide a warning if there will be minor loss of functionality. If you are performing an integrated installation by using the DVD, you will not encounter these problems.

  2. Disconnect any serial cables connected to UPS devices. If you have an uninterruptible power supply (UPS) connected to your destination computer by a serial cable, remove that connection before running Setup. Setup detects devices that are connected to serial ports, and UPS devices can cause problems with the detection process. You can leave your computer connected to a UPS for power as long as the UPS itself is plugged in. However, you should make sure that you have enough power for the entire installation, which can take a long time.

  3. Plug laptops into an AC power source.

  4. Check for file and servicing store corruption issues. To ensure that your computer does not have any file corruption issues, we recommend that you run Check Disk (Chkdsk.exe), System File Checker (SFC.exe), and System Update Readiness tool (CheckSUR.exe) by using the following procedure.

    To check and fix any file corruptions

    1. Open an elevated Command Prompt window (click the Start button, type command in the Start Search box, right-click Command Prompt, and then click Run as administrator).

    2. Run the following command (assuming that C is the system drive): chkdsk c: /F

    3. After the command in step 2 completes, run the SFC /Scannow command.

    To check and fix any servicing store corruptions

    1. Download KB947821 update from Microsoft Download Center (https://go.microsoft.com/fwlink/?LinkId=109180).

    2. Double-click the Windows6.0-KB947821-NNN.msu file (where NNN is x86, x64, or ia64), which will run the System Update Readiness Tool (CheckSur.exe).

Planning to Deploy SP2

To determine which SP2 deployment scenario or combination of scenarios is best for your organization, consider the following questions. Note that the Microsoft Deployment Toolkit documentation (https://go.microsoft.com/fwlink/?LinkId=108442) contains best practices and tools to help you answer questions about integrated image installation. For example, you should consider the following questions.

  • Are you updating existing computers that are running Windows Server 2008, performing new installations, or upgrading a previous version of Windows to Windows Server 2008?

  • Which installation option should I use?

  • Where will the service pack files be stored?

  • Are there any impacts on my change and configuration management processes?

  • How should I test and validate the service pack or image installations before deployment?

  • What network capacity will you need to ensure that the service pack deployment does not adversely affect the network or cause significant performance issues for other business applications?

  • How do I determine that the service pack was successfully installed?

Application compatibility

Application Compatibility Toolkit (ACT) 5.0 helps you identify and manage your overall application portfolio, which reduces the cost and time involved in resolving issues. Among many other features, ACT 5.0 has a new integrated interface that enables you to manage the entire toolkit from a single location. In addition, you can run ACT 5.0 in your current environment (including Windows operating systems from Windows 2000 onward) so that you can test all operating system configurations before you begin deployment. For more information, and to download ACT 5.0, see "Application Compatibility" (https://go.microsoft.com/fwlink/?LinkID=71359).

Installation options

There are three ways that you can deploy SP2, as explained in the following table.

Method Explanation

Installing SP2 by using Windows Update

In a Windows Update installation, Windows Update downloads the applicable portions of the service pack to the destination computer and works within the operating system to install the service pack. This method requires relatively low bandwidth and minimizes network traffic because only the changes needed for a specific computer are applied.

This method is used in Scenario 1: Installing by using Windows Update.

Installing SP2 by using the stand-alone installation

In a stand-alone installation, you install the service pack to update computers that already have an operating system. The download size of the stand-alone package is larger than the package applied with Windows Update. This method is recommended for the following situations:

  • Applying SP2 to computers with limited or no Internet connectivity.

  • Applying the service pack to more than one computer by using deployment tools such as Systems Management Server (SMS) 2003, WSUS Server, System Center Essentials, or System Center Configuration Manager 2007.

This method is used in the following scenarios:

  • Scenario 2: Installing the stand-alone package by using the installer executable file

  • Scenario 4: Deploying by using WSUS

  • Scenario 6: Deploying SP2 by using SMS 2003 or System Center Configuration Manager

Installing SP2 by using the integrated installation

In an integrated installation (also known as a "slipstream installation"), the service pack is integrated into the operating system, and therefore the operating system and service pack are installed simultaneously. Use the integrated installation to upgrade computers running Windows XP and to perform clean installations on computers that do not have an operating system. You cannot use the integrated installation to upgrade computers running Windows Server 2008 to SP2. For an overview of supported upgrade paths from previous versions of Windows, see https://go.microsoft.com/fwlink/?LinkId=100331.

If you choose this option, you cannot uninstall the service pack when the installation is complete. Instead, you would need to reinstall the entire operating system.

This method is used in the following scenarios:

  • Scenario 3: Creating or updating a custom image

  • Scenario 5: Deploying SP2 by using Windows Deployment Services

Deploying SP2

The following scenarios describe some of the ways that you can deploy SP2.

Small-scale scenarios

  • Scenario 1: Installing by using Windows Update

  • Scenario 2: Installing the stand-alone package by using the installer executable file

Large-scale scenarios

  • Scenario 3: Creating or updating a custom image

  • Scenario 4: Deploying by using WSUS

  • Scenario 5: Deploying SP2 by using Windows Deployment Services

  • Scenario 6: Deploying SP2 by using SMS 2003 or System Center Configuration Manager

Small-scale scenarios

The following scenarios are applicable to businesses and individuals who want to deploy SP2 to a relatively small number of computers.

In this section:

  • Scenario 1: Installing by using Windows Update

  • Scenario 2: Installing the stand-alone package by using the installer executable file

Scenario 1: Installing by using Windows Update

This method of installation is for individual users who are currently running Windows Server 2008 and have configured Windows Update to download and install updates.

To install the service pack by using Windows Update

  1. Ensure that you are connected to the Internet.

  2. Do one of the following:

    • If your computer is set to install updates automatically, when prompted, follow the instructions to install SP2.

    • To initiate the installation manually, perform steps 3 through 7.

  3. Click Start, click Control Panel, double-click Windows Update, and then click Check for Updates.

  4. Select the SP2 update (KB948465). If there are other updates displayed, make sure that SP2 is the only update selected, and then click Install.

  5. After Setup downloads the update, accept the Microsoft Software License Terms and then click Install.

  6. Setup will begin the installation. When prompted, click Restart now. During this second installation phase, Setup will prevent you from logging on while the service pack is being installed. The installer may automatically restart the computer several times during this process.

Warning

Do not restart the computer or turn the power off, even if the computer remains in an unknown state for a long time. If you do, the computer may go into an unbootable state.

  1. When the Windows logon prompt appears, this indicates that Setup is completed. At this time, you can log on to the computer.

  2. To confirm that SP2 is installed, right-click Computer and then click Properties. You will find a reference to the service pack in the Windows Edition section.

Scenario 2: Installing the stand-alone package by using the installer executable file

The installer executable file contains every file necessary to install the service pack. This file is self-extracting, and you can run it either from the command line or by double-clicking the file within Windows Explorer.

To install SP2 by using the stand-alone package

  1. Copy or download the installation file (Windows6.0-KB948465-X86.exe, Windows6.0-KB948465-IA64.exe, or Windows6.0-KB948465-X64.exe) to a computer. You can download SP2 from the Microsoft Download Center at https://go.microsoft.com/fwlink/?LinkId=145430.

  2. To run the package, use the command-line options listed later in this section, or double-click the file within Windows Explorer. It may take several minutes to extract the installation files, and even longer if you are installing SP2 by using a shared network resource.

  3. Follow the instructions in the Setup wizard.

  4. After the first phase of installation is complete, the computer will automatically restart. During this second installation phase, Setup will prevent you from logging on while the service pack is being installed.

  5. Setup is complete when you are presented with the Configuration Updates screen and login prompt. At this time, you can log on to the computer.

  6. To confirm that SP2 is installed, right-click Computer and then click Properties. You will find a reference to the service pack in the Windows Edition section.

Command-line options

Use the options listed and described in the following table to define the way SP2 is installed. You can precede the following options with either a forward slash (/) or a hyphen (-). Note that the options are not case-sensitive.

Use the following syntax, where NNN is x86, x64, or ia64:

windows6.0-kb948465-NNN.exe [/quiet] [/nodialog] [/norestart]

windows6.0-kb948465-NNN.exe [/quiet] [/nodialog] [/forcerestart | /warnrestart[:<Seconds>]] [/promptrestart]

For example, to run the installation file in quiet mode without restarting the computer, type:

windows6.0-kb948465-x86.exe /quiet /norestart

Options Description

/forcerestart

If a restart is required, this option forces any open applications or documents to close.

/nodialog

Suppresses the success or failure dialog box at the end of the installation.

/norestart

Does not restart the computer after the installation is complete, even if a restart is required to complete the installation. You should use this option in conjunction with the /quiet option.

/promptrestart

If a restart is required, a dialog box notifies the user that a restart is required to complete Setup. You should use this option in conjunction with the /quiet option.

/quiet

Runs the installation in quiet mode. This mode shows no user interface during the installation of the updates. This is the same as unattended mode, except that the user interface is hidden. No prompts will appear during the installation process except the success or failure dialog box at the end of the installation. To suppress this dialog box, you must also specify the /nodialog option.

/unattend

Installs the service pack in unattended mode. Only critical error prompts and a progress bar will appear during the installation. For example, Microsoft Software License Terms is not shown, and the computer will be automatically restarted.

/warnrestart[:<seconds>]

If a restart is required, a dialog box notifies the user that the computer will restart in the specified number of seconds. The user can either cancel the restart or restart the computer immediately. The default setting for the automatic restart is 30 seconds.

/wsus

Returns a failure code if the previous installation attempt failed. This option is needed only when you are deploying SP2 in a Windows Server Update Services (WSUS), SMS, or System Center Configuration Manager environment, or in any non-Microsoft product that uses the Windows Update Agent to report installation success.

/? or /help

Displays command usage.

Large-scale scenarios

The following scenarios are applicable to businesses that want to deploy SP2 to multiple computers or deploy custom images, or both. We recommend that you use the SP2 integrated DVD to install SP2. Although it is not recommended, if you have custom Windows Server 2008 images that you want to update, you can boot the Windows image, apply the service pack, and then recapture the image. This online method is the only way to update images with SP2; SP2 cannot be installed to or uninstalled from an offline image of Windows Server 2008. You will need to obtain the latest version of the Windows OPK or Windows AIK.

The Microsoft Deployment Toolkit (https://go.microsoft.com/fwlink/?LinkId=108442) is the recommended methodology and solution to help you deploy Windows Server 2008. This toolkit can assist you in building and deploying custom images, including zero-touch deployments using Systems Management Server 2003 and System Center Configuration Manager 2007.

In this section:

  • Scenario 3: Creating or updating a custom image

  • Scenario 4: Deploying by using WSUS

  • Scenario 5: Deploying SP2 by using Windows Deployment Services

  • Scenario 6: Deploying SP2 by using SMS 2003 or System Center Configuration Manager

Scenario 3: Creating or updating a custom image

Use this installation method if you have an automated process for reproducing images.

When capturing custom images, you can use the Windows OPK or Windows AIK that was released for Windows Server 2008. To update an existing Windows Server 2008 image, boot into the image and then update it with SP2. You can only use an online method to update images with SP2. Also, you cannot install or uninstall SP2 from an offline image of Windows Server 2008. For example, there is no comparable support for the /integrate option from previous versions of Windows.

Note

You can reduce the size of the image before you reproduce it by running the compcln.exe command, which removes the files that were archived during the SP2 installation. For more information, see Windows Component Clean Tool.

Scenario 4: Deploying by using WSUS

WSUS enables you to deploy the latest Microsoft product updates to computers running the Windows operating system. By using WSUS, you can fully manage the distribution of updates that are released through Microsoft Update to computers in your network. For general information about WSUS, see https://go.microsoft.com/fwlink/?LinkID=94244.

Before you begin, note the following:

  • We recommend that you deploy the KB947821 update to your server computers before you deploy SP2. This update is available from the Microsoft Download Center (https://go.microsoft.com/fwlink/?LinkId=109180), and the Windows6.0-KB947821-NNN.msu file will ensure that each computer is ready to be updated.

  • If your WSUS server is running Windows Server 2003, you will need to install an update to ensure that SP2 is downloaded successfully. For more information, see Knowledge Base article 938759 (https://go.microsoft.com/fwlink/?LinkId=108519).

  • If your organization is using the Service Pack Blocker Tool to block the user from installing SP2, publishing the service pack to WSUS will automatically override the block, and SP2 will be installed.

Eventually, SP2 will synch automatically to your WSUS server as long as the server is configured to synchronize Windows Server 2008 service packs. Until then, use the following steps to manually import the service pack from the Microsoft Update Catalog site. The package that is installed contains both the prerequisite packages and SP2. This entire package will be downloaded to each destination computer, unlike with Windows Update, where only the components that are needed for a specific computer are downloaded.

To manually import SP2

  1. Open the WSUS Administrator console, expand the Update Services node, and then expand the node for the WSUS server.

  2. Right-click the Updates node and click Import Updates.

  3. In the Microsoft Updates Catalog web site, search for Vista SP2.

  4. In the results, click Add to add one or more of the following updates to your basket:
    Windows Server 2008 Service Pack 2 – Standalone (x86)
    Windows Server 2008 Service Pack 2 – Standalone (x64)
    Windows Server 2008 Service Pack 2 – Standalone (ia64)

  5. Click View basket.

  6. Confirm your selections and click Import to import these packages.

Scenario 5: Deploying SP2 by using Windows Deployment Services

This scenario explains how to use Windows Deployment Services to install an integrated version of Windows Server 2008 with SP2. However, it does not explain how to set up Windows Deployment Services. For more information, see the following step-by-step guides (depending on which version of Windows Deployment Services you have):

To deploy an image of Windows Server 2008 with SP2, you can do either of the following:

  • Add the Install.wim image from the DVD that contains the integrated version of Windows Server 2008 SP2 to your Windows Deployment Services server.

  • Create a customized install image from a reference computer, and then add it to your Windows Deployment Services server by using the following procedures to create a capture image and reference computer, and to create an install image that contains the new image.

To create a capture image and a reference computer

  1. Add the Boot.wim file located in the \Sources folder on the Windows Server 2008 with SP2 DVD to your Windows Deployment Services server.

  2. Create a capture image from the Boot.wim file, and then add it to the Windows Deployment Services server.

  3. Create a reference computer that contains Windows Server 2008, SP2, and any programs and settings that you want to include in the image.

  4. At the command prompt, change directories to \Windows\System32\Sysprep.

  5. Run the following command: sysprep /oobe /generalize /reboot

To create an install image that contains the new image

  1. Restart the computer, and then press F12.

  2. Select the capture image that you created in step 2 in the preceding procedure.

  3. In the Image Capture Wizard, select the appropriate drive, and then provide a name and description for the image. Click Next to continue.

Important

You will only see drives that contain operating systems prepared with Sysprep.

  1. Click Browse and then browse to a local location where you want to store the captured install image.

Important

You must enter a local location to save the new image; otherwise, you will not be able to capture the image. In the event of a network malfunction, this will prevent the image from being corrupted.

  1. Type a name for the image by using the .wim file name extension, and then click Save.

Important

You must use the .wim file name extension; otherwise, the capture will fail.

  1. Follow the rest of the instructions in the Image Capture Wizard.

  2. Now that you have the custom install image on your server, you can perform a Pre-Boot Execution Environment (PXE) boot on a client computer and install the image. For more information, use the steps in the Windows Deployment Services Step-by-Step Guide (https://go.microsoft.com/fwlink/?LinkId=84628)

Scenario 6: Deploying SP2 by using SMS 2003 or System Center Configuration Manager

You can deploy SP2 with System Center Configuration Manager 2007, System Center Essentials, or SMS 2003. For a description of the options you can use to install SP2 (especially the /wsus option), see the Command-line options section earlier in this guide.

  • Configuration Manager 2007. You have two options when deploying SP2 with Configuration Manager. The first option is to distribute the software by creating a software distribution package and advertisement. For more information about this option, see "Software Distribution in Configuration Manager" (https://go.microsoft.com/fwlink/?LinkId=109191). Or you can deploy SP2 as a software update by using Software Updates Management with Configuration Manager 2007. The main advantage to this second method is that there are no command-line settings to configure or detection logic to author. In Configuration Manager 2007, SP2 will be listed as an available update after a successful sync from the Software Update Point. For more about this option, see "Software Updates in Configuration Manager" (https://go.microsoft.com/fwlink/?LinkId=109202).

  • System Center Essentials. System Center Essentials is a new management solution in the System Center family of IT systems management products, specifically designed for IT professionals working in midsize businesses. For more information about System Center Essentials, download "Overview: System Center Essentials 2007" (https://go.microsoft.com/fwlink/?LinkID=89185).

  • SMS 2003. You have two options when deploying SP2 with SMS. You can distribute the software by creating a software distribution package and advertisement. For more information about this option, see "Distribute Software" (https://go.microsoft.com/fwlink/?LinkId=109218). Or you can deploy SP2 as a software update by using the Inventory Tool for Microsoft Updates (ITMU). For more information about deploying software updates by using SMS 2003 and ITMU, see the Microsoft TechNet article "SMS 2003 Inventory Tool for Microsoft Updates" (https://go.microsoft.com/fwlink/?LinkId=108463).

Before you begin deployment with any of these tools, note the following two issues:

First, when using Configuration Manager 2007 or SMS, if a computer has a problematic driver (as discussed previously in this guide), you will not receive a warning or error preventing you from installing on the computer. To minimize problematic driver issues for SP2, do the following:

  1. Prepare your Helpdesk staff with information about how to recognize and correct problematic driver issues.

  2. Test SP2 installations before deployment. If needed, install updated drivers from Windows Update or hardware vendors as they become available.

  3. Install the SP2 update on your Software Update Points.

  4. Configure Configuration Manager 2007 or SMS collections and your Software Update Points as needed, to deploy SP2 to client computers gradually.

For computers that have problematic drivers for which updates are not available, you will need to correct driver issues after installing SP2. For more information, see https://go.microsoft.com/fwlink/?LinkId=113723.

Second, when using each of these tools on a computer running Windows Server 2003, you must install the KB938759 update https://go.microsoft.com/fwlink/?LinkId=108519) to ensure that SP2 is downloaded successfully. For SMS and Configuration Manager, you must apply this update to every site server, software update point, and administration console. Note that this update is already included in Windows Server 2008 and Windows Server 2008, and that this update is not available for Windows XP. In addition, you must start the Distribute Software Update Wizard from a computer running Windows Server 2003 (with KB 938759 applied), Windows Vista, or Windows Server 2008.

Windows Component Clean Tool

The Windows Component Clean Tool (COMPCLN.exe) can be used to remove the files that are archived after Windows Vista SP2 or Windows Server 2008 SP2 is applied. It also removes the files that were archived after Windows Vista SP1 was applied, if they are found on the system. Running this tool is optional.

Installing Windows Server 2008 service packs increases the amount of disk space that is used by the operating system. This space is used to archive files so that the service pack can be uninstalled. Typically, you should run COMPCLN.exe if you want to reclaim this disk space after applying SP2 and if you will not need to uninstall SP2. You cannot uninstall Windows Vista SP2 or Windows Server 2008 SP2 after you run this tool on an image.

This tool can be used online or offline.

Option Description

/? or /h

Displays this list of command-line options.

/o:[offline_Windows_directory_path]

Specifies the path to the Windows directory of the offline Windows partition.

/quiet

Runs in quiet mode. No console output is provided.

/hide

Hides all packages (service packs) that are cleaned up.

/verbose:<log_file>

Provides additional diagnostic data in the log file.

Important

Upon completion, you will not be able to remove Windows Vista SP2 or Windows Server 2008 SP2 from the computer online or offline.

Uninstalling Windows Server 2008 SP2

You can remove Windows Server 2008 SP2 by using either Programs and Features (in Control Panel) or the command line. Note, however, that you cannot uninstall SP2 offline by using any method. You also cannot uninstall the service pack and other updates that were installed by using an integrated installation.

To uninstall SP2 by using Programs and Features

  1. Open Control Panel, click Programs, and then click View Installed Updates.

  2. In the Microsoft Windows list, right-click Service Pack for Microsoft Windows (KB948465), and then click Uninstall.

  3. When prompted, restart the computer.

Uninstall Windows Server 2008 SP2 from the command line

You can remove Windows Server 2008 SP2 from the command line by either specifying the path to the package that was used for installation (the path to the expanded .cab file), or by specifying the package identity (the package name).

Option 1: Using the package that was used for installation

  1. Open an elevated Command Prompt window (click Start, type command in the Start Search box, right-click Command Prompt, and then click Run as administrator).

  2. Run the following command, assuming that Windows6.0-KB948465-NNN.exe is in the C:\temp folder:
    C:\temp\Windows6.0-KB948465-NNN.exe /x:C:\temp

    Where NNN is x86, x64, or ia64.

  3. To create a sandbox (a virtual environment), type:
    md <sandbox>

  4. To remove SP2, type:
    start /w pkgmgr.exe /m:c:\temp\Windows6.0-KB948465-NNN.cab /up /s:<sandbox>

  5. After Pkgmgr.exe completes, you will be prompted to restart the computer (unless you specified the /quiet option).

Option 2: Using the package identity

  1. Open an elevated Command Prompt window (click Start, type command in the Start Search box, right-click Command Prompt, and then click Run as administrator).

  2. Run either of the following commands:

    • Using the 5 language package: start /w pkgmgr /up /p:"VistaSP2-KB948465~31bf3856ad364e35~NNN~~6.0.0.QQQQQ"

    • Using the package that contains all languages: start /w pkgmgr /up /p:"VistaSP2-KB948465~31bf3856ad364e35~NNN~~6.0.1.QQQQQ"

    Where NNN is x86, x64, or ia64 and QQQQQ is the build number..

  3. After Pkgmgr.exe completes, you will be prompted to restart the computer (unless you specified the /quiet option).

Troubleshooting

To confirm that SP2 is installed, right-click Computer and then click Properties. You will find a reference to the service pack in the Windows Edition section.

When installing SP2, some computers may run into issues that block the installation or otherwise cause it to fail. These issues may include the following:

  • A problematic BIOS or application

  • A corrupted hard disk

  • Memory failures

  • Software and file system synchronization issues. For performance reasons, the file system keeps a copy of the contents of some files in the memory, and it can take a while for these contents to be written back to the hard disk. Therefore, sometimes the contents of the files on the hard disk may be slightly out of synchronization with the memory.

To work around installation problems, perform the following steps in the specified order:

  1. Ensure that you have enough disk space, as specified in the "Check disk space requirements" table under Perform pre-deployment tasks earlier in this guide. Then restart the computer and try again to install SP2. This will ensure that all files are synchronized properly.

  2. If the installation still fails, download and extract the KB947821 update from the Microsoft Download Center. The Windows6.0-KB947821-NNN.msu file will ensure that the computer is ready to be updated. Then try again to install SP2. For information about this update, including information about how to obtain it, see https://go.microsoft.com/fwlink/?LinkId=109180.

  3. If the installation still fails, open an elevated Command Prompt window, and then run the chkdsk /f command. The Chkdsk tool checks the file system and metadata for errors, and then it fixes the errors, if possible. Then try again to install SP2.

  4. If the installation still fails, open an elevated Command Prompt window, and then run the MdSched.exe command. The Windows Memory Diagnostic tool tests the random access memory (RAM) on your computer for errors. Then try again to install SP2.