Software Deployment Question

MS Office troubles

09/17/2008 2550 views
I have been tasked with developing MS Office 2003 transforms that will work together. We have a large user base that needs different MS Office components. Pretty much all users will use Word, Excel, and PPT. We have some that will use Access and some that will use Publisher, and some that may use both. The problem I am having is whatever transform I use first seems to be the only one that has an effect. I am creating the transforms with the 2003 resource kit and distributing with ZENworks 7. The problems also occur if I take zen out of the equation and install via command-line referencing the mst. When I run the second install with the full interface it comes up asking if I want to add features, repair, or remove. When I select add it has all the options from the original mst selected and none of them from the mst I specified.

Is there something obvious I am missing?
0 Comments   [ + ] Show comments


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

All Answers

are you using just one commandline with a transform list e.g: "TRANSFORMS=1033.mst;Transform1.mst;Transform2.mst" or are you attempting to use more than one msiexec command with each transform applied?
Answered 09/17/2008 by: kiptek
Second Degree Green Belt


User would have "tranforms=basic.mst" one day and may get "transforms=access.mst" or "transforms=publisher.mst" another day.

We ultimately want to chain the installs with app launcher shortcuts so if the user clicks on MS word it would install the basic.mst and if a week later they clicked on Access it would then apply that transform. Doing one transform with everything set to install on first use is not an option because we do have users who we do not want to have Access or Publisher.
Answered 09/18/2008 by: cchkb
Yellow Belt

If I recall you need to replace the cached transform and then perform a re-install with ADDLOCAL=<feature> (ex. Access).
Answered 09/18/2008 by: AngelD
Red Belt

Thanks that gets me a lot closer. Only thing is there are other things in the transform file that I wanted applied. Most I can get around by modifying the original mst to include them, but is there a way to add the desktop shortcut via msiexec switches? Also how would you replace the cached transform?
Just to clarify here are the cmd lines I am using.

msiexec /i "...\pro11.msi" TRANSFORMS="...\basic.MST" /qb-
followed by
msiexec /i "...\pro11.msi" ADDLOCAL=ACCESSFiles /qb-
Answered 09/18/2008 by: cchkb
Yellow Belt

Here is a vbscript I've used before to replace a cached transform (with the same transform name) and performed a reinstall.

On Error Resume Next
Dim ProductCode : ProductCode = "<ProductCode for MS Office 2003>" '// ex. {CC14CF6A-7D60-413A-934C-3150D422DA6D}
Dim MstFileName : MstFileName = "same_name_as_the_already_installed_transform.mst" '// basic.MST

Dim FSO : Set FSO = CreateObject("Scripting.FileSystemObject")
Dim WSHShell : Set WSHShell = CreateObject("WScript.Shell")
Dim ScriptPath : ScriptPath = StrReverse(Split(StrReverse(WScript.ScriptFullName),"\",2)(1))

'// Replace cached transform
Dim oFile : Set oFile = FSO.GetFile(WSHShell.ExpandEnvironmentStrings("%WinDir%\Installer\" & ProductCode & "\" & MstFileName))
oFile.Attributes = oFile.Attributes Xor 1
FSO.CopyFile ScriptPath & "\" & MstFileName, WSHShell.ExpandEnvironmentStrings("%WinDir%\Installer\" & ProductCode & "\"), True
oFile.Attributes = oFile.Attributes Or 1

'// Reinstall with replaced transform
Dim MSIERROR : MSIERROR = WSHShell.Run("msiexec.exe /fomusv " & ProductCode & " /qb!", 1, True)
Answered 09/18/2008 by: AngelD
Red Belt

What if the transform names do not match?
Answered 09/19/2008 by: cchkb
Yellow Belt

This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