Release Notes 6.8.0
With the major release of ACMP 6.8.0, we aim to fulfill our quality standards and guarantee you a smooth workflow. The following new functions and improvements have been implemented:
ACMP Intune Management
A new solution is making its way into ACMP, creating the possibility of a hybrid infrastructure. With ACMP Intune Management, you can integrate any number of Intune tenants into ACMP with multi-tenancy capability without having to log out and log back in every time you switch.
All Intune devices are imported and consolidated with existing ACMP clients. Apps are also imported and can be assigned to devices and groups. The optimal implementation also includes the import of users and groups from the Entra ID, users are linked to ACMP contacts or newly created.
The deep integration of the data can be used in reports, queries, asset management, license management, helpdesk and more. The familiar functions of the ACMP Intune Connector are also included, such as sending notifications, locking and deleting devices, and resynchronizing devices.
The ACMP Intune Connector will be discontinued with this module, customers who have licensed the connector will be migrated and must deactivate it in the AESB before updating to ACMP 6.8. Customers can obtain further details actively from their sales contact.
Further details on the new module can be found on the product page.
ACMP CAWUM
This release enables the distribution of drivers and tools from the third-party catalogs of Dell, Lenovo and HP in CAWUM. The drivers can be selected granularly and tested and distributed using the familiar CAWUM mechanisms.
In addition to the new feature in ACMP CAWUM, bugs have also been fixed. One of these bugs was a script error when opening the Microsoft catalog for an update, which has now been fixed.
ACMP Desktop Automation
ACMP Desktop Automation has been expanded and changed in some areas. As of ACMP 6.8, the menu item "Desktop Automation" is available for the first time in the ACMP Console, which is divided into the familiar "Client Commands" area and the new "Unix Scripts". Scripts for the interpreters bash (Linux) and zsh (Mac) can be stored and distributed here. These are supplemented by the familiar test and release processes so that you can further develop your Unix scripts in a structured manner.
The Unix agent must also be updated separately in this process.
ACMP Container
Optimizations in ACMP can achieve clearly noticeable and measurable performance improvements in the loading times of container filters in very large environments. In some tests, loading times were reduced by up to 50%.
The biggest visible change is the integration of Unix script management into the containers. It is now possible to explicitly assign Unix clients to a container and thus obtain a tidy tab view for the containers, which only contains usable actions.
ACMP database support
ACMP database support has also been expanded with this release. An Azure database can now be used in addition to the Microsoft SQL Server. This extension means that the ACMP server can now also be operated completely in an Azure environment if desired.
In addition to extending compatibility, the security of the database has also been comprehensively improved. Due to improved protection mechanisms in the ACMP database, it is possible that some SQL commands in Advanced Queries and Client Commands can no longer be used. These are rare exceptions that can be recognized by the error message 'Access denied'.
ACMP Agent
The ACMP agent is an elementary component of the infrastructure of this solution and stability is our constant concern.
In the course of this, 2 errors were fixed that could occur during updates and could still lead to contact interruptions with the ACMP server afterwards. These errors are always given high priority by us and, where possible, eliminated through extensive testing procedures. Should you still encounter problems with the stability of the agent, please contact our support team at any time so that we can work together to develop long-term and sustainable solutions.
ACMP vulnerability management
This release improves the clarity and data homogenization in our ACMP vulnerability management. It is now possible to view the file path of a vulnerability at the main level. This means that relevant data can be found more quickly.
In addition, the relationship between vulnerability findings and items has been optimized so that queries can be made much more easily and quickly.
ACMP Helpdesk
In the ACMP Helpdesk, an attachment can now be sent when closing tickets; the Attachments tab is now also available in the "Close ticket" dialog.
In addition, the modification date field of an article in the knowledge base is now also available in queries.
ACMP OS Deployment and Network Boot Service
The stability of the ACMP OS deployment has been improved and a crash error has been fixed that occurred when a client was to be rolled out via the context menu in a query.
This update adds option 82 to the Network Boot Service (NBS). This is necessary in larger network environments if the DHCP server supplies this option and it must be passed on for a successful rollout. In addition, the update behavior in the NBS is improved in order to avoid update errors of the OpenSSL library in the NBS and to make the process more stable.
Update note and further information
The ACMP Temp directories for consoles and agents have been moved. For the ACMP Agent, the directory is now located under "C:\Windows\System32\config\systemprofile\AppData\Local\Aagon\Temp" or "C:\Windows\SysWOW64\config\systemprofile\AppData\Local\Aagon\Temp". The directory of the ACMP Console is now: "C:\Users[User]\AppData\Local\Aagon\Temp". Especially for environments that have restricted their PowerShell execution locations, it is mandatory after the update to extend the exceptions by the mentioned directories and thus ensure error-free functioning of ACMP.
There is now a new option "Job execution mode" under "Agent Installation". This can be used to set whether jobs should always generate a job log. This gives you the freedom to decide whether a log entry should also be created for jobs that initially only check whether a change is created in the system or not. This is particularly important for institutions that have to prove their activities for compliance purposes. Currently, only Managed Software and CAWUM jobs are supported, as these are the only ones that currently have the check function.
Fields that were previously only available in the client details are now also available in the queries, specifically the hardware ID and the class description.
Our Advanced Queries now display more and clearer error messages, which is also important to increase the security within the ACMP database. See ACMP Database Support.
In 2023, the DNA database was exchanged and replaced with a more comprehensive one. The technical implementation of the old DNA database will be removed with this release, which will also maintain the security of ACMP.
Components to be updated
The ACMP Gateway and the Network Boot Service must be updated separately following the ACMP Server Update.
Note: At the following point in the manual, you will find a list of all additional components that may need to be updated separately. From there you can navigate to the relevant components and find instructions on how to update them if you are not familiar with the process. Manual link
Changelog
Further details on the corrected and improved points can be found in ourchangelog.