HELP! Trying to create a mst for Office 2003 for alternate drive letter
I am attempting to create a mst to run with the Office 2000 msi to install Office on a Citrix/Terminal server. The application has to be installed on the E: drive. The issue I am running into is since this is a TS installation it has to use the included termsvr.mst file. (It will not install in a TS environment without this transform). However, this transform file only installs to C:\. I am using WISE Package Studio 5.60 Standard. I have tried to use two transforms, the required one and another for drive E:\ installation, but when I try to use them it errors saying the mst. files do not exist. I am attempting to use Citrix Installation Manager to install. However, I can get a manual install to work I would be happy. The Citrix IMS piece is easy.
0 Comments
[ + ] Show comments
Answers (2)
Please log in to answer
Posted by:
mgroover
18 years ago
Try this instead in your commandline for installation:
MSIEXEC /I msifilename TRANSFORMS=transformsfilename ROOTDRIVE="E:\"
Should do the trick. This forces it to use E:\ as rootdrive.
// martin
MSIEXEC /I msifilename TRANSFORMS=transformsfilename ROOTDRIVE="E:\"
Should do the trick. This forces it to use E:\ as rootdrive.
// martin
Posted by:
CitrixGuy
18 years ago
MSIEXEC /I msifilename TRANSFORMS=transformsfilename ROOTDRIVE="E:\"
Thanks
I found the issue. For some reason even though I run the command line to install using a certain transform. It keeps trying to use an old transform file. I once was attempting to use a different transform file. The Installer defaults to that one which is no longer there, even though the command line specifies somethng totally different. Example I have a command line which tells it to use TERMSRVR.MST, but the error log says : Error applying transforms. Verify that the specified transform paths are valid.
\\Sharename\Ctxapps\Installation Manager MSI Files\Office2000\CustomOffice2000.MST.
I once had a file named CustomeOffice2000.mst but no longer. It's like it is stuck pointing to that file. How can I "flush" this pointer out? Should I reinstall Windows Installer?
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.