PREREQUISITES FOR GoPro Foris Desktop version 20.3.2.53039 for 32-bit and 64-bit edition of Microsoft Office( versions 2013 or 2016) 1) The following packages are requiered by GoPro Desktop a) .NET Framework 2.0 (or later version that provides CLR version 2.0 b) .NET Framework 4.6.1 (or later version that provides CLR version 4.0) Detailed explanations and instructions on how to provide these .NET packages for different versions of Windows are provided in the article : ".NET Framework Versions and Dependencies", found here : https://msdn.microsoft.com/en-us/library/bb822049(v=vs.110).aspx c) Microsoft WSE 3.0 Runtime Microsoft WSE 3.0 Runtime can be downloaded here : https://www.microsoft.com/en-us/download/details.aspx?id=6545 2) Older versions of GoPro Foris Desktop must always be uninstalled before new version is installed 3) Installers are are available both for both perUser installations and perMachine installations. a) GoPro.Foris.Desktop.All.User.msi : Installer for standard users without administrative privileges. Installs all GoPro Foris Desktop components into user's local app data folder. b) GoPro.Foris.Desktop.All.Admin.msi : Administrative installer to distribute centrally. Installs all GoPro Foris Desktop components into "Program Files". c) GoPro.Foris.Desktop.Importer.User.msi : Installer for standard users without administrative privileges. Installs Importer into user's local app data folder. d) GoPro.Foris.Desktop.Importer.Admin.msi : Administrative installer to distribute centrally. Installs Importer into "Program Files". 4) Installer command line parameters for msiexec a) All installer parameters will only add settings to the Current User registry (HKCU). * NOTE: This means that when using the Admin installers, the command line parameters will only be available for the user running the installer, not for other user on the same machine. * When using Admin installers it is recommended to use the provided Group Policy to set connection settings. (GoPro.Foris.Desktop.admx and en-US\GoPro.Foris.Desktop.adml) * NOTE : Administrative installer must be run with administrative privileges, otherwise the Outlook and Office add-in registration fails b) The folllowing command line parameters can be set when installing using msiexec * TARGETDIR - Install folder * SKIPPREREQUISITES - true or false * SERVERURL - url to GoPro Foris Server * AUTHTYPE - Type of authentication, possble values are: * "GoPro" - GoPro Username and Password authentication * "WA" - Windows authentication * "X509" - X509 authentication c) Example install with parameters, using msiexec. * NOTE. There must not be any spaces between parameter name and = msiexec /i GoPro.Foris.Desktop.All.User.msi SERVERURL="https://myserver.mycompany.com/server" AUTHTYPE="WA" /qn msiexec /i GoPro.Foris.Desktop.All.Admin.msi SKIPPREREQUISITES="true" /qn msiexec /i GoPro.Foris.Desktop.Importer.User.msi SERVERURL="https://myserver.mycompany.com/server" SKIPPREREQUISITES="true" AUTHTYPE="GoPro" /qn 5) Example scenarios Admin install of full GoPro Foris desktop (GoPro.Foris.Desktop.All.Admin.msi) a) Full Admin install with group policy server settings * Administrator uses group policy to install msi on perMachine level. * The msiexec process must be run with administrative rights, otherwise Outlook add-in registration will fail. * Adminstrators set the server url and authentication type using group policy, users can not change the settings. * No command line parameters are used b) Full Admin install with group policy default settings * Administrator uses group policy to install msi on perMachine level. * The msiexec process must be run with administrative rights, otherwise Outlook add-in registration will fail. * Adminstrators set the default server url and default authentication type using group policy, users can change the settings. * No command line parameters are used 6) Example scenarios User install of full GoPro Foris desktop (GoPro.Foris.Desktop.All.User.msi) a) Full User install with group policy server settings * Each user installs software on perUser level. (using msi directly, not msiexec) * No need for administrative access to their machine. * Adminstrators set the server url and authentication type using group policy, users can not change the settings. * No command line parameters are used b) Full User install with group policy default settings * Each user installs software on perUser level. (using msi directly, not msiexec) * No need for administrative access to their machine. * Adminstrators set the default server url and default authentication type using group policy, but user can change the settings. * No command line parameters are used c) Full User install with group policy running the msi with parameters * Group policy runs perUser install on behalf of the end user. * The software is installed on perUser level. * Uses msiexec quietly with no UI using the command line options /qn * No need for need administrative access to their machine. * Default values for SERVERURL and AUTHTYPE are provided on the command line * Example : msiexec /i GoPro.Foris.Desktop.All.User.msi SERVERURL="https://myserver.mycompany.com/server" AUTHTYPE="WA" /qn 7) The importer installers explained The examples in 5) and 6) apply to the importer installers as well, both GoPro.Foris.Desktop.Importer.Admin.msi and GoPro.Foris.Desktop.Importer.User.msi. 8) Installer logs * Log files for the installation can be found in the %TEMP% folder. Location of the %TEMP% folder depends on the user that ran the installer. * If support for Outlook and Office is installed then separeate log files for the Add-in registration are created. Those files are: - %TEMP%\adxregistratorOutlookUninstall.log - %TEMP%\adxregistratorOfficeInstall.log