MIT - Massachusetts Institute of Technology



[pic]

Deployment Guide for the RC1 Version of Windows Vista Service Pack 1

Microsoft Corporation

Published: November 2007

Author: Trina Gorman

Abstract

This document provides IT administrators with instructions for planning and deploying Windows Vista Service Pack 1 (SP1). This guide includes technical information, procedures, and recommendations for installing Windows Vista SP1 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 Vista and update installations.

[pic]

Copyright Information

This document supports a preliminary release of a software product that may be changed substantially prior to final commercial release, and is the confidential and proprietary information of Microsoft Corporation. It is disclosed pursuant to a non-disclosure agreement between the recipient and Microsoft. This document is provided for informational purposes only and Microsoft makes no warranties, either express or implied, in this document. Information in this document, including URL and other Internet Web site references, is subject to change without notice. The entire risk of the use or the results from the use of this document remains with the user. Unless otherwise noted, the example companies, organizations, products, domain names, e-mail addresses, logos, people, places, and events depicted herein are fictitious, and no association with any real company, organization, product, domain name, e-mail address, logo, person, place, or event is intended or should be inferred. Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation.

Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property.

© 2007 Microsoft Corporation. All rights reserved.

Active Directory, Microsoft, MS-DOS, Visual Basic, Visual Studio, Windows, Windows NT, Active Directory, and Windows Server are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.

All other trademarks are property of their respective owners.

Contents

Deployment Guide for the RC1 Version of Windows Vista Service Pack 1 5

Glossary 5

Introduction to SP1 7

Before You Deploy SP1 7

Obtain the installation files 7

Pre-deployment tasks 7

Review changes to SP1 functionality 8

Customer Experience Improvement Program 8

WAIK and OPK 9

Group Policy management tools 9

Planning Your Deployment 10

Application compatibility 10

Installation options 11

Deploying SP1 12

Small-scale scenarios 13

Scenario 1: Installing using Windows Update 13

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

Command-line Options 15

Scenario 3: Installing using the integrated Windows Vista SP1 DVD 16

Large-scale scenarios 16

Scenario 4: Deploying using WSUS 16

Scenario 5: Creating an integrated custom image using the DVD 17

Scenario 6: Deploying using Windows Deployment Services 17

Scenario 7: Updating a custom image 19

Scenario 8: Deploying using SMS or SCCM 19

Uninstalling SP1 19

Deployment Guide for the RC1 Version of Windows Vista Service Pack 1

This is preliminary documentation and is subject to change. This document applies to the RC1 version of Windows Vista Service Pack 1. This guide contains information about functionality that may change, and some of the scenarios are not yet supported.

This document is for IT administrators who are deploying Windows Vista® Service Pack 1 (SP1). This guide includes technical information, procedures, and recommendations for installing SP1 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 Vista and update installations. For more information about deployment, see the following:

• Business Desktop Deployment 2007 Documentation ()

• Windows Vista Deployment Step-by-Step Guide ().

• System Center Configuration Manager 2007 ()

[pic]Note

To provide feedback, e-mail vistafb@.

Glossary

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

|Term |Definition |

|Integrated installation |Also known as "slipstream installation," in this installation method the service pack is |

| |integrated into the operating system, and therefore the operating system and service pack are |

| |installed simultaneously. You can use the integrated installation to upgrade computers and to |

| |perform new installations on computers that do not have an operating system. |

|Package |A collection of files that represents an update or optional component. Packages include the |

| |component files as well as the necessary metadata needed to manage it. The package can be |

| |compressed into single cabinet file (.cab) file. |

|Service pack |Service packs are the means by which product updates are distributed. Service packs are packages|

| |that may contain updates for system reliability, program compatibility, security, and more. All |

| |of these updates are bundled together for easier downloading and installation. A service package|

| |includes all fixes released to date as well as improvements to existing components. |

|Stand-alone package |A standalone package contains all of the files needed for the package to be installed on any |

| |computer. In contrast, when you install the SP1 package from Windows Update, only the files that|

| |are needed for that specific computer are downloaded and installed. For more information, see . |

|Update |• Noun: Refers to any update, update rollup, service pack, feature pack, critical update, |

| |security update, or hotfix that improves or fixes a software product that is released by |

