Although I'm aware that support for version 1.8 has ended, I'm going to try anyway.
Here's the situation:
I'm setting up a WAPT server running version 1.8 with the aim of eventually migrating the project to a more current Enterprise version.
Everything is going well, a small Debian 10 installation, configuration OK. Security via Sophos OK.
Certificate OK. Packages OK (or almost, but that's just Python scripting, so it's manageable).
And now I've run into a problem.
I don't want to deploy a self-service system. I want my colleagues and myself to be able to administer the software on our user workstations.
However, although the majority of our network runs on Windows 10, we're slowly but surely migrating to Windows 11.
In my tests, deployment on Windows 10 is OK (modifying the machine, checking for updates, installing the package, uninstalling it, etc.).
On Windows 11, however, it's more complicated.
The console is already showing Windows 10 Pro instead of Windows 11.
For testing purposes, I opened the self-service area, and it turns out that I can install a package through the self-service area but not uninstall it (even with a clean script published), and I can't do anything concrete through the console.
For example, when I click on "Edit machine" to set package dependencies, the buttons are grayed out (except for cancel).
I don't know if I've covered everything, but I'm keeping an eye out if you have any ideas or need any further information.
Thanks in advance, and have a good day.
