The Windows OEM Preinstallation Kit (OPK) and the Windows AIK have been updated for SP1. These kits include two new tools that you should use when creating images:

• Boot critical driver tool (PostReflect.exe). PostReflect is a command-line tool that is used to reflect all boot-critical device drivers out of the driver store in an offline image (see Terminology used in this guide for a definition of "offline"). Driver reflection is the process of installing a driver on a computer that may or may not have a device for that driver. Typically, this involves copying the driver files to the destination location so that the driver can be loaded by the operating system during the boot process. If all of the boot-critical drivers are reflected in the image, it can be deployed to various hardware configurations. After applying SP1 online and creating an image for the computer, you must run this tool on the offline Windows image. This is necessary because SP1 contains boot-critical drivers for the hardware abstraction layer (HAL) and matching changes to the kernel. If the updated versions of boot-critical drivers for the HAL and the kernel are not correctly installed on the computer that you are deploying SP1 to, the operating system will not boot on that computer or on any computer that has a different CPU or hardware configuration.
  
• Windows Vista SP1 File Removal tool (Vsp1cln.exe). Vsp1cln.exe is an optional tool that you can run after you install SP1. This tool removes older versions of components that have been updated in SP1, which are stored during the installation in case you need to uninstall SP1 later. Saving these older components increases the amount of disk space that is used. Typically, you should run Vsp1cln.exe if you want to reclaim this disk space after applying SP1 and if you will not need to uninstall SP1. Note, however, that you cannot uninstall SP1 after you run this tool. You can use this tool both online and offline, but you must have SP1 installed and you must use the correct version of the tool. If you are running this file on an offline image, you should use the Vsp1cln.exe included in the Windows OPK or AIK. However, if you are running this file online (on a computer that you are booted into), you should use the Vsp1cln.exe file located at %windir%\system32\vsp1cln.exe.
  

To download the Windows AIK, see http://go.microsoft.com/fwlink/?LinkID=54863. To obtain the OPK, contact your Technical Account Manager.

After you install SP1, you will be temporarily unable to manage domain-based Group Policy from that computer because of the following changes:

• The Group Policy Management Console (GPMC) will be uninstalled.
  
• Gpedit.msc will default to the Local Group Policy Editor.
  

Because of these changes, use Remote Desktop to connect to another computer to manage Group Policy. Shortly after the release of Windows Server 2008, an updated GPMC with greater functionality will be released as part of the Remote Server Administration Tools (RSAT). The updated GPMC will include the ability to use Starter Group Policy objects (GPOs), which enable you to configure common scenarios more easily. It will also include more powerful search and filter capabilities to make it easier to find and edit settings and add comments about the settings (or the GPO itself), as well as to set Group Policy Preferences (also known as PolicyMaker) to further enhance the manageability of Group Policy. For more information about Group Policy Preferences, see http://go.microsoft.com/fwlink/?LinkID=103735.

