Slipstream Office 2003 SP2

[IT Rider]

October Patch release Issues

I'm now receiving errors for slipstreaming the October patch releases. Any ideas?

[IT Rider]

Windows update error?

After applying all the office 2k3 updates to my installation build...I installed a new system with the runonce command setup. Everything installed perfect...however, when I go to windows update and use the all in one selection-->custom, it shows that I still need to have some office updates applied.

But, if I go to http://office.microsoft.com and check for updates directly from MS for my office package, it states everything is up to date.

Ideas?

[MyStur]

In the guide for office xp it says that we must change the last input

from

TRANSFORMS=C:\XPCD\$\$1\install\Applications\Office2003\Unattended.MST /qb-

to

TRANSFORMS=Unattended.MST /qb-

but i can not change the last.

what must i doo

i have office 2003 pro

[OverFlow]

Hello all

I have gotten a lot of useful stuff from here and thought i might give something back

this is a file called SlipOff.cmd it integrates service packs and hotfixes to office 2003

just put SlipOff in the folder where your service pack or hot fixes are extracted to and run it

Optionally you can add an argument for the folder that contains your office 2003 files

(SlipOff.cmd d:\my Office) or whatever if you dont it will check to see if they are at c:\office and ask for the location if not found.

notes if you wish to Slip service pack 2 extract SP2 in a folder by itself and run SlipOff from that folder

then run it from the folder containing the post SP2 extracted hotfixes.

It will list the number of hot fixes added and give an elapsed time

It will also create log files with the same name as the hotfix for trouble shooting

Thanks to all of you who have helped me without even knowing it.

a newer version is posted further down this page - link below

http://www.msfn.org/board/index.php?s=&amp...st&p=592679

SlipOff.cmd

Edited December 10, 2006 by OverFlow

[OverFlow]

Here is the fix for the slipstreamed office patches are not recognized by Microsoft update even though office update says its fine.

Microsoft Update checks the registry for patches in the add remove programs regkeys and if they are not listed there it says you need them. Well, if they are slipstreamed into the installation they are not going to be in add remove programs - go figure!

Solution: Install updates on one machine and export the resulting "missing" registry keys to a file that can be run after the slipstreamed office install, and before checking at Microsoft Updates. An 'example' file is attached but I recommend making your own.

My key was found here. >

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\9040110900063D11C8EF10054038389C\Patches]

Office.reg

Edited December 10, 2006 by OverFlow

[JTG]

It's hard to believe that we have to go thru this kind of crap when we are using an officially MS supported process. to build complete installation files. I found a number of posts in other forums that this has been a known issue with MS for quite some time now yet it's still unresolved. Thanks everyone for posting this info, I was starting to think I was loosing it until I found others were having the same problem. I am going to run some tests with WSUS but I am sure it will think the updates are required....

[pppx00]

I can't slipstream a lot of Hotfixes because I'm getting this ERROR:

No valid sequence could be found for the set of patches.

Here's a few ones that I can't slipstream:

-office2003-KB920103-FullFile-ENU

-office2003-KB923088-FullFile-ENU

-office2003-KB923094-FullFile-ENU

BTW. All this updates doesn't finish with the both "f", that's mean something?

[OverFlow]

I can't slipstream a lot of Hotfixes because I'm getting this ERROR:

No valid sequence could be found for the set of patches.

Here's a few ones that I can't slipstream:

-office2003-KB920103-FullFile-ENU

-office2003-KB923088-FullFile-ENU

-office2003-KB923094-FullFile-ENU

BTW. All this updates doesn't finish with the both "f", that's mean something?

here is the microsoft answer to your question

http://support.microsoft.com/kb/913754

[djackson]

This has probably been covered elsewhere, but there seems(?) to be an easier way to slipstream both hotfixs and servicepacks into the full Office 2003 suite administrative installs.

1. perform normal administrative install, ie setup.exe /a, into your prefered destination path, eg "x:\Office 2003"

2a. download and extract the full servicepacks required to your prefered destination path, eg "x:\Office 2003 SP"

2b. download and extract the all hotfixs required to your prefered destination path, eg "x:\Office 2003 HF"

3. in "x:\Office 2003 SP" you should have the servicepack/hotfix *.msp files + ohotfix.exe, ohotfix.ini, ohotfixr.dll

4. edit the following lines in ohotfix.ini (watch out for the difference between Office and Visio)

IsNormalUpdate=0 (where 0 = admin install, 1 = normal workstation install)
AdminUsesShortFilenames=1 (where 0 = Visio, 1 = Office [1 also works for FrontPage, Project, OneNote])
AdminPath=x:\Office 2003\PRO11.msi (x:\Office 2003\PRO11.msi = the destination msi file for the application you wish to update)

5. run ohotfix.exe (SP or HF), this will now slipstream any/all(?) .msp files into your Office application. You'll get a completion dialog at the end.

6. Burn to CD/DVD, and test running the setup.exe as normal.

You may be able to combine steps 2a and 2b and slipstream all msp files (both SP and HF) at the same time (untested), but I prefer to slipstream them separately.

I've tested this with Office, OneNote, Project, Visio and FrontPage under Windows XP, and slipstreamed servicepack 2 for each application + post SP2 hotfixs without issue. Have not tried slipstreaming hotfixs on top of hotfixs, it may work. I reslipstream all hotfixs over an admin install + SP.

