Create an .msi of the Meridian server installer which supports command-line arguments (similar to client installer)

It would be extremely useful to create the Meridian server installer as an .msi rather than .exe, and to also support command-line arguments for choosing the components to install (similar to the client installer). The .exe does support a response file but, compared to an msi and command-line arguments, they're tedious to create and use.

  • Aaron Swain
  • Jul 2 2019
  • Future consideration
  • Attach files
  • Chris Tsangarides commented
    September 13, 2019 17:43

    Thank you again for the suggestion and additional comments.

    This idea is being considered for a future release of Meridian. Stay tuned for updates.

    Chris Tsangarides
    Product Manager
    Accruent

  • Pierre Riegert commented
    July 21, 2019 16:34

    Hi Chris,

     

    Most of the time, we must install Meridian on multiple (4 or 5) environments at customer site (Development, Technical tests, Functional tests, Production, sometimes for training also). We are doing the installation on the first environment and the customer is responsible to install the other environments. The production environment is installed by people that do not have any Meridian knowledge. They just follow a list of tasks written in a document.

    Due to the number of parameters to consider during Meridian Setup, it is recommended to script as many steps as possible to avoid errors.

    Therefore, a .msi setup can be great. It can also be a tool that can help to script the installation steps including patches and/or tools to control the installation and provide explicit warnings about the communication between the different Meridian components (protocols, ports, firewall, rights on files and folders, etc.).
    Please refer to my previous post (MER-I-318). The real issue here is the complexity of Meridian installation and the huge number of patches to deal with.

      

    With Kind Regards

    Pierre

  • Chris Tsangarides commented
    July 19, 2019 20:24

    Thank you again for the suggestion.

    The client is a much simpler setup than the server and is also performed many more time more than a server.

    The current process that you describe is the way to install a server, for example on Dev environment, and use the response file to replicate the installation on a QC and finally a Production environment.

    Can you help me understand how significant the time savings would be should this process be made simpler? For example, how many server installations per week/month would this impact, and how many hours would that save, and so on.

    This will help development prioritize work.

    Chris Tsangarides
    Product Manager
    Accruent

  • Chris Tsangarides commented
    July 09, 2019 12:15

    Thank you for your suggestion.

    Development is currently reviewing your idea. Stay tuned for updates.

    Chris Tsangarides
    Product Manager
    Accruent