From this point on all changes to the folder base path are controlled by the client and automatically synced to the registry. At the next start of the PowerFolder client the folder base path is read from the registry and the overwrite flag set to false. A second key (foldersbase.overwrite) is also written to the registry and set to true. Msiexec /i installer.msi /qn FOLDERBASEPATH=C:\testĭuring installation, the folder base path is written to the registry of the local user (foldersbase). The installation can also be done completely silent (requires console with administrator privileges):
Msiexec /i installer.msi FOLDERBASEPATH=C:\test It is also possible to set the parameter via command line parameter: If no folder path was set the installer proposes the default path $HOME/PowerFolders. The installer proposes the folder base path already set in the registry. With the MSI installer the folder base path can be set during the interactive installation process. The REMOVE property names features to be removed.The ADDLOCAL property allows specifying features to be installed by their name.All features with a level lower than INSTALLLEVEL will be installed. The INSTALLLEVEL property can be set manually.The default value is provided by GetSystemDefaultLanguageID. For possible values see Language Identifier Constants and Strings. The LANG property determines the language of the installed shell extensions.The INSTALLDIR property is used to customize the directory where the main files (PowerFolder.exe, jar etc.) will be placed.
Windows Installer allows to override this behaviour in the following ways: The public installer property CONFIG_URL must be set.Ĭreate an entry in the Windows Startup folder to automatically launch PowerFolder.Ĭreate registry entries for Kerberos Authentification.Ĭreate registry entries to use the WebDAV client.īy default, all features with a level of 1 will be installed.
Integrate PowerFolder into Windows Explorer etc. Main PowerFolder components, including the jar, binaries and entries in the start menu and desktop. The Windows client installer supports some command line options to make it easier to deploy it with batch scripts or package deployment tools: Next time one of the existing clients start, it will compare the installed version to the version mentioned in the PowerFolderPro_LatestVersion.txt and will offer the updated version to the user. If you want to have all existing clients to detect the new version, you need to edit the PowerFolderPro_LatestVersion.txt in the client_deployment directory and set the version number to the number of the updated clients. This can be useful if you want to start with a slow rollout making the updated clients only available for new users. However existing clients will not detect automatically that there is a new version yet.
Once you've updated the clients in the client_deployment directory, they will be available for download on your web interface. The clients connecting to our public cloud don't offer to enter the URL to your server!ĭownload links to the latest Generic Clients: Please take care you download the Generic Client version when updating the clients on the PowerFolder Server. During runtime the clients in the client_deployment directory have to be updated manually whenever a new version should be deployed to the user's devices.
After the initial download of the clients to the client_deployment directory of the Server Maintenance Folder, the server will NOT automatically update the client if a new version is released by PowerFolder, except if the client installation packages are deleted and the service restarted.