[Taniniver]

@markajm and iii333

Thanks a lot for the info. I tried the Office Update website, and that didn't show any updates required, so the issue is with the Microsoft Update website.

FYI iii333, since you wanted to know, I'm installing from harddisk.

Thanks again

[mik99]

iii333, on Aug 20 2006, 06:19 AM, said:

To insert my original Office CD doesn't help . On the net I found the needed DLL Microsoft.Office.Interop.InfoPath.SemiTrust.dll is included in Office 2003 PIA download. I downloaded this package and I tried to incorporate it in my Administrative Installation Point without success .

Any help would be very appreciated!

ok, same problem here

i tried 3x slipstreaming, tryed all that iii333 did, but no success

only way to bypass office installation, is not installing InfoPath

any solution?

ps: iso made with UltraISO

This post has been edited by mik99: 29 August 2006 - 10:55 AM

[iii333]

mik99, on Aug 29 2006, 11:53 AM, said:

only way to bypass office installation, is not installing InfoPath

any solution?

To copy office installation on HD of each computer where you want to install office

I was wrong: Office 2003 PIA doesn't contain the file Microsoft.Office.Interop.InfoPath.SemiTrust.dll . It only applies on it...

[Kiki Burgh]

hi all! i tried this link as suggested by jftuga ... everything went on smoothly & i even created an ISO ... but when i tried installing it & checked on Help ... About - it didn't show as SP2 ... attached are a couple of screenshots: 1 from another machine where i installed SP2 separately while the other where i used the slipstreamed SP2 ... any suggestion? thanks!

Attached File(s)

•  SP2.JPG (12.49K)
  Number of downloads: 51
•  SP2_maybe.JPG (8.78K)
  Number of downloads: 39

[monnezza]

Taniniver, on Aug 24 2006, 03:50 PM, said:

Hi All

I'm trying to create a network installation source for Office 2003 Professional, with SP2 and all hotfixes applied, but running into trouble.

I have run the initial install from CD with the /A option, entered the product key and registration info. Then I have downloaded Office 2003 Service Pack 2, extracted this and applied it to the MSI files. Up to this point is absolutely fine, no problems. I can install from here, and Office 2003 with SP2 installs fine.

The problem comes with trying to integrate the post-SP2 hotfixes. Through installing Office 2003 with SP2 then visiting Microsoft Update, I have found that the following further updates are required at the moment:

Security Update for PowerPoint 2003 (KB916518)
Security Update for Word 2003 (KB917334)
Update for InfoPath 2003 (KB920103)
Update for Outlook 2003 Junk Email Filter (KB920907)
Security Update for Office 2003 (KB921566)
Security Update for Excel 2003 (KB918419)
Security Update for Office 2003 (KB914455)
Update for Outlook 2003 (KB913807)
Update for Office 2003 (KB907417)

I have downloaded the administrative installers for each of these, extracted the MSP files, and then used msiexec to apply them to the office11.msi file in the installation source. This all goes OK, there are no errors generated. However, if I then perform a new clean install from this source, the system does not seem to think these updates have been applied. Visiting the Microsoft Update website, it still downloads and applies them.

Can anyone offer any advice as to anything I might have done wrong, or why this might be failing?

Drac0, on Aug 28 2006, 07:48 AM, said:

iii333, on Aug 20 2006, 04:19 PM, said:

I need a help, please!

So, I've created an Administrative Installation Point using my Office11 Pro CD and slipstreamed SP2 & all Hotfixes following this. After that I've successfully installed updated Office form HD. But, after burning (with Nero and UltraISO) my Updated Administrative Installation Point on CD I can't install Office from this CD. I tried to do it on several Windows machines and I always had this error



To insert my original Office CD doesn't help . On the net I found the needed DLL Microsoft.Office.Interop.InfoPath.SemiTrust.dll is included in Office 2003 PIA download. I downloaded this package and I tried to incorporate it in my Administrative Installation Point without success .

Any help would be very appreciated!

Did you find a fix for this iii333 ? I have the exact same issue. When installed directly from the hard drive, no problems at all. But if I burn the files to cd I get this same error. Only solution I've come up with is NOT to install InfoPath. Installation is fine then.

But why would it install perfectly from the HDD but not CD?