However, the same reg file issues exist that were raised by OverFlow above. The Office update site is aware of the hotfixs, but Microsoft update is not. Go figure...

My unelegant workaround is

1. in a virtual PC install one application, ie, Office

2. go to Microsoft update, scan for updates, then install the updates

3. find and export the registry changes for that app for future use (you'll find them in a block, look for a hotfix number, eg, 924424)

I had probs with using the same registry entries for different apps, thats why I this is so tedious.

To test

4. reset your virtual PC to an Office free snapshot

5. install the same app from step 1 above

6. import the reg file from step 3 above

7. go to Office update, you're up to date (hopefully)

8. go to Microsoft update, you're up to date (hopefully)

I'm no expert on ohotfix.ini, I was just following the splipstream instructions in this post and saw the .ini file and thought "whats this for?" and started tinkering. Seemed to work for me.

As usual "caveat emptor" applies, ie, no care and no responsibility taken for damage caused to your PC setup during the creation of this process, always try it in a virtual PC first.

Hope this helps...

[OverFlow]

Two things DJackson

One; I didnt raise an issue. I pointed out the fix and gave an example.

You also misquoted me.

Two; my slipstream script is much easier to use than all of your instructions.

[OverFlow]

I updated the script so it will extract the hotfixes for us and if SP2 exists it will slip it in first then do the remaining hotfixes.

Just put it in the folder with the downloaded xxx-FullFile-xxx.exe updates and run it.

Optionally run it with an argument specifying your office 2003 folder (SlipOff.cmd d:\my Office)

Default is c:\office. You will still be prompted if needed.

It will also still create log files with the same name as the hotfix for trouble shooting

Be sure to read monnezza's Post here:

http://www.msfn.org/board/index.php?s=&amp...st&p=558964

After slipstreaming Update for InfoPath 2003 (KB920103) into Office 2003 Professional with SP2 there are two errors in PRO11.MSI. (really nice info and documentation!)

It is still neccessary to create a .reg file.

I install office to a virtual machine, run MS update, and then export the "patches" key to a file named 'Office.reg'. My key is located at. >

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\9040110900063D11C8EF10054038389C\Patches]

I just export the entire Key and then execute the resulting Office.reg file after installing my slipstreamed office and before using Microsoft Update.I just export the entire Key and then execute the resulting Office.reg file after installing my slipstreamed office and before using Microsoft Update.

This post has been edited by OverFlow: Dec 10 2006, 01:26 PM

I started a new thread for this --> http://www.msfn.org/board/index.php?showtopic=89038

SlipOff.cmd

Edited December 18, 2006 by OverFlow

[Pis19]

Hi everybody!

I don't know if this problem has already been solved, but I didn't find any solution at this time. The problem appears when I try to integrate SP2 and all the post SP2 hotfixes in Office 2003 CD, so to burn it and install it with everything integrated.

The problem is caused by the hotfixes that have two .msp inside. They are:

KB917151

KB921566

KB923272

KB924424

In the first three there are MSO.msp and PVMSO.msp, in the last one there are MSXML5.msp and PVMSXM5.msp.

When I try to integrate them, I always receive an error when integrating the second .msp (PVMSO or PVMSXM5). I try with both the standard method both IT Rider method, but always failed:

First method:

msiexec /p C:\Hotfix\MSO.msp /a C:\Office11\PRO11.msi shortfilenames=true /qb

msiexec /p C:\Hotfix\PVMSO.msp /a C:\Office11\PRO11.msi shortfilenames=true /qb

IT Rider method:

start /wait msiexec /p C:\Hotfix\MSO.msp /a C:\Office11\PRO11.msi /qb /lv* C:\Hotfix\KB917151_1.txt

start /wait msiexec /p C:\Hotfix\PVMSO.msp /a C:\Office11\PRO11.msi /qb /lv* C:\Hotfix\KB917151_2.txt

So, at the end I can integrate only MSO.msp, and not also the second .msp. The error I receive is this (mine in Italian, but it's the same):

Someone has solved this???? B)

Edited December 2, 2006 by Pis19

[OverFlow]

Hi everybody!

I don't know if this problem has already been solved, but I didn't find any solution at this time. The problem appears when I try to integrate SP2 and all the post SP2 hotfixes in Office 2003 CD, so to burn it and install it with everything integrated.

The problem is caused by the hotfixes that have two .msp inside. They are:

KB917151

KB921566

KB923272

KB924424

Yes there is another post on here somewhere about this I couldn't find it quickly

The PV, I believe, stands for Project and Visio which you probably don't have so they wont install.

As long as the ones without the PV at the beginning install and office updates shows that you are up to date you were successful.

OK?

Edited December 3, 2006 by OverFlow

[Pis19]

Yes there is another post on here somewhere about this I couldn't find it quickly

The PV, I believe, stands for Project and Visio which you probably don't have so they wont install.

As long as the ones without the PV at the beginning install and office updates shows that you are up to date you were successful.

OK?

Yes, very accurate answer man!

Ok, I will delete the PVMSO integrating strings: in fact, I don't have Project and Visio!

Thank you very much!

[hector]

So is the consensus here that it's messy to try to slipstream anything past Office 2003 SP2 because sometimes internet update sites don't recognise you've actually got the hotfixes due to a flawed checking method?