There are two installation types:
Basically, the functionality of the Fabasoft Cloud Enterprise Client and Fabasoft Cloud Client is the same.
Attention: The installation of the Fabasoft Cloud Enterprise Client and the Fabasoft Cloud Client on the same computer is not supported.
Fabasoft Cloud Enterprise Client
To install the Fabasoft Cloud Enterprise Client (into the per-machine installation context), perform the following steps:
The Fabasoft Cloud Enterprise Client is installed in the following folder:
C:\Program Files\Fabasoft\Cloud\Client\.
Note: The installation of the Fabasoft Cloud Client and the Fabasoft Cloud Enterprise Client on the same computer is not supported.
Fabasoft Cloud Client
To install the Fabasoft Cloud Client (into the per-user installation context), perform the following steps:
The Fabasoft Cloud Client is installed in the following folder: C:\Users\<username>\AppData\Local\Fabasoft\
Note:
This chapter is about the advanced configuration for the Fabasoft Cloud Enterprise Client installation.
By default, the Fabasoft Cloud Enterprise Client setup will register all web browser extensions for all supported web browsers. The extension for Mozilla Firefox will always be installed locally. For Google Chrome and Microsoft Edge this will require a connection to the respective online extension store of the web browser. If no connection to the store is available you can specify that a local version of the extension should be registered instead. This only works for Microsoft Windows workstations that are joined to a Microsoft Active Directory domain (security feature of the web browsers).
msiexec /i <msipath> EXTLOCAL=1
Note:
To prevent these web browser extensions from being installed, there are parameters that can be specified when installing the MSI package:
msiexec /i <msipath> CHROMEEXT=0 EDGEEXT=0 FIREFOXEXT=0 THUNDERBIRDEXT=0
For example, the following command disables the installation of the Google Chrome extension:
msiexec /i CloudClientEnterprise.msi CHROMEEXT=0
The Native Client Service can be used to synchronize or provide data even without an interactively logged in user. The service is designed to run without user interaction, therefore a password for applications is used. If the Native Client Service is installed via setup, you will automatically be asked to create a password when you start synchronization. If the password is expired, you will automatically be asked to recreate a password. The password will be stored within the Credential Manager of Microsoft Windows.
The service is by default configured to automatically start with the operating system, so you do not have to log in after a restart of the system after you have configured the synchronization with the password for applications. If the specified user logs on interactively to the respective device, the processes of the service are stopped, and an interactive process takes over the synchronization until it is terminated again.
msiexec /i <msipath> INSTALLNCLSERVICE=1 NCLSERVICE_ACCOUNT="<fully qualified Windows account name>" NCLSERVICE_PASSWORD="<Windows account password>"
Note:
This chapter is about the own deployment of the web browser extensions and the corresponding policies.
The Microsoft Edge Extension is automatically deployed when running the Fabasoft Cloud Enterprise Client setup using the Microsoft Store. The deployment of the Microsoft Edge Extension is described in the official Microsoft Edge documentation: https://docs.microsoft.com/en-us/deployedge/microsoft-edge-policies#extensioninstallforcelist: new window
If you want to use the Microsoft Store for automatic deployment the following key has to be deployed:
HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Edge\ExtensionInstallForcelist
"1"="jdibaejnifcnoojmhgcbaohifohjamlg"
Note: If there are security policies rolled out (e.g. ExtensionInstallBlocklist or NativeMessagingBlocklist, see also https://learn.microsoft.com/de-de/deployedge/microsoft-edge-policies: new window) then it should be considered to allow the functionality for the Microsoft Edge Extension.
HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Edge\ExtensionInstallAllowlist
"1"="jdibaejnifcnoojmhgcbaohifohjamlg"
HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Edge\NativeMessagingAllowlist
"1"="com.fabasoft.nmhostpu"
The Google Chrome Extension is automatically deployed when running the Fabasoft Cloud Enterprise Client setup using the Google Chrome web store. The deployment of the Google Chrome Extension is described in the official Chromium documentation: https://chromeenterprise.google/policies/#ExtensionInstallForcelist
If you want to use an own policy for automatic deployment, the following key has to be deployed:
HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Chrome\ExtensionInstallForcelist
"1"="icjlkccflchmagmkfidekficomdnlcig;https://clients2.google.com/service/update2/crx"
Note: If there are security policies rolled out (e.g. ExtensionInstallBlocklist or NativeMessagingBlocklist, see also https://chromeenterprise.google/policies/: new window) then it should be considered to allow the functionality for the Google Chrome extension.
HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Chrome\ExtensionInstallAllowlist
"1"="icjlkccflchmagmkfidekficomdnlcig"
HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Chrome\NativeMessagingAllowlist
"1"="com.fabasoft.nmhostpu"
The Mozilla Firefox Extension is automatically deployed when running the Fabasoft Cloud Enterprise Client setup. If the Fabasoft Cloud Client setup will be installed the deployment of the Mozilla Firefox Extension is described in the official Mozilla documentation: https://developer.mozilla.org/en-US/Add-ons/WebExtensions/Alternative_distribution_options/Add-ons_in_the_enterprise: new window
If you want to deploy the Mozilla Firefox extension on your own the following keys has to be deployed:
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Mozilla\Firefox\Extensions\Install]
"1"="file://C:\\Program Files\\Fabasoft\\Cloud\\x64\\CloudFirefoxExtension.xpi"
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Mozilla\Firefox\Extensions\Locked]
"1"="nmextmozpu@fabasoft.com"
https://github.com/mozilla/policy-templates/blob/master/README.md#extensions: new window
Note: Without changing the Mozilla Firefox preferences (as described in the documentation: extensions.autoDisableScopes, extensions.enabledScopes), each user will be notified on the next application startup, that a new Mozilla Firefox Extension was installed. In this case, the user must explicitly confirm, that the Mozilla Firefox Extension should be enabled.
An update is only possible if the version number of the new package is higher than the version number of the installed package. If this is the case, the old package is automatically uninstalled when the new package will be installed. Otherwise, the Fabasoft Cloud Client setup terminates with an error message or in case of the Fabasoft Cloud Enterprise Client the setup terminates with a corresponding exit code.
During the update process, the installation is carried out with the same setup parameters as the current version is installed. If the setup parameters are to be changed, this must be explicitly specified via the respective parameter or an explicit uninstallation must take place beforehand.
If a downgrade is necessary, please uninstall the package itself first and then install the older package.
When the same version of the Fabasoft Cloud Client will be installed again the repair mode will be triggered. The repair mode only re-registers the already installed components, but does not change the installed features like the web browser extensions or the update service even if they are applied as new parameter.
For uninstalling the Fabasoft Cloud Client or the Fabasoft Cloud Enterprise Client manually use the “Apps and Features” dialog provided by Microsoft Windows.
For uninstalling the Fabasoft Cloud Client or the Fabasoft Cloud Enterprise Client automatically, a signed Microsoft PowerShell script file is provided, which is added to the installation directory. This script includes the product code of the currently installed version and can be used by a deployment tool (like Microsoft Software Center) for uninstalling this version even if it was automatically updated before.
Fabasoft Cloud Client: %LOCALAPPDATA%\Fabasoft\uninstall.ps1
Fabasoft Cloud Enterprise Client: %PROGRAMFILES%\Fabasoft\Cloud\uninstall.ps1
To avoid that users have to make settings on their own and for best performance deploy following settings on the clients:
For more information about the meaning of these keys, consult http://msdn.microsoft.com: new window.
The users have the possibility to make different settings in the options dialog. These settings can also be set by the administrator using group policies so that the users can no longer change them.
To ease the group policy setup, you can find the corresponding administrative template here: Policy Templates: new window.
The predefined settings can be defined in the following registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Fabasoft\NativeClient\Cloud
For more information about the functionality, see https://help.cloud.fabasoft.com/index.php?topic=doc/User-Help-Fabasoft-Cloud-eng/the-fabasoft-cloud-client.htm#options-dialog: new window
The data in these locations must not be removed or modified. The configuration settings will be written during the setup process and/or when logging in with the Fabasoft Web Browser Client.