Release Notes 6.10.0
With ACMP 6.10.0, we are taking the next step in the ongoing development of our client management platform. This major release introduces significant enhancements in key areas: from secure and compliance-compliant data erasure to significantly expanded Windows Update management—which incorporates extensive feedback from our customers—as well as an enhanced Intune import and more comprehensive inventory management for Unix systems. In addition, this release includes further improvements that make administrators’ daily work more efficient and organized.
OS Deployment – Secure Data Wiping for Endpoints
Whether it’s device replacement, lease returns, or disposal, secure data wiping has often required the use of external service providers, manual coordination, and incomplete documentation. The Wipe Boot Templates introduced with ACMP 6.9.0 have been expanded into a comprehensive solution with ACMP 6.10.0: Starting immediately, specific storage devices can be selected for wipe operations, and various erasure methods and standards can be configured. Depending on the storage type, different methods are available, including multiple overwrites for HDDs (Peter Gutmann, NIST, DOD, and many more) or specialized methods such as Sanitize or Secure Erase for SSDs. Wipe operations can be fully initiated via PXE and centrally controlled. In addition, reports on the erasure process are generated and saved, ensuring audit-proof documentation of data erasure.
Disk and partition numbers are now also inventoried. This simplifies the configuration of Wipe Boot Templates, as the relevant storage devices can be identified directly using the inventory data.
The OS installer for the boot images has been equipped with a new OpenSSL library. After updating to ACMP 6.10.0, a rebuild of the boot images is required, which can be performed directly from the console with a single click thanks to the rebuild function introduced in ACMP 6.9.0. This contributes to improved security during data transmission.
WUM
With ACMP 6.10.0, Windows Update Management has been expanded in several areas.
The behavior of the Windows Update Collection has been significantly improved. As a result, Update Collections can now be made available directly in the Kiosk as standalone objects without having to go through a Job Collection. For updates requiring a restart, you can configure how often the restart dialog should be displayed. If no user is logged in on the client, an automatic restart can be performed without interrupting active sessions. Additionally, users can be automatically prompted to close running applications before installing Office updates.
ACMP now includes the default sync profile “All Updates,” which is available immediately after installation and can be assigned to a file repository without additional configuration. Sync profiles can also be set up so that all updates are automatically synchronized without having to manually adjust the profile for new products or classifications.
Furthermore, the same filter control is now available in the test and release rings as in the Windows Update Collections.
During initial setup, the First Steps Wizard and the settings (under System > Settings > Windows Update Management > Products) display recommendations for product and language selection based on existing inventory data. A prerequisite for product selection is that a metadata download has been performed beforehand. Client-side troubleshooting has also been enhanced, and updates installed via WUM will now be visible in the client’s native Windows Update history, ensuring that the update status is consistently traceable regardless of the installation method.
In addition, further improvements have been made: The Job Monitor has been enhanced with more precise logging for WUM jobs, metadata and setup downloads have been supplemented with additional diagnostic information, and third-party updates will now be imported even without product assignment. The WUM database has been expanded with numerous new display fields, including the total size of updates, installation and uninstallation behavior, and the status of Windows Server Update Services. We also provide new queries for error analysis.
ACMP Intune Management
Intune Management has been enhanced with selective import. When importing from Intune, you can now specifically control which clients, groups, apps, and users are transferred to ACMP. This provides greater clarity, especially in large environments or BYOD scenarios, and ensures that only relevant devices and users are visible in ACMP.
ACMP Core
The collection of optional Windows features has been moved to a standalone agent task. As a result, the software scanner runs faster, which particularly accelerates rollouts and OSD processes. The new scanner can be flexibly configured in the agent scheduler. When updating to ACMP 6.10.0, the startup condition of the software scanner is transferred once to the new scanner for optional Windows features, allowing it to start directly with the existing settings.
Inventory
The software scanner has been enhanced so that SQL Server 2025 instances are detected and correctly identified as SQL Server in license management.
On Windows clients with ARM architecture, operating system information is now fully read, and a BitLocker profile can be assigned.
ACMP Windows Agent
Agent deployment has been optimized: The size of the client package has been reduced, and both deployment and startup behavior have been improved.
UNIX Agent
The expansion of inventory data enhances transparency within the UNIX environment. Hardware inventory now includes additional information on chassis, battery, TPM, GPU, and display.
In addition, a login history is now recorded, documenting past logins on the client. The optimization of logging for Unix scripts also ensures better traceability and faster problem resolution.
Job / Client Monitor
The display of container-based jobs in the Job Monitor has been optimized. After renaming Client Commands or Job Collections, the current name is now displayed immediately. This improves traceability, especially for recurring jobs.
Database
With ACMP 6.10.0, two optimizations were made to the database: Index defragmentation has been improved, and handling of large data sets has been optimized. To benefit from these optimizations, it is recommended to follow the instructions in the online manual.
ACMP Desktop Automation - Client Commands
The “Uninstall Software” module has been added.
MSI installations are hidden to prevent errors during uninstallation. For MSI packages, the corresponding MSI module is recommended instead.
Execution of the “Execute PowerShell Script” module in the console context is now reliably supported, both as a logged-in user and when impersonating another user.
The new “Show Balloon Tip” module provides an additional notification type that can be used to inform users while a client command is running.
ACMP Managed Software
The execution of agent tasks has been optimized. If multiple MSW packages are running simultaneously, the system prevents scanners from being queued twice if the previous scan has not yet completed. This reduces the resource load on both the client and the server.
ACMP Security
Global accounts can now be assigned access control lists (ACLs) to control which users are allowed to view, edit, or use global accounts.
Additionally, the OpenSSL version has been updated to 3.5.6 to ensure the security of data transmission in the long term.
The white paper on NTLM has been expanded and now describes in greater detail which configurations are required to ensure the highest level of security with NTLM, as well as the prerequisites and limitations of operating without NTLM. As soon as Microsoft provides a fully-fledged successor protocol, it will be evaluated as a permanent replacement.
End-of-Life
The ACMP Command Launcher was removed from the product with ACMP 6.10.
The ACMP Kiosk was introduced as its successor as early as ACMP 6.0.0, and the Command Launcher was marked for end-of-life with ACMP 6.9.0.
Before updating to ACMP 6.10, ensure that existing configurations have been migrated from the Command Launcher to the ACMP Kiosk. Whether the Command Launcher is still in use can be determined in the ACMP Console under Client Management – ACMP Kiosk by checking for a corresponding notification message.
If only the ACMP Kiosk is being used, no further action is required.
Updated Components
After the ACMP update, the following components must be updated separately: the ACMP Gateway, the Network Boot Service, the Unix Agent, the Unix Offline Scanner, and the ACMP Helpdesk Web Interface
Note: The manual lists 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 unfamiliar with the process.
Changelog
For more details on the fixes and improvements, please refer to our changelog.