| |Microsoft. For definitions of each of these types, see article 824684 in the Microsoft Knowledge|

| |Base (). |

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

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

| |product. Upgrading typically leaves existing data and preferences intact and replaces existing |

| |software with the newer version. |

| |• Verb: To update existing program files, folders, and registry entries to a more recent |

| |version. Upgrading (unlike performing a new installation) leaves existing settings and files in |

| |place. |

Introduction to SP1

Windows Vista SP1 is a set of updates and fixes for Windows Vista that addresses feedback from our customers (along with improvements that are delivered to users through Microsoft Update).

In addition to previously released updates, SP1 focuses on specific reliability and performance issues, supports new types of hardware, and adds support for a few emerging technology standards. For more information, see Windows Vista Service Pack Overview. SP1 also improves the IT administration experience. SP1 is not intended to be a vehicle for releasing new features—however, some existing components do gain enhanced functionality through SP1.

For more information about SP1, see the following:

• Overview of Windows Vista Service Pack 1 ()

• Selected improvements in Windows Vista SP1 on the Microsoft Connect Web site ()

Before You Deploy SP1

You should review the following information before you deploy SP1.

• Obtain the installation files

• Pre-deployment tasks

• Review changes to SP1 functionality

Obtain the installation files

• Windows Update. The public Windows Update server does not contain the RC1 version of SP1. You need to run a script that points your computer to a test server that contains SP1. With this change, the test Windows Update server will offer SP1 to your computer and once you accept the download, it will download SP1 to your computer. The release and availability of the script will be communicated to you in a separate document or email. When SP1 is released, the public Windows Update server will contain SP1.

• Stand-alone package The RC1 version of SP1 is available at the Microsoft Connect Web site. When SP1 is released, SP1 will be available from the Microsoft Download Center (and through other channels).

• Integrated installation. For the RC1 version of SP1, the integrated version (.iso files) of Windows Vista and SP1 will only be available on the Microsoft Connect Web site. When SP1 is released, SP1 will be integrated into the retail media. This is also available as part of the media kit for Volume License customers.

Pre-deployment tasks

You should perform the following tasks before you install SP1. If you are installing using Windows Update, then you should perform these tasks before you accept the Microsoft Software License Terms.

• Check disk space requirements. The following are the approximate disk space requirements for the system partition:

|Installation option |Approximate Requirement |

|Stand-alone installation |• x86-based - 4.5 GB |

| |• x64-based - 7.5 GB |

|Windows Update |• x86-based - 5 GB |

| |• x64-based - 8.5 GB |

[pic]Note

SP1 is only supported for x64-based and x86-based computers.

• Back up important data. A system restore point is automatically taken before the installation of SP1 begins (for Windows Update and stand-alone installations), which backs up system files. However, you may want to back up any user data before you begin.

• Read the release notes ().

• Disconnect any serial cable connected to a UPS devices. If you have an uninterruptible power supply (UPS) connected to your destination computer, disconnect the connecting serial cable before running Setup. Setup automatically attempts to detect devices connected to serial ports, and UPS equipment can cause problems with the detection process. It is fine to leave your computer connected to a UPS for power.

• Uninstall any previous versions of SP1. Microsoft does not support upgrading to this version from any previous version. For more information, see Uninstalling SP1.

• Plug laptops into an AC power source.

• Close all open programs. (including anti-virus programs)

Review changes to SP1 functionality

Customer Experience Improvement Program

To help improve the quality of SP1, installing RC1 version of SP1 will activate the Customer Experience Improvement Program (CEIP) for the computer regardless of the previous settings. This program will be activated until SP1 is uninstalled.

CEIP collects basic information about computers and how users use the product. CEIP may also collect limited information about other software that is running on the computer in order to improve how SP1 interacts with that software. These reports are sent to Microsoft, and are used to:

• Improve the features that are used most often.

• Create solutions for common issues.

CEIP does not take actions other than those described in the privacy policy, and you can choose to stop participating at any time after installing SP1. During the SP1 installation metrics are sent to Microsoft but none of these metrics contain personally identifiable information. For more information, see Microsoft Customer Experience Improvement Program ().

WAIK and OPK

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