hi all,
I have a solution, I'll explain you how I did:

The problem is Update for InfoPath 2003 (KB920103):

you don't need Office 2003 PIA
you need Windows Installer SDK (x86) v1.1

After slipstreaming Update for InfoPath 2003 (KB920103) into Office 2003 Professional with SP2 there are two errors in PRO11.MSI.
To fix:

• download Windows Installer SDK (x86) v1.1:
  
• double click downloaded IntelSDK.msi and follow the instruction to install
  
• go in the folder where you have install to (default D:\MsiIntel.SDK) then under folder Tools (D:\MsiIntel.SDK\Tools)
  
• double click Orca.msi and install it
  
• backup PRO11.MSI slipstreamed with Update for InfoPath 2003 (KB920103)
  
• run Orca
  
• with Orca open PRO11.MSI slipstreamed with Update for InfoPath 2003 (KB920103)
  
• then in the Tables column (left) click on File, scroll down the rigth column until end, at the bottom you will see the last two rows like:

          File                                        Component_                      Sequence
IPCLRWRP.DLL_0001            Global_PIA_XDocsWrapper2            4550
INFOPATH.CFG                      Global_PIA_XDocsWrapper2            4551

• change the numbers under Sequence into:

          File                                        Component_                      Sequence
IPCLRWRP.DLL_0001            Global_PIA_XDocsWrapper2              270
INFOPATH.CFG                      Global_PIA_XDocsWrapper2              271

 PRO11.MSI.jpg (148.66K)
Number of downloads: 224

• save PRO11.MSI
  
• create image, burn it and try...

[Drac0]

Thanks monnezza, will give it a try.

[Kiki Burgh]

hi! anything about my earlier inquiry? any feedback would be greatly appreciated.

[Drac0]

Drac0, on Sep 11 2006, 01:22 PM, said:

Thanks monnezza, will give it a try.

Finally got around to giving this a try, works perfectly.

Cheers.

[IT Rider]

Though there are fixes to the KB920103, I still have yet to get this one working easily.

I have found a solution that is simple for the pesky hotfixes that will not work with the typical slipstream syntax. It is:

e.g. (Where *.msp is your hotfix and *.msi are the installation files).

start /wait msiexec.exe /p c:\office2k3\pvmso.msp /a c:\office2k3\pro11.msi /qb /lv* c:\office2k3\logfile.txt

start /wait msiexec.exe /p c:\office2k3\pvmso.msp /a c:\office2k3\owc11.msi /qb /lv* c:\office2k3\logfile.txt

For some reason, some of the new patches require you to have the autorun.inf file in the source directory and for it to create a logfile. I put both the installation msi files in the script because I really didn't want to figure out which hotfix went with each. You will get an error if it cannot be applied to one of the msi files.

I hope this helps.


Note: The error I was getting was from this script found on many websites. It did not work with my source files.

msiexec /p D:\Office2003SP2\MAINSP2ff.msp /a D:\Office2003\PRO11.MSI shortfilenames=true /qb

This post has been edited by IT Rider: 10 October 2006 - 09:34 AM

[IT Rider]

Finally, KB920103 worked!

After I installed all of my hotfixes using my previous post info, I re-applied the KB920103 hotfix by itself.

start /wait msiexec.exe /p c:\office2k3\infopath.msp /a c:\office2k3\pro11.msi /qb /lv* c:\office2k3\logfile.txt


I tested it...and well, it did not work as planned, even though it slipstreamed okay. Again, like others, it asked for the CD.

So, I used monnezza's method using the Windows Installer SDK (x86) v1.1 and orca. Worked great! Thanks monnezza! How you would know to go there for the fix is beyond me. Take care.

[IT Rider]

October Patch release Issues

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

Attached File(s)

•  error.jpg (33.72K)
  Number of downloads: 93

[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=&...st&p=592679

Attached File(s)

•  SlipOff.cmd (3.23K)
  Number of downloads: 126

This post has been edited by OverFlow: 10 December 2006 - 12:45 PM

[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]

Attached File(s)

•  Office.reg (12.96K)
  Number of downloads: 57

This post has been edited by OverFlow: 10 December 2006 - 12:20 PM

[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]

pppx00, on Nov 23 2006, 12:50 AM, said:

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.