The unattended installation of SGO products is possible with some limitations following the next steps.
You can run any of our installers with the (double hypen) "--mode unattended" parameter. Doing it this way, without any other parameter will install in the default paths.
Installing in the default paths is always what we recommend, as using different paths will mean having to pay extra attention to permissions or any other security considerations in your OS to allow your software to work properly. Anyway there are other parameters you can use to change the default installation paths:
--prefix PATH TO YOUR INSTALLATION FOLDER
--env PATH TO WHERE YOU WANT YOUR CONFIG FILES TO BE
--shared PATH TO WHERE YOU WANT THE CONFIG FILES COMMON TO ALL SGO PRODUCTS TO BE
--media PATH TO WHERE YOU WANT YOUR VIDEO FILES TO BE
--projects PATH TO WHERE YOU WANT YOUR PROJECTS TO BE
All the paths you pass as parameters have some limitations (imposed by the internal xml parser of the installer):
1.- The path must be between double quotation marks "
2.- The path must use slashes / instead of backslashes \ regardless of the OS you are using
3.- The path must not contain spaces in folder names. This is only supported in the --prefix parameter.
For example...
MY_SGO_INSTALLER.exe --mode unattended --prefix="c:/Program Files/MY_FOLDER" --media="z:/MEDIA/SGO"
...will install the program and create the folder for media files in the paths specified, while other paths are created in the default locations.
All of our software have to be installed with the user that is going to use it. Multiple users installations is not supported. Installing with the Administrator or root user is not supported.
The installation will run in a different thread and you will not get any output when it finishes.
There are parts of the installation that need elevated/Administrator/root privileges, in the regular installer you get asked for permission or an admin/root password, but as you are running an unattended installer, the goal is to not have to manually enter anything:
- In windows: your user has to be in the Administrators group and you can call the installer from a "Run as Administrator" console, but make sure that the user that installs is actually the user that is going to use it.
- In OSX or Linux: you'll have to include your user in the /etc/sudoers file and allow him to run root commands without password (you can disable it after you finish installing), then run the installer with a sudo. If you don't know how to do this, please contact your system administrator.
There are other difficulties in OSX that come from the nature and security specifications of this OS. You might need to specifically allow the installer to be ran in that system in the security settings. You'll also notice that our installers come in .dmg packages, you'll have to mount them to be able to run the installer that comes inside them. If you don't know how to do this, please contact your system administrator.
About the upgrades.
You can also install upgrades in unattended mode but in this case you'll only pass the --mode unattended parameter and the installer will detect and use the paths you used in your original installation. If you pass any other parameter, it will override the current paths, so if it is not exactrly the same path you used in your previous installation you'll end up with the upgrade files in a wrong path and this can cause all kind of trouble.