Dear all
I'm currently deploying Office2003.
I started creating a admin-install, slipstreamed the service pack and all patches.
Then I created a mst-file using the ORK fro Office2003.

When I now try to distribute the msi and the mst, the mst is not applied to the Office.....[&o]
It does not matter whether I use ZEN to distribute or a command-line on a client.... it's installing office and thats all.....

Does anyone know whats going wrong?

(In the same environment I already deployed Acrobat 6 with MSI & MST - using ZENworks without any problems).

Thanks, Werner
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
I have to correct something:

Only some settings are not applied.... like Tools/Options/File location etc.
The Company Name (for example) is correctly applied from the mst....

cheers, Werner
Answered 11/26/2004 by: whenz
Yellow Belt

Please log in to comment
0
Have you tried opening the MSI in Orca, then applying the MST?

Should give you some pointers, or at least an error message which may help.

Rob.
Answered 11/29/2004 by: MSIPackager
Third Degree Black Belt

Please log in to comment
0
What is the Orca?
Regards, Werner
Answered 11/29/2004 by: whenz
Yellow Belt

Please log in to comment
0
It is a program that allows you to open / edit windows installer databases at table level.

More info, and link to the SDK here: http://support.microsoft.com/kb/255905/EN-US/

Once you've downloaded / installed it, open your msi, then apply your mst file. All changes that the mst makes are highlighted in green...

It's also really good for validating your packages - you shouldn't have to worry too much about that with this one though as its an admin install. As it's an MS product there will (no doubt) already be 100's of validation errors [:-]

Regards,
Rob.
Answered 11/29/2004 by: MSIPackager
Third Degree Black Belt

Please log in to comment
0
I should add that I found that the Office 2003 MSI must do some funky things because editing its transform in ORCA can sometimes break the EULA acceptance. You'll know if that happened if using the transform results in a EULA not accepted error.

SO edit lightly (in general, editing existing properties seems to be ok, adding rows isn't.) and don't think ORCA is a piece of junk. It's Office. Gotta love how MS adheres to it's own Windows Installer standards.
Answered 11/29/2004 by: VikingLoki
Second Degree Brown Belt

Please log in to comment
0
I have managed chaining office 2k3 with sp1. I d/l'd entsetup.exe from ms ; renamed and applied the setup.ini file to point to the mst and ohotfix dir. Used CIW creating the mst and ohotfix to apply the service pack/patches ok. It is not possible to use an AIP if you want a LIS (local installation source) and it is implied indirectly that to slipstream/chain sp1 with office you need the compressed cd source on cd or copied to newtork and not an AIP. We tried using an administrative installation point first with no success (chaining with SP1). It didn't show any errors but didn't update properly. Changing to a newtork copy of the cd and everything worked fine.
An AIP works fine if appling SP1 to an existing install but not slipstreaming or chaining.
If some one has indeed chained sp1 with an AIP that would be good to know....
Hope this helps :)
Answered 11/29/2004 by: exup
Senior Yellow Belt

Please log in to comment
Answer this question or Comment on this question for clarity