Windows Vista Service Pack 2 Deployment Guide

This guide is for IT administrators who are deploying Windows Vista® Service Pack 2 (SP2). This document includes technical information, procedures, and recommendations for installing Windows Vista SP2 in a business or corporate environment. Although this guide includes some basic operating system information, it assumes that you already have a working knowledge of Windows Vista and update installations. For more information about deployment, see the following Microsoft resources:

Microsoft® Deployment Toolkit Documentation (http://go.microsoft.com/fwlink/?LinkId=108442)
Windows Vista Deployment Step-by-Step Guide (http://go.microsoft.com/fwlink/?LinkID=66066)
Microsoft System Center Configuration Manager 2007 (http://go.microsoft.com/fwlink/?LinkId=100278)
Windows Automated Installation Kit (Windows AIK) (http://go.microsoft.com/fwlink/?LinkId=96105)
Windows Server® Update Services (WSUS) (http://go.microsoft.com/fwlink/?LinkID=94244)

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

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

Terminology used in this guide

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

Term	Definition
Integrated 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. This is also known as "slipstream installation."
Offline	In the context of updating images, "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 the ImageX tool in the Windows Automated Installation Kit (Windows AIK).
Online	In the context of updating images, "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 includes 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 Windows Vista 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 Windows Vista 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 (http://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 Windows Vista SP2
Before you deploy Windows Vista SP2
- Obtain the installation files
- Perform predeployment tasks
- Review changes to Windows Vista SP2 functionality
Planning to Deploy Windows Vista SP2
- Application compatibility
- Installation options
Deploying Windows Vista SP2
- Small-scale scenarios
- Large-scale scenarios
Uninstalling Windows Vista SP2
Troubleshooting

Windows Vista SP2 is a set of updates and fixes for Windows Vista 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, Windows Vista SP2 focuses on specific reliability and performance issues, support for new types of hardware, and support for select emerging technology standards. Note that although Windows Vista SP2 is not intended to be a vehicle for releasing new features, some existing components do gain enhanced functionality through Windows Vista SP2. For more information about Windows Vista SP2, see the following Microsoft TechNet article:

Notable Changes in Windows Server® 2008 Service Pack 2 and Windows Vista Service Pack 2 (http://go.microsoft.com/fwlink/?LinkId=134024)

Complete the following steps before you deploy Windows Vista SP2:

Obtain the installation files.
Perform predeployment tasks.
Review changes to Windows Vista SP2 functionality.

Obtain the installation files

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

Windows Update . Windows Update contains Windows Vista SP2, so Windows Vista SP2 will be installed automatically on computers that are set to receive automatic updates. However, before Windows Vista SP2 is installed, the user must accept the Microsoft Software License Terms.
Stand-alone package . You can download Windows Vista SP2 from the Microsoft Download Center at http://go.microsoft.com/fwlink/?LinkId=107075.
Integrated installation . Windows Vista SP2 is integrated into the Windows Vista 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. You can create your own integrated installation images by installing Service Pack 2 on a Windows Vista computer and then capturing the image.

Perform predeployment tasks

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

Verify that Windows Vista Service Pack 1 (SP1) has been installed. Windows Vista Service Pack 1 must be installed before you install Service Pack 2.

Check disk-space requirements. The following table lists the approximate disk-space requirements for the system partition. For more information about each method, see Installation options.

Note
These requirements will increase if there are language packs on your computer. Wave 0 includes language packs for English, German, Japanese, French and Spanish only. Wave 1 will include all supported languages.

Installation method

Approximate disk-space requirements

Stand-alone installation

x86-based: 1.8 gigabytes (GB) to 3 GB
x64-based: 3.2 GB to 5 GB

Windows Update

x86-based: 684 megabytes (MB)
x64-based: 863 MB

Integrated installation

x86-based: 10 GB
x64-based: 13 GB

Note
For more information about system requirements for Windows Vista, see http://go.microsoft.com/fwlink/?LinkId=108506.

Note
Windows Vista SP2 is supported only for x64-based and x86-based computers.

Back up important data. For Windows Update and stand-alone installations, Setup automatically creates a system restore point before the installation of Windows Vista SP2 begins; this restore point backs up system files. However, you may want to back up any user data before you begin installing Windows Vista SP2.
Read the release notes (http://go.microsoft.com/fwlink/?LinkId=129467).
Ensure that drivers are up to date. Check Windows Update and the hardware vendor for updated drivers. Windows Update and the Windows Vista SP2 standalone installer include new functionality that might block Windows Vista SP2 installation if a problematic driver is installed or it might provide a warning if there will be minor loss of functionality. If you are performing an integrated installation by using the DVD, you might not encounter these problems.
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.
Plug laptops into an AC power source.
Check for file 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 file corruption
1. Open an elevated Command Prompt window by clicking the Start button, typing command in the Start Search box, right-clicking Command Prompt, and then clicking 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, type the following at the command line: SFC /Scannow
To check and fix servicing store corruption
1. Download KB947821 from the Microsoft Download (http://go.microsoft.com/fwlink/?LinkId=109180).
2. Double-click Windows6.0-KB947821-NNN.msu (where NNN is either x86 or x64) file which will run the System Update Readiness Tool (CheckSur.exe).
3. After the command in step 2 completes, type the following at the command line: SFC /Scannow

Review changes to Windows Vista SP2 functionality

The following section outlines some of the changes in Windows Vista SP2. For a more complete list of the changes, see the Microsoft TechNet article "Notable Changes in Windows Vista SP2" (http://go.microsoft.com/fwlink/?LinkId=129469).

To determine which Windows Vista SP2 deployment scenario or combination of scenarios is best for your organization, consider the following questions. Note that the Microsoft Deployment Toolkit documentation (http://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 Vista with SP1, performing new installations, or upgrading a previous version of Windows to Windows Vista?
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" (http://go.microsoft.com/fwlink/?LinkID=71359).

Installation options

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

Method	Explanation
Installing Windows Vista 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 Windows Vista 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 Windows Vista SP2 to computers with limited or no Internet connectivity. Applying the service pack to more than one computer by using deployment tools such as Microsoft Systems Management Server (SMS) 2003, Microsoft® System Center Essentials, or System Center Configuration Manager 2007. This method is used in the following scenarios: Scenario 2: Installing the stand-alone package Scenario 4: Deploying by using WSUS Scenario 6: Deploying by using SMS or System Center Configuration Manager
Installing Windows Vista 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 Vista to Service Pack 2. For an overview of supported upgrade paths from previous versions of Windows, see http://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 by using Windows Deployment Services

Method

Explanation

Installing Windows Vista 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 Windows Vista 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 Windows Vista SP2 to computers with limited or no Internet connectivity.
Applying the service pack to more than one computer by using deployment tools such as Microsoft Systems Management Server (SMS) 2003, Microsoft® System Center Essentials, or System Center Configuration Manager 2007.

This method is used in the following scenarios:

Scenario 2: Installing the stand-alone package
Scenario 4: Deploying by using WSUS
Scenario 6: Deploying by using SMS or System Center Configuration Manager

Installing Windows Vista 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 Vista to Service Pack 2. For an overview of supported upgrade paths from previous versions of Windows, see http://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 by using Windows Deployment Services

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

Small-scale scenarios

Scenario 1: Installing by using Windows Update
Scenario 2: Installing the stand-alone package

Large-scale scenarios

Scenario 3: Creating or updating a custom image
Scenario 4: Deploying by using WSUS
Scenario 5: Deploying by using Windows Deployment Services
Scenario 6: Deploying by using SMS or System Center Configuration Manager

Small-scale scenarios

The following scenarios are applicable to businesses and individuals who want to deploy Windows Vista 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

Scenario 1: Installing by using Windows Update

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

To install the service pack by using Windows Update

Ensure that you are connected to the Internet.
Do one of the following:
- If your computer is set to install updates automatically, when prompted, follow the instructions to install Windows Vista SP2.
- To initiate the installation manually, perform steps 3 through 7.
Click Start, click Control Panel, double-click Windows Update, and then click Check for Updates.
Select the Service Pack 2 update (KB948465). If there are other updates displayed, make sure that Service Pack 2 is the only update selected, and then click Install.
After Setup downloads the update, accept the Microsoft Software License Terms and then click Install.

Setup will begin the installation. When prompted, click Restart now. Setup will prevent you from logging on while the service pack is being installed.

Caution
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.

When the Windows logon prompt appears, this indicates that Setup is completed. At this time, you can log on to the computer.
To confirm that Windows Vista 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 all of the files 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 Windows Vista SP2 by using the stand-alone package

Copy or download the installation file (Windows6.0-KB948465-X86.exe or Windows6.0-KB948465-X64.exe) to a computer. You can download Windows Vista SP2 from the Microsoft Download Center at http://go.microsoft.com/fwlink/?LinkId=107075.
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 Windows Vista SP2 by using a shared network resource.
Follow the instructions in the Setup wizard.
After the first phase of installation is complete, the computer will automatically restart so that updates can be configured.
Setup is complete when you are presented with the Windows logon prompt. At this time, you can log on to the computer.
To confirm that Windows Vista 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, described in the following table, to define the way Windows Vista 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, and NNN stands for either x86 or x64.

Syntax:

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 does not show a user interface during the installation of the updates. This is similar to unattended mode, except that the user interface is hidden during quiet mode. 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 Windows Vista 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 Windows Vista SP2 to multiple computers or deploy custom images, or both. We recommend that you use the Service Pack 2 integrated DVD to install Windows Vista SP2. Although it is not recommended, if you have custom Windows Vista 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 Windows Vista SP2; Service Pack 2 cannot be installed to or uninstalled from an offline image of Windows Vista. You will need to obtain the latest version of the Windows OPK or Windows AIK.

The Microsoft Deployment Toolkit (http://go.microsoft.com/fwlink/?LinkID=95464) is the recommended methodology and solution to help you deploy Windows Vista and 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 by using Windows Deployment Services
Scenario 6: Deploying by using SMS 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.

Note
Service Pack 1 must be installed before Service Pack 2 can be installed. These service packs must be installed online. They cannot be installed on an offline Windows image.

When capturing custom images, you can use the Windows AIK that was released for Windows Vista SP1 and Windows Server 2008. To update an existing Windows Vista RTM image, boot into the image and then update it with Windows Vista SP1 and SP2. To update an existing Windows Vista SP1 image, boot into the image and then update it with Service Pack 2. You can only use an online method to update images. Also, you cannot install or uninstall Service Pack 2 from an offline image of Windows Vista or Windows Server 2008. For example, there is no comparable support for the /integrate option from previous versions of Windows. If you do not wish to sequence the installation of SP1 and SP2 on a Windows Vista RTM computer, you can also reimage the computer with a Windows Vista SP2 complete operating-system image.

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 Windows Update to computers in your network. For general information about WSUS, see http://go.microsoft.com/fwlink/?LinkID=94244.

Before you begin, note the following:

We recommend that you deploy the KB947821 update to your client computers before you deploy Windows Vista SP2. This update is available from the Microsoft Download Center (http://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 Windows Vista SP2 is downloaded successfully. For more information, see Knowledge Base article 938759 (http://go.microsoft.com/fwlink/?LinkId=108519).
If your organization is using the Service Pack Blocker Tool to block the user from installing Windows Vista SP2, publishing the service pack to WSUS will automatically override the block, and Windows Vista SP2 will be installed.

Eventually, Windows Vista SP2 will synch automatically to your WSUS server as long as the server is configured to synchronize Windows Vista 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 Windows Vista 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 installed.

To manually import Windows Vista SP2

Open the WSUS Administrator console, expand the Update Services node, and then expand the node for the WSUS server.
Right-click the Updates node and click Import Updates.
In the Microsoft Updates Catalog web site, search for Vista SP2.
In the results, click Add to add the following updates to your basket: Windows Vista Service Pack 2 – Standalone (x86) and/or Windows Vista Service Pack 2 – Standalone (x64).
Click View basket.
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 Vista 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):

Windows Deployment Services Step-by-Step Guide (http://go.microsoft.com/fwlink/?LinkId=84628)

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

Add the Install.wim image file from the DVD that contains the integrated version of Windows Vista 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 a reference computer

Add the Boot.wim file located in the \Sources folder on the Windows Vista with SP2 DVD to your Windows Deployment Services server.
Create a capture image from the Boot.wim file, and then add it to the Windows Deployment Services server.
Create a reference computer that contains Windows Vista, Service Pack 2, and any programs and settings that you want to include in the image.
At the command prompt, change directories to \Windows\System32\Sysprep.
Run the following command: sysprep /oobe /generalize /reboot

To create an install image that contains the new image

Restart the computer, and then press F12.
Select the capture image that you created in step 2 in the preceding procedure.

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 the Sysprep tool.

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.

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.

Follow the rest of the instructions in the Image Capture Wizard.
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 following guide:
- Windows Deployment Services Step-by-Step Guide (http://go.microsoft.com/fwlink/?LinkId=84628)

Scenario 6: Deploying Windows Vista SP2 by using System Management Server or System Center Configuration Manager 2007

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

Configuration Manager 2007. You have two options when deploying Windows Vista 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" (http://go.microsoft.com/fwlink/?LinkId=109191). Alternatively, you can deploy Windows Vista 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, Windows Vista 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" (http://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" (http://go.microsoft.com/fwlink/?LinkID=89185).
System Management Server. You have two options when deploying Windows Vista SP2 with System Management Server. You can distribute the software by creating a software-distribution package and advertisement. For more information about this option, see "Distribute Software" (http://go.microsoft.com/fwlink/?LinkId=109218). Alternatively, you can deploy Windows Vista SP2 as a software update by using the Inventory Tool for Microsoft Updates (ITMU). For more information about deploying software updates by using System Management Server and ITMU, see the Microsoft TechNet article "SMS 2003 Inventory Tool for Microsoft Updates" (http://go.microsoft.com/fwlink/?LinkId=108463).

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

When using Configuration Manager 2007 or SMS 2003, if a computer has a problematic driver do the following:
1. Prepare your Helpdesk staff with information about how to recognize and correct problematic driver issues.
2. Test Windows Vista SP2 installations before deployment. If needed, install updated drivers from Windows Update or hardware vendors as they become available.
3. Install the Windows Vista SP2 update on your Software Update Points.
4. Configure Configuration Manager 2007 or System Management Server collections and your Software Update Points as needed, to deploy Windows Vista SP2 to client computers gradually.
Second, when using each of these tools on a computer running Windows Server 2003, you must install the KB938759 update http://go.microsoft.com/fwlink/?LinkId=129405) to ensure that Windows Vista 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 Vista 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.

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 Vista 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.

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

Important
You cannot uninstall Windows Vista SP2 or Windows Server 2008 SP2 if you ran the Windows Component Clean (COMPCLN) tool.

To uninstall Windows Vista SP2 by using Programs and Features

Open Control Panel, click Programs and Features, and then click View Installed Updates.
In the Microsoft Windows list, right-click Service Pack for Microsoft Windows (KB948465), and then click Uninstall.
When prompted, restart the computer.

Uninstall Windows Vista SP2 from the command line

You can remove Windows Vista 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

Open an elevated Command Prompt window, by clicking Start, typing cmd in the Start Search box, right-clicking Command Prompt, and then clicking Run as administrator.
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 or x64.
To create a sandbox, which is a virtual environment, type md <sandbox>.
To remove Windows Vista SP2, type start /w pkgmgr.exe /m:c:\temp\Windows6.0-KB948465-NNN.cab /up /s:<sandbox>.

Where NNN is x86 or x64.
After Pkgmgr.exe completes, you will be prompted to restart the computer, unless you specified the /quiet option.

Option 2: Using the package identity

Open an elevated Command Prompt window, by clickingStart, typing cmd in the Start Search box, right-clicking Command Prompt, and then clicking Run as administrator).
Run one 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 or x64, and QQQQQ is the build number.
After Pkgmgr.exe completes, you will be prompted to restart the computer, unless you specified the /quiet option.

To confirm that Windows Vista 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 Windows Vista SP2, some computers may run into issues that block the installation or otherwise cause it to fail. These issues may include the following:

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:

Ensure that you have enough disk space, as specified in the "Check disk space requirements" table under Perform predeployment tasks earlier in this guide. Then restart the computer and try again to install Windows Vista SP2. This will ensure that all files are synchronized properly.
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 Windows Vista SP2. For information about this update, including information about how to obtain it, see http://go.microsoft.com/fwlink/?LinkId=109180.
If you previously used Windows Update to try to install Windows Vista SP2, try using the Stand-alone package. You can download Windows Vista SP2 from the Microsoft Download Center at http://go.microsoft.com/fwlink/?LinkId=107075
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 Windows Vista SP2.
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 to install Windows Vista SP2 again.

About This Guide