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

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.

here is the microsoft answer to your question http://support.microsoft.com/kb/913754

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

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