Installation mit dem Congree Update Agent

From version 6 036, the Congree clients can also be updated automatically by the server in addition to the normal update process. To change over, you must configure this once and update all Congree Authoring Clients or Congree Control Center with the new version. All future updates of the Congree Authoring Client or the Congree Control Center can be triggered automatically by the server. In addition, the Congree Deployment Assistant is now available in 2 versions: complete (without identification in the file name) and "Lite" (e.g. "Congree-Deployment-Assistant-v6.0.18476.08.20220201.036-x86-Lite.exe"). You can use the full version for any installation, whereas the lite version can only be used to install or update the Congree Authoring Client or the Congree Control Center. The Lite version will obtain the required modules from the server and is therefore significantly smaller.

If the Congree Update Agent is installed on a client computer, only the server needs to be updated in the future. The individual client computers "fetch" the current version when they are used for the first time after a server update. This process does not require administrator rights.

Configuration and functionality of the Congree Update Agent at a glance

1. In the client configuration of the Congree Deployment Assistant, add the "Congree Update Agent" module to the clients.

2. Enter the host name.

3. Restart the server.

4. Install a Congree Authoring Client or the Congree Control Center with the full Congree Deployment Assistant or the "Lite" package

5. Enter the host name.

6. The client is installed

Scenarios and different areas of application

In general, we recommend switching to the automatic update. However, depending on the infrastructure, in certain cases it may be better to stay with the manual system.

When the server is updated, the update files are gradually distributed to the individual client computers. This distribution is triggered according to the pull principle: The server does not send files to the individual clients on its own, but the clients check at startup whether new updates are available on the server and, if so, download the required files.

If the bandwidth is limited or a large number of clients are usually started at the same time, this can lead to an undesirable load on the intranet. If the expected workload is too high, we recommend that you do without the auto-update completely or only for some clients.

You can also use both update variants simultaneously in your company, but a client computer will always be updated in the same way. To do this, create two different client configurations in the Congree Deployment Assistant, one with and one without the Congree Update Agent. The clients without the Congree Update Agent still have to be updated manually. The clients with the agent fetch the update themselves. In this way, you can, for example, treat client computers in a subnetwork with a lower bandwidth or in a remote part of the company (e.g. office abroad) differently to the clients at the server location.