For more information about these changes, see the release notes (http://go.microsoft.com/fwlink/?LinkId=107076) and the Windows Vista Service Pack 1 Overview (http://go.microsoft.com/fwlink/?LinkID=100279).

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 SP1 by using Windows Update, you may need to install as many as four prerequisite updates: KB949939, KB937287, KB935509, and KB938371. These are permanent packages designed to ensure that the computer will still function properly if SP1 is later uninstalled. If your computer is not receiving SP1 from Windows Update, see KB article 948343 at http://go.microsoft.com/fwlink/?LinkId=115521 for possible reasons.

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 SP1.
     
   • To initiate the installation manually, perform steps 3 through 7.
     

     Note

     Because of the prerequisite updates, if you do not initiate the installation, it may take more than five days before you are prompted to install SP1 (one day for each prerequisite, and one or more days to begin the download of SP1). Also note that SP1 will not be offered to any computer that has a known problematic driver. For more information including a list of problematic drivers, see the “Method for Cause 5” section of KB article 948343 (http://go.microsoft.com/fwlink/?LinkId=115521).

3. Click Start, click Control Panel, double-click Windows Update, and then click Check for Updates. The following updates will be offered one at a time if they are not already installed:

   • KB949939 (This update may require a restart.)
     
   • KB937287 (This update may require a restart.)
     
   • KB935509 (This update is only for computers running Windows Vista Enterprise or Windows Vista Ultimate and requires a restart.)
     
   • KB938371 (This update requires a restart.)
     

   Repeat this step until you have installed each of these prerequisite updates, each time waiting 10 to 15 minutes for the installation of the update to complete.

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

5. Select the SP1 update (KB936330). If there are other updates displayed, make sure that SP1 is the only update selected, and then click Install.

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

7. 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 will automatically restart the computer several times during this process.

   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.

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

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

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. The executable file will automatically install the following updates if they are not already installed:

• KB937287*
  
• KB937954
  
• KB935509*
  
• KB938371*
  
• KB936330 (SP1)
  

  Note
  KB937287, KB935509, and KB938371 are permanent packages and cannot be uninstalled. These packages are permanent to ensure that the computer will still function properly if SP1 is later uninstalled.

  Note
  The KB949939 update is not required and it will not be installed when installing using the stand-alone package.

1. Ensure that your drivers are up to date. If there is a problematic driver on the computer, you will not receive a warning or error preventing you from installing SP1. For more information including a list of problematic drivers, see the “Method for Cause 5” section of KB article 948343 (http://go.microsoft.com/fwlink/?LinkId=115521).

2. Copy or download the installation file (Windows6.0-KB936330-X86.exe or Windows6.0-KB936330-X64.exe) to a computer. You can download SP1 from the Microsoft Download Center at http://go.microsoft.com/fwlink/?LinkId=107075.

3. 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 SP1 by using a shared network resource.

4. Follow the instructions in the Setup wizard.

5. 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. The installer will restart the computer several times during this phase.

6. Setup is complete when you are presented with the Windows logon prompt. At this time, you can log on to the computer.

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

Use the options listed and described in the following table to define the way SP1 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 XXX stands for either x86 or x64.

Syntax:

windows6.0-kb936330-XXX.exe [/quiet] [/nodialog] [/norestart]

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

For example, to run the installation file in quiet mode without restarting the computer, type windows6.0-kb936330-x86.exe /quiet /norestart.

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

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

After you install SP1, you should test to ensure that all of your hardware devices function properly, and correct any problematic drivers. For information about how to correct problematic drivers, see http://go.microsoft.com/fwlink/?LinkID=113062. Before you recapture the image, you must run Sysprep, Postrefllect.exe, and VSP1cln.exe (optionally). Note that when you run Vsp1cln.exe, you will not be able to uninstall SP1. For more specific instructions for this scenario, see "Install Windows Vista Service Pack 1" (http://go.microsoft.com/fwlink/?LinkId=113735). This topic is also included in the Windows AIK documentation (Waik.chm) and the OPK documentation (Opk.chm).

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 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 SP1. This update is available from the Microsoft Download Center (http://go.microsoft.com/fwlink/?LinkId=109180), and the Windows6.0-KB947821-XXX.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 SP1 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 SP1, publishing the service pack to WSUS will automatically override the block, and SP1 will be installed.
  

Eventually, SP1 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 SP1. 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.

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

4. In the results, click Add to add the following updates to your basket: Windows Vista Service Pack 1 – Standalone (x86) and/or Windows Vista Service Pack 1 – Standalone (x64)

5. Click View basket.

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

This scenario explains how to use Windows Deployment Services to install an integrated version of Windows Vista with SP1. 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 Update Step-by-Step Guide for Windows Server 2003 (http://go.microsoft.com/fwlink/?LinkId=66145)
  
• Windows Deployment Services Role Step-by-Step Guide (http://go.microsoft.com/fwlink/?LinkId=84628)
  

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

• Add the Install.wim image from the DVD that contains the integrated version of Windows Vista SP1 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.
  

1. Add the Boot.wim file located in the \Sources folder on the Windows Vista with SP1 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 Vista, SP1, 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

6. Run Postrefllect.exe and VSP1cln.exe offline by using the instructions in "Install Windows Vista Service Pack 1" (http://go.microsoft.com/fwlink/?LinkId=113735).

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.

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

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

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

7. 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 "PXE booting a client to install an image" section in one of the following two guides (depending on the version of Windows Server that you have):

   • Windows Deployment Services Update Step-by-Step Guide for Windows Server 2003 (http://go.microsoft.com/fwlink/?LinkId=66145)
     
   • Windows Deployment Services Role Step-by-Step Guide (http://go.microsoft.com/fwlink/?LinkId=84628)
     

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

• Configuration Manager 2007. You have two options when deploying SP1. 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). Or you can deploy SP1 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, SP1 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).
  
• SMS 2003. You have two options when deploying SP1. 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). Or you can deploy SP1 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" (http://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 SP1, do the following:

1. Prepare your Helpdesk staff with information about how to recognize and correct problematic driver issues.
   
2. Test SP1 installations before deployment. If needed, install updated drivers from Windows Update or hardware vendors as they become available.
   
3. Install the SP1 update on your Software Update Points.
   
4. Configure Configuration Manager 2007 or SMS collections and your Software Update Points as needed, to deploy SP1 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 SP1. For more information, see http://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 http://go.microsoft.com/fwlink/?LinkId=109188) to ensure that SP1 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.