Silent installation

<< Click to Display Table of Contents >>

Navigation:  Bizagi Studio > Bizagi Studio installation > Bizagi Studio Server Installer > Bizagi Studio server system requirements >

Silent installation

Overview

The silent installation is an unattended installation done by a system administrator in a user's or in multiple users' workstations remotely. This section explains how to install the Bizagi Studio Server installation throughout a silent installation, enabling deployment to multiple users' workstations.

This option is available when having admin rights exclusively.

 

Before you start

Make sure that:

PCs or laptops of users, comply with the minimum requirements as described at System requirements

You have already downloaded the installer as described at Downloading Bizagi Studio.

You have system admin rights to be able to deploy the installation into your users' workstations

 

Alternatives

When planning to install Bizagi Studio through a silent installation, consider either of these two alternatives:

1.The first alternative considers creating a .msi file, compliant to be run with msiexec or system management software such as Microsoft's SCCM.

2.The second alternative considers recording an installation to create a .iss file, so that a massive deployment relies on such configuration.

 

note_pin

If you are going to install a new version over an existing installation, use the same method used for the first installation. For example, if for the first installation you used .msi file, install the new version using .msi. If it is not possible to use the same method, first uninstall the existing version, and install it again. See uninstall Bizagi Studio.

 

Installation with a .msi file

For this alternative, you use an administrative installation and carry out the following:

 

note_pin

Through this alternative,  prerequisites such as Microsoft .NET Framework 4.8 and redistributable C++ 2013 are not installed; as opposed to when running the regular and assisted installation. For this alternative, you need to have Microsoft .NET Framework 4.8 and redistributable C++ 2013 previously installed.

 

1. Use a command prompt to create Bizagi Studio .msi

Use the following options to create the .msi file, with admin rights:

 

[Bizagi_Installer] -a

 

Consider:

[Bizagi_Installer]: should be replaced by the location of Bizagi Studio .exe installer, including the full path to this file.

The name of the installer should be Bizagi Studio Setup.exe inside quotation marks.

For further information on these options, refer to http://helpnet.flexerasoftware.com/installshield22helplib/installshield22helplib.htm.

 

silent_01

 

This command starts an assisted procedure to unpack the installer's content into a .msi, and you should specify a network location while carrying out the assisted steps:

 

silent_02

 

silent_03

 

When done, you are able to locate Bizagi Studio.msi at the network path as specified during the assisted steps.

 

If you want to execute the files in a different machine, make sure you take all the files unpacked as shown below.

 

silent_04

 

2. Deploy the installation by relying on the .msi file

Use the msiexec command to run Bizagi Studio.msi from the network path, while using ISSETUPDRIVEN=1 to avoid pop-ups, as follows:

 

"[Network_location]\Bizagi Studio.msi" /qn companyname=[Company_name]

 

Consider:

[Network_location]: should be replaced by the network path as specified during the assisted steps (where Bizagi Studio.msi is at)

[Company_name]: use this command in case you own an Enterprise subscription of Studio Collaboration Services. Type in your company's name.

 

 

silent_05

 

If you want to print logs, consider the following command:

 

/L*v [path]\[fileName].log

 

for example

 

C:\Users\User\Downloads>msiexec /i "C:\Users\User\Downloads\Bizagi Studio.msi" /qn companyname=WholeProduct /L*v C:\temp\BizagiInstallLog.log

 

After a successful installation, Bizagi Studio is presented as an installed program and display its shortcut:

 

silent_06

 

For further information on these options, refer to http://helpnet.flexerasoftware.com/installshield22helplib/installshield22helplib.htm.

 

 

Installation with an .iss file

Bizagi Studio installer relies on InstallShield and so, through command-line options you may create a .iss file to make use of a preset configured installation. This process should be executed for EACH Bizagi version; that is, an .iss file should be created for each Bizagi version.

 

To do so, carry out the following:

 

1. Use InstallShield 's commands to register .iss instalation

Use InstallShield 's commands such as /r, /f1 and optionally /verbose (most useful to troubleshoot), to record the configuration for a installation as follows:

 

[Bizagi_Installer] /r /f1"[Output_ISS]"

 

silent_07

 

Consider:

[Bizagi_Installer]: should be replaced by the location of the BizagiStudio .exe installer, including the full path to this file (ideally a shared drive). The name of the installer should be Bizagi Studio Setup.exe inside quotation marks.

[Output_ISS]: should be replaced by the location where you want to create the ISS configuration file, including how you want to name this file. Usually, when this option is left unspecified, the ISS file will be created as C:\Windows\setup.iss.  Make sure that you define the .ISS extension.

 

note_pin

Consider:

A full path for all options above is recommended (not using relative paths).

You may also use quotes for such paths, to avoid issues when these have blank spaces.

No blank spaces should be left between the option and its path value.

 

For further information on these options, refer to http://helpnet.flexerasoftware.com/installshield22helplib/installshield22helplib.htm.

 

Once the command is entered, follow regular steps of an assisted installation as presented by the wizard and instructed at Quick start installation. If you want you can set the URL of the Studio Collaboration Services. If not, leave the checkbox unselected.

 

silent_08

 

After a successful procedure, Bizagi Studio is presented as an installed program and display its shortcut.

 

note_pin

In addition to the above, you may verify a successful procedure by locating the appropriate logs at the Event Viewer, or rely on the verbose log to troubleshoot.

 

silent_09

 

 

2. Deploy the installation by relying on the .iss file

Use InstallShield 's commands such as /s, /f1 and optionally /verbose, to run a silent installation of Bizagi Studio as follows:

 

[Bizagi_Installer] /s /f1"[ISS_file]" /verbose"[Output_Log]"

 

silent_10

 

Consider:

[Bizagi_Installer]: should be replaced by the location of the Bizagi Studio .exe installer, including the full path to this file (ideally a shared drive). The name of the installer should be Bizagi Studio Setup.exe.

[ISS_file]: should be replaced by the location where you created the ISS configuration file as in a previous step.

[Output_Log]: should be replaced by the location where you want to store a verbose log, including how you want to name this file.

 

For example

 

C:\Users\User\Downloads>"Bizagi Studio Setup.exe" /s /f1"C:\Users\User\Downloads\ISSstudioInstaller.ISS" /verbose"C:\Users\User\Downloads\InstallerLog.log"

 

note_pin

Consider:

A full path for all options above is recommended (not using relative paths).

You may also use quotes for such paths, to avoid issues when these have blank spaces.

No blank spaces should be left between the option and its path value.

 

For further information on these options, refer to http://helpnet.flexerasoftware.com/installshield22helplib/installshield22helplib.htm.

 

Note that this silent installation will create a setup.log file on the local path. After a successful silent installation, the process exits with a 0 (zero) error status code. Alternatively, you may rely on the verbose log to troubleshoot:

 

silent_11

 

InstallShield have the following ResultCodes:

 

Result Code

Meaning

0

Success

-1

General error

-2

Invalid mode

-3

Required data not found in the ISS file

-4

Not enough memory available

-5

File does not exist

-6

Cannot write to the response file

-7

Unable to write the log file

-8

Invalid path to the InstallShield silent response file

-9

Not a valid list type (string or number)

-10

Data type is invalid

-11

Unknown error during setup

-12

Dialogs are out of order

-51

Cannot create the specified folder

-52

Cannot access the specified file or folder

-53

Invalid option selected

 

note_pin

You may also verify a successful installation by locating the appropriate logs at the Event Viewer.