Security Rollup Package
Posted 16 October 2002 - 04:35 PM
Posted 24 November 2002 - 09:16 PM
Installing Windows 2000 with Hotfixes
This scenario explains how to create a combination installation of Windows 2000 integrated with SP3 and post-SP3 hotfixes in a shared distribution folder on a network. You do not need to perform separate installations of either Windows 2000 or the Windows 2000 hotfixes.
An attempt to slipstream an SP3 hotfix into an integrated SP3 shared distribution folder might cause Windows 2000 to stop working (because of the SP3.cat file getting overwritten and SP3 files becoming untrusted). For more information on this issue, see article Q290074, "Slipstreaming Earlier Fixes Into an Integrated Installation Share Breaks the Share," in the Microsoft Knowledge Base.
· This process installs the Windows 2000 hotfixes during Windows 2000 Setup.
· Because Windows 2000 Setup requires the 8.3 naming convention for all files and folders in the distribution folder, you must change the hotfix file names (from Q######_XXX_YYY_ZZZ_LL to Q######).
Preparing for the Installation
Before you run Windows 2000 Setup to deploy the installation of Windows 2000 and the Windows 2000 hotfixes across a network, you must copy the Windows 2000 and Windows 2000 hotfix installation files to a shared distribution folder and complete the following tasks.
If you are an OEM and plan to install any additional OEM files (for example, device driver, application, or component files) on the destination computers, create a $1 subfolder within the $OEM$ subfolder. The $1 subfolder maps to systemdrive, the destination drive for the Windows 2000 installation.
In the following procedure, "E:" represents the drive name of the network or computer where your distribution folder is located.
To install Windows 2000 integrated with SP3 and Windows 2000 hotfixes
1. Connect to the network or computer on which you want to create the distribution folder.
2. Create an i386 distribution folder by typing the following (using the appropriate drive name):
3. Use the command-line utility xcopy to copy the files and subfolders from the Windows 2000 integrated SP3 installation CD to the E:i386 folder. For example, if D: is your CD-ROM drive, type the following:
xcopy /e /i /v d:i386 e:i386
4. Edit E:i386dosnet.inf to add svcpack to the [OptionalSrcDirs] section as follows:
5. Create an E:i386svcpack folder. For example, to create a svcpack subfolder within the i386 folder, type the following:
6. Copy the hotfix executable program (Q######_XXX_YYY_ZZZ_LL.exe) to the E:i386svcpack folder by using the 8.3 naming format (Q######.exe), where ###### represents the actual hotfix number.
If you are deploying multiple hotfixes, rename all of the hotfix package files.
7. Expand the hotfix to a unique temporary location. For example, to expand the files to the sample folder, type the following:
8. Copy the catalog files (.cat) and hotfix binary files (such as .exe, .dll, .sys) as follows:
a. Copy Q######.cat to E:i386svcpack folder. If multiple hotfixes are to be deployed 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 format Q######.cat.
b. If any binary files exist in multiple packages, keep only the file with the highest version number.
c. Delete any binary files to be replaced in the i386 folder (usually you can identify the file name by an underscore at the end in the shared folder).
d. Copy the hotfix binary files and any subfolders for the hotfix to the i386 folder.
For example, i386uniproc* files in the hotfix need to be copied to the i386uniproc folder of the shared installation folder. There is no need to copy Update.exe, update.inf, spmsg.dll, spcustom.dll, spuninst.exe, update.ver, or symbols files.
10. Step 8 can be cumbersome if you are installing multiple hotfixes. This step is necessary only if the hotfixes contain updated system files that are required to start the computer to GUI mode or to prevent a virus attack during upgrade.
11. Delete the E:i386svcpack.in_ file.
12. Create a new svcpack.inf file at E:i386svcpack.inf, with the following content:
Q######.exe /switches (the recommended switches for hotfixes are /q /n /z)
If you will be deploying multiple hotfixes together, add an entry for each hotfix under [SetupHotfixesToRun] (as shown following this paragraph), and then add the Qchain.exe file to make sure that the correct files get replaced after the installation. You must also copy Qchain.exe to the svcpack folder. The following lines are a sample of the [SetupHotfixesToRun] section for an installation in which multiple hotfixes are installed.
Q123456.exe /switches (the recommended switches for hotfixes are /q /n /z)
Q123478.exe /switches (the recommended switches for hotfixes are /q /n /z)
Q123490.exe /switches (the recommended switches for hotfixes are /q /n /z)
13. If you will be installing multiple hotfixes, copy Qchain.exe to the E:i386svcpack folder.
You can find Qchain.exe on the Microsoft Web site.
Posted 25 November 2002 - 02:56 PM
Posted 28 December 2002 - 07:18 AM
The following value in the .SIF file used by Setup is
corrupted or missing:
Value 0 on the line in section [SourceDisksFiles]
with key "sp3.cab."
Setup cannot continue. To quit Setup, press F3.
Any idea what causes this ??
The line in txtsetup.sif looks like this:
sp3.cab = 2,,,,,,_x,39,0,0
Posted 05 January 2003 - 06:33 PM
I was using Datacenter server, wanted to update to SP3, and got "This service pack has not been qualified by your hardware vendor for installation on this copy of Windows 2000 Datacenter Server."
So I thought this may just be a driver I have loaded [or *some* kind of conflict] and thought, well, I can *extract* these files...
And I can simply dump the i386 directory from Service Pack 3 into the folder structure of my Windows 2000 Datacenter Server.
So i did this, and made a bootable iso with all files said and done.
I went to install using the cd, and i got that same error message you did.
When I did some more reading, it turns out that the correct action isn't to dump the i386 contents from the service pack into the original i386 tree...
But to run update -s:<dir>, where <dir> is the root directory of your original install.
This makes sense, when you think about it. First, we must realize that any of these win2k service packs have to work for every version from professional to advanced server. With Datacenter, it took me a *lot* of searching, but I *eventually* tripped across the page below...
Which had the exact same problem I had... except with a fix for update to allow Datacenter to work too.
Anyway, it's my thought that if, rather than copying the files into the source directory of your original win2k you should run update with the -s switch.
If I'm not mistaken you seen the suggestion to copy the files in an earlier post. I think the author *probably* meant [though i shouldn't speak for anybody] to run update -s:<dir> which would then copy the files over for you.
I hope I am understanding your problem correctly, and I further hope this is the solution
Posted 04 May 2003 - 11:24 AM
and if so does anyone know how?
Posted 22 August 2003 - 07:32 AM
Posted 22 August 2003 - 08:21 AM
I Get Page cannot be Displayed Trying to go to Anything under this Site. I can only find his pages in the little Cached link next to the real link, but I can't download the file from. Anybody know what happened to this guy? He is still on the Staff list at University of Wisconsin as of Aug 20.....
The actual link for that site is:
Just thought you all might want to know....
Posted 04 September 2003 - 07:17 AM
Posted 15 September 2003 - 01:44 AM
Posted 20 December 2004 - 09:00 PM
both IE6 and MP9 can be added to a windows installation by using a CMDLINES.TXT file which you would create in the $OEM$ folder
is it possible to add media player 9 and/or IE6 to a SlipStream of windows 2000 so it installs itself with windows 2000??
and if so does anyone know how?