Release Notes 6.6.0

With this major release of ACMP, our solution is equipped for the future and offers many optimizations for more efficient and secure work.

ACMP license types - Subscription

In order to meet current market requirements, we support a new way of licensing ACMP. From now on, all ACMP modules are also available as subscriptions on request.

Improved update mechanism

The update mechanism has been fundamentally revised. Among other things, a more stable agent update with less network load is included. In addition, the system can be patched down to ACMP 6.6.0 more easily in future. This enables a faster roll-back of the server, console and agents in the event of problems with an ACMP update.

In the course of this, the client inventory was also expanded to include the information "parked ACMP version".

The update dialog itself now contains further supporting information (e.g. which components also need to be updated) and checklists for a quick and successful ACMP update. The mechanism will take effect for the first time with ACMP 6.6.1.

Please note that at least one ACMP Console requires access to the following domain: acmpupdate.aagon.com Port 443

ACMP Console

With this update, the ACMP Console is available as an MSI and can also be installed "silently" without admin rights via client command and parameters.

The Aagon Community can now also be accessed directly via the ribbon menu "System=>Help".

ACMP CAWUM

It is now possible to use an additional local WSUS for the ACMP CAWUM updates or to operate cascading download systems. This means that Windows updates can be checked for integrity and security before distribution and ACMP CAWUM does not have to communicate directly with the Internet.

ACMP CAWUM is also extended by an additional information field. The date of a failed update is recorded here when an error occurs for the first time.

ACMP OS Deployment

Thanks to the direct integration of LAPS into the current Microsoft operating systems, it is now possible to use automatically generated and rotating passwords for local administrator accounts. This offers a significantly higher level of security. We have adapted the ACMP OSD rollout process so that you can now also finalize the rollout with a corresponding domain user and thus the local administrator is no longer required on the system to be rolled out.

ACMP Desktop Automation

It is now possible to search for a specific client command in all jobs and containers and automatically replace it with a new one. This is very helpful if, for example, a client command for software distribution is to be replaced by a different version.

As of this version, the Package Wizard no longer contains the option to add a job delay. This option is now natively included in the job control and is therefore centrally located for more consistent operation of ACMP.

ACMP Kiosk

The filter options in the ACMP Kiosk now display Windows 11 23H2 correctly.

ACMP Gateway

It is now possible to pass the client certificate as a parameter via the command line when installing the agent. This means that it is no longer necessary to distribute the certificates separately.

ACMP License Management

In addition to the DNA catalog, the central data from the ACMP Core inventory is also very important for the creation of license packages in license management. We have therefore improved the interoperability between the modules so that data such as manufacturer name etc. can now also be transferred directly for manual recognition patterns.

ACMP BitLocker Management

Previously, the minimum system requirements in our solution were defined higher than they were actually necessary for BitLocker. These requirements have been adjusted accordingly so that configuration with a TPM module 1.2 is now also possible.

ACMP Vulnerability Management

When a container is created from a vulnerability, if you are logged in as a client administrator, you are first asked for which client the container should be created.

ACMP Defender Management

The ACMP Defender Management has been completed with additional event IDs and now also displays the limit exceedance of memory consumption and CPU utilization. This corresponds specifically to the Microsoft Defender event IDs 5014 & 5015.  

ACMP Asset Management

A problem with the number profiles in ACMP Asset Management has been fixed. These could not be adjusted in the meantime or changes were not saved.

ACMP Jobs

The behavior and control of jobs have undergone some changes in this version. For example, it is now possible to make a client accessible again by restarting an agent if a system job from a client command or MSW package hangs. Due to the batch processing of system jobs, parallel execution was previously not possible. Parallel execution is only available for the agent restart.

Another adjustment in job control is the harmonization of manual and container jobs. The behavior of manual jobs now corresponds to that of container jobs. As a result, manual jobs are no longer incorrectly displayed as executed if the client is restarted before execution and has therefore actually rejected the job.

Furthermore, the calculation of profile assignment has been significantly optimized in Job Management. This enables a noticeable improvement in performance in large client landscapes.

The starting conditions for push jobs have been expanded with this update and further aligned with the generally available starting conditions.

ACMP Container

By adjusting the calculation of the client-container relationship, a significant improvement in performance is noticeable, especially in large environments.

In addition, a display error has been fixed that was still taking decommissioned clients into account in the client count of containers.

ACMP parameter control

Adjustments to parameters for client commands and MSW packages were previously not transferred to the ACMP kiosk or jobs in a standardized way or at all. In some cases, elements had to be linked to the ACMP Kiosk or jobs again. This has now been adjusted in a user-friendly way and changes to parameters are transferred or removed completely for all types, and new default values are adopted if required.

ACMP compatibility & security

With ACMP 6.6.0, the OpenSSL version used is updated to 3.1.5.

The ACMP hardware scanner has been updated to support and recognize the latest hardware.

The functionality of ACMP Console & ACMP Agent can be considered compatible with "Windows on ARM" after initial tests. However, there may still be some limitations in the inventory data. We therefore recommend a test in your environment before using the ACMP Agent fully productively.

The ACMP Agent is now also compatible with Windows Core systems.

Internally, ACMP has been communicating with TLS 1.2 or higher for some time now. As of this version, our external interfaces (e-mail service, file repos, ACMP document API, ACMP web interface) will no longer accept requests from participants under TLS 1.2. Please check the settings in your environment before updating. Further information on this topic can be found in our Community.

Components to be updated

If you are using the following components, please update them following the ACMP 6.6.0 update: ACMP Gateway, ACMP Web Interface, ACMP Network Boot Service