• Boot critical driver tool (PostReflect.exe). PostRevlect is a command-lin tool used to reflect all boot critical device drivers out of the driver store in an offline image. Driver reflection is the process of installing a driver on a computer that might or might 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 SP1 is applied online and an image is created for the computer, this tool must be run on the offline Windows image because SP1 contains boot critical drivers for the hardware abstraction layer (HAL) and matching changes to the kernel. If the changed versions of boot-critical drivers for the HAL and the kernel are not correctly installed on the computer that you are deploying to, the operating system will not boot, nor will the image boot on any computer that has a different CPU or hardware configuration.

• Windows Vista SP1 File Removal tool (Vsp1cln.exe). An optional tool that you can run after you install SP1 to remove older versions of components that have been upgraded to new versions in SP1. You may want to run this file because installing SP1 increases the amount of disk space that is used by the operating system (since the older versions of components are stored in case you need to uninstall SP1). 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. You can use this file both online and offline, but you must have SP1 installed. You cannot uninstall SP1 after you run this tool on an image.

To obtain these kits:

• WAIK. The WAIK is located on the Connect website, in the Downloads section of Windows Beta Programs . The download file is named: "Windows (6001-16659-070916-1443) Windows AIK - EN-DE-ES-FR-JA".

• OPK. The OPK is available as a download to a limited number of OEMs and system builders. To obtain the OPK, contact Technical Account Manager.

Group Policy management tools

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, you should use Remote Desktop to connect to another computer to manage Group Policy. At a later date, an updated GPMC that contains greater functionality will be released as part of the Remote Server Administration Tools (RSAT). The updated GPMC will include additional functionality, including the ability to use Starter Group Policy objects (GPOs) which will allow you to more easily configure common scenarios. It will also include more powerful search and filter capabilities to make it easier for you to find and edit settings and add comments on at the setting (or the GPO itself).

[pic]Note

Deploying SP1 using Group Policy is not supported for the RC1 version of SP1.

For more information about these changes, see the release notes () and the Overview of Windows Vista Service Pack 1 ().

Planning Your Deployment

You have various options in terms of how to deploy SP1. To determine which deployment scenario or combination of scenarios is best for your organization, consider the following questions. Business Desktop Deployment 2007 () contains best practices and tools to help you answer the following questions.

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

• Where will the service pack files be stored?

• 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?

Application compatibility

A goal for SP1 is that applications that run on Windows Vista will continue to work after SP1 is installed. If you encounter compatibility issues during testing, you should report any bugs that you find.

Application Compatibility Toolkit (ACT) 5.0 was developed specifically to help you with this process. This toolkit helps you identify and manage your overall application portfolio, which reduces the cost and time involved in resolving issues. ACT 5.0 has several features including a new integrated interface that enables you to manage the entire toolkit from a single location. More importantly, you can run ACT 5.0 in your current environment (which can include Windows operating systems beginning with Windows 2000) so that you can test all operating system configurations before you begin deployment.

ACT 5.0 includes a variety of tools that can help you with testing and the next release of ACT will include a separate node for SP1 test results. For more information and to download ACT 5.0, see Application Compatibility ().

Installation options

There are three ways that you can deploy SP1:

|Method |Explanation |

|Installing SP1 using |Windows Update downloads the service pack to the computer and works within the operating system to install |

|Windows Update |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 the following scenarios: |

| |• Scenario 1: Installing using Windows Update |

|Installing SP1 using |In a stand-alone installation, you install the service pack to upgrade computers that already have an |

|the stand-alone |operating system. This method is recommended for: |

|installation |• Applying SP1 to computers without (or with limited) Internet connectivity |

| |• Applying the service pack to more than one computer using deployment tools such as Systems Management |

| |Server 2003 (SMS), WSUS Server. or System Center Configuration Manager 2007 (SCCM). |

| |The download size of the stand-alone package is larger than the package applied with Windows Update. |

| |This method is used in the following scenarios: |

| |• Scenario 2: Installing the stand-alone package |

| |• Scenario 4: Deploying using WSUS |

| |• Scenario 8: Deploying using SMS or SCCM |

|Installing SP1 using |An integrated installation (also known as "slipstream installation") means that the service pack is |

|the integrated |integrated into the operating system, and therefore the operating system and service pack are installed |

