PREREQUISITES FOR GoPro Desktop version 21.2.5.230 for 32-bit and 64-bit edition of Microsoft Office( versions 2016 or 2019)


1) The following packages are requiered by GoPro Desktop

	NET Framework 4.8 (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


2) Older versions of GoPro 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.Desktop.User.msi	: Installer for standard users without administrative privileges. Installs GoPro Desktop Sidebar and importer components into user's local app data folder.
	b) GoPro.Desktop.Admin.msi	: Administrative installer to distribute centrally. Installs GoPro Desktop Sidebar and importer components into "Program Files".	
	a) GoPro.Importer.User.msi	: Installer for standard users without administrative privileges. Installs GoPro Desktop importer into user's local app data folder.
	b) GoPro.Importer.Admin.msi	: Administrative installer to distribute centrally. Installs GoPro Desktop 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.Desktop.admx and en-US\GoPro.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
		* ENDPOINT - url to GoPro Server

	c) Example install with parameters, using msiexec. 
		* NOTE. There must not be any spaces between parameter name and =

		msiexec /i GoPro.Desktop.User.msi  ENDPOINT="https://myserver.mycompany.com/GoPro/api"  /qn
		msiexec /i GoPro.Desktop.Admin.msi SKIPPREREQUISITES="true"  /qn


5) Example scenario Admin install of full GoPro desktop  (GoPro.Desktop.Admin.msi)

	Full Admin install with group policy server settings
		* Administrator uses group policy to install msi on perMachine level. 
		* Adminstrators set the endpoint url using group policy, users can not change the settings.
		* No command line parameters are used 
		* NOTE: The msiexec process must be run with administrative rights, otherwise Outlook add-in registration will fail.
	
6) Example scenarios User install of full GoPro desktop  (GoPro.Desktop.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 need administrative access to their machine. 
		* Adminstrators set the endpoint url, using group policy, users can not change the settings.
		* No command line parameters are used 

	b) 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 ENDPOINT and AUTHTYPE are provided  on the command line
		* Default value for endpoint url are provided  on the command line.
		* Example : msiexec /i GoPro.Desktop.User.msi  ENDPOINT="https://myserver.mycompany.com/GoPro/api"  /qn


7) The importer installers explained

	The examples in 5) and 6) apply to the importer installers as well, both GoPro.Importer.Admin.msi and GoPro.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