The Meetingmaker installer appearently was created with InstallShield. Therefore, the procedure is based on the generic procedure for InstallShield.

Download and unpack the installation file. It has become hard to find it on their corporate site because they require you to get an account, but once you're in it seems that at least the client binaries are free to download.
For your convenience, here is the URI:

ftp://ftp.meetingmaker.com/support/mm/v87/87_win_client_en.zip


Unpack this file and change into this directory (87_win_client_en). Its contents look like:

Comparam.ini
data1.cab
data1.hdr
data2.cab
data3.cab
data4.cab
data5.cab
ikernel.ex_
layout.bin
Setup.exe
Setup.ini
Setup.inx
upgrade.lst


Open "Setup.ini" in your editor and change the appropriate values. For instance, I have:

[Startup]
AppName=Meeting MakerŪ
FreeDiskSpace=512
[Languages]
Default=0x0009
count=1
key0=0x0009

# Enable installation of specific driver Y or N
[Drivers]
IP=Y
TCP=Y
SSL=Y

[UserConfig]
DisplayReadme=N
Hosts=192.168.0.13
ReplaceHostsFile=Y
# DefaultClientLocation="C:\Program Files\meetingmaker"
ForceLocation=Y
LaunchMM=N

# Options for local data - Ask, Move, Delete, No
[LocalData]
LocalDataPref=Delete
LocalDBBackupDir="mmclnt32.backup"[size=12]

As you can see, you can conveniently preconfigure your Meetingmaker Server's IP address.

Now run the installer with the Record option:

Setup.exe /r

Install it the way you like. Once finished, the installer should have left the following answerfile for you:

C:\windows\setup.iss

Copy this file into the installation folder, and for future installs you can now call the installer with this answerfile, and make it silent too. It will also pick up the values from Setup.ini.

Setup.exe -s


You can use this for integration with RunOnceEx or WPI etc.

For instance I use WPI and there I have put in this command:

"%wpipath%\Install\87_win_client_en\Setup.exe" -s

There are some values in setup.iss that you can fiddle with for more control.

---