Worldwide*
Quick Links|Microsoft.com Home
Microsoft*
Search Microsoft.com for:
OEM Partner Center 
|Your Profile|Site Map|Contact Us
Search OEM

Advanced Search
(Change Location)
Preinstalling Hotfixes
 
Slipstream Updates

The first option is to slipstream the hot fix into the I386 source that you will be installing from. These critical updates have to be slipstreamed into the installation share. They cannot be installed as traditional hotfixes from within Windows. The below example discusses installing Q823980. The hotfix is slipstreamed to an exiting networked opktools configuration. If you use a CD-based installation, follow the same process under the i386 folder of your installation CD.

  1. Create a C:\OPKTools\lang\eng\sku\pro.sp1\x86\i386\svcpack folder. For example, to create a svcpack subfolder in the i386 folder, type the following from a command prompt:

    MD C:\OPKTools\lang\eng\sku\pro.sp1\x86\i386\svcpack

  2. Copy the hotfix executable program (XXX-KBnnnnnn-YYY-ZZZ.exe) to the C:\OPKTools\lang\eng\sku\pro.sp1\x86\i386\svcpack folder by using the 8.3 naming format (Qnnnnnn.exe), where nnnnnn represents the actual hotfix number.

    copy WindowsXP-KB823980.exe C:\OPKTools\lang\eng\sku\pro.sp1\x86\i386\svcpack\Q823980.EXE

    If you are deploying multiple hotfixes, copy and rename all of the hotfix package files using the same method.

  3. Expand the hotfix contents to a unique temporary location. For example, to expand the files to a folder named c:\hold, type the following:

    C:\OPKTools\lang\eng\sku\pro.sp1\x86\i386\svcpack\Q823980.exe /X

    When prompted, enter c:\hold as the destination.

  4. Copy the catalog file and the associated hotfix binaries from the c:\hold folder as follows:

    Copy C:\hold\SP2\update\KB823980.cat to the C:\OPKTools\lang\eng\sku\pro.sp1\x86\i386\svcpack folder. If you will be deploying multiple hotfixes together, make sure that you copy all catalog files from each of the hotfixes to be deployed. Each hotfix has a unique catalog file that you must copy in the KBnnnnnn.cat format. If you are shipping the SP1 release of the OS use the SP2 folder contents. If you are shipping the RTM OS, use the SP1 folder contents.

  5. Copy the hotfix binaries into the C:\OPKTools\lang\eng\sku\pro.sp1\x86\i386 folder from the c:\hold\sp2 directory:

    copy c:\hold\sp2\rpcss.dll C:\OPKTools\lang\eng\sku\pro.sp1\x86\i386
    copy c:\hold\sp2\rpcrt4.dll C:\OPKTools\lang\eng\sku\pro.sp1\x86\i386
    copy c:\hold\sp2\ole32.dll C:\OPKTools\lang\eng\sku\pro.sp1\x86\i386

    You do not have to copy Update.exe, Update.inf, SPmsg.dll, SPcustom.dll, SPuninst.exe, Update.ver, or symbols (.pdb) files.

  6. Delete the following files:

    del C:\OPKTools\lang\eng\sku\pro.sp1\x86\i386\rpcss.dl_
    del C:\OPKTools\lang\eng\sku\pro.sp1\x86\i386\rpcrt4.dl_
    del C:\OPKTools\lang\eng\sku\pro.sp1\x86\i386\ole32.dl_

    Important: In the above step you are deleting the original windows files that will be replaced by the updated hotfix files. Failure to delete the original files will prevent the updated files from being used in place of the originals.

  7. Delete the original C:\OPKTools\lang\eng\sku\pro.sp1\x86\i386\svcpack.in_ file.

  8. Create a new Svcpack.inf file in C:\OPKTools\lang\eng\sku\pro.sp1\x86\i386, with the following content:

    [Version]
    Signature="$Windows NT$"
    BuildNumber=2600
    MajorVersion=5
    MinorVersion=1

    [SetupData]
    CatalogSubDir="i386\svcpack"

    [ProductCatalogsToInstall]
    kb823980.cat

    [SetupHotfixesToRun]
    Q823980.exe /q /n /z

    Important: If you plan to deploy multiple hotfixes together with this method, add an entry for each hotfix under both [ProductCatalogsToInstall] and [SetupHotfixesToRun] (as shown following this paragraph). The following lines are a sample of these sections for an installation that multiple hotfixes are installed in. If you are installing a service pack, you do not have to include details about the service pack because it is included in the installation independent of this process.

    [ProductCatalogsToInstall]
    KB123456.cat
    KB123478.cat
    KB123490.cat

    [SetupHotfixesToRun]
    Q123456.exe /q /n /z
    Q123478.exe /q /n /z
    Q123490.exe /q /n /z

  9. Edit the C:\OPKTools\lang\eng\sku\pro.sp1\x86\i386\Dosnet.inf file and make the following changes. Add the following section to the file:

    [OptionalSrcDirs] svcpack

  10. Use this Slipstreamed i386 for your installation.

The above critical updates whose installation process was unique can also be chained with the regular critical updates.

Return To Top

Winbom.ini Option

Use the Add an Application step of Setup Manager to add updates to your Configuration Set In the Application Preinstall section, below the Setup command section is a section to input command-line arguments. Here you can include the switches to install the update silently.

The following is an example of how it will look in the winbom.ini:

Example if the Updates will be located on a network share:

[OemRunOnce]
"KB824146","""\\OPKSERVER\OPKTools\Updates\KB824146.exe"" /Q /Z /N"
"Q323255","""\\OPKSERVER\OPKTools\Updates\Q323255.exe"" /Q /Z /N"

Example if the updates will be included on the local drive.

[OemRunOnce]
"KB824146","""C:\Sysprep\Updates\KB824146.exe"" /Q /Z /N"
"Q323255","""C:\Sysprep\Updates\Q323255.exe"" /Q /Z /N"

Rather than using Setup Manger to add the updates, they can be manually added to the Winbom.ini using Notepad.

Return To Top

Batch File Method

Instead of adding each individual update to the Winbom.ini, a single batch file can be used to automate the install of the updates.

  1. On the Technician Computer, open the command prompt.
  2. Change to the root of the folder that contains all the updates from the Supplement CD’s.
  3. Run the following command:

    DIR *.exe /s /b >> Update.bat

    This will redirect a bare recursive directory listing of the updates directory to a batch file named "Update.bat".

  4. Edit the batch file to add the desired switches (/q, /n, etc.) to the individual applications that will be preinstalled.

Example Update.bat if files will be on the local drive:
C:
CD\Sysprep\Update
KB824146.exe /Q /Z /N
Q323255.exe /Q /Z /N

Example Winbom.ini entry:

[OemRunOnce]
"Hot Fix","""C:\Windows\System32\cmd.exe""/c C:\Sysprep\Fix\updates.bat"

Example Updates.bat file if the files will be located on a network share

\\OPKSERVER\OPKTools\Updates\KB824146.exe /Q /Z /N
\\OPKSERVER\OPKTools\Updates\Q323255.exe /Q /Z /N

[OemRunOnce]
"Hot Fix","""C:\Windows\System32\cmd.exe""/c \\OPKSERVER\OPKTools\updates.bat"




©2009 Microsoft Corporation. All rights reserved. Terms of Use |Trademarks |Privacy Statement
Sign in to Windows Live ID