Installation with the Congree Update Agent

Starting from version 6.036, Congree clients can be automatically updated by the server in addition to the regular update process. To switch to this method, you need to configure it once and update all Congree Authoring Clients or the Congree Control Center to the new version. All future updates of the Congree Authoring Client or the Congree Control Center can then be automatically initiated by the server.

Additionally, the Congree Deployment Assistant is now available in two versions: full (without any designation 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, while the Lite version is only for installing or updating the Congree Authoring Client or the Congree Control Center. The Lite version will fetch the necessary modules from the server, making it 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 will "fetch" the current version the first time they are used after a server update. This process does not require administrator rights.

Overview of the Configuration and Functionality of the Congree Update Agent

1. Add the "Congree Update Agent" module to the clients in the client configuration of the Congree Deployment Assistant.

2. Specify the hostname.

3. Restart the server.

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

5. Specify the hostname.

6. The client will be installed.

Scenarios and Different Use Cases

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

When the server is updated, the update files are gradually distributed to the individual client computers. This distribution is initiated based on the pull principle: the server does not send files to the clients on its own, but the clients check at startup if new updates are available on the server and download the necessary files if they are.

If bandwidth is limited or if many clients are usually started simultaneously, this can lead to an undesirable load on the intranet. If the anticipated load is too high, we recommend opting out of auto-update completely or for some clients.

You can also use both update methods 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. Clients without the Congree Update Agent must continue to be updated manually. Clients with the agent will fetch the update automatically. This way, you can treat client computers in a subnet with lower bandwidth or in a remote company location (e.g., an office abroad) differently from the clients at the server location.