Release Notes 6.9.2
With this maintenance release of ACMP, we aim to remain true to our quality and service standards and provide important bug fixes.
OpenSSL: Closing vulnerabilities
The OpenSSL version used in ACMP has been updated to fix known vulnerabilities (see OpenSSL changelog). The boot images in OS Deployment need to be rebuilt so that the OpenSSL version within the images is updated.
Job Management: Bugfix Windows Update Collection
Due to optimizations in the agent's job management when executing jobs with restarts, it may happen after the update to 6.9.2 that pushed jobs (especially Windows Update Collections) that are still displayed as running in the Job Monitor are continued after the update. In the worst case, this could result in agents installing Windows updates and then restarting the system if the option “Restart computer if necessary” is enabled in the update collection that was pushed in the past.
If the old jobs are deleted from the Job Monitor before updating to 6.9.2, they will not be resumed by the agents after the update.
OS Deployment: Bug fix Network Boot Service
In 6.9, it could happen that a client did not receive a boot loader from the TFTP server in the NBS despite being assigned a rollout template. The bug has been fixed.
SQL server load
After an update to ACMP 6.9, the SQL server load was sometimes increased, depending on the customer setup. We have implemented appropriate optimizations to fix the problems.
Helpdesk web interface: Setting a category when creating a ticket
In ACMP 6.9, it was not possible to set the category when initially creating a ticket. The error has been fixed.
WUM: Error correction Third-party files
When subscribing to third-party updates, it could happen that these were displayed as released and not downloaded. The error has been fixed.
CC module JavaScript
Due to a change in the Windows JavaScript engine with Windows 11 24H2, the call ScriptResult = 0; no longer worked with the CC module JavaScript. From ACMP 6.9.2 onwards, the call SetScriptResult(0); must be used. SetScriptResult is a new function and therefore requires an adjustment in existing client commands.
File repository on Synology NAS
Depending on the respective setup and DSM version, synchronization could fail for a file repository (UNC) on a Synology NAS. For this case, there is now a new config value EnableUncCopyResumption under TDistribFileRepositoryConfig. Set to True by default, the sync service behaves as before. If the value is set to False, the files are no longer written as .part~ files and then renamed, but are written directly as target files. In addition, if the setting is set to False, resuming is no longer possible if a file has not been completely transferred. Incomplete files are always transferred completely again.
Microsoft SQL Server 2025
We now officially support Microsoft SQL Server 2025.
New CC module Random
There is a new client command module that returns an integer pseudo-random number.
Self-service web interface: New configuration option
Previously, the first item in the info list was opened both during login and when loading the self-service web interface. From now on, the default behavior can be set in web.config. InfoListOpenFirstItem controls the information page, while InfoListLoginOpenFirstItem overwrites the value for the login page. Setting True leaves the top item open, while False closes everything.
[..]
<add key="InfoListOpenFirstItem" value="true"/>
<add key="InfoListLoginOpenFirstItem" value="true"/>
</appSettings>
Affected components
The following components must be updated manually after installing the update: ACMP Gateway, Network Boot Service, and Helpdesk Web Interface. Instructions for doing so are available in the ACMP online help.
Attention: After downloading version 6.9.2, the helpdesk web interface may incorrectly display a different version than the ACMP server version.
This behavior will no longer occur after installing version 6.9.2 and updating the web interface.
Changelog
As always, you can find out what has been corrected and improved in detail in our changelog.