eDOCS 5.3 MSI Scripting Tips + Tricks

May 16th, 2011

Since Open Text moved from using the “setup.exe” to a MSI file, things have gotten easier. However, customizing that MSI for individual installations still takes some work. Then there is the whole issue of deploying it out to your workstations. Make that them out to your workstations. There are separate MSI’s depending on if your workstation is 64 or 32 bit.

1. Find yourself a good editor. Open Text in their presentations have suggested Orca MSI editor. I’ve been using InstEd. I can’t compare the two because I haven’t used Orca, but I’ve been happy with InstEd.

2. Use Transforms. It is quicker and easier to create and edit Transforms. You can have different Transforms for different installations. Say you only want to install DM Imaging on certain machines, create a separate transform. You don’t mess with the original MSI distributed by Open Text and it keeps your command line a lot shorter.
Sample: msiexec.exe /i “%dmfiles%\eDOCS DM 5.3 Extensions (x86).msi”¬†TRANSFORMS=”%dmfiles%\eDOCS53Transform86.mst” /qn /l*v “%TEMP%\DMInstall.log”

3. Testing for your processor. I write command files for doing the installation for our clients. If they have an automated way to distribute the installation, they can either pick what they like from the command file or use the command file to push the install. Because many of our clients are in a mixed environment with new machines being 64 bit and the old ones still being 32, we needed a good way to test which MSI to install. I borrowed this test from someone else because it works well.

4. We always had a separate step for applying the custom registry keys. Here is the other thing that is great about using transforms, you can import them directly into the transform. That way, MSIEXEC takes care of applying them for you. With InstEd, you simply right-click on a component and import your registry file.

Please feel free to share your own tips and tricks. Lord knows I’m still learning myself. What do you find useful?