|installation |simultaneously. You can 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 SP1.) For an overview of supported |

| |upgrade paths from previous versions of Windows, see . |

| |If you choose this option, you cannot uninstall the service pack when the installation is complete (you |

| |would need to reinstall the entire operating system). |

| |This method is used in the following scenarios: |

| |• Scenario 3: Installing using the integrated Windows Vista SP1 DVD |

| |• Scenario 5: Creating an integrated custom image |

| |• Scenario 6: Deploying using Windows Deployment Services |

| |• Scenario 7: Updating a custom image |

Deploying SP1

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

Small-scale scenarios

• Scenario 1: Installing using Windows Update

• Scenario 2: Installing the stand-alone package

• Scenario 3: Installing using the integrated Windows Vista SP1 DVD

Large-scale scenarios

• Scenario 4: Deploying using WSUS

• Scenario 5: Creating an integrated custom image

• Scenario 6: Deploying using Windows Deployment Services

• Scenario 7: Updating a custom image

• Scenario 8: Deploying using SMS or SCCM

Small-scale scenarios

The following scenarios are applicable to businesses who want to deploy SP1 to a small number of computers.

Scenario 1: Installing 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. Assuming your computer has all latest updates except SP1, to install SP1 by using the test server of Windows Update, you may need to install as many as three prerequisite updates.

[pic]To install the service pack by using Windows Update

|1. Ensure that you are connected to the Internet. |

|2. Run the script given to you by Microsoft. |

|3. If your computer is set to automatically install updates, then when prompted, follow the instructions to install SP1. |

|Or, to initiate the installation, follow steps 4-7. |

|[pic]Note |

|Because of the prerequisite updates, if you do not initiate the installation, it may take more than 5 days before you are |

|prompted to install SP1 (1 day for each prerequisites, and 1 or more days to begin the download of SP1). |

|4. Click Start, click Control Panel, click Windows Update, and then click Check for Updates. The following updates may be |

|offered one at a time if they are not already installed: |

|• KB937287 (may require a restart before installing) |

|• KB935509 (only for Windows Vista Enterprise and Windows Vista Ultimate computers that are running BitLocker, and it |

|requires a restart.) |

|• KB938371 (requires a restart) |

|Repeat this step until you have installed each of these prerequisite updates. |

|5. Click Start, click Control Panel, click Windows Update, and then click Check for Updates. A list of updates is |

|displayed (one of which is KB936330). |

|6. Select the KB936330 update, which is SP1. Do not select any other updates, and then click Install. |

|7. Setup will proceed after the computer is restarted. During this second phase of installation, you will be prevented |

|from logging on while the service pack is installed. The installer will automatically restart the computer a few times |

|during this phase. |

|[pic]Caution |

|Do not restart the computer or turn the power off, even if the computer stays in an unknown state for a long time. If you |

|do, the computer may be in an unbootable state. |

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

|and you will receive a final dialog box which will indicate whether the upgrade was successful. |

|[pic]Note |

|To confirm SP1 is installed, right click on My Computer and click Properties. If the installation was successful, you will|

|find a reference to the service pack in the Windows Edition section. |

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

The stand-alone SP1 installer executable contains every file necessary to install the service pack. The executable is self-extracting and you can run it either from the command line or by double-clicking the file within Windows Explorer. The executable will automatically install the following updates if they are not already installed:

• KB937287

• KB937954

• KB935509

• KB938371

• KB936330 (SP1)

[pic]Note

KB937287, KB935509 and KB938371 are permanent packages and cannot be uninstalled. These are permanent in order to ensure that the computer functions properly if SP1 is later uninstalled

[pic]To install SP1 using the stand-alone package

|1. Copy the installation file (Windows6.0-KB936330-X86.exe or Windows6.0-KB936330-X64.exe) to a computer. |

|2. Run the package either using the command-line options listed below, or by double-clicking the file within Windows |

