Microsoft Windows XP Professional Resource Kit 2003
ISBN: N/A
EAN: N/A
EAN: N/A
Year: 2005
Pages: 338
Pages: 338
A service pack is a collection of updates pertaining to an operating system. These updates might address operating system reliability, application compatibility, setup, and security issues.
A hotfix is a collection of one or more files that can be applied to the operating system to correct a problem.
Typically, Microsoft packages service packs and hotfixes with a setup program that installs updates to your computer. The service pack or hotfix setup program copies files and updates settings automatically if your operating system configuration meets requirements specific to the service pack or hotfix. Typically, you restart your computer after installing a service pack or hotfix before the updates to your computer take effect.
| Warning | Apply a hotfix only if directed to do so by a Microsoft Knowledge Base article that describes your problem exactly or under the direction of your support representative. For information about the Microsoft Knowledge base, see the Microsoft Knowledge Base link on the Web Resources page at http://www.microsoft.com/windows/reskits/webresources |
Check the documentation that comes with your service pack or hotfix for the specific name of the setup program. You can usually run service pack or hotfix setup programs from the command prompt. In addition, you can customize your installation by using parameters.
In this chapter, ServicePack.exe refers to generic service pack setup programs. Table 4.2 lists parameters used for customizing Microsoft Windows 2000 Service Pack 1 and Windows 2000 Service Pack 2 installations. Before using these parameters, check your service pack documentation for changes.
| Command-Line Parameter | Description |
|---|---|
| -u | Run an unattended installation of the service pack. |
| -f | Force other applications to close at shutdown. After installing the service pack files and before restarting the computer, this parameter closes all applications. |
| -n | Do not back up files for Uninstall. In a typical service pack installation, files necessary for uninstalling the service pack are saved to your hard drive. If you use this parameter, you cannot uninstall the service pack. |
| -o | Overwrite OEM files without prompting. |
| -z | Do not restart the computer when the installation completes. |
| -q | Quiet mode no user interaction required. |
| -s:[x \distribution folder name] | Integrated installation mode maps to a distribution server location, where x is the letter assigned to the hard drive where your distribution share resides. |
If you use the -q or -u parameter to run ServicePack.exe in quiet or unattended mode and want to update OEM-supplied files, you must also use the -o parameter. If you do not use the -o parameter, files such as the hardware abstraction layer (HAL) and disk miniport drivers are not updated.
For the remainder of this chapter, Hotfix.exe generically refers to the hotfix setup program, and Q######_XXX_YYY_ZZZ_LL.exe (described below) is used for specific examples. If you plan to install a hotfix, check its documentation for any changes to this naming convention. Typically, Windows hotfix setup programs follow this naming convention:
Q######_XXX_YYY_ZZZ_LL.exe
In the preceding naming convention, the variables have the following meanings:
Q###### is the Microsoft Knowledge Base article number (for example, Q123456)
XXX is the platform or operating system
YYY is the service pack level
ZZZ is the hardware platform
LL is the language
To find an article in the Microsoft Knowledge Base, click the Microsoft Knowledge Base link on the Web Resources page at http://www.microsoft.com/windows/reskits/webresources
Table 4-3 lists parameters that you can use with Hotfix.exe to customize your hotfix installation. Before using these parameters, check your hotfix documentation for changes.
| Command-Line Parameter | Description |
|---|---|
| -y | Uninstall the hotfix (can be used with -m or -q). |
| -f | Force other applications to close at shutdown. After installing the hotfix files and before restarting the computer, this parameter closes all applications. |
| -n | Do not back up files for Uninstall. In a typical hotfix installation, files necessary for uninstalling the hotfix are saved to your hard drive. If you use this parameter, you cannot uninstall the hotfix. |
| -z | Do not restart the computer when the installation completes |
| -q | Quiet mode no user interaction required |
| -m | Unattended mode. Use this parameter to run an unattended installation of the hotfix. |
| -l | List installed hotfixes. This is useful to check for compatibility against the requirements of your hotfix. |
If your service pack version is newer than the hotfixes, the installation stops and silently exits if you included the -m or -q parameters. If you did not use these parameters, an error message appears, stating that the version is incorrect. In addition, if the language version of the hotfixes does not match the operating system s language, Setup is always interrupted. If no version conflict exists, Setup installs the hotfixes without user intervention.
To successfully deploy your service pack, prepare for the deployment. Assess the updates and enhancements contained in your service pack and determine how they will affect your organization. Also, you might wish to perform other steps when planning the deployment, including these important tasks:
Choose an installation method.
Choose deployment tools and files.
Check space requirements.
Test the deployment in your environment.
Depending on a number of factors, including the homogeneity of operating systems your computers are running and your company s security policies, you can choose one of the following methods to install your service pack:
The update installation is the standard method used to install Windows NT based service packs. Using this method, you install your service pack on your existing operating system.
The integrated installation was introduced with Windows 2000 Service Pack 1. Using this method, you simultaneously install the operating system and your service pack.
The combination installation was also introduced in Windows 2000 Service Pack 1. Using this method, you install your service pack with a variety of other components or third party applications by using a combination of update and integrated installation processes.
For more information about applying these installations and scenarios that might relate to your deployment, see Update Installation, Integrated Installation, and Combination Installation later in this chapter.
After you select your installation method and one of the associated scenarios for your installation, review the scenario to determine whether you might need one or more of the following deployment tools and files:
Microsoft Systems Management Server (SMS provides a variety of tools to help you deploy service packs. Using the SMS version 2.0 software distribution feature, you can simultaneously upgrade all of the SMS client computers in your site with your service pack. You can allow your users to run the service pack installation whenever they like, or you can schedule the service pack installation to run at a specific time. You can also schedule it to run on SMS client computers at a time when no users are logged on to the network.
| Note | SMS provides tools for upgrading your current computers, but not for the installation of new computers that do not have an operating system already installed. |
Setup Manager (Setupmgr.exe) is a wizard-based tool that can help you create or update the Unattend.txt answer file, the Cmdlines.txt file, and the network distribution share (a requirement if you want to include drivers or files from the network in your service pack installation). Setup Manager is available in the Deploy.cab file in the \Support\Tools folder on your Windows XP Professional operating system CD. For more information about Setup Manager, see Support Tools earlier in this chapter.
The Unattend.txt answer file identifies how Windows XP Professional Setup interacts with the distribution folders and files you create and it supplies information about your pre-installation requirements. The answer file also supplies Setup with all of the information that the end user is prompted to provide during a typical Windows XP Professional installation. For example, Unattend.txt contains a FullName entry in the [UserData] section, which prompts the user to provide a full name. You can create or modify the Unattend.txt answer file by using a text editor or Setup Manager. For a complete list of section headers and keys that you can use in your answer file, see Deploy.chm in the \Support\Tools folder on your Windows XP Professional operating system CD.
The Cmdlines.txt file contains a list of the commands that run during Windows XP Professional GUI mode setup. For example, these commands can run an application setup command or another executable file. You can create the Cmdlines.txt file by using a text editor or Setup Manager.
For more information about tools that to use when deploying a service pack or hotfix, see Support Tools earlier in this chapter.
A service pack requires a certain amount of space on your computer s hard drive for installation, storage, and to uninstall. Check your service pack documentation for space requirements, and then remember to reserve space for the Uninstall file if you wish to remove the service pack later.
Testing a service pack in your environment can include the following steps:
Use a cross-section of the types of computers deployed in your environment that will receive the service pack. Test computers that have a typical sample of software and hardware devices used in your organization.
Install your service pack on each of these computers in the same way that you expect to install it in your environment:
Update existing Windows XP Professional based computers to the service pack.
Upgrade existing computers that are running Windows 98, Windows 98 Second Edition (SE), Windows Millennium Edition (Me), Microsoft Windows NT Workstation 4.0, and Microsoft Windows 2000 Professional to Windows XP Professional integrated with the service pack.
Install Windows XP Professional integrated with the service pack on computers with no existing operating system (that is, a clean installation).
Verify that the applications and hardware continue to work as expected for the various scenarios.
During an update installation, a service pack is applied to a computer that is already running Windows XP Professional. The ServicePack.exe program automatically installs the updated system files and makes the necessary registry changes. After the computer restarts, the installation is completed and the operating system is running with an updated file set.
A number of methods for creating the update installation are supported since the release of Windows 2000 Service Pack 1. These include manually running the ServicePack.exe program or running a script that starts the ServicePack.exe program. You can use a combination of installation parameters whether you run ServicePack.exe manually or by using a script. Or you can use SMS to install a service pack. Also supported are a variety of distribution media, including CD ROM, network distribution share, Web download, and Microsoft Windows Installer. Table 4-4 lists the advantages and disadvantages of using ServicePack.exe versus using SMS.
| Method | Advantages | Disadvantages |
|---|---|---|
| ServicePack.exe | Parameters are available to customize your installation. Can be scripted to automate the installation. You do not need to purchase additional software to install the service pack on your computers. | You cannot set the installation to start and end at a specific time. |
| SMS | Installation is automated. Can be scheduled to start and stop the installation automatically (for example, at night when employees do not need their computers). | You must purchase SMS separately. |
For more information about using Systems Management Server, see your SMS product documentation.
The update installation scenarios described in this section include procedures you can use to meet your installation requirements. These scenarios focus on the network distribution share, the distribution media most commonly used by IT professionals. For the procedures in the following scenarios, drive E is a mapped network share or a local hard disk and drive D is the CD-ROM drive.
Scenario 1: Installing a service pack manually or by using a script
Scenario 2: Installing a service pack by using SMS
Scenario 3: Installing a hotfix
You can use a script or manually install a service pack on Windows XP Professional based computers from a network distribution share.
To install a service pack manually
Connect to the network or computer on which you want to create the distribution folder.
On the network distribution share, create a distribution folder for the service pack. For example, to create a distribution folder named SP, type mkdir E:\SP.
Copy the contents of your service pack onto the network distribution share.
or
To install the service pack from the network distribution share, run ServicePack.exe. For example, to install the service pack from a distribution folder named SP, type E:\SP\ServicePack.exe.
| Note | When running ServicePack.exe by using a script or batch file, include the following in your script: ServicePack.exe -u -q. This installs the service pack in unattended mode, with no user interaction. For more information about the parameters you can use with ServicePack.exe, see Table 4-2 earlier in this chapter. |
You can install a service pack on Windows XP Professional based SMS client computers from a network distribution share by using SMS.
| Warning | SMS 2.0 Service Pack 2 is required to support Windows XP Professional service pack installations. |
To use SMS to install a service pack
Create the SMS package by importing the package definition file for your service pack. In the package, provide the path to the service pack source files.
Distribute the SMS package to the distribution points.
Create the advertisement to notify SMS clients about the service pack.
To use SMS for an update installation, you must have an understanding of SMS as well as a working knowledge of software distribution. Also, your SMS infrastructure must be in place before you deploy the service pack. For more information about SMS, see your SMS product documentation.
When using SMS to distribute software, first create the SMS package, which contains the files and instructions that direct the software distribution process. When you create the SMS package, you specify the location of the package source files (where SMS obtains the files) and the package definition file (.pdf) for distributing the service pack.
A package definition file is a specially formatted file that contains all of the information necessary to create the SMS package. If you import this file, SMS immediately creates the package. After you use a package definition file to create a package, you can modify it the way you would any other SMS package.
Each predefined SMS package also contains SMS programs, which are command-line executables that run on each targeted computer to control the execution of the package. Each program is a different combination of options that you create for installing the package. For example, the package definition for the service pack includes programs that install the service pack with or without user input. These SMS programs must be compatible with the installation files for the package.
To create an SMS package
Connect to the network or computer on which you want to place the source files.
On the network or computer, create a source files directory for the service pack. For example, to create a source files directory named SP, type mkdir E:\SP.
Copy the service pack executable files to the source files directory that you created in step 2. For example, to copy the service pack executable files from a service pack CD in the CD ROM drive (D) to the source files directory named SP, type xcopy D:\ E:\SP /e.
In the SMS Administrator console, select Packages.
On the Action menu, point to New, and then click Package from Definition.
On the Welcome page, click Next.
Click Browse from the package definition list, and then navigate to the folder where the package definition file for the service pack was created. When you find the package definition file, click it to import the service pack package definition file, and then click Next.
On the Source Files page, click Always obtain files from a source directory, and then click Next.
In the Source directory box, enter the path to the package source files (see step 3).
Click Next, and then click Finish.
Select Programs.
In the details pane, double-click the service pack program.
In the Program Properties property sheet, on the General tab, verify that the predefined Command line is the correct setup command for your needs.
Click the Requirements, Environment, and Advanced tabs to check and modify the options that control the execution of your program. For more information about the options on these tabs, see your SMS product documentation.
Click OK.
| Warning | If you download your service pack from the Microsoft Windows Service Pack Web site, you must extract the compressed program file before you can copy it to the source files directory. Check the documentation included with your service pack for information about extracting the compressed program files. |
After you create the SMS package for the service pack, you can distribute the package to your distribution points. Distribution points are shares on site systems where SMS copies the package source files for access by the client computers.
To distribute an SMS package to distribution points
In the SMS Administrator console, select Packages, select the SMS package that you created for the service pack, and then select Distribution Points.
On the Action menu, point to New, and then click Distribution Points.
In the New Distribution Points wizard, click Next, and then select the distribution points you want to use.
All the distribution points for all sites are listed, so you can select all the distribution points now.
Click Finish.
The package is immediately distributed to the selected distribution points.
| Note | Your distribution points must have sufficient disk space for the SMS package. For instructions about how to check the disk space for distribution points from the SMS Administrator console, see your SMS product documentation. |
After you distribute the SMS package to the distribution points, you can create the advertisement that offers the package to the SMS clients.
To create an advertisement
Create a collection of SMS clients to receive the installation program. You can base the collection on a query or direct membership rules. For more information about creating a collection, see your SMS product documentation.
Right-click the collection that will receive the program, and then click All Tasks/Distribute Software.
In the Distribute Software Wizard, click Next.
Click Distribute an existing package, click the SMS package for the service pack, and then click Next.
In the Distribution Points dialog box, make sure the desired distribution points are selected, and then click Next.
In the Advertise a Program dialog box, click Yes. Advertise a program, click the program you want to advertise, and then click Next.
In the Advertisement Target dialog box, confirm that the collection of clients selected in step 2 is listed, and then click Next. If this collection is not listed, click Browse to find the collection you want.
In the Advertisement Name dialog box, fill in the advertisement name if appropriate, and then click Next.
Specify any subgroups that should also receive this advertisement, and then click Next.
Confirm or change the time the advertisement is offered and specify whether the advertisement should expire and when.
On the Assign Program page, click Yes to assign the program.
Click Next, and then click Finish.
SMS clients refresh the list of advertised programs on a configurable polling interval, set to 60 minutes by default. After the service pack advertisement is received on a client, it is either displayed for selection by users in the Advertised Program Wizard in Control Panel, or, if assigned (mandatory), runs according to the specified schedule.
You can install a hotfix on Windows 2000 based and Windows XP Professional based computers from a network distribution share.
The following procedure describes how to install a hotfix by running the Q######_XXX_YYY_ZZZ_LL.exe program.
To install a hotfix
Connect to the network or computer on which you want to create the distribution folder.
On the network distribution share, create a distribution folder for the hotfix files. For example, to create a distribution folder named Hotfix, type:
mkdir E:\Hotfix
Copy the hotfix executable file to the distribution folder that you created in step 2. For example, to copy the hotfix executable file to the distribution folder named Hotfix, type:
xcopy C:\Q######_XXX_YYY_ZZZ_LL.exe E:\Hotfix
To install the hotfix from the network distribution share, run the Q######_XXX_YYY_ZZ.exe program. For example, to install the hotfix from the distribution folder named Hotfix, type:
E:\Hotfix\Q######_XXX_YYY_ZZZ_LL.exe
You can create an integrated installation of the Windows XP Professional operating system and your service pack on a network distribution share. When you run the ServicePack.exe program in integrated mode, it applies the service pack directly to the Windows XP Professional installation files. Therefore, you do not need to perform separate installations of the operating system and your service pack.
| Warning | You cannot uninstall a service pack that you install in integrated mode. |
After the ServicePack.exe program creates the integrated installation, you can run Windows XP Professional Setup (Winnt32.exe) to install the operating system integrated with the service pack.
The following integrated installation scenarios focus on the network distribution share, the distribution media most commonly used by IT professionals. Depending on your installation requirements, choose from two integrated installation scenarios, which are detailed in the following sections. For the procedures in the following scenarios, drive E is a mapped network share or a local hard disk and drive D is the CD-ROM drive.
Scenario 1: Installing Windows XP Professional Integrated with the service pack from a network distribution share.
Scenario 2: Installing Windows XP Professional Integrated with the service pack by using Remote Installation Services (RIS).
You can create an integrated installation of the Windows XP Professional operating system and a service pack on a network distribution share. During an integrated installation, the service pack and Windows XP Professional Setup are installed at the same time.
To create an integrated installation of Windows XP Professional and your service pack
Connect to the network or computer on which you want to create the distribution folder.
On the network distribution share, create a distribution folder for the Windows XP Professional installation files. For example, to create a distribution folder named WinXP\i386 to mirror the location of the installation files on the operating system CD, type:
mkdir E:\WinXP\i386
Insert your Windows XP Professional operating system CD into the CD ROM drive, and then copy the contents of the \i386 folder on the CD to the distribution folder that you created in step 2. For example, to copy the \i386 folder from the Windows XP Professional operating system CD to the distribution folder named WinXP, type:
xcopy D:\i386 E:\WinXP\i386 /e
From your service pack CD, run the ServicePack.exe program in integrated mode by using ServicePack.exe -s. For example, to apply the service pack located in the CD ROM drive to the Windows XP Professional installation files located in the distribution folder named WinXP\i386, type:
D:\i386\ServicePack.exe -s:E:\WinXP\i386
Customize Windows XP Professional Setup, as needed.
After ServicePack.exe creates the integrated installation, you can deploy Windows XP Professional to your users computers from the network distribution share in attended or unattended mode. During the integrated installation process, Windows XP Professional Setup (Winnt32.exe) installs the integrated operating system with the service pack already applied.
When you run the ServicePack.exe program in integrated mode (ServicePack.exe -s:), a .log file is created in the systemroot folder on the computer that is running the ServicePack.exe program. If you plan to update more than one version of Windows XP Professional on this computer, you should rename the Svcpack.log file after you update each version. This ensures that you do not overwrite the current log file when you update additional versions of Windows XP Professional.
This scenario describes your options using Remote Installation Services (RIS) to install Windows XP Professional integrated with your service pack.
RIS supports two types of operating system images:
Remote Installation Setup (RISetup) images
Remote Installation Preparation (RIPrep) images
Installing Windows XP Professional from a RISetup image is similar to installing directly from the Windows XP Professional operating system CD, but in this case, the source files reside on the RIS server. You use RISetup.exe to create and install from the image.
A RIPrep image is an installation of Windows XP Professional that contains specific configuration settings made by the administrator. Typically, it also contains locally installed applications. In this scenario, you install your service pack to integrate it into the Windows XP Professional installation. You use RIPrep.exe to replicate the local (RIPrep) image to a RIS server, and then restore that image to a new computer on the network. RIPrep.exe can replicate single disk partitions only, and requires that your image reside on drive C.
For more information about RIS, including creating and installing RISetup and RIPrep images, see Automating and Customizing Installations in this book.
The combination installation uses both update and integrated installation processes to install your service pack with a variety of other components, such as the operating system, hotfixes, or additional Microsoft and third-party software that your installation might include.
You can install Windows XP Professional and hotfixes, as well as additional applications, in unattended mode.
Follow these steps to create a combination installation of the Windows XP Professional operating system and hotfixes on a network distribution share. You do not need to perform separate installations of the Windows XP Professional operating system or hotfixes. This process can only be accomplished in unattended mode.
Before you run Setup to install the Windows XP Professional operating system and hotfixes, you must change the Hotfix file names (from Q######_XXX_YYY_ZZZ_LL to Q######), because Windows XP Professional Setup requires the 8.3 naming convention for all files and folders in the distribution folder.
Follow these steps to create the distribution folder:
Connect to the network or computer on which you want to create the distribution folder.
On the network distribution share, create an \i386 distribution folder. For example, to create an \i386 distribution folder, type:
mkdir E:\i386
Within the \i386 folder created in step 2, create an \$OEM$ subfolder to contain any additional files, drivers, and folders you need for your installation. For example, to create an \$OEM$ subfolder within the \i386 folder, type:
mkdir E:\i386\$OEM$
To install additional files (for example, device driver, application, or component files) on users computers, within the \$OEM$ subfolder created in step 3, create a \$1 subfolder. For example, to create an \$1 subfolder within the \$OEM$ subfolder, type:
mkdir E:\i386\$OEM$\$1
The \$1 subfolder maps to the Windows XP Professional installation drive; for example drive C.
| Note | The $OEM$ and distribution folders are deleted from users computers after Windows XP Professional Setup is completed. |
Using Setup Manager or Notepad.exe, create an Unattend.txt file that contains the following section header, key, and value:
[Unattended]
OemPreinstall = Yes
For information about using Setup Manager to customize an Unattend.txt answer file, see Automating and Customizing Installations in this book.
For a complete reference to answer file sections headers and keys, see Deploy.chm, which is in the Deploy.cab file in the \Support\Tools folder on your operating system CD.
To run Windows XP Professional hotfixes during Windows XP Professional setup, add the following section header and line to the Cmdlines.txt file for each hotfix:
[Commands]
"Q###### -n -q -z"
Q###### is the Microsoft Knowledge Base article number (for example, Q123456). For example, to install the Q123456.exe hotfix, add the following line to the [Commands] section header in the Cmdlines.txt file:
[Commands]
"Q123456 -n -q -z"
For information about creating and using a Cmdlines.txt file, see Automating and Customizing Installations in this book.
You must copy all of the files needed for the installation to your distribution folder. The distribution folder contains the installation and executable files for the Windows XP Professional operating system and the Windows XP Professional hotfixes, as well as any device driver and other files that you want to install.
To copy the files necessary for the installation
Copy the contents of \i386 and all its subdirectories on the Windows XP Professional operating system CD to the \i386 distribution folder on your network distribution share.
Copy the following files to the \i386\$OEM$ subfolder on your network distribution share:
Hotfix executable file
Unattend.txt and Cmdlines.txt files
For information about files contained in the \i386\$OEM$ subfolder, see Automating and Customizing Installations in this book.
Copy any folders that contain additional device driver, application, or component files that you want to install on the system drive to the \i386\$OEM$\$1 subfolder on your network distribution share.
You can deploy the installation of the Windows XP Professional operating system and the Windows XP Professional hotfixes to your users computers from the network distribution share. During the installation process, Windows XP Professional Setup (Winnt32.exe in unattended mode) installs the operating system and applies the hotfixes.
To deploy the installation
Verify that the installation and executable files for the Windows XP Professional operating system and the Windows XP Professional hotfixes exist in your distribution folder.
Customize Windows XP Professional Setup as required.
Run Windows XP Professional Setup (Winnt32.exe) in unattended mode to install the Windows XP Professional operating system and the hotfixes from the network distribution share.
| Note | You can also use Winnt.exe for unattended installations of the operating system, but Winnt.exe is a less versatile tool than Winnt32.exe You cannot use Winnt.exe to perform an operation system upgrade, and you can only use Winnt.exe from within the MS-DOS preinstallation environment. |
For more information about running Winnt32.exe in unattended mode, see Automating and Customizing Installations in this book.