Release Notes 6.8.3
With this bugfix release from acmp, we want to live up to our quality standards and guarantee you a smooth workflow.

acmp Agent
In the previous version, it could happen in rare cases that the complete reinstallation of an acmp agent failed if the acmp server was not immediately and permanently accessible and it would have been necessary to repeat the installation several times. This error has now been fixed.

acmp Desktop Automation
Due to an authorization adjustment in the OS deployment, client commands for inplace upgrades could no longer be executed without errors. With this release, the error has been fixed and the client commands work as expected again.

acmp OS Deployment
When multi-tenancy was activated, it could happen that clients were not assigned during a rollout. The error handling has been improved and now solves this problem.

acmp SQL compatibility
With acmp updates, the Microsoft SQL Server is checked for compatibility by the acmp server and an update installation is refused if the necessary compatibility is not given. Furthermore, the acmp database instance is automatically set to the highest possible compatibility level of the Microsoft SQL Server used.
This customization function did not work with a previous release, which is why there were restrictions with acmp CAWUM, for example. In this case, Windows updates could not be refused.
With this release, the compatibility level will be corrected accordingly if necessary and the functions will work as intended again.

Components to be updated
No further components need to be updated.

Changelog
As always, you can find out what has been corrected and improved in detail in our changelog.