|Explorer. It may take several minutes to extract the installation files (and longer if you are installing 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 restart. |

|5. Setup will proceed after the computer is restarted. During this second phase of installation, you will be prevented |

|from logging on while the service pack is installed. The installer will automatically restart the computer a few 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 |

|and you will receive a final dialog box which will indicate whether the upgrade was successful. |

Command-line Options

You can use the following options to define the way the RC1 version of SP1 are installed. You can precede the following options with a forward slash (/) or a hyphen (-). The options are not case sensitive.

Syntax:

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

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

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

|Options |Description |

|/quiet |Runs the command 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 additionally specify |

| |/nodialog. |

|/norestart |Does not restart the computer after the installation is complete, even if a restart is required|

| |to complete the installation. This option is intended for use with the /quiet option. |

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

|/unattend |Installs the service pack in unattended mode. Only critical error prompts and a progress bar |

| |will appear during the installation. For example, the EULA is not shown and the computer will |

| |be automatically restarted. |

|/warnrestart[:] |If a restart is required, a dialog box notifies the user that the computer will restart in the |

| |specified seconds. The user can click to cancel or restart immediately. The default is 30 |

| |seconds. |

|/promptrestart |If a restart is required, a dialog box notifies the user that a restart is required to complete|

| |Setup. Intended for use with /quiet. |

|/nodialog |Suppresses the success or failure dialog at the end of installation. |

|/wsus |Returns a failure code if the previous installation attempt failed. This option is only needed |

| |when deploying in a WSUS, SMS or SCCM environment or any non-Microsoft product that uses the |

| |Windows Update Agent (WUA) to report installation success. |

|/? or /help |Displays command usage. |

Scenario 3: Installing using the integrated Windows Vista SP1 DVD

For RC1 version of SP1, the integrated version is available as an .iso file. Once you download the file, you can burn it to a DVD or apply it to a virtual machine.

When SP1 is released, SP1 will be added to the Windows Vista DVD. At that time, you can use this DVD to deploy the integrated operating system to your computers.

Large-scale scenarios

The following scenarios are applicable to businesses that want to deploy SP1 to multiple computers and/or want to deploy custom images. If you have custom Windows Vista images that you want to update, you can use the Windows Vista SP1 integrated DVD to recreate the custom images to include SP1 (Scenario 6). Optionally, you can boot the Windows image, apply the service pack, and then recapture the image (Scenario 7). You will need to obtain the latest version of the Windows OPK, or Windows AIK.

Business Desktop Deployment (BDD) 2007 () is the recommended methodology and solution to help you deploy Windows Vista. BDD 2007 can help you build custom images and deploy Windows Vista remotely. You can also use BDD for zero touch deployments using SMS and SCCM. A prerelease version of BDD will be available to support the RC1 version of SP1. Until then, you can use the latest version of Windows OPK or Windows AIK to initiate your deployments.

Scenario 4: Deploying using WSUS

This scenario is not supported for the RC1 version of SP1.

Windows Server Update Services (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 their network. For more information, see .

When SP1 is released, you will be able to download SP1 by synchronizing your WSUS servers.

[pic]Note

The package that is installed contains the prerequisite packages and SP1 together. 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.

[pic]Note

The destination computer will restart multiple times during the installation.

[pic]To deploy SP1 using WSUS

|1. Ensure that your WSUS server is configured to synchronize Windows Vista service packs. |

|2. Synchronize your WSUS server. |

|3. Locate the SP1 package and approve it for the appropriate target groups. |

Scenario 5: Creating an integrated custom image using the DVD

This scenario applies to you if you have an automated process for reproducing images. Once SP1 is released, you can use the DVD with the integrated version of Windows Vista and SP1 to recreate your images (using the same procedures that you used previously). To do this, you will need to install the updated Windows OPK and Windows AIK. Then use your answer file, configuration sets, and other resources to create the image. You will need to prepare the operating system using Sysprep and then recapture the updated image.

For instructions about how to do this, see the "Install Windows Vista Service Pack 1" topic of the Windows AIK documentation (Waik.chm) or the OPK (opk.chm).

Scenario 6: Deploying using Windows Deployment Services

This section explains how to use Windows Deployment Services to install an integrated version of Windows Vista with SP1. However, this section does not explain how to set up Windows Deployment Services. For more information, see the documentation that is included with the tool, and the following links (depending on which version you have):

• Windows Deployment Services Update Step-by-Step Guide for Windows Server 2003 ()

• Windows Deployment Services Role Step-by-Step Guide ()

To deploy an image of Windows Vista with SP1, you can:

• Add the Install.wim image from DVD that contains the integrated version of Windows Vista SP1 to your Windows Deployment Services server. (This scenario is not supported until RTW.)

• Create a customized installation image from a reference computer and then add it to your Windows Deployment Services server. For instructions, use the following procedure.

[pic]To create an install image that contains Windows Vista and SP1

|1. Add the Boot.wim located in the \Sources directory on the Windows Vista with SP1 DVD to your Windows Deployment |

|Services server. |

|2. Create a capture image from the Boot.wim and 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. From a command prompt, change directories to the \Windows\System32\Sysprep. |

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

|6. When the reference computer restarts, press F12. |

|7. In Windows Boot Manager, select the capture image that you created in Step 2. |

|8. Choose the appropriate drive, and then provide a name and description for the image. Click Next to continue. |

|[pic]Important |

|You will only see drives that contain operating systems prepared with Sysprep. If you do not run the command in step 4, |

|you will not see any drives to capture. |

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

|[pic]Important |

|You must enter a local location to save the new image or you will not be able to capture the image. This requirement is |

|enforced to avoid image corruption in the event of a network malfunction. |

|10. Type a name for the image (use the .wim file name extension), and then click Save. |

|11. Click Upload image to WDS server. |

|12. Type the name of the Windows Deployment Services server, and then click Connect. |

|13. If prompted for credentials, provide a user name and password for an account with sufficient permissions to connect to|

|the Windows Deployment Services server. |

|14. On the Image Group list, choose the image group in which to store the image and click Finish. |

|15. Now that you have the custom install image on your server, you can PXE boot a client computer and install the image. |

|For more information, use the steps in the "PXE booting a client to install an image" section of the appropriate guide: |

|• Windows Deployment Services Update Step-by-Step Guide for Windows Server 2003 |

|() |

|• Windows Deployment Services Role Step-by-Step Guide () |

Scenario 7: Updating a custom image

This scenario applies to you if you have an existing Windows image that you want to update. To update an existing custom Windows image, boot into the image, and install SP1. Then run Sysprep along with the new SP1 deployment tools (Postreflect.exe and Vsp1cln.exe) before you recapture the image. This "online" update method is the only supported method of updating images with SP1—you cannot install or uninstall SP1 to an existing image offline without booting into it.

For instructions on how to do this, see the "Install Windows Vista Service Pack 1" topic of the Windows AIK documentation (Waik.chm) or the OPK (opk.chm).

Scenario 8: Deploying using SMS or SCCM

For the RC1 version of SP1, you can deploy SP1 as a standard software distribution package using System Center Configuration Manager (ConfigMgr) 2007 or Microsoft Systems Management Server (SMS) 2003. See the Command-line options section for a description of the options you can use to install SP1.

Uninstalling SP1

You cannot upgrade from previous versions of SP1. Therefore, if you have installed a previous version on your computer, you have to uninstall the old version before installing the newer version. It is not possible to uninstall the permanent prerequisite updates (KB937287, KB935509 and KB938371). This is true for prerelease and final versions of SP1. However, you can uninstall KB936330 and KB937954. In addition, you cannot uninstall the service pack and other updates that were installed using an integrated installation.

[pic]Note

Uninstalling SP1 requires a minimum of 500 MB of free space on the system volume.

You can remove SP1 using the Programs and Features or using the command line.

[pic]To uninstall SP1 using Programs and Features

|1. Open Control Panel, and click Programs and Features. |

|2. Select View Installed Updates. |

|3. Under the list of Microsoft Windows, select Service Pack for Windows (KB936330). |

|4. On the top menu, click Uninstall. |

[pic]To uninstall SP1 using the command line

|1. Open an elevated command prompt (Click Start, type command in the Start Search box, right-click CommandPrompt, and then|

|click Run as administrator). |

|2. Run the following command (assuming Windows6.0-KB936330.exe is in C:\temp) C:\temp\Windows6.0-KB936330.exe /x:C:\temp |

|3. To create a sandbox, run md |

|4. To remove SP1, run start /w pkgmgr.exe /m:c:\temp\Windows6.0-KB936330.cab /up /s: |

|5. Once Pkgmgr.exe is done, you will be prompted to restart the computer (unless you specified the /quiet command with |

|Pkgmgr.) |

................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download