The Configuration tab contains conservative values. Among other things, these values are adapted to the infrastructure, which contains a large number of clients. These settings can be adjusted at any time.
The distribution of updates in the ACMP environment can also be optimized by setting up distributed file repositories (see Distributed File Repositories). This is recommended especially for companies with multiple locations.
The degree of distribution of updates is calculated on the basis of the managed clients. Clients that were inventoried with the OneScanClient as well as manually entered clients are not taken into account.
If you have selected the condition Start installation if XY % of the managed clients have parked the update in the Configuration tab, make sure that the selected value is not set too high. Otherwise, mobile clients or clients which are used only rarely might delay the installation of updates, because the entered percentage is difficult or impossible to reach.
The installation of updates which affect the server requires a reboot during the installation. Since the ACMP system is unavailable for this time, you should plan the installations for a time when the ACMP system is little used. In the details of the update you can check if an update affects the server. To do so, double click on the appropriate update.
After the installation of an update, the web interfaces for the Helpdesk may have to be newly installed. In such a case, you will receive a warning message during the installation of the update. After the installation, you should deinstall the old web interfaces and then install the new web interfaces. The necessary setup files are archived in the Web Interfaces Setup directory within the ACMP release Clients.
In the tab Manage updates all important updates appear in the sequence in which they were released by Aagon. In this exact order the updates must be released for distribution, and afterwards installed. This means that if an update is released, all previous updates which have not yet been released are released at the same time. Updates are installed in an analoguous procedure.
Last change on 10.03.2014