Deploying and updating clients

Deploying clients to users/devices

Preparing clients for download

When is started for the first time, it will start to download the so-called Generic Clients to the client_deployment directory of the Server Maintenance Folder. The clients will then be available for download in the web interface to logged-off users on the log-in page and to logged-in users on the Download Clients tab.

After the client has been downloaded by the user from the web interface, it needs to be installed. After the installation, the client will ask for the server URL, username and password to connect to the server.


Updating clients to a new version

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. 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.

(Warnung) Please take care you download the Generic Client version when updating the clients on the PowerFolder Server. The clients connecting to our public cloud don't offer to enter the URL to your server! 

Download links to the latest Generic Clients:

Notifying clients about a new version

Once you've updated the clients in the client_deployment directory, they will be available for download on your web interface. However existing clients will not detect automatically that there is a new version yet. (Glühbirne) This can be useful if you want to start with a slow rollout making the updated clients only available for new users.

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.

(Haken) 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.

Deploying on Windows with the .exe installer using silent mode

The Windows client installer supports some command line options to make it easier to deploy it with batch scripts or package deployment tools:

/NORUN - Don't start program after setup is done.
/NOJAVA - Don't check for and download JRE automatically.
/KERBEROS - Enables Kerberos authentication support.
/S - Run installer silent, required for all options below:
/NODESKTOP - Don't create desktop shortcuts.
/NOQUICKLAUNCH - Don't create quicklaunch shortcuts.
/NOSTARTUP - Don't start PowerFolder automatically when Windows starts. 
/NOSHELL - Don't create shell enhancements.
/SERVERURL - Setup PowerFolder to connect to the given server URL.

(Info) Silent uninstall can be performed by executing the uninstall.exe in installation directory with the command line /S.

Deploying on Windows using MSI

The MSI package is provided to support automated installation via command line, Active Directory or software deployment/packing solutions. As such, it does not feature a GUI, but can be customized using standard mechanisms like msiexec or transforms. Administrators can use Orca to inspect the MSI package, edit values and create transforms.

FeatureDefault LevelDescription
PowerFolder1Main PowerFolder components, including the jar, binaries and entries in the start menu and desktop.

The JRE distributed with PowerFolder.

ShellExtensions1Integrate PowerFolder into Windows Explorer etc.
ServerConfig1Set server URL on installation. The public installer property CONFIG_URL must be set.
StartupEntry1Create an entry in the Windows Startup folder to automatically launch PowerFolder.
DesktopShortcut1Create a shortcut on the Desktop
Kerberos_Support2000Create registry entries for Kerberos Authentification.
WebDAV_Support2000Create registry entries to use the WebDAV client.

By default, all features with a level of 1 will be installed. Windows Installer allows to override this behaviour in the following ways:

With the MSI installer the folder base path can be set during the interactive installation process. The installer proposes the folder base path already set in the registry. If no folder path was set the installer proposes the default path $HOME/PowerFolders.

It is also possible to set the parameter via command line parameter:

msiexec /i installer.msi FOLDERBASEPATH=C:\test

The installation can also be done completely silent (requires console with administrator privileges):

msiexec /i installer.msi /qn FOLDERBASEPATH=C:\test

During installation, the folder base path is written to the registry of the local user (foldersbase). A second key (foldersbase.overwrite) is also written to the registry and set to true. At the next start of the PowerFolder client the folder base path is read from the registry and the overwrite flag set to false. From this point on all changes to the folder base path are controlled by the client and automatically synced to the registry.


msiexec /i PowerFolder_<VERSION_NUMBER>_Installer.msi

Default: Install all features with a level equal to 1.

msiexec /i PowerFolder_<VERSION_NUMBER>_Installer.msi INSTALLDIR=E:\PowerFolderDefault installation, but use folder E:\PowerFolder for program files.
msiexec /i PowerFolder_<VERSION_NUMBER>_Installer.msi CONFIG_URL=https://powerfolder.example.comDefault installation with a custom server, for on-premise servers.
msiexec /i PowerFolder_<VERSION_NUMBER>_Installer.msi ADDLOCAL=Kerberos_SupportDefault installation plus Kerberos registry entries.
msiexec /i PowerFolder_<VERSION_NUMBER>_Installer.msi INSTALLLEVEL=32767Install all features. 32767 is the greatest level allowed.
msiexec /i PowerFolder_<VERSION_NUMBER>_Installer.msi INSTALLLEVEL=0Install nothing.
msiexec /i PowerFolder_<VERSION_NUMBER>_Installer.msi INSTALLLEVEL=0 ADDLOCAL=PowerFolder,ShellExtensions,ServerConfig, StartupEntryDefault install, minus the bundled JRE.
msiexec /i PowerFolder_<VERSION_NUMBER>_Installer.msi REMOVE=Bundled_JRERemove the bundled JRE from an existing installation.